SAP FICO Month-End Closing: A Step-by-Step Checklist

Month end closing in SAP FICO is the systematic process that the finance team carries out at the end of each accounting period to verify, record and report all business transactions accurately. It consists of Financial Accounting (FI) which includes general ledger, accounts payable, accounts receivable and asset accounting and Controlling (CO) which includes cost centers, internal orders and profitability. A good close follows the cut-off principle. Each expense and each revenue item is recorded in the period in which it truly belongs. It also confirms that sub-ledgers agree to the general ledger, that adjustments such as accruals, depreciation and foreign currency valuation are posted and that costs are allocated to the correct departments. Typically a company will run the close off of a calendar with set working-day deadlines and a named owner for each task so everyone is on the same page and there are no last-minute surprises. A checklist approach adds consistency, reduces errors and over time shortens the closing cycle. The close, when done right, provides management with reliable financial statements, auditors with a clear trail of evidence, and the next period with clean data. This guide gives you that SAP month-end closing checklist, from pre-closing prep to troubleshooting the most common errors, so your team can close faster and with more confidence every month.

What is SAP FICO Month End Closing?

Month-end close refers to the set of tasks that a finance team performs at the end of an accounting period to ensure that all business activity is recorded, reconciled, and reported correctly. In SAP, this period-end closing hits both modules. Financial Accounting (FI) consists of general ledger, accounts payable, accounts receivable and asset accounting. Controlling (CO) covers cost centers, internal orders and profitability analysis.

There are four reasons for this. First, it applies the cut-off principle. Expenses and revenue must fall in the period they belong to, not in the period in which someone happened to enter them. Second, it ensures that the sub-ledgers (vendors, customers, assets) match up with the general ledger. Thirdly, it enables you to make period end adjustments like accruals, depreciation and foreign currency valuation. Fourth, it produces financial statements that are reliable to management, banks and auditors.

Most mature organizations have a closing calendar with fixed working-day deadlines, e.g., sub-ledger checks on Working Day 1, depreciation and accruals on Working Day 2, Controlling allocations on Working Day 3, and final review and period lock on Working Day 4. Write this down, with an owner for each task. This is the single best habit for a faster financial close process.

Things to Do Before You Start Closing

Pre-closing activities prepare the system and the data prior to any period-end postings start. The main reason to close a run late is because you skip them and then have to reverse and re-post entries when you find problems halfway through. First, we need to review 3 areas: posting period control, pending documents and sub-ledger reconciliation in SAP.

Opening and Closing of Posting Periods (Transaction Code OB52)

Posting periods are periods of time when users are allowed to post. They are stored in transaction OB52. Each company code is assigned a posting period variant, and in the variant you define by account type (assets, customers, vendors, G/L accounts, materials) which periods are open.

A sensible setup in a close looks like this. The period being closed is open until all adjustments have been posted. The next period is left open so that daily business can continue. All prior periods are locked to avoid back dated entries. Periods 13-16 are reserved for year-end adjustments and audit entries.

A good tip is to make use of the authorization group field in OB52. Once the primary closing work begins, you can limit the closing period to a small number of finance users. This prevents business users from posting late invoices or journals that will mess up numbers you have already reconciled. Note that the MM posting period (maintained through MMPV) is separate from the FI period and both need to be handled correctly.

Complete all incomplete document postings and parking

Parked and held documents do not hit the ledgers until posted, so they silently distort your reports. When you park a vendor invoice, you have a missing expense and a missing payable. A held journal entry is an adjustment you thought you made, but you did not.

Check all parked documents (created by transactions like FV50, FV60, or FV70) and post or delete them before closing. All vendor invoices received by month-end are to be entered in the proper period and all customer billing documents released to accounting. Run any recurring entries that are due. Request departments to submit expense claims and journal requests late, by a published cut-off date. If you get these items early the cut off will be clean and you will not have to make correcting entries the next month.

Perform Sub Ledger Reconciliation Checks

Sub-ledger reconciliation is the process of proving that the detailed records for vendors, customers, and assets match the general ledger. In SAP, each sub-ledger is linked to a reconciliation account and the sum of all individual balances should match the balance of that G/L account. If the two figures don't match up then something is wrong. Some manual posting into a reconciliation account, some interface failure or a posting made in the wrong period. It is important to identify and correct these differences early, because every subsequent closing step, including valuation, accruals and financial statements, is based on these balances. In practice, you can compare the balance reports of vendors (FBL1N), customers (FBL5N), and the G/L accounts (FAGLB03 or FS10N) and check each gap line by line. You also look at open items which should have been cleared, e.g. unapplied payments or old credit notes. The same applies to Asset Accounting and Inventory, where you should use the asset reconciliation report and material ledger checks. Document all discrepancies and resolutions so your team can create a reference for future closes. Doing this step well gives you the confidence that your ledgers are consistent, and avoids the costly corrections that show up when errors are found after the period is locked.

Accounts Payable (AP) and Accounts Receivable (AR) Audit

Start with balance comparisons for payables and receivables. Use FBL1N for vendors, FBL5N for customers, and FAGLB03 or FS10N for the G/L reconciliation accounts. Check any gap before proceeding.

Then check open items. It's also worth looking for payments received that were never applied to invoices, vendor credit notes that were never offset, and old items that should have been cleared. Run the automatic payment program (F110) for items due based on your schedule.

Then deal with foreign currency. Keep the exchange rates for the month-end date in OB08 and run foreign currency valuation in SAP (FAGL_FC_VAL in S/4HANA and new G/L, or F.05 in the old systems) so that open items and balances are displayed at the closing rate.

Finally post accruals for goods and services received but not yet billed and review customer balances for doubtful debts. If your accounting policy requires a provision then post it now.

Asset Accounting (FI-AA) and Inventory (MM) Checks

Asset accounting and materials management also post to the general ledger and therefore each needs to be verified separately.

For assets, ensure all acquisitions, retirements and transfers for the period are recorded. Assets under construction are settled to final assets on completion of construction (using distribution rules in AIAB and settlement in AIBU). Run the asset reconciliation report (ABST2) to see that the asset sub-ledger is matching with the G/L.

For inventory, make sure you have posted goods receipts and goods issues in the correct period. If you are using the material ledger with actual costing, run the period end valuation steps. Then close the SAP MM period properly, so that no material movements fall into the wrong period.

Two transactions are the main drivers of most of the work in this area: depreciation posting and GR/IR clearing.

Run Depreciation Posting (AFAB)

Depreciation is a monthly entry that occurs regularly. It is one of the biggest entries in the close. Transaction AFAB runs the SAP depreciation run for a company code, fiscal year and period.

Go in a careful order. Post all acquisitions, retirements and transfers first as depreciation computed before these are complete will be incorrect. AFAB can be first run in test mode which will show errors without posting anything. Please look at the error log and fix the assets which are causing the problem. Then run it again in update mode. Always run the periods in sequence, because SAP expects earlier periods to be finished before later periods.

Then reconcile the depreciation expense in G/L with the asset reports after posting. Verify that each asset is assigned to the correct cost center so that the expense reaches the right department in controlling.

Account Clearing After Goods Receipt/Invoice Receipt (GR/IR) (F.13 / MR11)

GR/IR clearing account is a transitory account. The system credits it when goods are received. The system debits the invoice on receipt. If they match, the account is zeroed out. Any balance at month-end is goods received not invoiced, or invoices posted without goods. Each balance requires an explanation.

Clear items on the GR/IR account where the goods receipt and invoice receipt match using automatic clearing, F.13. For remaining items, for example, when goods have been received but the invoice will never arrive or when a price difference has to be written off, use MR11 (GR/IR account maintenance). Review old open items and determine whether to write off, accrue or follow up with purchasing and vendors.

Many companies also accrue the GR/IR at month end for goods received but not yet invoiced and reverse it automatically on the first day of the next period. Auditors will question any large unexplained balances left on this account which will distort the balance sheet and the cost of goods sold.

Common Errors in Depreciation & GR/IR Runs

Even a prepared close has errors. These are the most common SAP FICO month-end closing errors, along with their typical cause and solution.

Depreciation run errors:

Error	Cause and Solution
The posting period expired.	In OB52 the asset account type is closed. Run again. Start the period.
Depreciation key area or incomplete.	Asset master data is not configured. Fix the master record and run again.
Cost center blocked or expired.	The cost center assigned to the asset is locked or has expired. Unblock the cost center or update the asset.
Asset not capitalized.	Asset capitalization date is blank. Enter the date or post-acquisition.
Previous run incomplete.	Assets not processed from a previous period. Finish those first.

GR/IR clearing mistakes:

Error	Cause and Solution
No results found.	Differences in quantities or values between goods receipt and invoice are normally due to price variances or partial deliveries. Check purchase order history.
No account determination found.	There are no accounts set up to allow for price differences or write offs. Ask your configuration team to keep them maintained.
MM period locked.	The material period is over. Open it before you post it.
Authorization failed.	The user is not in the role to clear the clearing. Request proper authorization.

A shared troubleshooting log of every error and fix is a good habit to keep. After a few closes this log becomes a useful guide and shortens each cycle.

Concluding Thoughts

A good month-end close in SAP is not a last-minute effort but preparation. Take care of posting periods, clear parked documents, reconcile every sub-ledger and do depreciation and GR/IR clearing in the correct order. Add a common closing calendar and clear ownership and your team will close faster with fewer corrections and numbers everyone can trust.

Explore SAP FICO Month-End Closing, Foreign Currency Valuation, Accrual Accounting, and Financial Statement Review to understand the complete financial closing process in SAP S/4HANA Finance .

Follow our WhatsApp Channel for SAP S/4HANA Finance updates, practical SAP FICO knowledge, and expert SAP FICO training insights.