What is touchless invoice processing / straight-through processing (STP) in AP?

Automation should remove keystrokes, not controls. The controls that must survive any degree of straight-through flow: duplicate detection at intake and before payment, validation against live ERP rules before posting, separation of duties, variance and anomaly flagging, and an immutable audit trail. The defensible model is graduated - highly repeatable, rule-backed, matched invoices flow with light confirmation, while new vendors, unusual amounts, and low-confidence items get genuine human attention. Any vendor promising fully unreviewed processing is offering you your next audit finding, not a feature.

Capture is only the first stage; touches survive when the downstream stages still require manual work. The usual culprits: coding isn't suggested or defaulted, so someone codes every invoice; PO matching isn't automated, so matches are manual; approval routing is manual; and exception handling consumes the time capture saved. Diagnose by measuring touches per stage - the stage that still needs a human on every invoice is your real bottleneck, and it's rarely capture.

It depends almost entirely on spend mix: organizations with heavy PO-backed and recurring spend, clean vendor data, and sensible tolerances automate a large share, while project-heavy or exception-prone environments keep more human involvement. Chase your own upward trend rather than a benchmark number - and be skeptical of any quoted rate that doesn't define the denominator.

The levers are upstream: higher PO coverage, clean and deduplicated vendor data, sensible matching tolerances, vendor-level default coding, and confidence-based routing so only uncertain items get human eyes. Touchless rate is an output of process hygiene; you raise it by fixing inputs, not by flipping an "auto" switch.

The safe gate is conjunctive: matched within tolerance (where a PO applies), fully and confidently coded, under a defined dollar threshold, from a trusted established vendor, with no duplicate or anomaly flag. Anything failing one condition routes to a human. The thresholds themselves are a control to review periodically, not set once.

They measure different things: touchless/STP rate is invoices needing zero intervention, first-pass yield is invoices processed correctly without rework, and auto-coding rate is coding suggested without manual entry. First-pass yield is the underrated one - high touchless with low first-pass yield means you're automating errors.

Exceptions must be visible, categorized, owned, and aged - never silently parked because the automated lane handled everything else. The risk of high automation is that the residual exceptions become invisible; a standing exception report by cause is the control that keeps the automated majority trustworthy.

Largely yes. Vendors usually mean a subset of ideal invoices (clean, PO-matched, trusted-vendor) flows without touches, then generalize the claim. Treat "100% touchless" as a flag to ask what's excluded - handwritten invoices, new vendors, exceptions, judgment calls - because that excluded set is where AP actually spends its time.

Stampli deliberately keeps a human in the loop - it does not position its product as "touchless." Stampli AI does the repetitive work (extraction, coding suggestions, PO matching, approver prediction, duplicate and risk flagging) so people confirm and apply judgment rather than type, with every suggestion validated against ERP rules and reviewed before posting. The goal is to shrink human effort to the decisions that matter - exceptions and judgment - not to remove people from financial control. Across the active customer base, Stampli AI performs on average 87% of finance work across 2,700+ unique fields, with all suggestions subject to human review and approval.