Ready-to-export accounting file: documents, entries and export together

The result is not just an entry: it is an accounting file ready to send, export or keep on your side.

An incomplete file costs time

Exported entries without structured documents, or documents without linked entries, is not a ready file. At quarter-end, rebuilding the document ↔ entry link or preparing a ZIP for the fiduciary becomes urgent. Concretely: entries exported but documents still in clutter, no coherent ZIP to send to fiduciary, document numbering misaligned with accounting exports, a file to rebuild before review or archiving, isolated export without document context. Example: the Alpine Menuiserie SA demo scenario ends with a Crésus export and a ZIP of numbered documents (01_2026-01-15_Swisscom_….pdf, 03_2026-02-03_Aligro_….pdf…) — a file ready to import into your ERP or send to your fiduciary, to download and archive on your side before server purge (~48h).

What "ready file" means with Cortex

1. Structured documents — Supporting documents separated, renamed and numbered — aligned with export numbering.
2. Entries validated by you — Proposed and checked entries, reviewed and validated before export.
3. Export to your tools — Native export to Crésus, WinBiz, Abacus, Sage, Banana or CSV/Excel formats per your software.
4. Document ZIP — ZIP archive of renamed, numbered PDF documents — ready to send or keep on your side.
5. Send to fiduciary — One coherent file per mandate: documents + entries + export — not scattered files.

What Cortex does not claim to do

• No 10-year storage at Cortex — Cortex purges sources within ~48h. Archive ZIP and export on your side per your obligations.
• Not universal export — Cortex exports to supported formats (Crésus, WinBiz, Abacus, etc.) — not every software on the market.
• Not an ERP replacement — Cortex prepares the file upstream. Your accounting software remains the reference tool.
• No machine-stamped ready file — The ready file is the result of your validation — Cortex organizes and proposes, you validate.

Use cases

• SME — Reduce sorting and manual re-entry on document clutter while keeping entry validation.
• Fiduciary — Receive structured client files (numbered documents, proposed entries) without changing ERP.
• Freelancer — Upload supporting documents, validate proposals, export to your usual software.

Swiss practical cases — delivering a complete file

Demo scenario: Alpine quarterly close → Crésus + ZIP

Demo scenario: Alpine Menuiserie SA produces a Crésus export and a ZIP (01_2026-01-15_Swisscom_….pdf, 03_2026-02-03_Aligro_….pdf…). The file is ready to import or send after you validate the entries.

Fiduciary delivery (Zurich) — one mandate, one ZIP

Instead of a messy Drive folder, the fiduciary receives numbered documents plus an aligned entry file. It keeps the ERP and responsibility; Cortex only organizes the upstream work.

Self-employed professional (Ticino) — NAS archive before purge

After a Banana or CSV export, the user downloads the ZIP and archives it on a NAS. Cortex purges source PDFs within ~48h — legal retention remains on the user’s side.

Incomplete file vs ready file

Contents of a Cortex ready file

Where to go by intent

Ready file ≠ machine-validated file

• Result of your validation — A ready file combines pillars 1 and 2: structured documents plus entries you validated. Cortex does not apply an “automatically validated” status.
• Your ERP stays in place — Crésus, WinBiz, Abacus, Sage and Banana remain your reference tools. Cortex supplies exports — it does not replace the ERP.
• Retention on your side — For archiving obligations, often 10 years in Switzerland, retain the ZIP and export outside Cortex. The product purges source PDFs quickly.

FAQ — ready-to-export accounting file

See a file ready to deliver

Explore the Alpine file demo · Product frame: Organised Accounting