Order-to-Cash Controls: Invoice, Collection, Credit Note and Bad Debt
Connect contract, delivery, invoicing, collection, credit notes and provisioning in one controlled revenue cycle.
Growth can hide a weak revenue cycle. Sales books a contract, operations delivers, finance invoices, and collections follows up—but no one owns the hand-offs. The result is unbilled revenue, disputed invoices, surprise credit notes and receivables that were never collectible.
Billing terms should be extracted before revenue or invoices are created.
Recognition, GST invoice and collection can follow different triggers.
They require commercial approval and GST/accounting treatment.
An old receivable is a risk signal, not just a collection report.
1. The operating framework
| Stage | Control | Key output |
|---|---|---|
| Customer onboarding | Legal/KYC, credit limit, tax status and contracting entity. | Approved customer master and credit decision. |
| Contract setup | Price, tax, milestone, acceptance, renewal, refund and termination extraction. | Billing and revenue memo. |
| Delivery | Evidence of goods dispatch, service performance or customer acceptance. | Milestone/dispatch record. |
| Invoice | Sequential invoice, GST fields, e-invoice applicability and contract tie-out. | Invoice and portal acknowledgement where applicable. |
| Collection | Due-date diary, allocation, deduction/dispute tracking. | Cash application and collection notes. |
| Credit note/bad debt | Independent approval, root cause, GST treatment and provisioning/write-off. | Approved note, ledger entry and recovery decision. |
2. CFO playbook
- Approve customer credit before the first non-refundable commitment.
- Convert every signed contract into a billing schedule and revenue-accounting memo.
- Separate invoice creation from credit-note approval.
- Track unbilled, billed-not-due, overdue, disputed and legally escalated amounts separately.
- Reconcile GST/e-invoice data to revenue and credit notes.
- Run weekly cash-application and unidentified-receipt review.
- Use ageing, dispute status and customer condition for expected-loss/provisioning; Board-approved write-off does not erase recovery rights unless legally settled.
3. Practical example
A SaaS contract is signed for ₹24 lakh annually, payable quarterly, with customer acceptance after implementation. Sales records the full value, but finance should distinguish contract value, revenue recognition, GST invoice timing and collection milestones. Acceptance evidence may be the key control for both revenue and billing.
4. Common failure points
- Billing from a sales email rather than the executed contract.
- Recognising revenue merely because an invoice was raised.
- Using credit notes to hide pricing disputes without root-cause analysis.
- Showing unapplied cash as customer advances for months.
- Writing off debt without legal/tax/GST review.
5. Evidence folder
- Customer KYC and credit approval
- Executed contract and term extraction
- Delivery/acceptance evidence
- Invoice/e-invoice file
- Collection and dispute log
- Credit-note approval
- Provision/write-off and recovery file
6. Finin2min takeaway
Design the evidence before the transaction.
Reliable compliance is the result of clear ownership, timely action, reconciled records and a documented escalation route—not a last-minute filing exercise.