The Consignment Revenue Recognition Problem
Under ASC 606 (and its international equivalent IFRS 15), revenue is recognised when — and only when — control of the promised good transfers to the customer. For semiconductor companies using consignment models, this means:
- Chips shipped to a customer hub are not revenue until the customer withdraws them
- Replenishment orders create complex multi-element arrangements if bundled with support
- Bill-and-hold arrangements require specific criteria to be met before recognition
- Variable consideration (rebates, price protection) must be estimated and constrained
SAP S/4HANA Configuration for Consignment
In SAP S/4HANA, consignment inventory is handled through the Consignment Fill-Up (CF) and Consignment Issue (CI) process. The key revenue recognition touchpoints are:
- Revenue Accounting and Reporting (RAR) — SAP RAR must be configured to defer revenue on CF orders and trigger recognition only on CI billing. Many implementations incorrectly book revenue at CF stage.
- Performance Obligation (POB) assignment — Each contract line must map to the correct POB. For semiconductor contracts with mixed hardware, software licences, and support, this mapping is non-trivial.
- Variable consideration estimate — Price protection clauses common in semiconductor distribution must feed into the RAR constraint calculation, or you risk over-recognising revenue.
Oracle Cloud Revenue Management
In Oracle Cloud SCM, the Revenue Management module handles ASC 606 through the concept of Customer Contracts. For consignment scenarios:
- Configure the Identify Performance Obligations rule to separate consignment replenishment from point-of-sale
- Use the Standalone Selling Price allocation for multi-element arrangements
- Set up automated journal entries to move deferred revenue from the consignment liability account to recognised revenue on consumption events
Common audit finding: Revenue recognised at shipment to consignment hub rather than at customer withdrawal. This is the single most frequent ASC 606 error we see in semiconductor ERP implementations, and it is correctable without a system re-implementation if caught early.
Need Help with Your Revenue Recognition Setup?
Razetime specialises in ASC 606 and IFRS 15 IT support for semiconductor and manufacturing companies. Get in touch to discuss your SAP RAR or Oracle Revenue Management configuration.
