Home › Invoicing
Invoices computed by code, issued by you
Money is arithmetic, not prose. Invoice totals, taxes and dates are computed deterministically; the model may describe an invoice, but it never calculates one. Issuing is an external action with its own approval.
Every account starts with a five-day trial. No card to start; prices are on the pricing page.
The invoice lifecycle
Draft
Lines, quantities, unit prices, tax and currency; totals are computed and re-checked on every change.
Issue
An external action: previewed, approved, then issued — with a PDF generated from the stored invoice, not from a template a model filled in.
Paid or void
State changes recorded with who and when; a void keeps the record.
Documents
Each issued invoice has a PDF in Documents. Generating other office documents — DOCX and XLSX from company data — is the same deterministic path.
Payments
Taking a payment or issuing a refund are financial actions with a financial approval level and per-plan limits. Authorising and verifying a Stripe account exists; the financial actions themselves are not available yet, and AOFON refuses them by name rather than guessing or simulating execution.
Questions people ask
Can the Assistant change an invoice total?
No. Totals are computed from lines by code; the Assistant can propose a line change, which is previewed and recomputed.