Limit set per customer
Credit limit configured per customer, per entity. Limits can be uniform or risk-tiered (gold / silver / bronze segments). Limit changes routed through approval.
Accounts Receivable | Credit Management
Per-customer credit limits set on the customer record. Live utilisation across open SOs, open invoices and open receipts. Breach blocks the next SO with a CFO override path. Exposure aging flagged per bucket. The trigger fires before despatch, not after the cheque has bounced.
How it works
Credit limit configured per customer, per entity. Limits can be uniform or risk-tiered (gold / silver / bronze segments). Limit changes routed through approval.
Available credit equals limit minus open SOs minus open invoices minus open receipts (configurable formula). Updates the moment a SO is saved or a receipt posts.
When a new SO would breach the limit, the SO save blocks with a CFO override path. The override captures reason and approver in the audit trail.
Customers with high outstanding in 90+ day buckets surface for limit review. The CFO sees concentration and aging risk on a single screen.
What the system does
| Capability | Input | Output |
|---|---|---|
| Per-customer credit limit | Customer + risk tier + limit | Limit + approval matrix |
| Live utilisation | Open SOs + invoices + receipts | Available credit, real-time |
| SO block | New SO + available credit | Allow / block / override path |
| Aging exposure | Customer outstanding by bucket | Risk flag on customer record |
| Override capture | CFO override + reason | Audit trail with approver |
| Concentration view | All customers + outstanding | CFO concentration dashboard |
Per-customer credit limit
Live utilisation
SO block
Aging exposure
Override capture
Concentration view
Compliance + integrations
The block fires at SO save, not at audit. The override leaves an audit trail. The concentration view feeds Schedule III credit risk disclosure.
Regulations we work within
Schedule III, Part I
Trade receivables aging disclosure pre-populated.
Ind-AS 109 (Expected Credit Loss)
ECL provisioning supported with portfolio analytics.
Companies Act, Rule 11(g)
Override audit trail captured.
Connects to
Credit Management FAQ
Yes. Default formula is limit minus open SOs minus open invoices minus open receipts. Configurable to include / exclude open SOs (some teams hold credit only against invoiced amounts), to include / exclude credit notes, and to include / exclude entity-specific items.
The override surfaces the breach amount, the customer's aging exposure, and the historical override pattern for that customer. CFO authorises with reason; the override is captured in the audit trail and visible on the customer record.
Yes. CRIF and CIBIL APIs are integrated. The bureau score (where available for B2B customers) feeds into the risk tier. Limit recommendations are surfaced at customer onboarding and at periodic review.
The customer aging buckets, payment behaviour and bureau scores feed into the Expected Credit Loss model. The ECL provision is computed at portfolio and customer levels per Ind-AS 109. The CA reviews the provisioning before period close.
More in Accounts Receivable
Quotes, SOs, invoices, receipts, credit limits, contacts and documents on one customer record.
See Customer 360Bank receipts auto-matched to invoices. Advances, partial payments and FX gain/loss inline.
See Receipt AllocationAutomated reminders across email, WhatsApp, call queues. Customer-history-aware tone.
See Payment Follow-upsConnect one entity, free. Configure the limit formula and the override matrix. The first SO breach surfaces the override screen, the audit trail and the concentration view.