THE PROCESS AT A GLANCE
From email to a case ready for review
Data, checks and decisions remain linked to the source document.

- CaptureRetain the invoice and propose the useful fields.
- CheckIdentify duplicates, missing references and discrepancies.
- Review and importAssign exceptions to an owner and record the transfer.
Manual invoice entry costs more than the minutes spent typing. Someone opens the attachment, identifies the supplier, copies references, searches for the purchase order, corrects the import and checks whether the same invoice arrived yesterday. Faster extraction helps only if it reduces that complete sequence.
For a finance or administration manager, the useful goal is supplier invoice processing with fewer repeated touches and a clear exception path. Kaliits uses OCRAgent as the document-processing core, then scopes the intake, validation and accounting handoff around your existing tools.
Find the repeated work before choosing a tool
Follow one invoice from arrival to a confirmed accounting record. Write down the fields entered, systems opened and reasons for returning to the document. Separate hands-on minutes from waiting for a missing receipt or approval.
If your software already accepts a reliable supplier import, structured invoice or native capture flow, test that first. A custom workflow earns its place when inconsistent documents or disconnected handoffs leave repeated work that those features cannot handle.
What OCRAgent does, and what Kaliits connects
OCRAgent extracts invoice information from changing supplier layouts. Its invoice reconciliation code can compare extracted lines with purchase-order and goods-receipt records, showing price or received-quantity differences. Its dossier workflow keeps extracted facts with source-page evidence for review.
Your implementation still needs a confirmed supplier lookup, required accounting fields, duplicate policy and a supported destination. Email intake and an ERP connector are scoped integration work. Reading a PDF does not establish that a record reached your software.
The practical sequence is: receive and identify the source, extract candidate fields, check references and arithmetic, show uncertain values, obtain the required decision, then import and confirm the destination record. A retry must retrieve or complete the same intended transaction rather than create another one.
A real case: Autohaus Frisch, Michelin and one exception in an order of 20
Kaliits worked on a real Autohaus Frisch case involving Michelin: 20 items were ordered, with one damaged or missing. This is a real case background, confirmed by Mehdi Kourchal on 4 October 2026, rather than an invented purchasing scenario.
The control question is precise: how does that one-item exception affect the evidence finance needs? A missing item and a damaged item require different receiving records. Keep the order, receipt or acceptance evidence and invoice together so the responsible team can establish the correct action.
OCRAgent's invoice comparison can surface a billed-versus-received difference when the reference records and line match are correct. Inspection acceptance and the handling of the exception must follow the agreed controls. No actual unit price, billed quantity, final supplier resolution or measured saving has been provided for this case, so no financial recovery is attached to it.
What the client examples actually establish
At Wawa Creative, Mehdi Kourchal reports 98% less time preparing product details from images and inserting listings into WooCommerce. That is relevant experience in moving unstructured information into a destination system. It is not a supplier-invoice saving.
At Smatch, his reported workflow result was response coverage: every lead in the described flow received a response. It illustrates why intake needs an owned next action. It does not establish invoice processing speed or financial ROI. Read the project scopes.
Measure the whole invoice, including exceptions
Illustrative calculation: 500 invoices per month at eight hands-on minutes each use 66.7 hours. If a pilot averages three minutes including checking, correction and failed-import recovery, it releases 41.7 hours. The reduction is 62.5% under those assumptions, not a Kaliits result or forecast.
Value that capacity using your own loaded labour cost, then subtract recurring processing, support and implementation costs. Reassigned staff time is capacity released; it is cash saved only if expenditure actually falls. Use the pilot measurement guide.
Start with one supplier family and one destination
First map the current steps and baseline. Then test normal invoices, weak scans, duplicates and missing references without posting. Next validate the import and retry behaviour with a named reviewer. Expand only after the agreed fields, controls and time measure pass.
If retyping is the main problem, review the systems integration offer. If invoices are blocked by receipt differences, review purchasing mismatch control.
Map my supplier invoice workflow. In your enquiry, describe the source, accounting software, approximate monthly volume and the step that consumes the most time. Start with a description; document sharing can follow through an agreed channel.

