A mid-sized ecommerce business receives 200 to 500 supplier invoices a month. Each one has to be captured, coded to the right account, matched to a purchase order where one exists, approved by the right person, and paid. Done by hand with a scanner and a spreadsheet, that is 10 to 20 hours of accounts-payable work per week. Vedron pulls invoices from the inbox, parses them with OCR, matches them to open POs, and routes them through an approval workflow before posting.
The mailbox-first flow
Suppliers mostly send invoices as PDFs attached to email. Vedron gives each company a dedicated inbox (invoices@yourcompany.vedron.io or a forwarded alias). A new email arrives, Vedron reads the attachment, parses it, and creates a draft invoice in the system within 30 seconds.
For paper invoices scanned on a shop multifunction, the same inbox accepts the scan via email. For hand-delivered invoices, the operator drops the PDF into Vedron via browser or mobile.
OCR accuracy
Modern OCR plus layout analysis extracts the right fields from a well-formed PDF with 95 to 99 percent accuracy on the key fields:
- Supplier name and tax id (VAT number, NIP, KSt number)
- Invoice number
- Invoice date
- Due date
- Line items with description, quantity, unit price, VAT rate
- Totals (net, VAT, gross)
For structured invoices under KSeF, XRechnung or Peppol, parsing is deterministic (100 percent) because the fields are typed.
Accuracy drops for low-quality scans (poor contrast, skewed, handwritten) and for unusual layouts. For a supplier whose invoice fails parsing, the operator trains Vedron once by correcting the fields on the first invoice; the layout is remembered and subsequent invoices from that supplier parse correctly.
Matching to purchase orders
Where the business issues POs to suppliers, Vedron matches each incoming invoice to the open PO. A match is based on supplier, PO number (if the supplier quoted it), line-item SKU and quantity. A full three-way match (PO, goods receipt, invoice) auto-approves the invoice.
For invoices without a PO (ad-hoc purchases, utilities, services), the operator codes the invoice to the right account directly.
Approval workflow
Approval rules are per company. Common patterns:
- Invoices under 500 EUR: auto-approve
- 500 to 5,000 EUR: single approver (manager)
- 5,000 to 25,000 EUR: two approvers
- Over 25,000 EUR: finance director sign-off
Approvers see a clean list of pending invoices with the original PDF next to the extracted fields. One click approves; one click rejects with a reason sent back to the supplier.
Posting to the books and export to DATEV
On approval the invoice posts to the books with the correct VAT split, the correct account per the chart of accounts, and the correct cost center. For German companies, the posted invoice exports to DATEV in the format the Steuerberater expects. For Polish companies, the posting is JPK-ready for the monthly SAF-T submission.
See post 139 for the full DATEV and multi-standard accounting workflow.
Payment run
Approved invoices become payable items. The payment run groups them by supplier and due date, generates a SEPA XML batch (pain.001), and sends it to the bank. The payment reference ties each payment back to the invoice for the bank reconciliation flow in post 148.
FAQ
How accurate is Vedron’s invoice OCR?
95 to 99 percent on key fields (supplier, invoice number, date, totals, VAT) for well-formed PDFs. 100 percent for structured e-invoices under KSeF, XRechnung or Peppol. Accuracy drops for low-quality scans; after one correction the layout is learned for subsequent invoices from the same supplier.
Can Vedron match invoices to purchase orders automatically?
Yes. Supplier, PO number, line SKU and quantity. A full three-way match (PO, goods receipt, invoice) auto-approves. Invoices without a PO are coded manually to the right account.
What approval workflow does Vedron support?
Per-company rules: a typical pattern is auto-approve under 500 EUR, single approver up to 5,000, two approvers up to 25,000, finance director over 25,000. Approvers see the PDF alongside the extracted fields in one view.
Does the posting flow into DATEV?
Yes. Posted invoices export to DATEV in the format the Steuerberater expects, with the right account per the chart of accounts and the correct VAT split. For Polish companies, the posting is JPK-ready for the monthly SAF-T.
How are payments made from the approved invoices?
The payment run groups approved invoices by supplier and due date, generates a SEPA XML batch (pain.001), and sends it to the bank. The payment reference ties each payment back to the invoice for bank reconciliation.
