The Close That Keeps Slipping
At TropiSip FMCG (name and details altered to protect identities), a Philippines-based beverage and snacks company operating across Luzon, Visayas, and Mindanao, the finance team had stopped committing to a closing date. The business processed over 100,000 transactions a day across procurement, production, distribution, and returns, all running on SAP S/4HANA with FI/CO, MM, SD, PP, and EWM tightly integrated, along with 3PL warehouses and retail POS feeds.
The expectation was a D+2 close. The reality had drifted to D+5, sometimes D+6 during peak promotion cycles. The CFO saw unresolved GR/IR balances crossing $15M, inventory variances nearing $8M, and repeated escalations from auditors. From the board’s perspective, this looked like a finance execution issue. From inside the system, it was anything but.
What SAP Was Showing Finance
Within SAP, finance was chasing numbers that refused to settle. GR/IR clearing accounts showed thousands of open items where goods receipts had been posted through MIGO, but invoices via MIRO had not aligned due to quantity and pricing mismatches. Inventory valuation through Material Ledger runs reflected inconsistencies between standard cost, moving average, and actual consumption driven by late postings.
Cost object controlling was equally unstable. Production variances from PP were not fully settled due to delayed confirmations, and SD billing documents did not always align with dispatches because of returns and promotional adjustments. The Closing Cockpit continued to show progress in task completion, but key reconciliations remained incomplete.
In SAP terms, the financial data was internally consistent based on what had been posted.
In Lydian speak, finance was trying to close a version of the business that only existed inside the system.
What Was Actually Happening in the Business
The breakdown began upstream. TropiSip relied heavily on 3PL warehouses across the Philippines, with inbound deliveries posted through EDI interfaces. During high-volume weeks, these interfaces lagged by 24 to 48 hours, meaning goods physically received were not recorded in SAP within the cut-off window. Procurement believed materials were available, but finance did not see them in inventory.
At the same time, production teams were issuing goods based on physical stock, while confirmations in SAP were delayed or partially posted. This created a mismatch between what had been consumed and what the system believed was still available. Warehouse movements added another layer, where stock transfers between storage locations were executed physically but posted late, distorting inventory positions.
In plain business terms, the company was running operations faster than it was recording them.
Where Sales Made It Worse
Sales added its own complexity. Promotions and distributor returns created high volumes of credit notes and adjustments, many of which depended on POS data feeds that were not synchronised in real time. SD billing documents were created based on dispatches, but returns were often processed days later, reversing revenue and inventory positions after the financial period had effectively closed.
Rebate accruals, tied to promotional schemes, depended on accurate sales and return data. When that data lagged, finance could not confidently calculate liabilities. Revenue looked inflated at first, then corrected later, creating volatility in reported numbers.
In Lydian speak, sales was booking revenue before the business had fully understood what it had actually sold.
Why SAP Did Not Flag the Problem
SAP did not treat any of this as an error. Each transaction, when posted, followed correct logic. Goods receipts updated inventory. Billing updated revenue. Production confirmations updated cost flows. The system’s integrity was intact.
What SAP does not inherently track is the timing gap between physical reality and system recording, unless explicitly governed. A goods receipt posted late is still a valid goods receipt. A return processed after cut-off is still a valid adjustment.
In plain business terms, SAP was faithfully recording events, but not questioning whether those events were recorded when they should have been.
Why Finance Took the Blame
By the time the problem reached finance, it appeared as a reconciliation failure. GR/IR accounts did not clear, inventory did not tie to the balance sheet, and variances accumulated across cost centres. The finance team extended working hours, ran manual reconciliations, and escalated issues across functions.
From leadership’s perspective, finance was delaying the close. From reality’s perspective, finance was the first function forced to confront the inconsistencies created elsewhere.
In Lydian speak, finance does not create the problem. It reveals it.
The Structural Nature of the Failure
The issue was not a system failure or a finance inefficiency. It was a structural failure of synchronisation across functions. Procurement, production, warehousing, and sales were all operating correctly within their contexts, but their timing, data quality, and posting discipline were misaligned.
SAP had integrated the functions technically. The business had not integrated them operationally.
The Question Leadership Should Ask
The relevant question is not why finance cannot close on time. It is whether the enterprise is operating in a way that allows finance to produce numbers that reflect reality.
Financial close is not a finance activity.
It is the final output of how well the business operates.
