ISC · Information Systems and Data Management · 10 practice questions
ERP Revenue Recognition: Shipment vs. Invoice Date
Recognize a sale when control transfers, not when the invoice is prepared. Below: one sale with one fact changed at a time to show what belongs in the December 31 accounts.
Try one first
Hint
Identify which system event most directly shows the company has completed its performance obligation and relinquished control of the goods.
Answer C. Because the company recognizes revenue when control transfers at shipment (FOB shipping point), the goods-issue/shipment confirmation is the direct operational evidence that performance has occurred. Triggering revenue, AR, inventory reduction, and COGS from the goods-issue event aligns timing and matching. If GL posting is batched, the system should record the goods-issue event (with the shipment date) so those entries are included in the day's batch instead of being delayed.
Why not A: Tempting because order entry is the first sales-related event and some systems allocate inventory at that time; however a sales order does not indicate transfer of control or delivery, so posting then would risk premature revenue recognition and mismatching with inventory/COGS.
Why not B: Tempting because invoicing commonly triggers AR and revenue postings, but if invoicing occurs hours after shipment it delays revenue recognition and can break matching with COGS. Since the company recognizes revenue at shipment, the invoice is a secondary document rather than the primary trigger.
Why not D: Tempting because many environments use nightly batch posting, but the batch timing itself is not the correct trigger, entries must be driven by the proper operational event (the goods-issue) and carry the proper event date. Relying solely on a generic EOD commit risks recording transactions in the wrong accounting period.
Same scenario, one fact changes
Base case
Orion sells goods for $10,000 that cost $6,000. Its ERP uses perpetual inventory. The goods ship December 31, Year 1, under FOB shipping point terms, with control transferring at shipment. Delivery occurs January 3, Year 2. Orion prepares the invoice January 2, Year 2. What should Orion recognize as of December 31, Year 1?
Answer: Recognize the sale in Year 1: debit accounts receivable $10,000; credit revenue $10,000; debit COGS $6,000; credit inventory $6,000.
Control transfers at shipment on December 31. The January invoice does not delay recognition of either revenue or COGS.
Before you open each one, predict the answer.
Change 1Change only the shipping terms to FOB destination, with control transferring on delivery.
Answer: Recognize none of the sale entries in Year 1. Recognize revenue, accounts receivable, COGS, and inventory reduction on January 3, Year 2.
Control transfers on January 3 delivery, not December 31 shipment. The goods remain Orion's inventory at year-end.
Change 2Change only the shipment date to January 2, Year 2.
Answer: Recognize none of the sale entries in Year 1. Recognize revenue, accounts receivable, COGS, and inventory reduction on January 2, Year 2.
FOB shipping point still makes shipment the trigger, but shipment now occurs after year-end.
Change 3Change only the invoice preparation date to December 28, Year 1.
Answer: Recognition remains December 31: debit accounts receivable $10,000; credit revenue $10,000; debit COGS $6,000; credit inventory $6,000.
The earlier invoice is a tempting but irrelevant date. Preparing it does not transfer control before the December 31 shipment.
Key points
- Remember: Find the control-transfer date first; the invoice date does not move it.
- Record both sides together: revenue and receivables, plus COGS and inventory reduction.
- For Orion's FOB destination version, delivery replaces shipment as the recognition trigger.
How the exam traps you
- Waiting for the January invoice to recognize the December shipment. Recognize the FOB shipping point sale on December 31, when control transfers.
- Recognizing revenue in December but waiting until January to record COGS. Recognize revenue and COGS together when control transfers.
- Using shipment as the trigger even after the terms change to FOB destination. Use the January delivery date because control transfers on delivery in that version.
Now the same facts as questions
Each question changes one fact from the one before. Watch which change flips the answer.
Question 1
Answer A. Correct. December 31 shipment transfers control and triggers both sides of the sale.
Why not B: Incorrect. Preparing the invoice later does not delay recognition.
Why not C: Incorrect. COGS and inventory reduction belong in the same period as revenue.
Why not D: Incorrect. These terms transfer control at shipment, not delivery.
Question 2
Answer C. Correct. Control transfers at January 3 delivery, after year-end.
Why not A: Incorrect. Shipment does not transfer control under the changed terms.
Why not B: Incorrect. Orion still controls the goods, so no COGS or inventory reduction is recognized.
Why not D: Incorrect. Revenue and AR are not recognized before control transfers in this scenario.
Question 3
Answer D. Correct. January 2 shipment places recognition in Year 2.
Why not A: Incorrect. The control-transfer event has not occurred by December 31.
Why not B: Incorrect. Revenue and AR cannot precede the January shipment in this scenario.
Why not C: Incorrect. Inventory remains Orion's at year-end, and no COGS is recognized.
Question 4
Answer B. Correct. FOB shipping point makes December 31 shipment the recognition trigger.
Why not A: Incorrect. Preparing an invoice does not transfer control.
Why not C: Incorrect. Delivery is not the control-transfer event under these terms.
Why not D: Incorrect. Both sides are recognized at control transfer, not on separate document dates.
Question 2
Hint
Focus on the exact system rule stated in the stem and identify the last document needed to satisfy it.
Answer A. The ERP records accounts payable only after the approved purchase order, receiving report, and vendor invoice all agree. The vendor invoice was entered on June 10, completing the three-way match, so the payable should be posted on that date. Approval of payment on June 25 relates to settlement, not initial recognition of the liability.
Why not B: Receipt of goods is necessary evidence, but without the vendor invoice the three-way match is incomplete; since the invoice wasn't entered until June 10, the payable shouldn't be recorded on June 8.
Why not C: An approved purchase order authorizes the purchase but does not confirm receipt or billing; under the stated three-way match rule it does not by itself trigger recording accounts payable.
Why not D: Approval of payment is part of the cash disbursement (settlement) process, not the trigger for initially recognizing the payable; the liability should already have been recorded when the match was completed on June 10.
Question 3
Hint
Focus on what the business needs at the moment the sales order is entered, not on general reporting or control features.
Answer B. The key factor is timeliness of processing and feedback. Online real-time processing is appropriate when the company needs immediate validation, file updates, or decision support at the point of entry (for example, checking inventory and credit before accepting an order). Batch processing is suitable when immediate results are not required and transactions can be accumulated and processed later.
Why not A: Transaction volume affects system design and performance considerations, but volume alone does not dictate online versus batch processing. The deciding factor is whether immediate results are required at entry.
Why not C: Prenumbered documents are an internal control for completeness and tracing, not a determinant of processing timing; they don't govern the choice between real-time and batch processing.
Why not D: Reporting schedules relate to when formal reports are produced, but they don't override operational needs. If the sales process requires immediate inventory and credit checks, real-time processing is appropriate regardless of external reporting timing.
Question 4
Hint
Focus on what an integrated ERP does when one transaction is used to update several modules automatically.
Answer A. In an integrated ERP, a single confirmed shipment transaction can update multiple modules (billing, A/R, inventory, and the general ledger). If shipment quantity is overstated, billing and accounts receivable will be overstated while inventory will be reduced too much. The misstatement remains until the transaction is corrected or reversed.
Why not B: This distractor appeals to candidates thinking about older, non-integrated systems that use separate departmental files. The stem, however, describes an integrated ERP where the same transaction record updates billing, A/R, inventory, and the GL, so the error would propagate beyond shipping.
Why not C: This choice relies on the assumption that invoicing is a separate manual step. The stem explicitly states that confirmed shipment automatically updates billing and accounts receivable, so the overstated shipment affects both inventory and accounting records.
Why not D: Period-end close aggregates and finalizes balances but does not automatically detect and correct incorrect source transactions. The incorrect shipment will remain until someone corrects or reverses it.
Question 5
Hint
Trace the transaction through the ERP modules in order: what entry was created at receipt, and what entry will the delayed invoice create when it finally posts?
Answer B. In this ERP design the liability is recognized when goods are received and accepted, not when the invoice later posts. Because those receipts already credited GRNI at 12/31/20X5, booking an additional top-side accrual for the same obligations would duplicate the liability. The appropriate action is to reconcile the delayed invoices to the GRNI balance and allow the AP postings to clear GRNI when they post.
Why not A: This is tempting because cut-off issues often prompt an extra accrual. However, the system already addressed cut-off by posting receipts to GRNI at year-end. A separate top-side accrual would double-count the same obligation when the ERP invoices later clear GRNI.
Why not C: This distractor appeals to the 'no invoice, no payable' intuition, but in an integrated ERP an accepted receipt commonly creates an accrued liability through GRNI. Reversing receipt entries would understate both inventory and liabilities at year-end.
Why not D: Classifying the accrual as an expense ignores that the underlying event (receipt and acceptance of goods) gave rise to a liability already recorded in GRNI. The obligation belongs in a liability clearing account, not as a new operating expense.
Question 6
Hint
Identify the event that changes the company's accounting position, not just the event that authorizes or settles the transaction.
Answer A. The company should record inventory and the related payable when it receives the goods because, under the stated facts, title passes at receipt. In an integrated ERP, the receiving event commonly triggers recognition of inventory and a corresponding accounts payable, with the vendor invoice later matched to the receiving report for payment. Purchase requisitions and purchase orders only authorize or order goods and, per the stem, do not by themselves create accounting entries.
Why not B: A purchase order is a formal request to a vendor, but the stem explicitly says purchase orders do not create accounting entries, and ordering goods does not establish receipt of inventory or the initial payable in this setup.
Why not C: A requisition initiates the internal purchase process but is only an internal authorization; it does not indicate the company has received the inventory or incurred a payable under the stated system.
Why not D: Payment approval occurs after receipt and invoice matching; waiting until payment would defer recognition of inventory and the liability and thus is incorrect for initial recording.
Common questions
Does the shipment date or invoice date determine ERP revenue recognition?
Control transfer determines recognition. For Orion's FOB shipping point sale, the December 31 shipment triggers recognition even though the invoice is prepared January 2.
What year-end entries are needed for goods shipped FOB shipping point before invoicing?
Orion debits accounts receivable and credits revenue for $10,000. It also debits COGS and credits inventory for $6,000 in Year 1.
Does preparing an invoice before shipment accelerate revenue recognition?
No. In Orion's early-invoice version, the December 28 invoice does not transfer control. Recognition still occurs at shipment on December 31.
Watch it solved
A full CPA ISC task-based simulation on Enterprise and accounting information systems, worked step by step.
ISC Simulation: Mapping Controls Through Order-to-Cash on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Enterprise and accounting information systems
- ERP Cores, Hybrid Architectures, and Best-of-Breed
- AP-to-GL Batch Recovery: Fix, Reprocess, and Reconcile
- ERP Vendor Master Data Governance: One Controlled Source
- Auditing ERP Automated Controls: ITGCs and Data Conversion
- ERP Data Residency: When Local Laws Govern Deployment
All Enterprise and accounting information systems practice →
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.