Invoicing
Draft to sent to paid, and chasing what is not.
Suvi creates, sends, tracks and chases invoices. Most owners drive it from WhatsApp.
The lifecycle
Draft to sent to fulfilled to paid, with refunded and cancelled as terminal states. Every transition is recorded with who made it, alongside a payments ledger, so a disputed invoice has a history rather than a current status.
Totals are computed server-side. Tax is applied by rule, including GST and HSN where relevant.
Creating one
In chat: "invoice Acme for 40 hours at the usual rate". Suvi resolves the client, applies your pricing, and shows a draft. You approve and it sends.
The pricing engine is deterministic. Fixed, formula, tiered and quoted modes are supported, and the model never computes a price. It selects the rule; the rule does the arithmetic.
Templates
Invoices render through a template that reproduces your existing design. See Template Studio.
Receivables and chasing
Overdue invoices surface in a chase queue with a cash forecast based on your actual payment pace rather than stated terms.
Chase messages are drafted, not sent. Suvi shows you the queue, you approve what goes out. Tone escalates with age if you let it.
Chasing is the feature owners enable last and value most. It works because it is boring and consistent, which is exactly the part humans are bad at.