When people describe automated invoices they usually mean invoices that get from arrival to payment without anybody typing anything, and that is achievable for a substantial share of a payables queue. What automation reaches, and what it deliberately does not, is worth being precise about, because the gap between the two is where every disappointed expectation lives.
The automatic path
The invoice arrives at a monitored address, is captured into a record, is validated against duplicates and known suppliers, is matched against its purchase order and goods receipt within tolerance, is routed by rule to an approver or clears without one, is coded from the order, and is scheduled for payment. No keying, no chasing, no decisions.
Where a person is required
An invoice with nothing to match against, because there was no order. An exception where price or quantity disagree and somebody has to establish why. A coding question the order did not answer. A supplier nobody recognises. Each of these needs context that no rule holds, and automating them would mean guessing where guessing loses money.
What decides your ratio
The share of invoices arriving with an order and a receipt behind them. That is your ceiling on the automatic path, it is set outside payables, and it is measurable today. Every claim about how many invoices can be automated should be read against your own figure rather than against an industry average.
Questions people ask about automated invoices
Can invoices be paid with no human involvement at all?
Where the match is clean and within tolerance, many organisations treat that as sufficient authorisation. It is a policy decision that should be written down rather than a configuration default.
What is the most oversold claim?
That automation reduces exception handling. Exceptions come from documents missing or disagreeing, which automation surfaces faster but does not resolve.
Where should we start?
By measuring your own purchase-order and receipt coverage. It tells you what the automatic path can ever cover.