SAP FICO Month-End Closing Checklist: Open Items, Accruals, Reconciliation and Reporting

Turn the close calendar into evidence

Month-end closing brings together complete postings, reviewed estimates, reconciliations and reporting decisions. The checklist is useful only when each task has an owner, a defined scope and evidence of its result. Marking a task complete without examining its output can leave duplicate accruals or unexplained open items in the final reports.

Start with one company code and period in a fictional practice case. Build the evidence from individual documents to account balances, then record what the reviewer accepted and which exceptions remain.

Core concepts to learn

Build a practice scenario

1. Step 1: Define the company code, ledger, period, currency and report cutoff for every comparison.
2. Step 2: Classify open items by reason, assign owners and retain invoice or payment references.
3. Step 3: Review each adjustment calculation, its posting document and any required follow-up reversal.
4. Step 4: Reconcile final balances and record the reviewer decision before closing the reporting pack.

Use sample, authorised or fictional data. Do not publish credentials, business data, account numbers or customer information in a portfolio. If a task has financial, security or production impact, include a review or approval step before any change.

What good work looks like

Fix the scope before comparing reports

A closing checklist starts with a shared reporting definition. Record the company code, ledger or accounting principle, fiscal year and period, cutoff date, reporting currency and responsible reviewer. Two correct reports can disagree when one uses a different ledger, includes a later posting or displays a different currency. Save selection parameters alongside every exported total.

Separate pre-close preparation from final close activities. Owners can review old exceptions and prepare recurring entries before month-end. Final adjustments and valuation depend on the closing data and approved accounting approach. SAP’s closing overview places valid postings and adjustments before closure of the previous accounting period. A successful background job alone does not show that the financial result was reviewed.

Worked example: an uninvoiced maintenance service

Assume a fictional business received a maintenance service in September, estimates its cost at Rs 12,000 and has not yet received the supplier invoice. For this simplified accrual exercise, exclude tax and currency differences. An approved September accrual debits maintenance expense Rs 12,000 and credits an accrued liability Rs 12,000. The evidence should identify the service period, estimate calculation and reviewer.

Suppose the agreed method reverses that accrual in October. The reversal debits the accrued liability and credits maintenance expense Rs 12,000. If the actual invoice then posts an expense of Rs 12,500 in October, the net October expense from these two entries is Rs 500. September retains the original Rs 12,000 estimate. Together they represent Rs 12,500, without counting the whole amount twice.

This demonstrates the arithmetic of one reversal-based method, not a universal posting policy. The appropriate accounts, reversal timing and adjustment treatment depend on the organisation’s accounting policy and configured process. Other accrual approaches may use different follow-up logic. Check the existing accrual and reversal documents before entering another adjustment for the same service.

Review open items without treating every item as an error

An unpaid invoice can be valid at month-end. Classify items by the action required: not yet due, overdue, disputed, payment blocked, awaiting a credit memo or awaiting clearing. For each exception, keep the document reference, amount, due date, owner and next action. Do not clear unrelated invoices and payments merely because their combined total happens to be zero.

Reconcile supplier and customer balances with the relevant general-ledger reporting scope. Check whether special transactions or different account selections explain a mismatch. Compare the key date consistently: an item cleared in October may still have been open at the September cutoff. A current open-item list is not automatically the right evidence for a historical closing date.

For GR/IR, reconcile by purchase-order item and investigate receipts, invoices and reversals. A credit balance can reflect goods received but not yet invoiced. Ask purchasing whether further deliveries or invoices are expected before considering account maintenance. Keep unresolved items with an explanation instead of hiding them inside a manual balancing entry.

Foreign currency and ledger checks

Consider an illustrative unpaid foreign-currency liability of USD 1,000. Its recorded local-currency amount is Rs 82,000. If the approved closing valuation uses Rs 84 per dollar, the illustrative increase is Rs 2,000. This is different from paying the supplier: the foreign-currency invoice remains unpaid, while the valuation reflects the relevant closing measurement.

Before interpreting the result, check the valuation date, exchange-rate basis, valuation method and ledger scope. SAP supports valuation approaches with different follow-up behaviour; do not assume every valuation is automatically reversed next month. Save the simulation or review output, the selected items and the resulting journal references. A second run must be understood in relation to earlier runs.

Build a sign-off pack that another person can follow

Create a small reconciliation bridge for each major balance: opening amount, current-period movements, approved adjustments and closing amount. For example, a prepaid balance of Rs 18,000 reduced by Rs 3,000 of recognised expense should close at Rs 15,000, assuming no other movements. Match the bridge to the posted documents rather than changing the spreadsheet to agree with the report.

The final pack should include completed tasks, unresolved exceptions, financial impact, document references and the reviewer decision. Distinguish a task that was executed from a task that was checked. If a late adjustment arrives after sign-off, record who approved it and which reports or dependent steps need to be repeated. Retain the previous report version so the change can be explained.

Must all accounts have a zero balance before closing?

No. Cash, inventory, receivables and liabilities normally carry balances. The aim is supported and appropriately reported amounts, not zero everywhere.

Is a balanced trial balance enough?

No. Equal debits and credits do not detect every wrong account, duplicate invoice or incorrect period. Combine balance checks with item-level evidence and business review.

What should a beginner submit?

Prepare a fictional task calendar, accrual calculation, open-item exception list and balance bridge. Include one late adjustment and explain how it changes the sign-off evidence. This makes the checklist a working control rather than a list of transaction names.

Official SAP references

• SAP month-end and year-end closing steps
• SAP accruals and deferrals
• SAP foreign currency valuation

Frequently asked question

What should a beginner practise after learning SAP FICO month-end closing?

Build one small, documented exercise that uses the concepts safely, validate the result, and explain the decisions and limitations. Repeating this cycle makes learning more reliable than collecting disconnected tutorials.