Skip to main content

Overview

Zeno CY is a quiet workspace for the document layer of accounting. It receives photos, scans, PDFs and email attachments, reads them locally on your device, and prepares clean records ready for your existing accounting software — without replacing it.

This page is a guided tour of what each screen does and how they fit together during a pilot rollout. Spend five minutes here before you click through the app for the first time.

What Zeno CY is — and is not​

It is a document-processing workspace. It accepts source files in any common shape, extracts the structured fields your bookkeeper needs (counterparty, totals, VAT, dates, line items), and keeps a clean register of what has been reviewed and accepted.

It is not an accounting program. It does not replace your bookkeeping system, your audit firm, or your accountant. It clears the document layer so the work that does require human judgment happens cleanly.

The screens you will use​

Documents​

The intake surface. You point Zeno at a folder (a local one, or a Google Drive connector), drop documents in, and watch the preview open with extracted fields. From the preview you decide what happens next: register, mark reviewed, exclude, or send back for accuracy review.

Registry​

The validated ledger. Once a document is registered it shows here with lifecycle state, VAT validation status, and links back to the source. The registry is the single source of truth for downstream matching, exports, and audit.

Wallets​

Optional. If your engagement covers blockchain wallet activity, you declare which addresses are in scope here. Zeno only stores public metadata — never private keys.

Transactions​

The wallet ledger view. Shows wallet transactions and their match status against documents in the Registry. Matching is assistive only — final acceptance always stays manual.

Billing​

Plans, usage limits, credits, invoices, and your workspace VAT profile. The screen most people only visit when they need to upgrade or to update VAT details.

Audit Log​

An immutable record of who did what, when. Built for compliance and audit reviewers — full transparency without anyone having to reconstruct the history later.

Settings​

Profile, team access, role configuration, and workspace-level VAT controls. Owner-only invites.

Who uses each screen​

A typical pilot involves three kinds of people:

  • Owner / Admin sets up the workspace, picks the storage source, and invites the rest of the team. Lives mostly in Settings and Billing.
  • Accountant runs the day-to-day flow. Lives mostly in Documents, Registry, and (where applicable) Transactions.
  • Auditor or Compliance reviewer is read-mostly. Lives in Audit Log and Registry.

You can be all three at once. Many pilot users start that way.

Core principles​

Four ideas shape every screen in the product. They are worth knowing because they explain why certain things require an extra click that other tools skip.

  • No silent auto-confirmation. Documents never enter the Registry until a human says so. Suggestions are suggestions.
  • Least-privilege access. Each role sees what it needs and nothing else.
  • Consent-first connectors. Google Drive and similar integrations only act after explicit consent.
  • Review-first data acceptance. A document is parsed automatically but registered manually.

These four together explain the product's pace. It is slower than a hands-off automation tool by design — and faster than the manual filing it replaces.

  1. Connect a source folder — local for fully on-device pilots, Google Drive when collaboration matters.
  2. Process one document end-to-end — watch the parse, check the extracted fields, run reparse if needed.
  3. Register it into the Registry — confirm it appears in the ledger with the period you expect.
  4. Validate billing and VAT — make sure the plan covers your pilot volume and the VAT profile is set before inviting others.
  5. Verify role access — confirm the Audit role can see the audit log, and that Accountant cannot do Owner-only actions.

If steps 1 through 5 work cleanly on a real document of yours, you are ready to invite the rest of the team.

Next​