The AI does the work. You keep control of every consequence.

The AI prepares and suggests; you confirm anything client-facing, money-moving or fiscal. Sylatris never sends an invoice, moves money, files VAT, or posts your books on its own. Full-auto exists only if you turn on a bounded rule (e.g. auto-reminders) — and the riskiest step, a final notice, still needs your OK.

e.g. “Issue this invoice?” → one confirm. The agent's red line never changes at any delegation level.

Once an invoice is issued, its amounts can't be silently edited — the system rejects it. Corrections go through a credit note, the way an accountant would, with a guard against over-crediting. Zero silent edits to booked revenue.

e.g. Wrong amount on a sent invoice → credit note, not a quiet rewrite. Editing a non-draft invoice is blocked at the API.

When Sylatris re-reads a document and reconciles a recorded invoice, it logs what changed, from what, to what — and if the figures land in a VAT period you may already have declared, it flags it for your accountant to review.

e.g. “VAT €198 → €201.60 — 1 field reconciled. Falls in a period you may have declared.”

Recall a sent invoice to draft in one tap (the number is released, no gap), or un-mark a payment. When it genuinely can't be reversed — a registered Peppol e-invoice, or a number that's no longer the latest — Sylatris tells you why and issues a credit note. Every invoice action is logged who/what/when in an append-only trail.

e.g. Recall to draft (local) · blocked for a transmitted e-invoice → credit note. invoice_events records send/recall/paid/converted.