Invoice templates are dead. Here's what replaced them.
Template-based capture made AP automation possible a decade ago. Today it's the reason so many AP teams still key invoices by hand.
2 min read · Slingstone
Why templates break
Legacy invoice capture works by teaching the system where fields live on each vendor's layout. It works well for the top vendors and falls apart in the long tail: the one-off contractor, the vendor who redesigned their invoice, the PDF that's really a photo of paper.
Every exception lands back on a person, and the AP team ends up maintaining templates as a part-time job.
Reading, not locating
Slingstone AP Automation uses vision-capable AI that reads an invoice the way a person does. It understands that a number next to 'Amount due' is the total, that a table of items is the line detail and that a date near 'Terms' is probably the due date — regardless of layout.
There's nothing to configure per vendor. A new vendor's first invoice is read with the same accuracy as one you've paid a hundred times.
Line items, not just headers
Header-only capture leaves your team splitting lines by hand when a bill spans departments or locations. Slingstone extracts line items and codes them individually, so allocations happen at capture rather than after.
Duplicates caught at the door
Every document is fingerprinted when it arrives. The same PDF emailed twice, or a scanned copy of an invoice already received electronically, is flagged before anyone spends time on it.
Legacy tools vs. Slingstone
| Legacy tools | Slingstone |
|---|---|
| Templates per vendor layout | No templates — AI reads any layout |
| Header fields only | Header and line items |
| New vendors start manual | New vendors captured from the first invoice |
| Duplicates found at payment time | Duplicates flagged at intake |