Automatically read, classify and post supplier invoices to your accounting or ERP system. We build custom invoice processing where standard tools fall short: industry-specific, with deep integrations, and ready for Peppol and the EU e-invoicing mandate in 2030.
Klippa, Basecone, AutoInvoice, FactuurSturen and Visma Scanner do a good job on standard PDF invoices, so we don't build a copy of those. Our clients come to us when those tools hit a wall: an industry-specific invoice format the standard parser can't read, an ERP integration that needs to go a little deeper, or an approval flow with multiple cost centres and budget categories that no off-the-shelf SaaS form accommodates. Often it's a combination: an organisation that wants not only to recognise invoices, but to match them straight away against purchase orders, contracts and framework agreements held in its own systems.
We build bespoke invoice recognition using modern OCR (Tesseract, PaddleOCR, Google Vision) and multimodal models such as Anthropic Vision and GPT-4o Vision that genuinely understand the nuance of an invoice. The result is a processing pipeline that fits into your ERP, not the other way around, and that grows with new supplier formats, new budget structures or a future move to Peppol-only e-invoicing. Get in touch if you run an accountancy practice, manage procurement flows in a large organisation, or need this as part of wider document workflow automation.
Our clients are SMEs processing fifty to five hundred purchase invoices a month, accountancy and bookkeeping firms handling client ledgers, and large organisations with formal procurement processes. What they share is a breaking point: the volume or complexity is too high for manual entry, but too specific for an out-of-the-box scanner.
Not every organisation needs the same thing. In the first conversation we advise which approach suits your invoice volume and systems landscape.
For SMEs manually booking fifty to five hundred purchase invoices each month. We build an ingestion flow in which invoices arrive by email, drop folder or Peppol, are read automatically by a combination of OCR and a language model, and then post directly as journal entries in Exact, Twinfield or AFAS. The approver receives a notification, approves with one click, and the invoice is ready for payment.
Accounting and bookkeeping firms often work for dozens of clients, each with their own bookkeeping package and their own records. We build a central processing pipeline that knows the correct chart of accounts for each client, automatically suggests the right general ledger account and cost centre, and only brings in a person when there is doubt. The LLM learns from previous postings — the same supplier on the same account, automatically.
For large organisations with a formal procurement process: incoming invoices are automatically matched against the purchase order and goods receipt (3-way match), with escalation to the right budget holder when discrepancies arise. Full Peppol BIS support for e-invoices, native UBL processing, and integration with SAP, Oracle or Microsoft Dynamics. An audit trail at every step, ready for your auditor's review.
A working processing pipeline in production, plus the tools to adjust and expand it yourself.
We are not committed to a single vendor or model. For each project we choose the combination that suits your invoice mix, your cloud environment and your budget, and we explain why.
For clean PDFs and e-invoices we work directly with the structured data. For scans and photos we combine classic OCR (Tesseract and PaddleOCR for local processing, Google Vision where cloud use is acceptable) with multimodal models such as Anthropic Vision and GPT-4o Vision. These models read an invoice as a whole: they understand that a number in the top right is the invoice number, even if the label reads "Invoice #" or "Faktura Nr.". For sensitive documents we run local models in your own environment, so invoice data never leaves your data centre.
The raw text is passed to a language model that extracts the fields you need: invoice number, invoice date, due date, VAT amounts per rate, cost centre, project code, supplier details, IBAN. We build business-rule validation around it: does the VAT total add up, does the invoice date fall within the financial year, do we know this supplier? If in doubt, the invoice goes to a human reviewer with the points of concern already flagged. This human-in-the-loop approach moves quickly to full automation once the model has learned the patterns.
The extracted data is then pushed into your system. For SMEs this is usually Exact Online, Twinfield, AFAS or Visma. For accountants, often Yuki or Snelstart per client. For enterprises, SAP, Oracle NetSuite, Microsoft Dynamics or Unit4. We process incoming Peppol invoices natively as UBL, and for outgoing invoices we connect to a Peppol Access Point. For specific integrations not covered here, we look at the existing API and build an adapter. Read more on our page about smart API integrations.
Four signs we see in organisations that have outgrown their standard scanning tool. If you recognise one of them, we would be happy to talk further.
Construction, healthcare or agricultural suppliers issue invoices with line items and codes that standard scanning tools cannot separate properly. A custom extraction model that understands your invoice patterns delivers clean data straight away.
Standard tools write to a single field in Exact or Twinfield. You have cost centre, project and VAT code logic that differs from invoice to invoice, and you want that filled in automatically before posting.
At fifty invoices a month, manual entry still works. At five hundred or more, it becomes a full-time job. A custom processing pipeline pays for itself quickly, especially if it can intervene more deeply in your processes.
The EU will require business-to-business e-invoicing via Peppol-style standards from 2030. If you build a platform now that handles both PDF and UBL, you won't have to scramble to switch later.
We review a representative set of your invoices (typically one hundred to two hundred documents across your main suppliers) and your current booking process. From this we produce an initial assessment of extraction quality per field, the integrations we need, and where the biggest time savings lie. At this stage we're candid about what we can and can't solve for you. Sometimes a standard tool supplemented with a small custom connector is more than enough, and our clients prefer to hear that up front rather than halfway through a project.
A short design sprint with your finance and IT teams. We choose the right OCR stack (Tesseract, PaddleOCR or Google Vision), decide which LLM handles the extraction work, and set up a proof of concept with which your team tests the first batch.
A working build every two weeks: more supplier formats, integration with your accounting system, the approval flow, and an audit log. You test continuously, and finance joins in on the UX decisions.
We start with one department or one set of clients, run in parallel with the old process for a period, and expand once extraction quality and approval speed are where they need to be.
New suppliers, new integrations, model updates and expansion into areas such as computer vision applications for receipts or contract analysis. Many clients extend into full procurement automation in year two.
What clients usually want to know before we start.
A free 30-minute introductory call. Send over a few sample invoices and, during that conversation, we can show you concretely where standard tools reach their limits, and where custom development makes the difference.
Appfront uses cookies and similar technologies to keep the website working properly, for analytics and for marketing. You choose what you allow. Read more in our privacy policy.
