Bill-and-Hold Revenue, Capitalized Costs, and a Related-Party Lease

1. Bill-and-hold revenue. Revenue is recognized only when the performance obligation is satisfied. A bill-and-hold arrangement requires, at a minimum: a substantive reason for the arrangement, identification of the goods as belonging to the customer, the goods being ready for delivery, the inability to use the goods for other customers, and a fixed delivery schedule. None of these is present. The goods remain in Halcyon's warehouse, the distributor has no fixed delivery schedule, the distributor can return the goods, and the side letter grants price protection. Control has not transferred. The $6.0M cannot be recognized; it remains inventory, and any cash received would be a liability or customer deposit.

2. Cloud configuration costs. Under ASPE, costs can be capitalized as an intangible asset only if they meet the recognition criteria, including probable future economic benefits, identifiable asset, and control. Configuration and customization costs for a cloud arrangement often do not meet these criteria because Halcyon does not control the underlying software or obtain a separate asset. The $1.2M should be expensed unless Halcyon can demonstrate a controlled, identifiable asset with probable future benefits. Capitalizing them to improve EBITDA is not supportable.

3. Related-party consulting contract. The $0.8M contract with the CEO's brother-in-law is a related-party transaction. ASPE requires disclosure of the relationship, the amount, and the terms. Omitting it is a misstatement and a governance failure, even if the amount is commercially reasonable.

Covenant quantification.

• As proposed: EBITDA $8.0M + $2.4M = $10.4M; debt/EBITDA = $36.8M ÷ $10.4M = 3.54x (passes 4.0x)
• Correct accounting: EBITDA $8.0M; debt/EBITDA = $36.8M ÷ $8.0M = 4.60x (breach)

The covenant test therefore depends entirely on revenue that cannot be recognized. The company is in breach unless it obtains a waiver.

Ethical issues. The CEO is asking you to record revenue without a completed sale, capitalize costs that do not qualify, and conceal a related-party transaction. The stated motive is to deceive the bank. That is not an accounting judgment difference; it is a request to misstate the financial statements and breach the lender's trust. Under the CPA Code, integrity, objectivity, professional competence, confidentiality, and professional behaviour all point to refusing. The fact that "everyone does this" is irrelevant; the standard is the applicable accounting framework, not industry practice.

Steps:

1. Do not record the entries. Prepare a written memo citing the ASPE criteria and the facts. State clearly that the $6.0M revenue, the $1.2M capitalization, and the omission of the related-party disclosure are not supportable.
2. Escalate to those charged with governance. Take the matter to the audit committee or board, not just the CEO. Provide the memo, the covenant calculation, and the draft disclosure. If there is no audit committee, go to the full board or the owners.
3. Document the instruction and your response. Keep contemporaneous records of the CEO's direction and your objections. This protects you and the company.
4. Correct the related-party disclosure. Disclose the consulting contract, the relationship, the amount, and the terms. Consider whether the contract itself was approved under the company's conflict-of-interest policy.
5. Address the covenant breach. Discuss a waiver or amendment with the bank before year-end. Do not use false revenue to avoid the conversation.
6. Consider escalation outside the company. If the board ignores the issue and the financial statements are misstated, consider reporting to the appropriate regulator or professional body, after taking legal advice. Resignation may be necessary if you cannot prevent the misstatement.
7. Do not sign a false management representation letter. If the financial statements are not corrected, you cannot provide the representations the auditor will require.

Judgment: The hardest part is the power imbalance. The controller is junior to the CEO, but the professional obligation is not discretionary. The right response is to refuse, document, and escalate, not to negotiate a smaller misstatement.

Memo: Year-end accounting and covenant disclosure

Conclusion. I cannot approve the proposed $6.0M revenue recognition, the $1.2M capitalization of cloud configuration costs, or the omission of the related-party consulting contract. Each is inconsistent with ASPE and would misstate the financial statements.

Revenue. The distributor has no fixed delivery schedule, can return the goods, and has price protection. Control has not transferred, so the $6.0M is not revenue. If the goods are shipped after year-end, revenue can be recognized then. Any cash received now should be recorded as a customer deposit or liability.

Cloud costs. The $1.2M does not meet the criteria for an intangible asset because Halcyon does not control the underlying cloud software and cannot demonstrate probable future economic benefits from a separate asset. The costs should be expensed.

Related party. The $0.8M consulting contract with your brother-in-law must be disclosed, including the relationship, amount, and terms. Non-disclosure is a misstatement and a conflict-of-interest issue.

Covenant. With correct accounting, EBITDA is $8.0M and debt/EBITDA is 4.6x, above the 4.0x covenant. The proposed revenue would have shown 3.54x, but that ratio would be based on revenue that cannot be recognized. The company needs a waiver or amendment from the bank. Presenting false revenue to avoid a breach would constitute a misrepresentation and could trigger default, acceleration, and personal liability for those who directed it.

Alternatives.

• Request a covenant waiver and provide the bank with a credible FY20X5 plan.
• Negotiate an equity cure or a subordinated shareholder loan.
• Reduce costs or defer capex to improve EBITDA.
• Ship the goods on normal commercial terms in January and recognize revenue then.
• Disclose the related-party contract and obtain retrospective approval under the conflict policy.

Recommendation. Correct the statements, disclose the breach, and negotiate with the bank now. I will provide the audit committee with the supporting analysis and will not sign a management representation letter that conceals these matters.