GST that is computed, not typed
Place of supply decides the split: same state gets CGST and SGST, different states
get IGST. It is worked out from the GSTINs on the document, recalculated on the
server when the bill is saved, and the identical arithmetic runs on every app —
held there by a shared set of test vectors, so the phone and the server cannot
quietly disagree.
Suggestions that stay suggestions
Start typing a party name and the ones you actually bill at this hour, on this
weekday, come up first. Pick one and the line items you usually raise together
follow, with quantities and your own recent prices already filled in. Every value
lands in an ordinary editable field. Nothing is committed because software guessed.
Payments that reconcile
Record part payments, and split one payment across several invoices with an explicit
amount against each. Outstanding balances follow one rule everywhere in the product,
so the figure on a report is the figure on the invoice. Overpayments are reported on
their own rather than quietly netted away.
Reports that show their working
Ageing and party balances are computed over your complete records, not over whatever
happened to be on screen. Each one states the basis it was calculated on, how many
bills it read, the date it describes and the build that produced it — so a number
can be traced back to the calculation that made it.
Credit and debit notes, properly linked
Notes are raised against the invoice they adjust and carry a statutory reason, so
the adjustment stays attached to the original for the return rather than floating
as a separate document nobody can place.
Shareable invoice links
Send a customer a link to the invoice instead of an attachment. Links can be revoked
when they should no longer work.