Executive Summary
Ship Confirm, the ERP transaction that marks a customer shipment as departed, is the most important inventory and financial event in a manufacturing operation's daily workflow.
A single ship confirm updates inventory, posts cost of goods sold, recognizes revenue, and advances accounts receivable. Whether the ERP is set up correctly for these postings is what decides whether the financial statements are right on the day of shipment or need correcting at period end.
What Ship Confirm Triggers in Manufacturing ERP
Confirming a shipment generates four simultaneous ERP postings.
Inventory relief
The shipped quantity is relieved from on-hand finished goods inventory. For lot-tracked shipments, the specific lot is relieved.
Cost of goods sold posting
The ERP debits Cost of Goods Sold and credits Finished Goods Inventory for the cost of the shipped items.
Revenue recognition
For FOB shipping point transactions, the ERP debits Accounts Receivable and credits Revenue at ship confirmation. Under FOB destination, revenue may be deferred until delivery is confirmed.
Accounts receivable accrual
The customer AR balance rises, representing the receivable for shipped goods not yet collected.
All four postings have to happen together and for the right amounts. Typical ship confirm errors include posting COGS at the wrong cost, recognizing revenue before the control criterion is met, and posting inventory relief to the wrong location or lot.
Cost of Goods Sold Journal Entry in Manufacturing ERP
The manufacturing ERP produces a two-part journal entry for cost of goods sold: the inventory relief entry and the COGS posting. These are always recorded together. Inventory decreases as COGS increases.
Standard cost COGS journal entry
Most common in discrete manufacturing. At ship confirm, the ERP posts at the predefined standard cost.
Example: 100 units of Item X shipped at a standard cost of $12.50 per unit.
| Account | Debit | Credit |
|---|---|---|
| Cost of Goods Sold | $1,250 | — |
| Finished Goods Inventory | — | $1,250 |
The revenue entry posts at the same time, at invoice price.
| Account | Debit | Credit |
|---|---|---|
| Accounts Receivable | Invoice price | — |
| Sales Revenue | — | Invoice price |
What happens to cost variances under standard costing
If Item X actually costs $13.20 per unit to produce, the $0.70 per unit difference posts to a manufacturing variance account, not to COGS at shipment. Variances accumulate over the period, are analyzed at close, and are generally absorbed into COGS or written to a variance expense account.
Average cost COGS journal entry
Debit Cost of Goods Sold and credit Finished Goods Inventory at the current average cost multiplied by the quantity shipped. Average cost is based on production completions, so later shipments may carry a different COGS for the same item.
FEFO lot-actual COGS
In lot-actual costing, the ERP debits COGS and credits Finished Goods Inventory for the actual cost of the specific lot that shipped. The same item shows different COGS entries between a January lot at $11.80 per unit and a March lot at $12.40 per unit. See lot and serial traceability for how that lot record is maintained.
Revenue Recognition at Ship Confirm: FOB Terms and ASC 606
Recognition of revenue at shipment is not automatic. It is contingent on the shipping terms agreed with the customer and on whether the performance obligation under ASC 606 is met at ship confirm. Most manufacturing B2B transactions recognize revenue at shipment under FOB shipping point terms, but the variations have to be matched to the ERP configuration.
- Under FOB shipping point (FOB origin), title and risk transfer when goods are handed to the carrier.
- Revenue: debit Accounts Receivable, credit Sales Revenue.
- COGS: debit Cost of Goods Sold, credit Finished Goods Inventory.
- This is the most common way US manufacturers sell to businesses.
- Title and risk transfer when goods reach the customer.
- At ship confirm, revenue and COGS do not post. Inventory moves to an in-transit account instead.
- Once delivery is confirmed, the ERP moves the inventory from in-transit through to COGS and posts revenue: debit Accounts Receivable, credit Revenue.
- The ERP must support deferred recognition for these shipments.
Drop ship: COGS without inventory relief
When a supplier ships direct to the customer, the ERP creates a debit to COGS and a credit to Accounts Payable or the GR/IR accrual when the supplier confirms shipment. No inventory account is posted, because the item never enters inventory. Revenue posts at the same time.
ASC 606 five-step model for manufacturing
Revenue is recognized as performance obligations are satisfied, typically on transfer of control. For FOB shipping point, that is usually ship confirm. Specific ASC 606 evaluation is required for bill-and-hold arrangements, customer acceptance provisions, and consignment sales.
Gross Margin Moving for Reasons Nobody Can Name?
20 minutes. Tell us your ERP, your costing method, and where the COGS postings look wrong. We will tell you whether it is configuration, lot costing, or return reversal.
Manufacturing-Specific COGS Complications at Ship Confirm
Three manufacturing-specific situations complicate the standard ship confirm COGS entry in ways generic accounting guides do not address, and that ERP configurations often get wrong.
An order for 500 units has 480 completed and 20 units in WIP. Shipping 480 and back-ordering 20 gives a clean COGS journal entry at standard cost.
If the 20 WIP units are shipped, the cost of those WIP units must go to COGS rather than being charged against the standard cost of finished goods. Most ERPs do not natively support shipping from WIP, so a separate WIP-to-COGS journal entry is required.
A producer shipping 10,000 units per day for 20 days at $15 standard cost shows $3,000,000 in COGS. If actual production cost is $15.40 per unit across 400,000 units produced, the $0.40 adverse variance equals $160,000.
The controller may charge it to COGS at close, expense it as a manufacturing variance, or split it between COGS and ending inventory. The ERP must separate material price, labor efficiency, and overhead variances for analysis.
For 50 units returned: debit Finished Goods Inventory and credit Cost of Goods Sold at the cost of the original shipment. At the same time, debit Revenue and credit Accounts Receivable.
The ERP must use the original cost, not today's average cost. Otherwise COGS drifts out of step as costs change across the period in which returns arrive.
AI Detection of COGS Posting Errors Before Period Close
COGS posting mistakes in a manufacturing ERP are additive. Each wrong ship confirm entry compounds the gross margin distortion over the period. Found by hand, they surface at month end through manual auditing of ship confirm transactions against expected COGS. Found by AI, they surface in real time, as each ship confirm posts.
A machine learning model trained on historical ship confirm postings defines expected COGS-to-revenue ratios by product line, customer, and shipment size.
If a cost of goods sold journal entry falls well outside that range, such as an older lot with an unexpected cost or a lot-actual outlier, the model flags the transaction immediately. Controllers can investigate while the shipment and lot record are still readily traceable, rather than discovering the error during post-close reconciliation or audit prep.
An agent reconciles daily ship confirm postings against sales order quantities, lot records, and expected standard-cost COGS.
It classifies variances as expected, lot-actual outlier, configuration error, or unmatched transaction. The controller receives a prioritized daily exception report rather than a raw dump of transactions, so review focuses on the postings that need action.
For more AI-powered finance and operations workflows, see manufacturing AI solutions. Approved postings then feed into inventory reconciliation at period close.
Frequently Asked Questions: Ship Confirm, COGS, and Revenue Recognition
COGS Posting Errors Showing Up at Period Close?
Tell us what ERP you run, whether you use standard or average costing, and where you see the most errors: COGS posting, ship confirm configuration, lot-actual cost outliers, or return reversal mismatches. GrayCyan will show you what AI COGS anomaly detection looks like on your current ERP.
See inventory write-offs and adjustments or ERP inventory management.
