Skip to main content

Quickstart

A practical checklist for your first pilot session. Plan twenty minutes, one real document, and a quiet room. Follow the five steps in order — by the end you should have one document registered and a clean idea of where Zeno CY fits into your workflow.

5-step pilot setup​

1. Open Documents and connect a source folder​

Go to Documents in the left sidebar. Pick one of two intake modes:

  • Local folder — pure local-session mode. The document is processed on your device and never leaves it. Best for the first try when you want to see the full local-first behaviour in practice.
  • Google Drive folder — connector mode, with explicit consent. Best when documents arrive through a shared inbox or when more than one person needs to drop files in.

After binding, you should see the folder name on screen and at least one test invoice or receipt inside it.

2. Ingest one document and wait for parse​

Select a test document from the connected source. Most documents finish parsing in under 30 seconds locally. The preview opens with extracted fields — counterparty, totals, VAT, dates.

If the preview never appears, jump to Processing issues before doing anything else.

3. Review extracted fields and reparse if needed​

Compare each critical field against the original document inside the preview. If extraction is incomplete or wrong, reparse:

  • Reparse (Canonical Route) — the stable production extractor.
  • Reparse (ZenoLab) — experimental extractor, where enabled.

Repeat until what you see in the preview matches what your bookkeeper would accept on paper. This step is the whole point of review-first design — you are checking the work, not trusting it blind.

4. Register the reviewed document into Registry​

In the right-side actions, choose Register. If your workspace has open periods configured, pick the correct one before confirming.

Open Registry and confirm the document appears with the expected status and period. This is the moment it becomes part of your validated ledger.

5. Send mismatched fields through Accuracy Review (optional)​

For mismatches you would like the extractor to learn from system-wide, click Send to Accuracy Review in the preview. Tick the fields that came out wrong, submit, and you are done. Only structured signals are shared — raw document bytes stay with you.

Optional operational setup​

These are not blockers for a first pilot session but matter before you invite the rest of the team:

  • Invite pilot users from Settings. Owner-only.
  • Verify Billing status allows the volume you plan to process.
  • Confirm Audit Log access for whoever holds compliance / audit roles.

You are ready for pilot when…​

  • at least one document is registered in the Registry,
  • the accuracy-review flow has been tested end to end,
  • billing status allows production use for the expected volume,
  • the role matrix (Owner / Accountant / Auditor) is confirmed.

If those four are true, invite the rest of the team and start processing real documents.

When something goes wrong​