Everyone wants to build the AI feature. Nobody wants to build billing. But for a B2B platform serving Thai care facilities, billing is exactly where trust is won — or quietly lost — long before anyone admires the clever model underneath.
CloudNurse charges real money to real facilities every month, in a market with very specific paperwork expectations. Here's what designing that billing taught me.
01 Billing is a trust surface
A facility decides whether it can rely on you partly by whether your invoice arrives correct, on time, and ready to hand straight to their accountant. A clean bill is invisible; a wrong tax invoice is remembered for months. Before billing is a revenue mechanism, it's a credibility signal — so it deserves the same care as anything clinical.
02 The four documents are not optional
Thai B2B billing runs on a specific paper trail, and the customer's bookkeeper — and the Revenue Department — expect every step:
Each document has a distinct legal and accounting role. Skip one, or mash two together to "simplify," and you haven't saved effort — you've created work for the customer's finance team. And work for the customer is the quietest form of churn.
03 Care is a subscription with surprises
Model both sides. There's the recurring base — monthly care fees, software seats — and a long tail of à la carte items: extra supplies, one-off assessments, ad-hoc services a resident needed this month. Real-world billing isn't a flat subscription; it's a stable base plus a stream of small, legitimate extras that all have to land on the right invoice.
04 Meet payers where they pay
In Thailand that means PromptPay QR and bank transfer first, cards a distant third. We wire PromptPay and Beam in directly, so a finance officer can settle an invoice from her phone in seconds. Every extra step between "I'll pay this" and "paid" is a step you later chase in your receivables report.
05 Tax is a first-class feature
VAT, withholding tax, correct buyer and seller fields, running document numbers that never collide. Get one field wrong and you haven't just made a typo — you've handed the customer's accountant a problem to untangle. Tax logic belongs in the core of the billing engine, designed in from the start, not bolted on the week before launch.
06 Reconciliation is the real product
The unglamorous heart of billing is matching money to documents: linking each incoming payment to the right invoice, flagging partial and over-payments, and closing the loop automatically. It's the part nobody demos and everybody depends on. Most of the value of a billing system lives in this quiet plumbing.
07 Margin you can actually see
Tie billing back to inventory and cost, so the business can read margin per resident, per service, per facility — not just top-line revenue. Revenue without cost visibility is a vanity number; margin is something you can make a decision with. Billing data is some of the richest signal a company has, if you let it talk to the rest of the system.
08 Idempotency and audit, again
Never double-charge. Never silently drop a charge. Log every document and every change, with who did what and when. It's the same discipline I apply to the clinical AI, for the same reason: in anything that touches money or medicine, "probably fine" is not a specification.
Build billing this way and it stops being the boring tax you pay for shipping software. It becomes one more place — alongside the charting and the family updates — where the platform quietly earns a facility's trust, one correct invoice at a time.