SAP Month-End Close Checklist

A step-by-step SAP FI/CO month-end close checklist covering posting period controls, sub-ledger reconciliation, GL close, and financial reporting. Built for SAP consultants, cost center accountants, and controllers managing the close in SAP S/4HANA or ECC.

Free download Excel, Word & PDF 28+ SAP close tasks
FI
CO
GL
+
Used by 2,400+ SAP finance teams
SAP Month-End Close Progress
Pre-Close (Day 1)
Open posting period (OB52)
Run recurring entries (FBD3)
Sub-Ledger (Days 2-3)
Run AP payment run (F110)
Execute asset depreciation (AFAB)
GL Close (Days 3-4)
Foreign currency revaluation (FAGL_FC_VAL)
Run CO allocation cycles (KSU5)
Reporting (Day 5)
Generate trial balance and P&L
Close posting period for prior month
38% Complete — 3 of 8 tasks done

Build your SAP month-end close checklist

Check off tasks, assign owners, and track your SAP close progress in real time.

1

Pre-Close Preparation (Day 1)

Open new posting period in OB52
Lock prior period for non-closing users
Run recurring entries via FBD3
Post accruals and deferrals (FBS1/F-65)
Notify business units of cut-off deadlines
Review parked documents and clear (FBV0)
Process GR/IR clearing (F.13)
2

Sub-Ledger Close (Days 2-3)

Run AP payment run (F110)
Clear AP open items and reconcile (FBL1N)
Run AR dunning and clear open items (F150/FBL5N)
Execute asset depreciation run (AFAB)
Close Material Ledger and settle (CKMLCP)
Reconcile bank statements (FF67/FEBAN)
Run tax reconciliation reports
3

GL Close (Days 3-4)

Execute foreign currency revaluation (FAGL_FC_VAL)
Run CO allocation cycles (KSU5/KSV5)
Run profit center assessment and distribution
Post intercompany eliminations
Reconcile GL to sub-ledgers (FAGLB03)
Review and post manual journal entries
Run balance carry-forward (FAGLGVTR)
4

Reporting and Period Lock (Day 5)

Generate trial balance and P&L (S_ALR_87012284)
Run flux analysis on key GL accounts
Prepare management reporting package
Review intercompany balances with counterparts
Obtain sign-off from finance leadership
Close posting period for all company codes (OB52)
Archive close documentation in SAP DMS
Live preview
SAP Month-End Close Checklist
Reporting Period:
0
Done
28
Pending
28
Total

How to close the books in SAP in four steps

1

Lock and prepare

Open the new posting period in OB52, lock the prior period for non-closing users, and run recurring entries and accruals. Notify all business units of cut-off deadlines so no late postings slip through.

2

Close sub-ledgers

Complete AP payment runs (F110), AR clearing, asset depreciation (AFAB), and Material Ledger settlement (CKMLCP). Reconcile bank statements and clear GR/IR to zero out the suspense balance.

3

Close the general ledger

Run foreign currency revaluation (FAGL_FC_VAL), execute CO allocation cycles, post intercompany eliminations, and reconcile GL balances to every sub-ledger using FAGLB03.

4

Report and lock period

Generate the trial balance and P&L, run flux analysis on material variances, prepare the management reporting package, obtain sign-off, and close the posting period across all company codes.

Download SAP month-end close templates

Excel (.xlsx)

Editable SAP close checklist with T-code references and formulas for status tracking.

Word (.docx)

Printable SAP close procedure document with sign-off fields for each phase.

PDF

Print-ready SAP month-end close checklist formatted for wall charts and team handoffs.

SAP month-end close timeline

A complete SAP month-end close runs over five business days. Here is how the checklist phases map to each stage of the close cycle.

D1
Pre-Close
  • Open posting period (OB52)
  • Run recurring entries (FBD3)
  • Post accruals and deferrals
  • Review parked documents
  • Process GR/IR clearing
D2-3
Sub-Ledger
  • AP payment run (F110)
  • AR dunning and clearing
  • Asset depreciation (AFAB)
  • Material Ledger close (CKMLCP)
  • Bank reconciliation
D3-4
GL Close
  • Foreign currency revaluation
  • CO allocation cycles
  • Intercompany eliminations
  • GL to sub-ledger reconciliation
  • Balance carry-forward
D5
Reporting
  • Trial balance and P&L
  • Flux analysis
  • Management reporting package
  • Finance sign-off
  • Close posting period
Pre-CloseSub-LedgerGL CloseReporting

Close faster in SAP with Bluecopa

Automate reconciliations, streamline journal entries, and cut your SAP month-end close from 10 days to 4.

Get a Demo →

How Bluecopa accelerates SAP month-end close

Bluecopa connects directly to SAP S/4HANA or ECC and automates the reconciliation, journal entry, and close tracking steps that consume most of the close cycle. Instead of exporting data to spreadsheets, your team resolves exceptions in a single workspace with a full audit trail.

1 Native SAP integration

Connect directly to SAP S/4HANA or ECC via RFC/BAPI. Pull trial balances, sub-ledger data, and open items without manual exports or flat files.

2 Automated reconciliation

Match GL to sub-ledger, intercompany, and bank balances automatically. Bluecopa flags exceptions so you fix issues instead of hunting for them.

3 Real-time close tracking

Replace spreadsheet status updates with a live dashboard. See which tasks are done, who owns what, and where the close is stuck across all company codes.

4 Audit-ready documentation

Every reconciliation, journal entry, and sign-off is logged with a timestamp and user trail. External auditors get the evidence they need without chasing people.

Do this, avoid that

✓ Do this

  • ✓ Lock the prior posting period immediately after opening the new one to prevent backdated entries
  • ✓ Run the Closing Cockpit (S_AC_TRN_COCKPIT) to sequence and monitor all close tasks in one view
  • ✓ Reconcile sub-ledger totals to GL control accounts before running any revaluation
  • ✓ Use substitution rules and validation rules to catch posting errors before they reach the GL
  • ✓ Document every manual journal entry with a business reason and supporting attachment
  • ✓ Test depreciation and allocation runs in a sandbox client before executing in production

✕ Avoid that

  • ✕ Running foreign currency revaluation before sub-ledger reconciliation is complete
  • ✕ Leaving the GR/IR clearing account unreconciled at period end
  • ✕ Closing the posting period before all company codes confirm their sub-ledger close
  • ✕ Relying on manual spreadsheets to track close tasks across multiple SAP company codes
  • ✕ Skipping the balance carry-forward step when opening a new fiscal year
  • ✕ Posting adjustments directly in production without parking them first for review

SAP month-end close terms, explained

T-Code

Transaction Code. A shortcut command in SAP that launches a specific program or function, such as FB50 for posting a journal entry or FAGL_FC_VAL for foreign currency revaluation. Every close task maps to one or more T-codes.

Posting Period

A time segment in SAP's fiscal year calendar (typically a calendar month) that controls when financial documents can be posted. Opening and closing posting periods via OB52 is the gating mechanism for the entire month-end close.

Closing Cockpit

SAP's built-in task orchestration tool (S_AC_TRN_COCKPIT) that sequences close activities, assigns owners, and tracks completion status. It replaces manual checklists with a system-enforced workflow across company codes.

CO Allocation Cycle

A Controlling module process that distributes costs from sending cost centers to receiving cost centers based on predefined rules. Executed via T-codes KSU5 (assessment) and KSV5 (distribution) before GL close to ensure accurate cost reporting.

Material Ledger Close

The process of settling actual costs against standard costs in SAP's Material Ledger (CKMLCP). Required for companies using actual costing to determine the real cost of goods manufactured and sold before closing the GL.

Foreign Currency Revaluation

An SAP process (FAGL_FC_VAL) that revalues open items and GL balances denominated in foreign currencies to the closing exchange rate. Posts unrealized gains or losses to comply with IFRS/GAAP reporting requirements.

Frequently asked questions

SAP month-end close is the process of finalizing all financial transactions for a given period within SAP ECC or S/4HANA. It involves opening and closing posting periods, reconciling sub-ledgers (AP, AR, asset accounting, Material Ledger) to the general ledger, running foreign currency revaluation, executing cost allocation cycles in CO, and generating financial reports. The goal is to produce an accurate set of financial statements that reflect the company's position at period end.
Most SAP-based organizations complete their month-end close in 5 to 10 business days. Companies with mature processes and automation tools often close in 3 to 5 days. The timeline depends on the number of company codes, intercompany transactions, currency exposures, and how much of the close is still manual. Automating reconciliations and using the SAP Closing Cockpit typically removes 2 to 3 days from the cycle.
The essential T-codes include OB52 (open/close posting periods), F110 (automatic payment run), AFAB (asset depreciation), FAGL_FC_VAL (foreign currency revaluation), CKMLCP (Material Ledger close), KSU5/KSV5 (CO allocation cycles), FAGLB03 (GL account balances), and S_ALR_87012284 (trial balance). For bank reconciliation, FF67 and FEBAN are standard. The Closing Cockpit (S_AC_TRN_COCKPIT) orchestrates all of these in sequence.
Intercompany close in SAP starts with matching intercompany invoices and payments across company codes, then reconciling the intercompany clearing accounts. Any differences must be identified and resolved before posting elimination entries. In S/4HANA, the Intercompany Reconciliation Monitor simplifies this by flagging mismatches automatically. The eliminations are typically posted in the consolidation company code or handled in a group reporting tool before generating consolidated financial statements.
The core close steps are the same, but S/4HANA simplifies several areas. The Universal Journal (ACDOCA) replaces separate tables for FI, CO, asset accounting, and Material Ledger, which means reconciliation between modules is eliminated. Real-time reporting replaces batch report generation. The Closing Cockpit is enhanced with Fiori apps for task monitoring. Foreign currency revaluation, CO period-end closing, and asset depreciation all run faster on HANA. The biggest difference is that S/4HANA reduces the number of reconciliation steps because the data is already unified.
Bluecopa connects directly to SAP via native integrations and automates the most time-consuming parts of the close: sub-ledger to GL reconciliation, bank statement matching, intercompany balance confirmation, and exception management. Instead of manually pulling data from SAP into spreadsheets, Bluecopa ingests trial balances and transactional data in real time, runs matching rules, and surfaces only the exceptions that need human attention. Teams using Bluecopa with SAP typically reduce their close cycle by 40 to 60 percent.

Related checklists