Invoice Verification Software: 14 Invoice Approval Tools

Anyone looking for an invoice approval tool will first come across programs that generate invoices. The term “invoicing software” dominates the discussion, even though it is only used at the very end of an incoming invoice’s processing path—after recognition, assignment, verification, and approval, during posting. Invoice verification software falls into different categories, and these categories differ less in their feature sets than in the specific stages of the process they cover.

This article categorizes the market into four classes, lists five selection criteria, and compares 14 providers based on these criteria. All information is taken from the providers’ websites, as accessed on September 23, 2026; where a secondary page or the developer documentation was consulted, this is noted in the table. If a website does not provide information, this is noted in the table. Konfuzio is a provider of an IDP platform and is included in this overview—with the same columns and the same sourcing rules as all the others.

This article describes how the audit itself is conducted—in terms of form, calculations, and substance—and the reasons why automation fails in practice. digital invoice verification.

Four Categories of Tools for Audit Review

The search terms „invoice verification software“ and „invoice approval tool“ lead to four categories of tools that perform different tasks:

• Invoicing and Accounting Software create and post outgoing invoices. A search for an invoice approval tool usually leads here first, even though these programs offer, at most, an approval workflow for incoming invoices without purchase order reconciliation. A subset of these tools is built around accounting as a cloud workflow. They accept incoming invoices, handle approval, and transfer the posting data to DATEV or a small ERP system; Candis, Flowwer, and Doxis SpendControl are examples of such tools.
• Document Management Systems (DMS) They store documents and retrieve them, thereby handling archiving. DocuWare and d.velop offer preconfigured workflows for incoming invoices that handle verification and approval within the document archive.
• IDP (Intelligent Document Processing) Platforms They extract data from documents, classify them, and forward the fields to the lead system in a structured format. They automate recognition and formal validation; approval takes place in the DMS or ERP.
• ERP Modules already have the purchase order reference in the system and support approval using value limits and substitution rules. Invoices in PDF or paper format must first be recognized—either within the module itself or through one of the two preceding classes.

These classes complement each other and cover different stages of the same process. An ERP system is aware of the order but can only see what someone enters into it. An IDP platform reads the document and is only aware of the order if it is integrated with the order.

Discrepancies arise at the interface between systems, which later become apparent as manual rework. Esker and Basware have built their products around this interface: Their platform sits in front of the ERP system and handles recognition, reconciliation, and approval for multiple ERP systems simultaneously. Especially in areas such as Freelance Accounting shows how important efficient digital processes are in order to be able to work independently of location and without errors.

Five Selection Criteria

When making your selection, the most important factor is how well the tool fits your own document workflow. Five criteria can help you decide:

• Integration of Order Data – Without access to the ERP or inventory management system, the substantive review must be done manually, regardless of the tool’s functionality. The software must be able to retrieve purchase orders and goods receipts on its own; otherwise, someone has to import them as a file.
• Interface Flexibility – A tool that accepts documents through only one channel and outputs results in only one format dictates the process.
• Threshold per field – The recognition software calculates a confidence score for each field, indicating how certain the model is. A threshold per field makes it possible to have only the uncertain fields reviewed. If the value for the invoice amount is above the threshold but the value for the supplier number is below it, an employee reviews only the latter. The threshold is based on the potential damage caused by a false positive—higher for the amount, lower for a free-text field. A single confidence score per document sends correct invoices to post-processing because a secondary field is uncertain.
• Exception Handling – Substitutes, value limits, and mobile approvals all contribute to the turnaround time, because every unresolved inquiry delays an invoice.
• Data Storage Location - Section 146(2a) of the Tax Code allows electronic books and records to be maintained and stored „in another Member State or in several Member States of the European Union.“ For a third country, paragraph 2b requires authorization from the tax authority upon request.

What Sets Flexible Interfaces Apart

On the input side, it’s the number of channels that matters. Invoices arrive on paper, as email attachments, via supplier portals, or as structured data records from another system. Software should monitor an inbox, read a network folder, and accept documents via a REST API (an application programming interface for data exchange between systems). Then no one has to forward invoices manually.

On the output side, it’s all about format and timing. The validated data is sent to the lead system—an ERP such as SAP or Microsoft Dynamics, or, in smaller companies, often DATEV. A webhook is an automatic notification sent to the target system as soon as a document has been validated; it transfers the data immediately after the validation. Exporting at fixed intervals is sufficient if the accounting department processes entries in batches anyway. In addition to JSON (the standard format for web interfaces), XML and CSV should also be supported, because not every target system can process JSON.

Flexible interfaces are characterized by two additional features. First, a feedback loop: If an employee corrects a value in the ERP system, the correction should be fed back into the recognition model. The model learns from this and makes the same error less frequently in documents from the same supplier. Second, the source reference: An output provides the confidence value and the position in the document for each field. For an automatically posted invoice, this makes it possible to trace where each value comes from.

Two examples from the table show how this works on provider sites. Doxis SpendControl lists four output formats—PDF, XLSX, CSV, and UBL—and an API that synchronizes data in both directions. Konfuzio accepts documents via email and through a REST API; the Developer Documentation Describes the webhook, as well as the confidence score and position for each field.

14 providers based on the five criteria

The table lists 14 providers that process incoming invoices side by side. Each row reflects what the provider’s linked page explicitly states as of September 23, 2026. Information from a second page of the same provider is linked or marked with „(Doc)“ for developer documentation. „N/A“ means the page does not provide any information on the matter. This describes the page. If you’re shortlisting a provider, ask about the empty cells during your discussion. There is no ranking, because the criteria carry different weight depending on the document flow.

Four observations can be drawn from the table.

The order reconciliation is tied to the class. xSuite and pds handle the purchase order within the same system and refer to the reconciliation as the „core“; OpenText describes validation rules on the page I read, but does not mention purchase order reconciliation. For DMS providers, it is a workflow step. The DocuWare manual describes it as follows: “If DocuWare finds a matching purchase order for a newly filed invoice and the difference does not exceed 5 euros (the default tolerance value), the invoice is transferred to the ‘Final Review’ workflow without any further intermediate steps.”

The tools related to accounting differ the most: Candis mentions three-way reconciliation, while Flowwer, Doxis SpendControl, and DATEV Belegfreigabe online do not mention any. IDP platforms provide the fields. Whether they perform the reconciliation themselves depends on the integration—Hypatos mentions it, while ABBYY and Konfuzio do not on the pages we reviewed.

Confidence values by field are not listed on any of the 14 linked pages. The websites list overall rates: ABBYY claims 99.5 percent accuracy; Esker states that „> 80% of incoming invoices are processed fully automatically“; and Basware claims 89 percent contactless processing. All three figures are listed on the respective provider’s website without specifying the population or measurement basis. They describe what the provider considers achievable and do not replace measurements based on one’s own document flow. For Konfuzio, the confidence value for each field is listed in the developer documentation. We were unable to verify whether Hypatos and ABBYY document this: The documentation is accessible only after logging in or via a support portal that blocks automated access.

Representation and value limits rarely go hand in hand. Only DocuWare mentions both, stating in the manual: „In the additional fields, define a custom approval limit and a supervisor to whom an invoice is also sent for review if this limit is exceeded.“ Candis and Flowwer refer to a designated substitute, while d.velop and Esker refer to an amount limit. The other sites mention neither a designated substitute nor an amount limit. An invoice for which the approver is on vacation and for whom no designated substitute has been specified remains pending.

Three of the linked pages specify the region where the data is stored. Candis (Germany), d.velop (AWS Frankfurt), and Doxis SpendControl (EU); Konfuzio lists the EU on a second product page. DocuWare, Konfuzio, and xSuite mention installation on the customer’s own servers; OpenText runs within the customer’s SAP instance. All others specify „Cloud“ without a region or provide no information—this is insufficient to address the question regarding Section 146 of the German Fiscal Code (AO).

Conclusion

An invoice approval tool is based on four tool classes, each designed for a different stage of the process. Which one is right for you depends on your specific document workflow: where the order data is stored, how many channels invoices come through, and whether your accounting department processes them in batches or immediately.

The table shows what remains unclear before the meeting with the provider. None of the linked pages list the confidence value for each field, and most are missing the substitution rule and the region where the data is stored.

Would you like to know which tool class best fits your document workflow and which of the 14 lines are relevant to you? Please feel free to contact us. Our experts will provide a no-obligation initial assessment.