If your organization runs Penta and is evaluating AP automation, the options can look similar on the surface. Most of them capture invoices, route approvals, and post to Penta.

The differences show up in how deeply a solution connects to Penta, and how much manual work it leaves behind for your team. The sections below cover the things worth looking at closely before you choose.

How deep the Penta integration goes

Most AP tools can move data in and out of Penta in some form. The more useful question is how much they pull directly from Penta, and how much your team still has to enter or reconcile by hand.

It helps to ask where the information on the screen comes from while an invoice is being processed. A deeper integration pulls your vendor master, PO lines, job data, cost codes, payment terms, and tax attributes directly from Penta and presents them on one screen, so the person working the invoice is not looking things up in a second window or re-keying data that already exists. A shallower one leaves more of that to your team, or holds the data in its own system so your information lives in two places and has to be kept in agreement.

When you evaluate a solution, ask to see exactly what it pulls from Penta and what your team still handles by hand. Ask what happens after an invoice is approved as well. It should post back into Penta cleanly, coded and ready for the payment run, so Penta stays your single source rather than one of two systems you maintain.

Whether validation happens as the invoice is entered

Because a deeper integration has your live Penta data on the screen, it can check an invoice against that data at the moment it is entered rather than after the fact.

That means catching a miskeyed amount, a unit price that does not match the PO, a missing or incorrect tax amount, or a cost code that was never set up for that job, at the point of entry, while it is still easy to fix. It is worth asking a solution how much it validates automatically as the invoice is coded, and how much only surfaces later as a rejected post or a correction at month-end.

Whether matching happens at the line level

Matching at the line level is worth asking about directly, because it affects how much of your process moves without a person stepping in.

A large invoice with a single line that does not match should not send the whole invoice to manual review. The lines that are clean can keep moving while the one exception is handled. It is worth asking whether matching is evaluated line by line, whether price and quantity tolerances can be configured, and how partial receipts and non-PO invoices are handled.

Whether overruns are caught before they post

This is a point specific to construction AP, and it is one of the more useful things to test in any evaluation.

Penta tracks remaining balances based on what has been posted. A company can have several invoices in flight against a single PO where the combination creates an overrun, and that overrun may not be visible until the last invoice is posted and it will not go through. A solution that only looks at posted balances cannot see that coming. One that tracks invoices in flight can flag the overrun across every related invoice before any of them post.

That difference can be what stands between knowing your committed costs as work progresses and finding them during the end-of-month close.

How exceptions get routed

The invoices that match cleanly were never the ones that take time. The time goes into what happens when something does not match, and how quickly the right person can act on it.

It is worth asking how a solution handles an exception once it flags one. Can it route a missing PO to purchasing, a tax question to the right reviewer, or a cost overrun back to the person who can resolve it, with the reason and the invoice already attached? And can you control who is allowed to change what along the way, so an approver sees what they need to see without being able to edit fields that should be locked? Routing that carries context and respects those roles keeps work moving instead of stacking up in one queue.

Whether you can keep what already works

Improving an AP process does not have to mean replacing everything around it. Many companies keep what already works, including their bank, their approval structure, and their document storage, and change only the part that needs it.

For a company on OnBase that uses it mainly as a document repository, there may be no need to leave it. For a company moving to PentaVault, the AP workflow can be built for that environment directly. It is worth asking whether a solution can work across those options and recommend the one that fits your setup, rather than requiring you to move everything at once.

Whether it fits your team's size and volume

Not every company running Penta needs the same solution. An organization processing a few hundred invoices a month with a small AP team has different requirements than one processing several thousand across multiple entities and approvers.

It is also worth understanding how a solution is licensed. Some approaches charge every user the same way whether they process invoices all day or only approve one now and then. Being able to license workflow access and document access separately can matter, so you are not paying for full document access for someone who only needs to approve. A structure that reflects your actual volume, team size, and how each person uses the system tends to fit better than one license type applied to everyone.

Questions worth asking

If your organization is evaluating AP automation for Penta, a few questions tend to surface the most useful information.

What is pulled directly from Penta, and what does my team still enter by hand? The answer tells you how deep the integration really goes.

What does the solution check automatically as an invoice is entered? Real-time validation catches errors while they are still easy to fix, instead of at month-end.

How does it handle an invoice in flight against a PO? A solution that only reads posted balances cannot warn you about an overrun before it happens.

Frequently asked questions

Does every AP automation solution integrate with Penta the same way?
No. Some solutions move data through exports and separate systems, while others pull directly from Penta data such as the vendor master, PO tables, job information, and cost codes. The depth of that integration affects how much manual work remains for your team and how many errors get caught early.

What does real-time validation mean in AP?
It means the solution checks an invoice against live Penta data as it is being entered, so issues like a wrong unit price, a missing tax amount, or a cost code that is not set up for a job are flagged at the point of entry rather than after posting.

What is line-level matching?
Line-level matching evaluates each line of an invoice against the PO independently, so a single line that does not match does not send the entire invoice to manual review.

Do we have to leave OnBase to modernize AP?
Not necessarily. For companies that use OnBase mainly as a document repository, it can often stay in place. For companies moving to PentaVault, the AP workflow can be built for that environment directly.

Why does it matter whether a solution tracks invoices in flight?
Penta tracks remaining balances on posted invoices. If several invoices are in flight against the same PO, the combination can create an overrun that is not visible until the last one is posted. A solution that tracks invoices in flight can flag that earlier, while there is still time to address it.