Margin is the number leadership looks at first. When it moves unexpectedly, the first question is always why, and the answer is expected quickly. In many Sage X3 environments, that answer takes days to assemble, because cost of goods sold (COGS) is made up of many components that are rarely reviewed together.
A margin that looks wrong is usually not one problem. It is a combination of standard costs, variances, adjustments, and timing, each posted through a different process. The way to explain it reliably is to break COGS into those components every month, look for outliers, and compare the results over time.
This guide explains what makes up COGS in a typical Sage X3 environment, how to review it at month-end, and how monthly trends help find costing problems before they become year-end surprises.
Signs your COGS and margin need a closer look
- Gross margin moves by more than expected from one month to the next, without a clear business reason.
- Some products or customers show negative or unusually high margins.
- The COGS account cannot be easily broken down into its components.
- Large variances are posted in some months and not in others.
- Margin by product in operational reports does not agree with the financial statements.
- Year-end adjustments are needed to correct inventory or cost of sales.
What makes up cost of goods sold
In a standard costing environment, COGS is rarely a single figure. It typically includes:
- Standard cost of goods shipped: the standard cost of each item delivered to customers.
- Purchase price variances: the difference between standard and the price paid for purchased items. See our guide to reviewing purchase price variances.
- Production variances: differences between standard and actual material usage, labor, machine time, and overhead on work orders.
- Inventory adjustments: count adjustments, scrap, write-offs, and obsolescence.
- Revaluations: the effect of changing standard costs on inventory on hand.
- Landed costs: freight, duty, and similar charges, depending on how they are treated.
Under average or FIFO costing, the components are different, but the principle is the same: COGS is the result of several processes, and each one needs to be understood separately.
Build a COGS bridge
The most useful monthly tool is a COGS bridge: a simple reconciliation that starts with the standard cost of what was shipped and adds each component until it reaches total COGS in the general ledger.
A typical bridge shows:
- 1. Standard cost of goods shipped
- 2. Purchase price variances
- 3. Production variances, by type
- 4. Inventory adjustments and scrap
- 5. Revaluations
- 6. Other cost of sales entries, including manual journals
- 7. Total COGS, agreed to the general ledger
Each line should be supported by a report or a list of transactions, and the total should agree to the ledger. When the bridge does not agree, the difference usually points to manual journals, unposted stock accounting, or transactions posted to the wrong account. Once the bridge is in place, explaining a change in margin becomes a matter of comparing this month's bridge to last month's and seeing which line moved.
Review margin by product and customer
The bridge explains total COGS. Margin by product and customer shows where problems are concentrated. Each month, review:
- Negative margins: products or orders sold below cost. These are either real pricing problems or signs of an incorrect standard, price, or unit of measure.
- Unusually high margins: products with margins far above the norm, which often indicate a standard that is too low or a cost that was not recorded.
- Margins that changed sharply: products whose margin moved significantly from the prior month or the same month last year.
- Customer-level differences: discounts, rebates, and pricing agreements that reduce margin for specific customers.
As with other costing reviews, this is much faster with a custom report that brings sales, standard cost, and variances together by product and customer, rather than reviewing items one at a time.
The common causes of unexpected margin movements
Incorrect standard costs
A standard that is too high or too low distorts margin on every sale of that product. Our guide to validating standard cost updates covers how to check standards before they take effect.
Work orders not closed
Production variances are often recognized when work orders are completed and closed. If work orders stay open across several months and are then closed together, variances that belong to earlier months land in one period and distort its margin.
Cutoff and timing
Deliveries recorded in one period and invoiced in another, or transactions posted with earlier dates, move cost and revenue between months. See our guide to backdated transactions and integration dates.
Sales pricing and discounts
Incorrect prices, discounts, rebates, and credit notes affect margin through revenue rather than cost. They need to be reviewed alongside COGS so that a revenue problem is not mistaken for a cost problem.
Returns
Customer returns reverse revenue and, if goods are returned to stock, reverse cost. If the return and the credit note are posted in different periods, or at different values, margin is distorted in both.
Inventory adjustments and write-offs
Large count adjustments, scrap, and obsolescence write-offs can move margin significantly in the month they are posted. These are real costs, but they should be visible as separate lines rather than hidden in total COGS.
Unit of measure and data errors
A wrong unit of measure or conversion factor on a product can make its cost or price wrong by a large factor, producing margins that are obviously incorrect once someone looks at the detail.
Use monthly trends to catch problems early
A single month rarely tells the whole story. Trends show whether a movement is a one-time event or a sign of a recurring problem. Useful trend views include:
- Gross margin percentage by month, for the business and by product family
- Each COGS bridge line as a percentage of sales, so that growing variances stand out even as volume changes
- The products with the largest variance each month, to see which ones appear repeatedly
- Production variances by work center or product family, to identify where actual performance differs consistently from standard
A variance that appears every month is not noise. It usually means a standard, a routing, a bill of material, or a process does not reflect reality. Finding it in the trend is much easier than explaining it in a single month's results, and much easier than correcting it at year-end.
A month-end review sequence
- 1. Confirm the period is complete.
Deliveries, invoices, receipts, production completions, and stock accounting for the period should be posted.
- 2. Build the COGS bridge and agree it to the general ledger.
- 3. Compare the bridge to last month and to the same month last year, and identify the lines that moved.
- 4. Review margin by product and customer for negative, unusually high, and sharply changed margins.
- 5. Investigate the outliers and classify each as a real business change, a timing difference, or an error.
- 6. Correct errors at the source, such as standards, prices, units of measure, or postings, and agree with Finance how to correct transactions already posted.
- 7. Update the trend views and note any variance that has now appeared for several months in a row.
- 8. Document the explanations so that the margin commentary is ready when leadership asks.
Preventing avoidable margin surprises
- Review standard cost inputs before each update.
- Close work orders promptly, so production variances are recognized in the right period.
- Agree on cutoff rules for deliveries, invoices, and production.
- Report inventory adjustments, scrap, and write-offs as separate lines.
- Review the COGS bridge and margin trends monthly, not only at year-end.
When to bring in help
Outside help is usually worthwhile when margin cannot be explained without significant manual work, when COGS cannot be broken into its components, when production variances are consistently large, or when year-end adjustments to inventory and cost of sales have become routine. In those situations, the work involves reviewing costing setup, production processes, and reporting together.
COGS and margin questions
What is included in cost of goods sold in Sage X3?
It depends on configuration, but under standard costing it typically includes the standard cost of goods shipped, purchase price variances, production variances, inventory adjustments, revaluations, and related cost of sales entries.
Why does our margin change so much from month to month?
Common reasons include work orders closed in batches, cutoff differences between deliveries and invoices, large inventory adjustments, and standard costs that do not reflect current costs. A COGS bridge shows which component moved.
What is a COGS bridge?
It is a reconciliation that starts with the standard cost of goods shipped and adds each variance and adjustment until it reaches total COGS in the general ledger. It makes month-to-month changes much easier to explain.
Why do some products show negative margins?
Either the product is genuinely sold below cost, or there is an error in the standard cost, the selling price, or the unit of measure. Reviewing the detail for those products usually shows which.
How far back should margin trends go?
Twelve months is a practical starting point. It shows seasonal patterns and makes recurring variances easy to see.
Related reading
- How to review purchase price variances under standard costing
- Before you roll Sage X3 standard costs
- Backdated transactions and integration dates
- Reconciling Sage X3 inventory valuation to the general ledger
- Month-end close checklist for Sage X3
- Sage X3 reporting services
- How to review overhead and landed cost variances in Sage X3
- Sage X3 finance and costing services
Need help explaining your margin?
If your margin is hard to explain each month, or variances keep appearing without a clear cause, a review of your costing setup and reporting usually shows where the differences are coming from. Schedule a discovery call to talk it through with a senior Sage X3 consultant.