Lesson 1 of 5
Why close testing is different
12 min
Listen to this lesson
Most SAP testing follows a transaction: create a sales order, deliver it, bill it, check the journal entry. Financial close is different. It is a set of tasks that run across all the transactions of a period, at a particular point in time, in a particular order, and each task depends on the ones before it. A process that works perfectly on the 10th of the month can produce wrong financial statements on the 31st. That is why close must be tested as a time-sequenced simulation, not as a list of independent test cases.
Three things that make close different
- Date-driven processing. Close tasks use key dates, posting dates and fiscal periods. Foreign currency valuation uses the exchange rate on a key date; depreciation posts for a period; accruals reverse on the first day of the next period. The same program gives different results on different dates.
- Period controls. Posting periods are opened and closed per company code and account type. Closing a period too early blocks late postings; leaving it open lets postings slip in after reports are run.
- Dependencies. Allocations need the costs posted first; settlements need the allocations; valuation needs the open items final; financial statements need everything. Run them in the wrong order and the numbers are wrong, often without an error message.
- Operational cutoffLast goods movements, billing and supplier invoices for the period
- Subledger closeDepreciation, inventory and GR/IR checks, open item reviews
- Accruals and correctionsAccrual postings, reclassifications, manual adjustments
- Controlling closeAllocations and settlements to cost objects and profitability
- ValuationForeign currency valuation of open items and balances
- ReportingTrial balance, balance sheet and P&L, then period lock
Defects that only appear at period end
| Defect | Why daily testing misses it | Contoso example |
|---|---|---|
| Valuation posts to the wrong account | Valuation only runs at period end | Unrealized exchange loss on a CAD receivable posted to revenue |
| Depreciation run fails for new assets | Assets are created during the month; depreciation runs once | Chicago plant 1720 machines have no depreciation terms |
| Settlement has no rule | Orders collect costs all month; settlement runs at close | Maintenance order costs stay on the order, never reach the cost center |
| Accrual reverses in the wrong period | The reversal date only matters on day one of the next period | Freight accrual reverses in the same period, doubling expense |
| Period opening missing for new account type | Daily tests use already-open periods | Asset postings blocked in the new fiscal year |
| Report mapping gap | Reports are not checked until close | A new G/L account is missing from the financial statement version |
Close-only defects and why ordinary testing misses them.
What changes in SAP S/4HANA
SAP S/4HANA records financial accounting and controlling line items together in the universal journal, so many reconciliations that used to be close tasks in SAP ECC disappear by design. Asset accounting and the material ledger also write to the same table. That makes close faster and more reliable, but it does not remove the need to test it. The tasks that remain are the ones that carry the most judgment and the most money: valuation, accruals, allocations, settlements, period control and reporting.
SAP S/4HANA also makes it easier to move work out of the close window. Because line items are posted in real time with full detail, some checks that used to wait for month end, such as reviewing GR/IR items or margin by product, can run during the month. That is good practice, but it changes the test: you must prove that the intra-period checks and the period-end tasks together give the right result, not just that each runs on its own.
- Days 1–25Intra-period checksGR/IR review and margin by product run during the month on real-time line items
- Day 0CutoffLast goods movements, billing and supplier invoices for the period
- Days +1 to +4Period-end tasksDepreciation, accruals, allocations, settlements, valuation and reconciliations
- Day +5Result and lockStatements reviewed against expected values; period closed
Who is involved
Close testing needs finance people, not just testers. At Contoso, Dan owns the result, GL, asset and cost accountants own individual tasks, Basis schedules the jobs, and Priya's team designs the test, prepares data and collects evidence. Agree early who writes the expected results: testers can calculate them, but the finance team must agree the accounting rules behind them, otherwise a disagreement about policy will surface as a "defect" in the middle of the mock close.
What would you do?
Contoso's integration test cycle passed every order-to-cash and procure-to-pay scenario. Dan, the finance process owner, asks whether finance is ready for go-live. What should Priya say?
- Close tasks are date-driven, controlled by posting periods and dependent on each other's results.
- Many close defects never appear in transaction-by-transaction testing.
- The universal journal removes some reconciliations but not valuation, accruals, allocations, settlements or reporting.
- Test year-end tasks before the first year end after go-live.
Check your understanding · not graded
Lesson check
1. Why must close be tested as a time-sequenced simulation?
2. Which close task depends on the exchange rate on a key date?
3. Costs remain on a maintenance order after close and never reach the cost center. Which close step likely failed?
4. What does the universal journal change about close?