IBC Warning Signs: Cash Stress Escalation

Quick View

Why It Matters

Early signals include repeated payroll delay, statutory arrears, cheque returns, lender covenant breach, overdue critical vendors, customer advances used for unrelated costs and dependence on uncertain funding.

Management should maintain a creditor and default register with amount, due date, dispute, security, guarantee and recovery status. A disputed invoice is different from an admitted unpaid debt.

IBC rights, thresholds, procedures and amendments must be checked from the current legal framework. Directors should not assume that informal negotiation suspends a creditor’s statutory rights.

Control Framework

Action Checklist

1. Prepare a 13-week cash forecast.
2. Age creditors and statutory dues.
3. Identify security and guarantees.
4. Freeze undocumented related-party transfers.
5. Document restructuring discussions.
6. Obtain insolvency advice before critical default.

Practical Example

Evidence to Keep

• Cash-flow scenarios.
• Creditor and default register.
• Loan and covenant documents.
• Statutory-dues schedule.
• Board papers and decisions.
• Restructuring and adviser correspondence.

Warning Signs

Management Decision

Set objective escalation triggers such as days of runway, unpaid statutory amounts, covenant breaches and critical supplier stops. Trigger a board meeting automatically.

During distress, preserve records and obtain advice before asset sales, preferences, guarantees or related-party payments. Ordinary decisions can be scrutinised later.

Document the decision, owner, due date and evidence expected. A verbal explanation should be converted into a board note, approved working, contract amendment, portal acknowledgement or reconciliation before the item is treated as closed.

Rules, forms, thresholds and interpretations can change. The operating team should use the latest official source and the actual company facts instead of copying a control from another entity or prior year.

Monthly Review Test

Ask four questions: Is the obligation or accounting treatment applicable? Has the underlying transaction been completely recorded? Does the evidence agree with the books and portal? Has an independent reviewer challenged the exception?

The review should distinguish a timing difference from an error, a judgement from a missing document, and a control failure from a one-time operational delay. Repeated small exceptions deserve root-cause action because they often become material during audit, fundraising, notice or distress.

Exception Review

The operating record should connect the control stages—liquidity signal, default signal, conduct signal, governance signal—to the same transaction population. If the source list, accounting ledger, tax return, board record and management dashboard use different populations, the review can appear complete while exceptions remain outside the test.

Management should define an exception threshold, but the threshold must not hide repeated failures. A small error occurring every month can signal weak master data, unclear ownership or a broken interface. The reviewer should record root cause, immediate correction and preventive action separately.

Closure requires evidence. At minimum, the file should show who prepared the work, who reviewed it, which source documents were used, what differences remained and when the next follow-up is due. Screenshots without context or spreadsheets without source references are not a durable control record.

The review should include a cash consequence. A compliant filing, contract or accounting entry can still leave a funding gap, customer obligation or creditor exposure that management must plan for separately.

Escalation triggers should be objective: overdue days, rupee exposure, missing approval, unresolved portal mismatch, covenant breach or customer impact. Once a trigger is crossed, the item should move from routine operations to named management or board review.