In revenue recognition practice, the handling of customer invoice disputes often troubles accountants. The following scenario comes from a real consultation by a practitioner: The company calculated September revenue at approximately 500k, but on October 14, a customer disputed all related invoices (approximately 45k) through their credit card issuer. The company has submitted the signed contract and supporting evidence to the bank, and the dispute is currently under bank review. The question is: Should the 45k still be included in September revenue?

The consultant's initial judgment is that the 45k revenue should still be recognized until the dispute is finally resolved; if the company ultimately loses, then a retrospective adjustment to September revenue should be made during the subsequent quarterly or annual closing. This view reflects the principle of handling 'uncertainty' in revenue recognition—that is, when the right to collect is disputed but no final conclusion has been reached, recognized revenue should not be reduced prematurely, but rather adjusted once the outcome is clear.

Accounting Principles and Uncertainty in Revenue Recognition

Under the accrual basis, revenue should be recognized when control of goods or services is transferred to the customer, provided that the amount can be measured reliably and it is probable that economic benefits will flow to the entity. In this case, September revenue was recognized upon completion of the contract, but the dispute arising on October 14 introduces new uncertainty. The disputed amount of 45k represents 9% of total September revenue of 500k, which is material and requires careful assessment.

The key point is: Does the dispute negate the condition of 'probable inflow'? The consultant believes that until the bank review is complete, it cannot be concluded that economic benefits will not flow in, so revenue should not be reduced prematurely. This treatment aligns with the moderate application of the prudence principle—neither overstating assets nor recognizing losses prematurely due to unresolved matters.

Two Common Treatment Approaches in Practice

  • Approach One (Preferred by the Consultant): Retain revenue during the dispute period, and when the bank ruling or legal outcome is unfavorable, reduce revenue in the current period (e.g., October or a subsequent quarter) and adjust accounts receivable. If the loss occurs after the quarterly closing, it may be treated as a subsequent event adjusting the September financial statements.
  • Approach Two (More Conservative): If the dispute evidence is clearly unfavorable to the company, or the bank review may last for an extended period, the 45k should be excluded from September revenue, and an allowance for doubtful accounts or a refund liability should be recognized. However, this approach requires sufficient evidence to support that collection is 'unlikely'.

The consultant did not provide the specific reasons for the dispute (e.g., service defects, unauthorized transactions, etc.), so the strength of the evidence cannot be assessed. If the company has provided the signed contract and performance evidence, and the contract terms are clear, the bank is more likely to support the company, making revenue retention more reasonable.

Timing and Accounting Treatment of Subsequent Adjustments

If the company ultimately loses, revenue must be reversed. In this case, two situations should be distinguished:

  1. If the loss occurs before the September quarterly closing (e.g., before the end of October), then September revenue is directly adjusted, reducing it by 45k, with a corresponding reduction in accounts receivable or recognition of a refund liability.
  2. If the loss occurs after the quarterly closing (e.g., in November or later), it is typically treated as a change in accounting estimate or a subsequent event, with revenue reduced in the period of discovery (e.g., Q4), rather than retrospectively restating September statements, unless the conditions for correction of a material error are met.

The consultant mentioned 'returning to September for adjustment during quarterly or annual closing,' which aligns with the common 'rolling adjustment' practice in the field—that is, during annual closing, all unresolved disputes are uniformly reviewed and final adjustments are made. However, note that if the annual statements have already been approved for issuance, only the current period can be adjusted.

Uncertainty Regarding the Bank Review Outcome

The duration and outcome of the bank review are both uncontrollable. The consultant did not specify the expected completion time of the bank review, but credit card disputes typically have a processing cycle of 30 to 90 days. During this period, the company should continuously assess the dispute status and disclose material uncertainties in the notes to the financial statements (if the amount is material).

Additionally, if the customer has a history of multiple disputes, or the disputed amount is disproportionately high relative to their bill, this may affect the credit risk assessment of accounts receivable, and consideration should be given to recognizing additional allowance for doubtful accounts.

Conclusion and Recommendations

Overall, the consultant's initial judgment is reasonable in most cases: while the dispute is unresolved, retain the 45k in September revenue and adjust after the bank ruling. However, it is recommended that the company take the following measures:

  • Continuously track the progress of the bank review and retain all communication records and copies of evidence.
  • At quarterly closing, assess whether the dispute constitutes a matter requiring an allowance, and consult with auditors.
  • If the dispute remains unresolved before the statements are approved, disclose the contingency in the notes.

Ultimately, accounting treatment should be based on specific facts and evidence, not merely subjective judgment. If the bank review outcome is unfavorable, promptly reduce revenue and adjust related accounts to avoid affecting the accuracy of subsequent period statements.

Thank you to the consultant for raising the question, and we also welcome other experienced accounting colleagues to share their experiences in handling similar cases.