Skip to content

Scanning

Review and correct

An analysis unfolds in front of you, proposes a result, and waits for your approval. Here is what happens between dropping the file and the saved record.

Updated on August 14, 2026

How an analysis unfolds

Progress is shown live, step by step, on the web and on mobile.

  1. 1

    Reading the document

    The file is fetched and turned into usable text, page after page.

  2. 2

    Extracting the data

    The information expected for this kind of document is identified and structured.

  3. 3

    Matching

    React Box tries to link what it read to what you already have: the supplier or payer in your third parties, the bank account in your cash section, the allocation accounts in your chart of accounts.

  4. 4

    Handing back

    The form opens pre-filled, with a confidence score on the extraction as a whole.

Tip

You can leave the page while the analysis runs: it carries on server-side and the result waits for you. A progress pill follows you around the app.

The review is yours

No record is saved on the strength of the analysis alone. Every recognised field stays open to correction, and doubtful values are the first to check: a total that does not match the sum of the lines, a due date earlier than the issue date, a supplier your directory has never seen. Correcting before validating takes seconds; correcting afterwards means reopening the record.

Warning

Artificial intelligence can be wrong, and confidently so. Treat the result as a draft entry, never as a source of truth.

Matching against your data

What React Box tries to link on its own, and what it leaves for you to decide.

  • The third party — a supplier recognised by its tax identifier or its name is attached to your directory; otherwise you are offered to create it from what was read.
  • The bank account — a statement is attached to the account whose IBAN matches; when in doubt, you pick the account yourself.
  • The ledger allocation — suggestions build on your past allocations, first those for the same supplier, then those across the whole organization.
  • The payer on a receipt — matched to your third parties when the name lines up, left free otherwise.

When it fails

A failed analysis is never a lost document.

  • Retry — useful after replacing a photo with a sharper scan, or after a passing incident.
  • Enter it by hand — every form remains usable without going through the scan.
  • The file stays attached — a reading failure erases nothing and never blocks saving the record.
  • Too many analyses in a row — launches are capped per organization. During a bulk import, wait a few minutes before resuming.

The credit it consumes

Every analysis is charged against your Atlas credit, in proportion to the volume processed. The breakdown by kind of processing — purchase invoices, receipts, statements — is available in your organization settings for the current cycle. Unused credit rolls over from one month to the next.

Note

If the credit runs out, analyses pause until the next top-up. All manual entry stays available: the product does not stop, only the automated assistance does.