[{"data":1,"prerenderedAt":183},["ShallowReactive",2],{"\u002Fblog\u002Faccounts-payable-automation-from-paper-chaos-to-stp":3},{"id":4,"title":5,"body":6,"description":174,"extension":175,"lastUpdatedAt":176,"meta":177,"navigation":178,"path":179,"publishedAt":176,"seo":180,"stem":181,"__hash__":182},"blog\u002Fblog\u002F0001.accounts-payable-automation-from-paper-chaos-to-stp.md","Accounts Payable Automation: From Paper Chaos to Straight-Through Processing",{"type":7,"value":8,"toc":163},"minimark",[9,13,16,21,24,27,31,34,41,47,53,59,63,66,80,84,87,93,104,115,119,122,130,134,142,145,149,152,160],[10,11,12],"p",{},"If your AP team still spends a meaningful chunk of its week keying invoice data into your ERP, chasing down approvals over email, and filing paper into lever-arch folders — you are not alone. Most Swiss finance teams are somewhere in the middle of a transition that frankly started too late and is moving too slowly.",[10,14,15],{},"Here is what that transition actually looks like in practice: where the bottlenecks really are, what AP automation actually fixes, and what the end state — straight-through processing — looks like for a mid-sized Swiss company.",[17,18,20],"h2",{"id":19},"what-is-straight-through-processing","What is straight-through processing?",[10,22,23],{},"Straight-through processing (STP) means an invoice arrives, gets validated, matched to a purchase order, approved, and queued for payment without anyone touching it manually. No data entry. No email threads. No lost invoices at the bottom of a pile.",[10,25,26],{},"For most companies, 100% STP is not realistic on day one. But even getting 60–70% of invoices processed without human intervention makes a measurable difference to your team's workload and your payment cycle times.",[17,28,30],{"id":29},"where-the-time-actually-goes-in-a-manual-ap-process","Where the time actually goes in a manual AP process",[10,32,33],{},"Before you can implement any invoice processing software, it helps to be honest about where the hours go. In a typical manual AP workflow, there are four places work piles up:",[10,35,36,40],{},[37,38,39],"strong",{},"Data entry."," Someone opens the PDF, reads the supplier name, invoice number, date, line items, and VAT amount, and types it all into the ERP. For a straightforward invoice this takes three to five minutes. Multiply that by two hundred invoices a month and you have spent a full working day on transcription alone.",[10,42,43,46],{},[37,44,45],{},"Approval routing."," The invoice gets emailed to a manager. The manager is travelling. Their deputy is not sure if they are authorised to approve. The invoice sits in an inbox for nine days. Late payment fees follow.",[10,48,49,52],{},[37,50,51],{},"Matching and exceptions."," The quantity on the invoice does not match the purchase order because the supplier delivered a partial shipment and invoiced the full amount. Resolving this takes emails, phone calls, and sometimes a credit note. Meanwhile the original invoice is parked in your ERP as a problem item.",[10,54,55,58],{},[37,56,57],{},"Archiving and audit prep."," At year-end or during a VAT audit, someone has to locate specific invoices. If they are stored as PDFs in a folder structure that only one person understands, this becomes a project.",[17,60,62],{"id":61},"the-root-cause-unstructured-invoice-data","The root cause: unstructured invoice data",[10,64,65],{},"These four bottlenecks share the exact same root cause. When invoices arrive as PDFs — or worse, as paper — the data inside them is locked away. Your ERP cannot read it. Your approval system cannot route it automatically. Your matching logic cannot compare it to a purchase order. A human has to extract it first.",[10,67,68,69,74,75,79],{},"Structured e-invoicing breaks this dependency. When a supplier sends you an invoice in a machine-readable format — whether that is via ",[70,71,73],"a",{"href":72},"\u002Fblog\u002Febill-for-utilities-and-subscription-billing","eBill",", over ",[70,76,78],{"href":77},"\u002Fblog\u002Fchoosing-between-ebill-and-peppol-for-your-business","PEPPOL",", or as a ZUGFeRD hybrid PDF — your ERP receives the data directly. Supplier name, UID, IBAN, line items, VAT breakdown, and your purchase order reference all arrive as structured fields, ready to be processed.",[17,81,83],{"id":82},"the-automation-stack-what-you-actually-need","The automation stack: what you actually need",[10,85,86],{},"There is no single accounts payable software that solves everything out of the box. A practical AP automation setup for a Swiss SME typically involves three layers:",[10,88,89,92],{},[37,90,91],{},"1. Invoice capture and ingestion","\nFor suppliers who send PDFs (and many will for a while yet), an OCR layer can extract the data and feed it into your ERP. The accuracy is never perfect, which is why moving suppliers to structured formats is worth prioritising. Every eBill sender or PEPPOL-connected supplier is one less invoice your OCR has to guess at.",[10,94,95,98,99,103],{},[37,96,97],{},"2. Automated three-way matching","\nOnce data is in your ERP, ",[70,100,102],{"href":101},"\u002Fblog\u002Fhow-three-way-matching-reduces-invoice-disputes","three-way matching"," compares the invoice against your purchase order and goods receipt automatically. Most ERP systems have this built in — the question is whether your master data is clean enough for it to work. Supplier IDs, product codes, and unit-of-measure conventions all need to be consistent.",[10,105,106,109,110,114],{},[37,107,108],{},"3. Rules-based approval routing","\nInvoices that match cleanly can be approved automatically within defined limits. Those that do not — wrong price, missing PO reference, quantity discrepancy — get routed to the right person immediately rather than sitting in a general inbox. ",[70,111,113],{"href":112},"\u002Fblog\u002Fhow-to-set-up-an-efficient-invoice-approval-workflow","Setting up those approval rules"," is less about technology and more about getting your internal sign-off policies written down clearly for the first time.",[17,116,118],{"id":117},"the-supplier-side-matters-as-much-as-the-internal-side","The supplier side matters as much as the internal side",[10,120,121],{},"A common mistake is to invest heavily in internal tooling while leaving supplier behaviour unchanged. If your fifty largest suppliers are still sending PDFs, your OCR layer is doing a lot of heavy lifting and your exception rate stays high.",[10,123,124,125,129],{},"Supplier onboarding is the unglamorous work that makes the numbers move. ",[70,126,128],{"href":127},"\u002Fblog\u002Fhow-to-onboard-your-suppliers-to-e-invoicing","A structured onboarding programme"," — communicating clearly what formats you accept, offering a simple registration path for eBill or PEPPOL, and following up with suppliers who have not made the switch — typically has a bigger impact on your STP rate than any software upgrade.",[17,131,133],{"id":132},"the-roi-and-metrics-of-ap-automation","The ROI and metrics of AP automation",[10,135,136,137,141],{},"If you cannot measure it, you cannot improve it. The metrics worth tracking are straightforward: processing cost per invoice, cycle time from receipt to payment approval, and your exception rate (the percentage of invoices that require manual intervention). We cover these in detail in ",[70,138,140],{"href":139},"\u002Fblog\u002Fkpis-every-ap-team-should-track-when-switching-to-e-invoicing","the KPIs every AP team should track",".",[10,143,144],{},"One number that often surprises finance teams: the cost difference between a manually processed invoice and a straight-through one. Industry benchmarks put manual processing at CHF 15–25 per invoice once you account for staff time, error correction, and late payment costs. STP brings that closer to CHF 1–3. For a company processing a thousand invoices a month, that gap is worth around CHF 150,000 per year.",[17,146,148],{"id":147},"where-to-start","Where to start",[10,150,151],{},"The right starting point depends on your current state. If you have no purchase order process at all, fixing that comes before any AP automation. If your ERP master data is inconsistent, clean that up first — automation amplifies bad data rather than fixing it.",[10,153,154,155,159],{},"For most Swiss companies the practical first step is to register as an eBill biller or PEPPOL participant and start converting your highest-volume suppliers. The ",[70,156,158],{"href":157},"\u002Fblog\u002Febill-mandates-for-swiss-federal-suppliers-in-2026","2026 federal B2G e-invoicing mandate"," is a useful forcing function — it means your suppliers who invoice the public sector are already being pushed towards structured formats, and that infrastructure can be pointed at you too.",[10,161,162],{},"The technology is not the hard part. The hard part is the internal alignment: agreeing on approval thresholds, cleaning up supplier master data, and getting your ERP configured to actually use the structured data it receives. But once that groundwork is done, the processing overhead drops sharply — and your team can spend its time on things that actually need human judgement.",{"title":164,"searchDepth":165,"depth":165,"links":166},"",2,[167,168,169,170,171,172,173],{"id":19,"depth":165,"text":20},{"id":29,"depth":165,"text":30},{"id":61,"depth":165,"text":62},{"id":82,"depth":165,"text":83},{"id":117,"depth":165,"text":118},{"id":132,"depth":165,"text":133},{"id":147,"depth":165,"text":148},"A roadmap for AP teams moving from manual, paper-based invoice handling to fully automated processing.","md","2026-04-21",{},true,"\u002Fblog\u002Faccounts-payable-automation-from-paper-chaos-to-stp",{"title":5,"description":174},"blog\u002F0001.accounts-payable-automation-from-paper-chaos-to-stp","qBbdkt3ejHPKtxnlq5k7cPuZDDRedkGE10zZPi_K7Pk",1776765748969]