The AP Automation Buyer's Guide: What to Look For

By Vaibhav Rane, Founder, Cresolv One

Every AP automation vendor's homepage looks similar: invoice capture, approvals, ERP posting, some percentage promising faster processing. The differences that actually matter show up once you're past the demo and into your real invoice volume — the messy 30-40% that doesn't match perfectly on the first pass. This guide is a framework for evaluating any AP automation platform, not just ours.

What to evaluate before you choose a platform

How deep does the matching go: three-way, or more? Matching an invoice against the PO is a start. Matching against the PO and the GRN catches the far more common problem: goods received don't match what was ordered. If a vendor can't explain their GRN-matching logic clearly, ask why.
Is GST and TDS validation built in, or bolted on? For Indian operations, tax compliance checks that happen after posting are checks that happen too late. Ask whether ITC eligibility, GSTIN validation, and TDS applicability are checked before an invoice is approved, not after.
What actually happens to exceptions? Every platform automates the clean invoices well. The real test is the other 30-40% — a price mismatch, a missing GRN, an unrecognized vendor. Does the system route these for fast resolution with context, or does it just dump them in a queue that becomes someone's full-time job?
Does it post directly into your ERP, or hand you a file to re-import? "Integration" means different things to different vendors. Ask specifically whether posting to SAP, Oracle, Tally, or Dynamics happens automatically, or whether someone still needs to manually push a batch.
Can vendors see their own invoice and payment status? If vendors still have to call or email your AP team to ask "did you get my invoice" or "when will I be paid," a large share of your team's time is being spent answering questions a portal should answer automatically.
Is SLA and bottleneck visibility live, or a monthly report? A control tower that only tells you where things stood last month doesn't help you fix a stuck approval today.

Questions worth asking any vendor

"Walk me through what happens to an invoice that doesn't match the PO or GRN — not the happy path, the exception path."
"Which ERPs do you actually post to natively, and which ones need a middleware layer or manual export?"
"What tax and compliance checks run automatically, and which ones are still on my team to catch?"
"What's your average time from invoice receipt to fully posted, across your real customer base, not your best case?"

A simple scorecard for AP automation

Score each vendor from 1 to 5 on the six criteria below, using what you saw on your own data, not what was described. Weight the rows by what hurts your team most today, and keep the notes so you can explain the decision later.

Criterion	What good looks like	What to ask for
Matching depth	Invoice, PO and GRN matched with tolerance rules; GSTIN alignment checked for multi-entity groups	Ask to see a mismatch caught and explained
Tax checks	GSTIN validation, ITC eligibility and TDS applicability checked before approval	Ask which checks run before approval and which run after posting
Exception handling	Each exception arrives with the reason, an owner and an age	Ask to see the exception queue on real data
ERP posting	Approved invoices post straight into the ERP	Ask for a live posting, not a file export
Vendor visibility	Vendors see invoice and payment status without calling your team	Ask to see the vendor view
Live control	Approval and SLA bottlenecks visible today, not in a monthly report	Ask for today's view, not a screenshot

How to run a fair pilot

The most reliable way to compare platforms is a short pilot on your own invoices. Take a batch of 50 to 100 invoices from one entity, and include the awkward ones on purpose: scans, invoices with no goods receipt, price variances, a wrong GSTIN, a vendor missing from your master.

Agree the measures before you start: how many invoices go through without a person touching them, what the exception reasons turn out to be, and how long an invoice takes from receipt to posting. Run the same batch through your current process so the comparison is fair. A vendor that is confident in the product will welcome this; one that steers you back to a prepared demo deserves a follow-up question.

Mistakes buyers commonly make

Judging by the clean invoices. Almost any platform handles a tidy PDF. Judge it on the exceptions.
Skipping the approvers. If approvers find the workflow slower than email, they will route around it, and the automation gains disappear.
Leaving tax rules until later. GST and TDS handling affects the design of matching and approval, so raise it in the first call, not the last.
Choosing on price per invoice alone. Include exception handling effort, ERP posting and vendor queries in what you compare.

Whatever you choose, write down what you expect to improve and by roughly how much before the pilot begins. It is much easier to judge a result against a target you set in advance than against one you remember afterwards.

What the first 90 days should look like

A realistic AP automation rollout is staged, not a switch-over. Start with one entity and the invoice streams that cause the most delay, such as PO-backed goods invoices, and leave the unusual streams for later. This keeps the early results easy to read and the first exceptions easy to trace to a cause.

Plan the weeks around three things: connecting to your ERP and vendor master, agreeing the matching tolerances and approval routes, and training the people who will clear exceptions. Ask any vendor who does the tolerance and workflow setup, how long it takes, and what it looks like when you want to change a rule yourself afterwards. Processes differ by company, so a platform that can only be configured by the vendor will slow you down every time your policy changes.

Total cost: what to include in the comparison

Price per invoice is the easiest number to compare and the least useful on its own. Build a fuller picture before you shortlist:

Set-up and integration effort, including your own IT time for ERP connections and master-data clean-up.
Exception effort after go-live. If the platform sends a third of invoices to a queue, the cost of clearing that queue belongs in the comparison.
Change costs. Ask what it costs to add an entity, a new invoice stream or another ERP later.
Vendor queries. Count the calls and emails your team handles today about invoice and payment status. A vendor portal that removes them is a saving even though it never appears on an invoice.

Red flags to watch for

The demo uses only clean, native PDFs. Real invoice sets include scans, photographs and unusual layouts.
An accuracy figure is quoted without saying which documents it was measured on.
"Integration" turns out to mean a CSV you import by hand.
Tax and compliance checks happen after the invoice is posted.
The vendor cannot show you an exception queue on real data.
Volume pricing is vague until late in the process.

Common questions

How many invoices should an AP automation pilot include?

Enough to include the awkward cases, which for most teams means 50 to 100 invoices from one entity. A clean sample of a few dozen will flatter any platform.

Should we automate matching or approvals first?

Start where the delay is. If invoices wait for someone to check them against POs and goods receipts, begin with matching. If they are matched but sit waiting for sign-off, begin with approval routing. Many teams do both once the first is stable.

Do we need clean vendor and PO data before we start?

Cleaner data helps, but you do not need perfect data. A pilot is a good way to find which master-data gaps cause the most exceptions, so you know what to fix first.

What should we ask about GST?

Ask whether GSTIN validation, ITC eligibility and TDS applicability are checked before approval, and how the platform handles a group that raises invoices against several registrations. Our guide to 7-way matching explains that last case in detail.

What to ask a reference customer

If a vendor offers a reference, use the call well. Ask a customer of similar size and in a similar industry, not their friendliest one. Questions worth asking:

How long did it take from signing to the first real use, and what slowed it down?
What did you have to change in your own process to get value from the AP automation software?
What does the team still do by hand that you expected to automate?
How does the vendor respond when something goes wrong?

Before you sign

Put the pilot result, the scorecard and the reference calls side by side and look for gaps between what you were told and what you saw. Confirm what is included in the price, how changes and new integrations are charged, and what support looks like after go-live. A short, clear contract and a realistic plan for the first three months are usually better signs than an ambitious promise.

Where Cresolv One fits

Cresolv One's AP Automation runs 7-way matching, which adds GSTIN and tax checks to the standard PO and GRN match, with configurable tolerance rules, checks GST and TDS compliance as part of the workflow rather than after it, and posts directly into SAP, Oracle, Tally, or Dynamics. Vendors get their own portal for invoice submission and payment tracking, and AP teams get a live control tower for SLA and bottleneck visibility, not a report that arrives after the fact.

Comparing vendors generally, not just this category? See our vendor-neutral evaluation framework.

If a vendor can't answer these questions clearly in a first call, that's worth noting before you get further into the evaluation. See our AP Automation platform.