Documents read and turned into data in your system Review where the recognition is unsure Invoices, receipts and ID documents

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 ID documents, and returns the data via an API. We make sure those documents are submitted from your process, that the data ends up in your own system, and that an employee only looks where the recognition is unsure.

What is a Klippa integration?

Klippa is a Dutch company that makes software for automatically reading and processing documents, and now operates under the name Doxis. Its document processing platform, formerly DocHorizon, recognises documents such as invoices, receipts and ID documents, extracts the data and returns it via an API. It also offers a product for invoices, expense claims and business payment cards.

An API that reads documents is only useful if the documents get there automatically and the data ends up in the right place automatically. Without an integration, documents are uploaded by hand, and the extracted data is copied into the accounting system or your own application. Uncertain recognition goes unnoticed, and an error only comes to light during review.

We build custom solutions because processes differ: which documents, where they arrive, which data you need, which checks you want, and which system they need to end up in. What the platform offers, and under which conditions, is set out in the Klippa and Doxis documentation; we build the connection to your process.

From document to data

Documents read from email, upload or scan, with the data going straight into your system.

Review when in doubt

A team member only looks where the recognition is uncertain or a line doesn't add up.

Multiple document types

Invoices, receipts, ID 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 arrive, and which data you need. Then we define when a recognition is good enough to proceed, and when a team member needs to take a look. We fine-tune that threshold using real documents, so review goes where it's needed.

1
Mapping your documents

Your document types, volumes, channels and the data you need.

2
Building the integration

Documents to the API, and data back to your system.

3
Review and rules

Confidence thresholds, rules, and a review screen for doubtful cases.

4
Go-live and maintenance

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.

Submission

Documents from email, upload or scan to the API.

Retrieval

Data returned as structured fields.

Confidence

Doubtful cases set aside.

Lines

Checks you define, such as VAT and totals.

Review screen

Document and data side by side.

Processing

Data to your accounting system, ERP or application.

Who we build a Klippa integration for

The integration is intended for organisations that process a lot of documents.

Accounts payable

Large volumes of purchase invoices. Posting is the core.

Accountancy firms

Receipts from many clients. Review matters most.

Customer onboarding

ID documents at sign-up. Confidence is what's needed.

Software suppliers

Recognition in your own product. The API is the core.

Technology and integrations

This page is about integrations with Klippa. For custom document recognition, see our page on AI document extraction and OCR, for employee expenses our page on an expense claims app, and for electronic invoices our page on a UBL integration. You can read about our approach on building software.

If you work in the financial sector with Hyarchis, see our page on a Hyarchis integration.

Klippa and Doxis Document processing API Invoices and receipts ID documents Structured data Confidence per field Custom validation rules Review screen Integration with accounting or ERP Audit log per document

Why Appfront for your Klippa integration?

A document that is read but whose data is retyped is only half automated. That's what we build on: documents that are submitted automatically, data that lands automatically, and review where it's needed.

Less manual work

Only doubtful cases need attention.

Fewer errors

Rules are checked before posting.

Scalable

More documents without more people.

Security and privacy in a Klippa integration

The integration processes documents containing financial data and sometimes personal data, such as proof of identity. Documents are only sent for the purpose for which they are needed, connections are encrypted, and access to the review screen is set up per 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 now operates under the name Doxis. Among other things, the platform reads invoices, receipts and ID documents, and returns the data through an API.

Klippa has changed its name to Doxis. The document processing platform that was called DocHorizon is now called Doxis AI.dp. For an integration, the name makes little difference; we work with the API and documentation as they currently stand.

Among others, invoices, receipts and ID documents, plus other documents the platform supports. Which ones suit your process, we test in the first step using real examples.

The document goes to a review screen, with the document and the extracted data side by side. A team member corrects or approves it, and then it moves on. You set where the threshold lies. At the start it is often set cautiously, and it shifts as it becomes clear that the 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 it: your accounting software, 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 ordinary purchase invoices. A custom integration makes sense if you process other documents, want your own checks, or want document recognition in your own product.

Documents that turn into data on their own?

Tell us which documents you process, how many there are and which system the data needs to end up in. We'll show you what the integration looks like.

Edit content