Check, propose, validate, export

The map, in order

Batch ingestion → reading → segmentation → extraction and evidence → deterministic controls → proposed entry → human review → export.

Banking and reconciliation are branches of the same file, not a second product. Nothing is exported until you validate.

Documents: batches, QR-bills, scans

A batch becomes named, numbered supporting documents — date, supplier, amount when those are read. A multi-page PDF is split when possible; unreadable pages stay in review.

QR-bills and difficult scans share the same queue. OCR reads; the reading detail is on the accounting OCR page.

Controls before AI

Debit / credit balance, Swiss VAT coherence and QR: numeric rules run before any remedial AI. Rates and filing: Swiss VAT page.

Human review and blocked export

For each reviewed document, Cortex suggests accounts, Swiss VAT and a label. They remain proposals, still tied to the document during review. Nothing is sold as already correct.

An incomplete line is not persisted. Without a validated file, export stays blocked. Proof levels: Controls and evidence.

Banking and reconciliation

Statements are processed in the product’s banking module. Reconciliation proposes a document ↔ statement link, often from the QR reference, still to review.

This is not a permanent bank connection, and not a second experimental engine. Matching belongs to the plans that include it.

Export to the software already in place

“Ready” is not a decorative badge: until the file is validated, export stays blocked. Formats and limits: Integrations page.

Out of scope

Cortex does not run payroll, does not issue your client invoices, and does not file with the FTA. It does not replace the fiduciary.

If you want a fully autonomous tool, this is the wrong product.

FAQ