# Touchless Invoice Processing: Measure Posting, Not Just Capture Source: https://www.digiparser.com/blog/touchless-invoice-processing [See all posts](/blog) Last updated on October 26, 2026 # Touchless Invoice Processing: Measure Posting, Not Just Capture Manufacturing Supplier invoices AP automation [![Pankaj Patidar](https://avatars.githubusercontent.com/u/17493609?v=4) Pankaj Patidar @thepantales ](https://x.com/thepantales) ![Touchless Invoice Processing: Measure Posting, Not Just Capture](https://www.digiparser.com/images/blog/touchless-invoice-stages.svg) Touchless invoice processing means an invoice reaches an agreed endpoint without human intervention. For an AP pilot, define that endpoint before you measure it. **A file extracted, an export sent and a bill posted are three different results.** This guide uses confirmed posting as the endpoint and shows how a 70% no-edit capture rate can coexist with only 40% touchless posting. This is for manufacturers receiving **supplier invoices**, with 11-500 employees. It is separate from processing customer POs for sales orders. If your useful destination is a reviewed spreadsheet, measure that result directly; you do not need to build full AP posting to benefit from document extraction. **Before you compare a touchless percentage, ask:** Touchless through which step, out of which invoices, and confirmed by which record? ## What counts as a completed touchless invoice? For this guide, count an invoice only when it has moved from intake to a **confirmed AP posting with no required human check, correction, approval or manual posting** along the way. The accounting system must provide evidence of the final result. A timeout or an unconfirmed destination write stays unresolved. Microsoft's metrics reference defines touchless rate around end-to-end completion without human intervention. Our recommendation is to write down the start, endpoint and population so that the percentage has a usable meaning. [Microsoft: agent metrics reference](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/agent-business-value-metrics-reference). Do not remove a necessary approval to increase the number. A reviewed invoice can be a successful business outcome even though it is not touchless. Track reviewed completion and exception resolution alongside automation. ## Follow the invoice through four checkpoints Checkpoint Evidence to retain What it does not prove Captured Source reference, extracted fields and item rows That the supplier, quantities or accounting treatment are approved Reviewed or automatically cleared Rule results, any reviewer decision and changed fields That the destination accepted the data Exported Delivery result and receiving reference where available That an accounting bill was posted Posted Confirmed destination bill ID and posting status That payment was approved or executed These are useful checkpoints even if your system uses different names. Microsoft Dynamics 365, for example, reports import failures, workflow status and automatically processed posted invoices separately. That separation is a useful design reference, not a requirement to use Dynamics. [Microsoft: vendor invoice automation workspace](https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/vendor-invoices-workspace). ## The same 20 invoices can produce 70%, 60% and 40% Consider a **constructed pilot of 20 unique supplier invoices**, all received in one fixed intake cohort. Sixteen are initially eligible for the proposed automatic route. Four require human review under the team's existing policy. No duplicate submissions, credit notes or cancelled invoices are included in this example. At the reporting cutoff, the results are: Invoices Count What happened 1-8 8 Captured, exported and confirmed posted without a human touch 9-10 2 Captured and exported automatically; a person then assigned accounting codes 11-12 2 Captured and exported automatically; posting result still unconfirmed 13-14 2 No extraction edits, but an exception required review before export 15-16 2 Extraction values required correction 17-20 4 Mandatory human-review route; outside the initial automatic-route eligibility **No-edit capture: 14 / 20 = 70%.** Invoices 1-14 needed no extraction correction. Two of them still needed review before export. **Unassisted export: 12 / 20 = 60%.** Invoices 1-12 reached export without a human touch. Four of those did not reach confirmed touchless posting. **Confirmed touchless posting: 8 / 20 = 40%.** Only invoices 1-8 meet the end-to-end rule at this cutoff. The two unconfirmed writes are not successes or proven failures; their outcomes need checking. The eligible-only posting rate is **8 / 16 = 50%**. That is a useful secondary view, but it must be labelled. It does not replace the 40% rate across all 20 invoices. These figures are our arithmetic example, not an industry benchmark or a measured DigiParser result. The lesson is that the same invoice batch supports several correct percentages that answer different questions. **An export success rate cannot stand in for a posting success rate.** **Use the example in your own pilot** [Download the plain-text pilot worksheet](/examples/touchless-invoice-processing/pilot-checklist.txt) to record the endpoint, cohort, reviewer and destination proof. Analysts can also [download the synthetic 20-invoice ledger as JSON](/examples/touchless-invoice-processing/example-ledger.json). The files contain examples and blank planning fields. They do not connect to DigiParser or an accounting system. ## Set up a pilot in six steps ### 1\. Agree the completion event Choose a result you can verify: a reviewed invoice register, an accepted draft bill, or a posted AP bill. Name it in every report. If the pilot ends at export, call the measure export completion, not touchless AP posting. Keep payment approval and execution separate. A posted bill is not proof that payment has been authorized or sent. ### 2\. Fix the intake cohort and counting rules Choose invoices by receipt window, not by which ones finished easily. Give each unique invoice a stable reference and keep its original source. Record repeat files against the same invoice instead of counting every email attachment as a new transaction. Record which invoices are eligible for the proposed automatic route and why. If eligibility changes during the pilot, show the change instead of silently moving difficult cases out of the denominator. Keep credit notes, exact repeats and cancellations visible in a separate count with the rule used to exclude them. Which numbers belong in the pilot report? Show the number received, unique invoices in scope, exclusions with reasons, initially eligible invoices, completed invoices with human work, confirmed touchless completions, unresolved invoices and the reporting cutoff. Report both overall and eligible-only rates with their denominators. Follow the same intake cohort through later updates so late completions do not disappear. ### 3\. Validate invoice meaning before handoff Compare supplier identity, invoice number, currency, amounts and item rows with the source. Check invoice total separately from remaining balance. Resolve ambiguous supplier or item references before using them in a destination record. Manufacturing invoices may also need PO and receipt checks, especially with partial deliveries. Use the [invoice field guide](/blog/invoice-data-extraction) and [three-way matching example](/blog/three-way-matching) for those tasks. Extraction supplies data; your purchasing and accounting rules decide whether the invoice is ready. ### 4\. Keep a review gate for the exceptions Name the person who resolves each exception and the evidence they need. A missing receipt may need receiving to update its record. An uncertain quantity needs a source check. An accounting question goes to the person responsible for AP coding or approval. Start with review where it is needed. Change a rule only after representative examples show why the change is useful. A legitimate manual check is not a failed automation project. ### 5\. Confirm the destination outcome Retain the receiving record ID and its actual status. Microsoft documents that automatic submission to a workflow needs an automated posting task in the configured process for end-to-end handling without manual intervention. Submission alone is not the last step. [Microsoft: invoice workflow and posting configuration](https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/submit-invoice-workflow-automatically). If an export times out, look for the destination record before sending it again. Use the destination's duplicate controls and an agreed retry process. Do not treat "request sent" as "bill posted," or create another bill just because the first response was lost. ### 6\. Review the exception reasons, not only the percentage Use the ledger to find the next improvement: repeated missing references, avoidable extraction edits, reviewer queues or a handoff with no clear response. Also measure time to usable output and the amount of review work. Keep unresolved invoices visible and state the cutoff. Do not choose a universal touchless target before seeing your mix of invoices and required controls. The useful goal is reliable completion with less avoidable work. ## Where DigiParser fits in the workflow [DigiParser's supplier invoice parser](/solutions/invoice-parser) extracts header fields and line items for review and structured output. Its documented **Reviews & Approvals** stages can be mandatory or conditional and run in sequence. When a reviewer is assigned, exports wait for the required approvals. [Read the review-stage guide](/docs/guides/reviews-approvals/overview). A mandatory review means that route includes a human touch. That can be exactly the control your team needs. DigiParser supports XLSX, CSV, JSON and XML exports, with configured integration routes for automatic delivery. [See export choices](/docs/guides/managing-data/exporting-data). Your receiving accounting process still needs its own tested mapping, duplicate controls, posting result and payment controls. For **11-50 employees**, one office/AP owner may manage extraction review and check the destination, with a named backup. At **51-200**, assign ownership of supplier, receiving and accounting exceptions according to the actual team. At **201-500**, agree the receiving-system owner and pilot approver across the teams involved. Headcount does not establish spending authority or require three levels of approval. ## Can an invoice be automated and still need review? Yes. Capture, routing and delivery can be automated while a person makes a required decision. Report that as reviewed automation rather than counting it as an end-to-end touchless invoice. ## What if Excel is our final destination? Use confirmed, reviewed spreadsheet output as the milestone. You can reduce retyping without creating an AP bill automatically. Test the source fields, line count, identifiers and actual receiving rows. Expand only when the next destination step has a useful, verified purpose. ## What should we do first? Define the completion event and fill in the [pilot worksheet](/examples/touchless-invoice-processing/pilot-checklist.txt). Then [evaluate DigiParser with representative supplier invoices](/solutions/invoice-parser), a reviewer and a known destination. Judge the pilot by the usable result and the work it removes, with each percentage tied to a named step. * * * [See all posts](/blog) Automate recurring documents next: [supplier invoice parser](/solutions/invoice-parser), [customer purchase order parser](/solutions/purchase-order-parser), and [extract data from PDF](/solutions/extract-data-from-pdf) hub. ## Transform Your Document Processing Start automating your document workflows with DigiParser's AI-powered solution. [Start Free Trial](https://app.digiparser.com/auth/join)[Schedule Demo](/contact)