{
  "id": 1004402,
  "title": "A 36% margin became 6% at month-end, and nothing was posted wrong",
  "url": "https://urgent.news/2026/08/15/a-36-margin-became-6-at-month-end-and-nothing-was-posted-wrong",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-15T09:20:55.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/_705cc6dba923dce49293c/a-36-margin-became-6-at-month-end-and-nothing-was-posted-wrong-56b1"
  },
  "original_language": "en",
  "account": "A small manufacturing company was built entirely within an SAP S/4HANA sandbox to observe the effects of month-end close on a healthy-looking margin. Revenue was 20,000, COGS at standard was 12,800, resulting in a margin of 7,200, or 36%. However, three days after the close, the margin had dropped to 1,200, or 6%. No incorrect postings were made.\n\nThree gates were responsible for this dramatic shift, occurring in this order: cost center revaluation, order variance, and actual costing. Gate 1, cost center revaluation (KSS1/KSII), occurred when the planned price for labor activity type was calculated as the planned cost divided by the planned activity quantity. Production orders consumed hours at this planned rate all month. When actuals arrived, depreciation posted against a plan of 3,000 proved to be 9,000, causing the actual activity rate to increase threefold. This occurred weeks earlier due to planning labor activity prices, and the impact was surprising to many.\n\nGate 2, order variance (KKS1/CO88), revealed that after applying the revalued rate (CON2), production orders no longer settled cleanly. The difference was split across variance categories and settled to variance accounts, rather than inventory. If it had gone to inventory, it would have remained on the balance sheet until the goods were sold, but that's not the case. Instead, the variance is parked, waiting for the next step.\n\nGate 3, actual costing (CKMLCP), is where the margin truly dies. This step rolls the variance into the material's periodic unit price and moves the portion belonging to what was already sold into COGS. Before this run, the P&L still appeared fine. However, after the run, the 6,000 that had been sitting in variance found its way onto the income statement. People often forget this step, and it's crucial to understand how it affects the margin. If there's a 3x error in planned depreciation, it would result in a 3x error in every labor hour the plant books, and it remains invisible for four weeks.\n\nThe key takeaway from this process is that a billing-time margin is a standard margin, reflecting the cost estimate, not the month. The three gates serve as a pipeline: revalue the rate, recompute the order, and move the difference to the sold goods. Skipping the third step would make the books look better than they are. For those responsible for product costing, catching a drifting activity rate before the close could help avoid this issue rather than explaining it afterward.",
  "summary": "I built a small manufacturing company end-to-end inside an SAP S/4HANA sandbox — one plant, one product, one month — specifically to watch what the month-end close does to a margin that looks healthy at billing time. Every number below comes from an actual document in that system. At billing, the month looked good Revenue 20,000 COGS at standard 12,800 Margin 7,200 = 36% Three days later, after…",
  "key_points": [
    "Margin drops from 36% to 6% after month-end close",
    "Three gates cause shift: cost center revaluation, order variance, actual costing",
    "Actual costing reveals 6,000 variance moves to income statement"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}