Import documents brought together at a port review desk

Guide

An OCR model update should not break your invoice import

Control OCR model changes with a reviewed regression sample, a stable import contract and a recovery path before switching the live invoice flow.

Read the guide

Published

Order, delivery, acceptance and invoice records with one discrepancy

An invoice workflow can work on Monday and produce different fields on Tuesday without anyone changing the ERP. The extraction provider may update a model, move a “latest” alias or retire a version. If the import assumes yesterday's output, a model change can become an accounting exception.

The Mistral changelog, checked on 9 October 2026, records the retirement of OCR 4.0 on 30 September and directs users to OCR 4.1. It also records changes to OCR aliases. This illustrates why the model used by a business workflow needs an identified owner and a reviewed transition.

Know which part of the workflow is changing

Record the model identifier, relevant processing settings and the fields your import expects. Keep this separate from the invoice's identity and processing history. A label such as “latest” does not explain which behavior produced a reviewed result.

Identify the boundary between extraction, normalization, human correction and ERP import. If a quantity changes type, the mapping may fail even when the text on the invoice was read correctly. Do not judge the transition only by whether the API returned success.

Compare the new output with a reviewed reference

Retain an authorized test set covering your actual documents: digital PDFs, faint scans, phone photographs, long tables, credit notes and difficult references. Keep reviewed values for the fields that determine the destination entry.

In a fictional test, the previous workflow preserves invoice reference 001247 and imports quantity 12 as a number. The candidate route returns reference 1247 and quantity “12 cartons.” The reviewer must decide whether the reference lost meaningful zeros and which unit the destination expects. Neither difference should be accepted through a silent conversion.

Compare line counts, units, dates, decimals, totals and references. Include documents previously sent to human review. A new model that reads clean invoices better may still increase review work on your difficult cases.

Protect corrections already approved by people

A reprocessed invoice may contain new extracted values beside a correction already approved by finance. Preserve the correction and its source. Show the new proposal as a difference requiring review rather than overwriting the approved value.

Track each processing attempt against the same document identity. Re-extraction is not a new supplier invoice. The destination should retain its duplicate and confirmation controls even when the extraction engine changes.

For recovery behavior around spreadsheets and imports, see reliable Excel workflows.

Make the cutover recoverable

Review the results before changing the production route. Start with a bounded sample or one invoice type. Keep the previous supported route available where feasible, with clear conditions for switching back.

If the previous model has been retired, rollback cannot mean calling an unavailable service. The fallback may be a supported alternative, queued processing or human review. Agree that plan before cutover.

An uncertain processing response needs investigation before another charged attempt. An uncertain ERP response needs a destination readback before another import. Treat those two confirmations separately.

Measure the operational effect

Compare unresolved field changes, hands-on review minutes and confirmed import outcomes before and after the transition. Record sample composition and exceptions. A synthetic test does not establish a production accuracy rate or financial saving.

Your current provider or ERP connector may already support version selection and staged changes. Use those controls when they satisfy the workflow. Kaliits can scope regression review, field mapping and import recovery around an existing document flow; provider support and destination permissions still need verification.

The invoice OCR test guide covers initial acceptance. This change review applies after the workflow is already in use. For a Kaliits diagnostic, describe the current model, destination fields and the exception you cannot safely recover today.

All articles

Related reading