Custom Klippa integration development
Appfront builds integrations with Klippa, which now continues under the name Doxis. The platform reads documents such as invoices, receipts and identity documents, and returns the data via an API. We make sure those documents are submitted from your process, that the data lands in your own system, and that a member of staff only looks where the recognition is uncertain.
What is a Klippa integration?
Klippa is a Dutch company that makes software for automatically reading and processing documents, and now continues under the name Doxis. The document processing platform, formerly DocHorizon, recognises documents such as invoices, receipts and identity documents, extracts the data and returns it via an API. There is also a product for invoices, expense claims and business payment cards.
An API that reads documents is only useful if the documents reach it automatically and the data ends up where it belongs without manual work. Without an integration, documents are uploaded by hand, and the extracted data is copied into your accounts or your own application. A reading that isn't certain goes unnoticed, and an error only surfaces during review.
We build custom software because processes differ: which documents, where they arrive, which data you need, which checks you want, and which system they should land in. What the platform can do, and under which conditions, is set out in the documentation from Klippa and Doxis; we build the connection to your process.
From document to data
Documents read from email, upload or scan, with the data sent straight into your system.
Review when in doubt
An employee only looks where recognition is uncertain or a line doesn't add up.
Multiple document types
Invoices, receipts, identity documents and other documents in the same process.
How we build your Klippa integration
We start with your documents: which types, how many, where they come in, and which data you need. We then define when recognition is reliable enough to proceed, and when an employee should check. We set that threshold based on real documents, so that review happens where it is needed.
Your document types, volumes, channels and the data you need.
Documents sent to the API, and data returned to your system.
Confidence thresholds, rules, and a review screen for uncertain cases.
Go-live, monitoring, and maintenance when the platform changes.
What a Klippa integration actually does
The components below feature in almost every Klippa integration. Which ones you need depends on your documents.
Submitting
Documents sent to the API from email, upload or scan.
Reading out
Data returned as structured fields.
Confidence
Uncertain cases set aside.
Lines
Checks you define, such as VAT and totals.
Review screen
Document and data side by side.
Processing
Data passed to accounts, ERP or application.
Who we build Klippa integrations for
The integration is designed for organisations that process large volumes of documents.
Accounts payable
Many purchase invoices. Posting is the core.
Accountancy firms
Receipts from many clients. Checking matters most.
Client onboarding
Identity documents at sign-up. The reliability is what counts.
Software suppliers
Recognition within your own product. The API is the core.
Technology and integrations
This page covers integrations with Klippa. For custom document recognition, see our page on AI document extraction and OCR; for staff expenses, our page on an expense claims app; and for electronic invoices, our page on a UBL integration. You can read about how we work under custom software development.
If you work in the financial sector with Hyarchis, see our page on a Hyarchis integration.
Why Appfront for your Klippa integration?
A document that is read but whose data is then retyped is only half automated. That is what we build on: documents that arrive automatically, data that flows through by itself, and human review where it is needed.
Less manual work
Only uncertain cases need attention.
Fewer errors
Rules checked before posting.
Scalable
More documents, fewer people.
Security and privacy in a Klippa integration
The integration processes documents containing financial data and sometimes personal data, such as identity documents. Documents are only sent for the purpose they are needed for, connections are encrypted, and access to the review screen is set by role.
The integration runs in a European data centre or in your own environment, with encrypted storage and daily backups. You decide how long documents are retained.
Frequently asked questions about a Klippa integration
Questions organisations ask before they get started.
Klippa is a Dutch company that makes software for automatically reading and processing documents, and it now operates under the name Doxis. The platform reads invoices, receipts and identity documents, among others, and returns the data via an API.
Klippa has been renamed Doxis. The document processing platform that was called DocHorizon is now called Doxis AI.dp. For an integration, the name change makes little difference; we work with the API and documentation as they currently stand.
Invoices, receipts and identity documents, among others, plus other documents the platform supports. In the first step, we test with real examples to establish which are suitable for your process.
The document then goes to a review screen, with the document and the extracted data side by side. A team member corrects or approves it, and processing continues. You set where the threshold lies. Initially it is often set cautiously, and it moves as it becomes clear that recognition works well for your documents.
Yes. For example, whether the VAT matches the total, whether the supplier is known, or whether an invoice has already been booked. A document that fails a check goes to the review screen.
In the system where you need them: your accounts, your ERP, or your own application. We integrate with the system you use, provided it has an interface.
Check that first. Many accounting packages already read in invoices, and that is enough for standard purchase invoices. A custom integration makes sense if you process other documents, want your own checks, or want document recognition inside your own product.
Documents that turn into data automatically?
Tell us which documents you process, how many there are, and which system the data needs to land in. We will show you what the integration would look like.