Automatic invoice processing means an invoice reaching payment without a person touching it, and a substantial share of a payables queue can work that way. The ceiling on that share is not a property of any product: it is the proportion of your invoices that arrive with a purchase order and a goods receipt behind them, which you can measure this week.
What the automatic path looks like
Arrival at a monitored address, capture into a record, validation against duplicates and known suppliers, matching against the order and receipt within tolerance, routing or automatic clearance, coding inherited from the order, and scheduling into a payment run. No keying, no chasing, no judgement calls anywhere along it.
What sends an invoice off it
No order, so nothing to match. No receipt, so the three-way match cannot complete. A price or quantity difference outside tolerance. An unrecognised supplier. Each needs a person, and each is generated upstream of payables rather than inside it, which is why the ceiling is not something payables can raise alone.
How to raise the ceiling
Purchase-order coverage and receipt timeliness, both of which are policy and habit rather than software. A threshold people know, a stated policy for invoices arriving without a reference, and making the receipt somebody's explicit job at the delivery point. All three are free, and all three raise the ceiling for any product you later buy.
Questions people ask about automatic invoice processing
Is it safe to pay without a person looking?
Where a clean three-way match within tolerance is treated as sufficient authorisation, many organisations do. It should be a written policy rather than a configuration default.
What proportion is realistic?
No higher than your measured order and receipt coverage. Any claim above that number describes a different organisation.
Does it reduce exceptions?
No. It clears the easy invoices faster and leaves the exceptions exactly where they were, which is where the effort is.