Blog · All

$9.84 and 8.2 days to process one invoice. Intelligent document processing, explained.

A supplier emails an invoice as a PDF. Before anyone can approve or pay it, somebody opens the attachment, reads the supplier name, the invoice number, the date, the lines and the total, types them into the accounting system, checks them against the purchase order, and sends the bill to the right person for approval. Then the next invoice arrives, from a different supplier, in a different layout.

Intelligent document processing, usually shortened to IDP, is the name for software that takes over the reading part of that routine. This article walks one invoice through it and shows where the rest of the work goes.

The numbers

Ardent Partners publishes the State of ePayables research on accounts payable. Its 2025 edition puts the average cost of processing a single invoice at $9.84 and the average time at 8.2 days. The average invoice exception rate is 18.4 percent, and 57 percent of suppliers can now send invoices electronically.

Accounts payable averages: Ardent Partners, The State of ePayables 2025
  • $9.84Average cost to process one invoice
  • 8.2 daysAverage time to process one invoice
  • 18.4%Average invoice exception rate
  • 57%Suppliers that can send invoices electronically

Source 1

Ardent reports these as accounts payable benchmarks. They are not a prediction for an individual business, and they cover the wider invoice process, which includes work beyond reading and entry. Close to one invoice in five does not go through cleanly.

What IDP is

Gartner, which tracks the category, describes IDP solutions as tools that take in documents in many formats and layouts, extract the data in them, and pass that data on to other applications and workflows. For this invoice example, we can group several of Gartner's required capabilities into five steps.

  1. Take the document in. The PDF arrives by email. A scan, a photo or a spreadsheet would be accepted the same way.
  2. Classify it. The software decides this is an invoice, not a statement, a quote or a payment notice.
  3. Extract the fields. Supplier, invoice number, date, purchase order number, each line, tax and total. IDP is built for layouts that vary, so the invoice number is found whether it sits top right on one supplier's page or in a table on another's.
  4. Review. Gartner's list includes checking by the software and checking by a person, with correction and override. In this example, a field the software is unsure of is shown to someone before it moves on.
  5. Deliver. The extracted data is passed to another application or written to a file.

That is the document reading and checking stage in this example: a document goes in, checked data comes out.

The rest of the invoice workflow

Extracting the data is one stage of the invoice workflow. The bill still needs to reach the accounting system, follow your matching and coding rules, and go to the right person for approval. Some IDP products handle parts of that workflow too, and where one fits your process, it is a good answer.

An agent, as we build them, is software that signs in to the systems your team already uses, with its own login, and does one repetitive job inside them by following rules your team wrote down with us. For invoices, the agent does the reading and then keeps going. It opens the accounting system, finds the supplier, enters the bill, checks each field it entered against the invoice, and checks the invoice against the order and receipt the way your team defined. The reading can come from the agent itself or from an IDP tool you already own. The two are not rivals.

The exception is the real test

At an average exception rate of 18.4 percent, what happens to the invoice that does not fit matters as much as what happens to the one that does. A purchase order number that is missing, a price that differs from the order, a supplier not yet on file, a total that does not add up: ask of any tool what it does then.

The answer we build to is that the agent stops on that invoice and returns it to a named person with what it found and why. It does not guess, and it does not hold the invoice without telling anyone. Ardent reports that the teams it ranks as best in class have exception rates 47 percent lower than everyone else, which suggests exceptions are worth designing for, not only cleaning up after.

Four questions to ask before you choose

  1. How many of your invoices arrive in layouts you do not control? The more they vary, the more the reading step matters.
  2. After the data is extracted, where does it go, and who enters it? If the answer is a person retyping from a spreadsheet, the routine has moved, not ended.
  3. Is each entry checked against the document before it is saved? Ask this of every tool.
  4. What happens to an exception, and who receives it? The answer should name a person and include the reason.
Who does what

The agent carries

  • Opening each invoice as it arrives by email, upload or scan
  • Reading the supplier, invoice number, date, purchase order number, lines and total
  • Finding the supplier and entering the bill in your accounting system
  • Checking each entered field against the invoice, and the invoice against the order and receipt
  • Stopping on an exception and returning it to a named person with the reason

Your team keeps

  • Approving each bill and releasing payment
  • Supplier conversations about disputes and credits
  • Rules for assigning expense categories and anything the rules do not cover
  • Deciding which suppliers and invoice types come first

What stays with your team

Your team keeps the decisions that carry its authority. Approving a bill, releasing a payment, settling a dispute with a supplier, deciding how a new kind of expense is coded: none of that moves. The tools differ in how much reading, entry and checking they carry before that point.

If supplier invoices are the routine your team would most like to hand off, tell us about it. We will look at one workflow with you and say plainly whether IDP, an agent, or the tool you already have is the right fit.

Tell us the task

Sources

  1. Ardent Partners, "State of ePayables (Part Nine): AP Benchmarks and Best in Class Performance", Andrew Bartolini, 22 January 2026, reporting figures from The State of ePayables 2025: AP's Unfinished Journey. Average invoice processing cost of $9.84; average processing time of 8.2 days; average exception rate of 18.4 percent; 57 percent of suppliers able to send invoices electronically; best in class exception rates 47 percent lower. https://payablesplace.ardentpartners.com/2026/01/state-of-epayables-part-nine-ap-benchmarks-and-best-in-class-performance/
  2. Gartner Peer Insights, "Intelligent Document Processing Solutions", market definition and required features, viewed 11 November 2026. https://www.gartner.com/reviews/market/intelligent-document-processing-solutions

This article is general information about automation tools. It is not legal, financial or technical advice for any particular business.

Book a demo