Duplicate detection: no document is booked twice

Kontevia checks every incoming document against those already processed. It recognises the same invoice or receipt even when it arrived once as a photo on WhatsApp and once as a PDF by e-mail. A suspected duplicate is flagged and the decision is left to you.

Kontevia
online

invoice_hosting_08.pdf

184 KB, PDF

11:20

Invoice processed: 3 line items, net €1,200, VAT 19 % €228, total €1,428. Not a duplicate. Category: software and hosting. Due in 14 days.

11:20

How it works

1

The document arrives by any channel

WhatsApp, e-mail or upload in the dashboard. The check runs across all channels together.

2

Comparison with existing documents

The new document is compared with those already processed. It does not matter whether it is a photo, a PDF or a screenshot.

3

Flagging the suspect

A possible duplicate is visibly flagged. Nothing is discarded or booked in silence.

4

The decision is yours

With one click you confirm the duplicate (the document is excluded) or mark it as a new document, for example for two identical purchases in a row.

Why duplicates are treacherous

A duplicate document is not carelessness, it is a natural consequence of how documents circulate. A supplier sends an invoice by e-mail and a week later sends it again as a reminder. A business owner photographs a receipt at the till and sends it again in the evening to be safe. A client hands the accountant a folder half full of documents already sent along the way.

The consequences are not cosmetic: an expense booked twice means overstated costs, a wrong VAT deduction and, in an audit, an assessment with penalties. And watching for duplicates by hand is exactly the kind of work in which a person makes mistakes after hundreds of documents and a machine does not.

A check that requires no discipline

The key property of a good duplicate check is that it does not rely on the sender's behaviour. Clients do not have to think about whether they have already sent a document, or by which channel. The system compares the documents themselves, so it catches the same receipt regardless of the form and channel it arrived in the second time.

The second key property is that a person has the last word. Two legitimate identical purchases in a row (two identical coffees, two identical tanks of fuel) look like a duplicate but are not. That is why a suspected document is never discarded automatically; it is flagged and waits for confirmation.

Typical situations the check catches

SituationWhat happens
The same invoice arrived by e-mail twiceThe second one is flagged as a possible duplicate
A receipt as a photo on WhatsApp and as a PDF by e-mailThe system recognises the same document across channels
A client handed over a folder with documents already sentDuplicates are flagged, new ones go through
Two genuine identical purchases in a rowFlagged for review, one click confirms both

Frequently asked questions

How does Kontevia recognise a duplicate?

It compares the documents themselves, not the files. It therefore catches the same invoice even when it arrived once as a photo and once as a PDF by a different channel. The suspected document is flagged and the decision stays with the user.

Can the check delete a document by mistake?

No. The check never deletes or discards anything automatically. A possible duplicate is only visibly flagged and waits for your confirmation; only then is it excluded.

What if I really have two identical purchases?

Two identical documents in a row (for example two identical fuel purchases) are flagged for review. With one click you confirm them as two separate documents and both are booked normally.

Does the check work for accountants with several companies?

Yes. The check runs within each company separately, so the same document in two different companies is correctly not treated as a duplicate, while a double submission within one company is caught.

Try it on your own documents

Send a few documents and see the extraction, categories and VAT for yourself. Free trial, no card needed.

Updated 7 September 2026