Invoice completeness is a financial assertion, not a report from the vendor
If the billing application is the book of original entry for subscriptions, completeness testing has to start in that application — not in the ledger summary it posts.
Insights
Notes from the file, not product commentary.
Short pieces on the evidence we actually ask for when a subscription biller’s application is treated as a financial record.
What actually happens when a subscriber changes plan mid-term
Proration rules are buried in product settings. Finance teams often learn the rule from a disputed invoice rather than from the accounting policy.
Usage-based billing under MFRS 15: estimates, constraints, and the invoice that arrives later
In-arrears usage invoices are easy to book. The hard part is the unbilled amount at period-end, and whether it should have been constrained.
Credit notes that never reach the ledger
Some billing applications can cancel an invoice in place. If the ERP only received the original charge, receivables and revenue are both overstated.
SST coding on recurring charges in Malaysian billing applications
A product marked “software, overseas, no SST” will bill that way forever. Recurring charges inherit the first person’s tax decision.