An accounts payable system can capture an invoice quickly and still leave a finance team with substantial work to do. The invoice may have no purchase order, refer to an unrecorded delivery or contain a price that conflicts with the contract. Somebody must establish what happened and what the business is authorised to pay.
That makes exception handling a useful starting point when comparing AP automation software with Curia's managed finance operations. The decision depends on where the human work remains and who will take responsibility for reducing it.
Modern AP software already does a great deal
A fair comparison must recognise what established products can do. Tipalti, for example, documents two- and three-way matching, configurable purchasing policies, invoice coding and approval workflows. It also provides tolerance thresholds and exception approval rules. Its matching functionality compares invoices with purchase orders and, where applicable, receipts. These are substantial process capabilities. Tipalti, Purchase Order and Invoice Matching
For an organisation whose processes fit the product and whose team can own the implementation and operation, a dedicated AP platform may be the right investment.
Curia addresses a different purchasing requirement: a partner to redesign and run an agreed workflow across the systems and working practices the business already has. The relevant comparison includes configuration, adoption, exception investigation and ongoing maintenance, as well as software functionality.
A company can also need both. Before buying additional technology, it should establish which existing capabilities can already solve the problem and which operational gaps remain.
Measure the full cost of processing an invoice
APQC's published cross-industry benchmark showed a median total AP processing cost of $6 per invoice, with a stated sample of 5,846 companies, when accessed on 28 September 2026. The measure includes personnel, systems, overhead, outsourcing and other costs. It is a broad reference point, rather than a UK-specific target or a forecast of what automation will save. APQC, Total cost to process accounts payable per invoice
The definition matters as much as the number. Comparing a software fee per invoice with the current team's fully loaded cost per invoice creates an incomplete comparison if people will still spend time maintaining supplier records, resolving mismatches and dealing with queries.
APQC's March 2026 analysis gives another perspective: top-performing organisations spent approximately $0.38 per $1,000 of revenue on AP, compared with $0.92 for bottom performers. The latter is roughly 2.4 times the former. The analysis points to process clarity, stronger controls and standardisation as improvement areas. It does not establish that a particular technology caused the performance gap. APQC, How Organizations Can Reduce Accounts Payable Costs
For a buyer, the implication is practical: investigate the underlying work before treating a product's automation percentage as the business case.
A small exception queue can contain most of the labour
Consider the following illustrative operation. It handles 10,000 invoices a month. Nine thousand clean invoices require one minute of human attention each. The remaining 1,000 need 20 minutes each to investigate and resolve.
| Invoice category | Monthly volume | Human minutes per invoice | Total monthly human time |
|---|---|---|---|
| Clean invoices | 9,000 | 1 | 150 hours |
| Exceptions | 1,000 | 20 | 333 hours |
| Total | 10,000 | 2.9 average | 483 hours |
Ten per cent of invoices account for approximately 69% of the human effort.
Halving the remaining work on clean invoices saves 75 hours a month. Halving the effort required for each exception saves roughly 167 hours. At an assumed loaded cost of £35 an hour, those changes represent about £31,500 and £70,000 of annual capacity respectively, before implementation and operating costs.
This example explains why a high headline automation rate can coexist with a busy AP team. As routine processing improves, the remaining work becomes more concentrated in difficult cases.
The same calculation also shows why preventing exceptions deserves attention. If missing purchase orders are the main cause, improving the purchasing process may deliver more value than making the resulting investigations faster.
All volumes, handling times and labour costs in this example are assumptions. The figures illustrate how to assess an opportunity and are not industry averages or Curia client results.
Follow one disputed invoice through the whole process
Imagine an invoice for a delivery that was only partly received. The purchase order covers the full quantity, the warehouse record shows a short delivery and a supplier email says the balance will arrive next week.
A useful workflow must bring those records together, establish which line items are affected and apply the company's rules for partial delivery. It then needs to prepare the permitted action or send the unresolved decision to the correct person with the relevant evidence.
An exception alert is one step in that process. The valuable outcome is a resolved case with an appropriate decision, an accurate record and an explanation that can be checked later.
This is where Curia's approach becomes relevant. It maps the work around the transaction, including the evidence gathering and hand-offs between procurement, operations and finance, then builds and operates the agreed workflow. The team's judgement remains available for cases where commercial interpretation or approval is required.
The workflow should also reveal repeated causes. A recurring mismatch may indicate an outdated price list or a receiving process that needs correction. Reducing those causes can prevent the same work from returning next month.
Compare responsibility as well as functionality
| Buying question | Evidence to request from an AP software provider | Evidence to request from Curia |
|---|---|---|
| Does it fit our transactions? | A demonstration using representative invoices, entities and exceptions | A proposed workflow grounded in actual volumes, systems and exception types |
| Who implements it? | Configuration, integration and migration scope; client responsibilities | Process redesign, implementation and testing scope; required client input |
| What happens outside the standard path? | Exception features, supported integrations and work left with the client | How evidence is assembled, cases are routed and the agreed workflow is operated |
| Who maintains it? | Division between product support, implementation partner and internal team | Monitoring and maintenance responsibilities, change scope and escalation arrangements |
| What does success cost? | Full subscription, implementation and retained operating cost | Full assessment, implementation and managed service cost, including retained client effort |
Product capabilities and service packages vary. These questions establish the scope of a particular offer and avoid assuming that every software purchase leaves the same work behind.
Faster processing should improve payment decisions
An invoice that becomes ready for payment sooner gives finance more room to manage it: resolve a dispute before the due date, evaluate an early payment discount or pay on the agreed terms without last-minute intervention.
Paying earlier can consume cash sooner. The working capital objective must therefore be defined explicitly. A reduction in processing time should support the company's payment policy, with discounts evaluated against liquidity and financing costs.
Measure due-date performance, discount capture where economically justified, duplicate payments and unresolved disputes alongside labour cost. A process that is cheap but pays incorrectly has failed its purpose.
What Curia should prove before the workflow goes live
Curia begins with an assessment using the client's own numbers, followed by a contained proof on the client's data. For AP, that should establish the baseline exception rate, active handling time, elapsed resolution time and causes of rework.
The proof should show that the workflow handles the agreed cases correctly, respects approval limits, attaches the supporting evidence and directs unresolved decisions to the appropriate person. Any claimed reduction in human effort should include checking and correction time.
Once performance and controls are agreed, Curia operates the workflow as a managed service and maintains it as requirements change within the agreed scope. That model is particularly relevant where finance has bought capable systems but still spends substantial time coordinating the work between them.
Bring Curia a sample of the invoices your team finds hardest to resolve. We will assess where the effort sits, what can be prevented and which workflow is worth proving. Discuss your AP workflow