Two Requests Before the Covenant Test
You are the newly appointed financial accountant at Halcyon Foods, a private company whose year end is 30 June 2025. Month-end close runs on a cloud ERP system with one shared super-user login used by the finance manager, Farah, and two clerks; the audit-trail function was switched off in January because, Farah says, it slowed processing. On 28 July Farah asks you to raise a credit note for Rs 2,300,000 to a major distributor, dated 30 June, for goods she says were verbally agreed as returns. No goods have come back and the distributor's ledger shows no such claim. She also asks you to capitalise Rs 1,800,000 of routine machine servicing as a plant upgrade; the work was invoiced in June and paid in July. Draft profit before these items is Rs 6,400,000 and a bank covenant requires Rs 8,000,000. Farah adds that the external auditor never looks at small items and that your probation review is next month.
1. Evaluate the two requests against the fundamental principles of professional ethics and the relevant accounting requirements.
Read the worked answer
Request 1 – the Rs 2,300,000 credit note. There is no return of goods, no written agreement and no evidence in the distributor's records. Dating a credit note 30 June when the arrangement was raised on 28 July would backdate a transaction to reverse revenue and reduce receivables in the year under audit. This breaches integrity (recording a transaction that has not occurred), objectivity (the motive is the covenant, not the facts) and professional behaviour. Under the revenue standard, revenue is reduced when a right of return or a price concession genuinely exists; a verbal claim unsupported by the customer cannot create one.
Request 2 – capitalising Rs 1,800,000 of servicing. IAS 16 allows subsequent costs to be capitalised only when they improve the asset beyond its originally assessed standard of performance, or replace a component, and future economic benefits are probable. Routine servicing maintains the asset and is expensed as incurred. Reclassifying it overstates profit and property, plant and equipment by 1,800,000 and understates expenses.
Combined motive. The two items together add Rs 4,100,000 to profit (6,400,000 + 4,100,000 = 10,500,000), comfortably breaching the covenant threshold of 8,000,000. The pattern shows the requests are driven by the covenant, which reinforces the objectivity and integrity concerns. The probation remark is an intimidation threat and must not influence the judgement.
2. What should you do, step by step, if Farah insists on both entries? Include documentation and escalation.
Read the worked answer
Step 1 – establish the facts. Ask for the distributor's written return authorisation, the original invoice and proof of the condition of the goods for the credit note; ask for the engineer's report and invoice for the servicing to determine whether any part genuinely upgraded the machine. Record what evidence exists and what does not.
Step 2 – explain the position in writing. Set out the relevant requirement, the amount of the misstatement and the effect on the covenant in a short memo to Farah. Offer the compliant alternatives: recognise the credit note in the following year when the returns are substantiated, and expense the servicing in the period incurred.
Step 3 – refuse to process the entries. The refusal should be professional, not confrontational, and should state that you cannot record transactions without support. Do not raise the credit note 'pending documentation' and do not post a reclassification journal.
Step 4 – escalate. If Farah insists, refer the matter to the managing director or the board, and to those charged with governance or the audit committee where one exists. Provide them with the documented evidence and the quantified effect.
Step 5 – external audit. Make sure the auditor is aware of the unresolved disagreement and the covenant pressure, including the request that was refused; do not wait to be asked during fieldwork.
Step 6 – protect yourself. Keep a dated record of requests, refusals and escalations; check the company's whistleblowing policy and the professional body's guidance. The probation threat should be documented as an intimidation threat. Acquiescing to protect your job would make you a party to the misstatement.
3. Separately from the two requests, identify the control weaknesses in the ERP environment and recommend improvements.
Read the worked answer
Weaknesses identified. (1) A single shared super-user login removes individual accountability; any posting can be made without knowing who made it, and privileged access is not restricted. (2) The audit trail was switched off, so changes, deletions and journal postings have no log; this destroys the evidence trail the auditor and management rely on. (3) A finance manager can both initiate and process a credit note, so there is no segregation between authorisation and recording. (4) Credit notes appear to be raised without a document-based approval workflow. (5) Month-end close has no visible review or sign-off, so unusual journals can pass unchecked.
Recommendations. Give every user a unique account with role-based permissions and multi-factor authentication; remove the shared login immediately. Re-enable the audit trail and make it immutable, with the log reviewed monthly by someone independent of the finance function. Introduce a credit-note approval workflow requiring the customer's return authorisation, goods-receipt evidence and a second approver above a threshold. Restrict journal posting and master-data changes to named users, with a monthly review of manual journals. Apply sequential numbering to credit notes and reconcile the sequence monthly. Require documented month-end review and sign-off, and include IT general controls in the internal audit plan. Report the control failures to those charged with governance, since the integrity of the accounting records is itself a board responsibility.