Covenant breach at the reporting date: current vs non-current classification
Ganiyu Foods Limited, a Lagos-based FMCG distributor, has a 400 million Naira term loan from a Nigerian bank, drawn in 2024 and contractually repayable in 2029. The facility has a debt-service-coverage covenant tested every 31 December. At 31 December 2025 the covenant is breached. On 20 January 2026, before the financial statements are authorised for issue, the bank issues a waiver letter.
Facts
- Term loan principal
- ₦400,000,000
- Contractual maturity
- 2029
- Covenant test date
- 31 December (annually)
- Covenant status at 31 December 2025
- Breached
- Waiver date
- 20 January 2026 (after reporting date, before authorisation)
Workings
At the reporting date (31 December 2025) Ganiyu Foods did not have the right to defer settlement for at least 12 months: the breach gave the bank the right to demand repayment. The waiver came after the reporting date, so it does not restore non-current classification. Presentation at 31 December 2025: borrowings of 400,000,000 Naira within current liabilities; nil within non-current borrowings. Disclose the breach, the classification consequence, and the post-year-end waiver as a non-adjusting event under IAS 10. Contrast case: if the covenant were tested only at 30 June each year (after the reporting date), the loan would remain non-current at 31 December 2025 under the 2024 amendments, but the company would disclose the covenant terms and the risk that the loan could become repayable within 12 months if the June test is failed. The knock-on effect is real: reclassifying 400 million Naira to current liabilities could push the current ratio from about 1.4 to about 0.8, potentially triggering cross-default clauses in other facilities. This is why liability classification review must happen before year-end, while there is still time to obtain waivers. No journal entry is required: reclassification between non-current and current is a presentation change only.
