Blog
Why reading and posting are kept apart in AI Zeny
Reading your books and writing to them carry very different risks. AI Zeny keeps them apart on purpose.
Facts reviewed on
Reading is safe to repeat
No API operation over your BUSY data changes your books. The reads are safe to repeat: a program can ask again after a timeout, and nothing is lost if it asks twice. The one exception is a named script, which may also call other systems from your PC: repeating it after a timeout may repeat what it did, so send an Idempotency-Key with it and a repeat is refused instead.
Posting is not
A voucher posted twice is a real mistake in your accounts. That is why posting is a separate step with its own rules:
- A voucher is previewed and validated before anything happens.
- It is posted only after you authorize it.
- The AI agent can draft a voucher, but never posts one by itself.
A voucher is previewed and validated, and posted only after you authorize it; the AI agent never posts one by itself. If a posting fails or its result is unclear, check in BUSY whether it was posted before you try again.
What it means for you
- Integrations that only read can run unattended.
- Anything that proposes a voucher — an order from your app, a receipt from a payment gateway — waits for a person to authorize it.
- When a posting fails or its result is unclear, the check happens in BUSY, not by trying again blindly.
More: voucher posting with your approval and authorize a voucher posting.