Day −2
Two working days before month end
Logistics finishes the month: goods movements, production confirmations and supplier invoices are posted before the cut-off.
Hands over: complete quantities for the period.
Everything that happens in SAP S/4HANA between the last goods movement of the month and signed-off financial statements: the order, the transactions and apps, what changed from SAP ERP, and how to close faster.
Each step needs the one before it: controlling starts when accounting has posted the period, and the material ledger only after every order is settled.
Period-end closing is the set of activities that finish one accounting period: posting everything that belongs to it, valuing it at the right rates, moving costs to the objects that explain them, and locking the period so the numbers stop changing. It runs every month, with extra steps at quarter end and a longer list at year end.
In SAP S/4HANA, Financial Accounting (FI) and Controlling (CO) post to one Universal Journal, the table ACDOCA. They close together instead of being reconciled afterwards. The order of the work still matters: an allocation run before the last invoice is posted, or a costing run before the last order is settled, gives a wrong result that has to be reversed and run again.
This page follows one monthly close from the logistics cut-off to the period lock, with most of the space on FI and CO: the two areas that decide when the books are really closed.
Close calendar
A typical plan for a manufacturing company with actual costing. Day −2 and Day −1 are the last working days of the month; WD1 to WD5 are the first working days of the next. Your own calendar depends on volumes, countries and how much runs during the month.
Pick a day and tick the tasks as they finish. The ticks stay on this page only: nothing is saved.
0 of 40 tasks done 0%
Day −2
Logistics finishes the month: goods movements, production confirmations and supplier invoices are posted before the cut-off.
Hands over: complete quantities for the period.
Day −1
Billing, payments and bank statements bring receivables, payables and cash up to date.
Hands over: complete subledgers and bank balances.
WD1
The new period opens for daily business while the old one stays open for closing postings. Assets are settled and depreciated.
Hands over: assets posted and the old period reserved for the close.
WD2
What is missing is accrued, foreign currency is valued at the closing rate and balances are regrouped. Controlling collects its tracing factors.
Hands over: a complete, valued general ledger to Controlling.
WD3
Cost centers are emptied in the right order, activity prices become actual and production orders get overhead, WIP, variances and settlement.
Hands over: settled orders and final activity prices to the material ledger.
WD4
The material ledger turns price differences into actual costs, projects settle and margin analysis receives its last amounts.
Hands over: final cost of goods sold and margins.
WD5
Statements, tax files and the hand-over to consolidation. The period closes for everyone except the closing team.
Hands over: signed-off numbers for the month.
Financial Accounting
Financial Accounting closes first because everything after it reads its postings. The goal is a complete and correctly valued period: every invoice and receipt in, what is missing accrued, foreign currency at the closing rate, and each balance on the right side of the balance sheet.
Accruals, valuations and reclassifications that make the balance sheet and the income statement right for the period. Most of it runs on WD1 and WD2.
OB52
Open the new period for daily business and keep the old one open only for closing postings. Account types (+, A, D, K, M, S) can be opened separately, and interval 3 controls postings that Controlling sends to Financial Accounting.
SAP S/4HANA: The Manage Posting Periods app (from 1809) maintains the same table. CO postings also check the FI periods.
F.14
Posts the recurring documents set up with FBD1, such as rents, leases or fixed fees.
FBS1F.81
Accrue the expenses and revenues that belong to the period. FBS1 documents carry a reversal date, and F.81 reverses them in the next period.
SAP S/4HANA: Accruals Management can take over recurring accruals and purchase order accruals, with review and approval before posting.
FAGL_FCV
Values open items and balances in foreign currency at the closing rate, in each currency of each ledger, and posts the exchange rate differences.
SAP S/4HANA: In SAP S/4HANA Cloud, Advanced Valuation can replace it with job templates in Schedule General Ledger Jobs; FAGL_FCV is then no longer used.
FAGLF101
Moves customers with credit balances and suppliers with debit balances to the other side of the balance sheet, and can sort receivables and payables by remaining term.
SAP S/4HANA: Balance sheet reclassification is one of the four Advanced Valuation processes.
F.13
Clears open items that balance to zero on open-item-managed accounts, such as bank clearing and GR/IR accounts.
F.01FBL3H
Check balances by financial statement version, then drill into line items before sign-off.
SAP S/4HANA: Fiori apps such as Trial Balance and Display Financial Statement read ACDOCA directly, with no totals tables.
Every goods receipt and supplier invoice of the period is in, and whatever has been received but not invoiced is accrued.
MIROMRBR
Post the invoices received for the period and release those blocked for price or quantity once the difference is explained.
F110
Pays due items and clears them. Schedule the last run of the month before the cut-off so bank and payables agree.
MR11F.19
Analyze the goods receipt / invoice receipt clearing account. MR11 writes off old quantity or value differences after approval, and F.19 analyzes the balance and reclassifies it for the balance sheet.
SAP S/4HANA: The apps Reconcile GR/IR Accounts (F3302) and Monitor GR/IR Account Reconciliation (F3303) give worklists, statuses and root causes, with optional machine learning proposals.
ACEPROPOSALRUNACEPOSTINGRUN
Accrues planned costs from the purchase order delivery schedule that are not yet covered by goods receipts or invoices. Proposals can be reviewed by the purchase order owner and approved by the G/L accountant before posting.
SAP S/4HANA: Job templates in the Schedule Accruals Jobs app; the review workflow is set in Manage Workflows for PO Accruals Review.
F.18
Sends balance confirmations to suppliers, usually at year end or for the auditors.
Revenue and receivables are complete, cash is applied, and receivables at risk are valued.
VF04VFX3
Bill every delivery of the period from the billing due list and release billing documents that did not reach accounting.
FF_5FEBAN
Import the bank statements and post-process the items that did not clear automatically.
F150
Runs dunning on overdue items, usually weekly, with a last run before the close.
F107
Value adjustments and provisions for receivables at risk, from the valuation run.
SAP S/4HANA: With Advanced Valuation in SAP S/4HANA Cloud, credit-risk-based impairment replaces it.
FAGLF101
Customers with credit balances are shown as liabilities on the balance sheet.
F.17
Sends balance confirmations to customers, usually at year end.
Asset Accounting posts in real time to every ledger in SAP S/4HANA. At period end, assets under construction are settled, depreciation is posted and the movements are checked.
AIBU
Settles the capitalized costs of assets under construction to the final assets when they go into use.
AFAB
Posts the planned depreciation of the period to the general ledger for every depreciation area.
SAP S/4HANA: Runs from the Schedule Asset Accounting Jobs app. Planned depreciation is recalculated with each asset transaction, so the run only posts; ASKB is no longer needed.
AW01NS_ALR_87011990
Asset Explorer for single assets and the asset history sheet for the movements of the period.
AFARAJAB
Recalculate depreciation if rules changed, then close the old fiscal year once depreciation is fully posted.
SAP S/4HANA: The fiscal year change happens with the balance carryforward (FAGLGVTR); AJRW is not used.
Cash is the first number auditors check. Every bank account agrees with its statement and every open item has an explanation.
FF_5FEBAN
Import electronic statements for all accounts up to the last day of the month and post-process what did not clear.
FBCJ
Close each cash journal for the period and agree it with the cash count.
F.13
Clear the bank clearing accounts automatically and investigate what is left.
FBL3H
The G/L balance of each bank account equals the statement; outstanding items are listed and explained.
The tax close turns the posted period into returns and statutory files. Deadlines are set by each country, so tax tasks often drive the calendar.
S_ALR_87012357
The classic advance return report for tax on sales and purchases (program RFUMSV00), by tax code and period.
Generates statutory reports and electronic returns for many countries from the posted data, with a monitor for deadlines and submissions.
Monthly tax ledgers (apuração) for ICMS, IPI, PIS and COFINS, then the SPED files: EFD ICMS/IPI and EFD-Contribuições every month, ECD and ECF once a year.
Both sides of every intercompany transaction must agree before group reporting can eliminate them.
Intercompany Matching and Reconciliation (ICMR) matches documents between company codes directly from ACDOCA, using matching methods made of rules.
SAP S/4HANA: Apps: Define Matching Methods, Schedule Matching Runs, Manage Assignments.
Assign reasons to unmatched items and post adjustments, with an approval workflow if needed.
SAP S/4HANA: Apps: Reconciliation Status Overview and Reconciliation Balances.
FBL1HFBL5HFBL3H
Check intercompany supplier, customer and G/L items by trading partner.
After the entity close, the data goes to consolidation, for example in SAP S/4HANA Finance for group reporting.
Controlling
Controlling turns the period’s costs into answers: what each cost center spent and passed on, what each order and product really cost, and what each customer and product earned. Inside CO the order is strict, so the steps below are numbered.
Empty the service cost centers and overhead orders into the cost centers, orders and products that used them.
KB31N
Enter the tracing factors the cycles use, such as headcount, floor space or kWh.
KO8G
Internal orders that collect overhead settle to their cost centers before the cycles run.
KSV5
Moves primary costs to the receivers and keeps the original cost element.
KSU5
Moves costs with an assessment cost element. Cycles run in the order of their dependencies.
SAP S/4HANA: Universal allocation adds the Manage Allocations and Run Allocations apps.
KSC5
Allocates activity quantities that are not confirmed directly, based on tracing factors.
KSII
Divides each cost center’s actual costs by its actual activity and, if the CO version revalues, charges the difference to the orders that consumed the activity.
SAP S/4HANA: Needs actual price indicator 5 on the activity type and revaluation set in the version. See the worked example below.
S_ALR_87013611KSBT
Actual, plan and variance by cost center, and the resulting activity prices. Anything left on a cost center should be explained.
Production orders and product cost collectors get overhead, then work in process and variances are calculated and settled. Start only when activity prices are final.
CO43KGI2
Applies the overhead rates of the costing sheet to production orders, collectively or one by one.
KKAOKKAX
Calculates WIP for orders not yet finally delivered. Product cost collectors value WIP at target cost.
KKS1KKS2
Explains the order balance by variance category: input price, input quantity, resource usage, lot size, output price and others.
CO88KO88
Posts WIP to Financial Accounting and the order balance to price difference accounts and the material ledger. Variance categories can also go to margin analysis.
Event-based production accounting posts WIP and variances when goods are issued, operations confirmed or orders delivered, so less is left for period end.
SAP S/4HANA: Available in SAP S/4HANA Cloud with scope item 3F0.
With actual costing, the material ledger turns the price differences collected during the month into actual costs of inventory and cost of goods sold.
MMPV
All goods movements and invoices are posted, product costing is closed, the next MM period is open and the previous period is closed in the material ledger.
CKMDUVMATCKMDUVACT
Distribute inventory and activity differences to the orders that consumed them.
CKMLCP
Selection, preparation and settlement. Settlement does single-level and multilevel price determination and the revaluation of consumption in one step.
SAP S/4HANA: Five steps instead of the eight in SAP ERP.
CKMLCP
Posts the revaluation of ending inventory and, if chosen, of consumption. The inventory revaluation is reversed on the first day of the next period.
CKM3CKMVFM
Material price analysis per material, and the value flow monitor for differences not yet distributed.
Projects and investment orders carry costs and revenues until they are settled to their receivers.
CJ45CJ44
Applies overhead rates to WBS elements and networks, collectively or one project at a time.
KKAJKKA2
Calculates revenue, cost of sales, work in process or reserves for customer projects, collectively or one project at a time.
Recognizes revenue with each cost, time or billing posting on customer projects, which leaves fewer adjustments for period end.
CJ8GCJ88
Settles projects to assets under construction, fixed assets, cost centers or margin analysis.
KO8GKO88
Settle after the overhead orders, to assets, cost centers or other receivers.
In SAP S/4HANA, margin analysis lives in the Universal Journal: each line carries its market segment, so revenue and cost of goods sold arrive with the posting itself.
Billing, cost of goods sold, settled production variances and project settlements must be in before margins are analyzed.
KE28
Spreads amounts posted at a high level, such as freight or rebates by customer group, down to products and customers.
KE30
Margins by product, customer and region. Fiori apps read the same data from ACDOCA.
The last CO steps decide whether the period can really be locked.
FI and CO post to the same journal entry in SAP S/4HANA, so they agree by design. The reconciliation ledger of SAP ERP is gone.
Cost centers with balances, orders not settled and materials with errors in the costing run are each a reason not to lock yet.
OKP1
Locks business transactions for the period by controlling area, fiscal year and version.
OB52
Closes the period for operational postings. A closing interval with an authorization group keeps room for late adjustments.
Worked example
Cost center 4100, a packaging line, plans its machine hour at 50.00. During the month it collects 120,000.00 of costs, including what the cycles assessed to it, and confirms 2,000 hours to two production orders.
At plan price the orders are charged 100,000.00 and 20,000.00 stays on the cost center. KSII recalculates the price from actual costs and actual hours and, with revaluation switched on in the CO version, charges the difference to the orders.
That is why the actual price calculation runs after the allocation cycles and before work in process, variances and settlement of the production orders.
| Object | Calculation | BRL |
|---|---|---|
| Cost center 4100: costs of the month | Primary and assessed costs | 120,000.00 |
| Cost center 4100: credit for activity | 2,000 h × 50.00 | 100,000.00 |
| Balance left on the cost center | Under-absorbed | 20,000.00 |
| Production order 1001 | 1,200 h × 50.00 | 60,000.00 |
| Production order 1002 | 800 h × 50.00 | 40,000.00 |
At the plan price of 50.00 per hour, 20,000.00 stays on the cost center: the orders were charged less than the hours really cost.
| Object | Calculation | BRL |
|---|---|---|
| Cost center 4100: costs of the month | Primary and assessed costs | 120,000.00 |
| Cost center 4100: credit for activity | 2,000 h × 60.00 | 120,000.00 |
| Balance left on the cost center | Cost center empty | 0.00 |
| Production order 1001 | 1,200 h × 60.00 | 72,000.00 |
| Production order 1002 | 800 h × 60.00 | 48,000.00 |
KSII sets the actual price at 120,000.00 ÷ 2,000 h = 60.00 and charges the 20,000.00 to the orders (12,000.00 and 8,000.00). The variance calculation then shows it as an input price variance.
Year end
The last period of the year runs the full monthly close. Then the fiscal year itself has to be closed in Asset Accounting and carried forward in the general ledger, while the new year is prepared in FI and CO.
OBH2.F.17 and suppliers with F.18, usually for the auditors.MI07 before the last costing run.KP26) and release the new standard costs (CK40N or CK24).FAGLGVTR carries forward G/L, customer, supplier and asset balances; F.07 can still carry forward customers and suppliers separately.OB53.OB52, ideally with an authorization group.AFAR recalculates planned depreciation when rules changed, before the carryforward.AJRW is no longer used.AJAB checks that depreciation is fully posted and locks the year for asset postings.SAP ERP vs SAP S/4HANA
Most of the close is still the same work, but several steps disappeared and others moved from period end into the day-to-day postings.
| Area | SAP ERP (ECC) | SAP S/4HANA |
|---|---|---|
| FI and CO | Separate FI and CO tables; cross-company CO postings brought back to FI with the reconciliation ledger, or with the real-time integration of the new G/L | One Universal Journal (ACDOCA); FI and CO close together, with no reconciliation step; CO postings also check the FI posting periods |
| Asset Accounting | Parallel depreciation areas posted periodically (ASKB); fiscal year change with AJRW | All areas post in real time to their ledgers; planned depreciation recalculated with each asset transaction; fiscal year change with the balance carryforward |
| Material ledger | Optional | Always active; actual costing optional; costing run reduced from eight steps to five |
| Profitability | Costing-based CO-PA common, kept in its own tables and reconciled with FI separately | Margin analysis in the Universal Journal; market segment derived with each posting |
| Foreign currency | FAGL_FCV | FAGL_FCV, or Advanced Valuation job templates in SAP S/4HANA Cloud |
| GR/IR | F.19 and MR11, worked through at period end | Reconcile GR/IR Accounts and Monitor GR/IR Account Reconciliation apps, with optional machine learning proposals, used during the month |
| Accruals | Manual accrual documents (FBS1) | Accruals Management: purchase order accruals proposed from the order, reviewed, approved and posted by job |
| Intercompany | Reconciliation with reports and spreadsheets | Intercompany Matching and Reconciliation (ICMR) on ACDOCA in near real time |
| Allocations | Assessment and distribution cycles (KSU5, KSV5) | The same cycles, plus universal allocation: Manage Allocations and Run Allocations apps |
| Production accounting | WIP and variances calculated at period end | Period-end runs, or event-based WIP and variances in SAP S/4HANA Cloud (scope item 3F0) |
| Orchestration | Schedule Manager (SCMA), Financial Closing cockpit add-on | Financial Closing cockpit in the core from 1709 (FCLOCO), SAP Advanced Financial Closing on SAP BTP |
SAP ECC
If you still close in SAP ERP 6.0, these steps are part of your month or your year. In SAP S/4HANA they are gone, for one reason: the Universal Journal posts FI, CO, assets and profit centers in the same journal entry, so there is nothing left to transfer or reconcile.
Classic or new G/L decides. The new G/L of SAP ERP already removed four of these steps: real-time integration replaced the reconciliation ledger, and document splitting builds balance sheets per profit center, segment or business area as you post. The asset steps stay in both.
KALC
Classic G/L onlyPart of your closeNot with the new G/L
In SAP ECC
Controlling allocations that cross company codes, business areas or functional areas change the books only inside CO. With the classic G/L, KALC posts those differences to FI through the reconciliation ledger before the financial statements. The new G/L does it in real time instead.
In SAP S/4HANABlocked
The system stops it with message FINS_ACDOC_CUST035: “Journal Entry is active: Reconciliation posting cannot be used any longer”. CO postings are already in the general ledger, and a reconciliation posting would duplicate them.
1KEK
Classic G/L onlyPart of your closeNot with the new G/L
In SAP ECC
Classic profit center accounting (EC-PCA) does not see the profit center of open payables and receivables, so 1KEK transfers them at month end to build a balance sheet per profit center.
In SAP S/4HANANot needed
The profit center is on every line of the Universal Journal, and document splitting gives payables and receivables their profit center when they are posted.
F.5DF.5E
Classic G/L onlyPart of your closeNot with the new G/L
In SAP ECC
In the classic G/L, payables, receivables and taxes are spread over business areas at period end so that each has its own balance sheet: F.5D calculates the adjustment and F.5E posts it (program SAPF180).
In SAP S/4HANARemoved
No longer in the closing menu. Document splitting builds balance sheets per profit center, segment or business area with each posting.
F.50
Classic G/L onlyPart of your closeNot with the new G/L
In SAP ECC
In the classic G/L, gives profit and loss items created by payments, such as cash discounts and exchange rate differences, the business area and profit center of the items they cleared.
In SAP S/4HANARemoved
No longer in the closing menu. Document splitting assigns these items as they are posted.
ASKBASKBN
Classic and new G/LPart of your closePart of your close
In SAP ECC
Depreciation areas that post to the G/L periodically, such as a second valuation for IFRS or tax, send their acquisition and production cost changes each month: ASKB with the classic G/L, ASKBN with the new G/L.
In SAP S/4HANARemoved
Every depreciation area posts in real time to its own ledger, so there is no periodic run.
ABST2
Classic and new G/LPart of your closePart of your close
In SAP ECC
Compares the asset subledger with the asset reconciliation accounts of the G/L and lists the differences to clear before the fiscal year is closed.
In SAP S/4HANARemoved
Assets and the general ledger are posted in the same journal entry, so there is nothing to reconcile.
AJRW
Classic and new G/LPart of your closePart of your close
In SAP ECC
Opens the new fiscal year in Asset Accounting before any asset posting to it. The G/L balance carryforward is a separate run.
In SAP S/4HANARemoved
FAGLGVTR opens the new year in Asset Accounting together with the general ledger balance carryforward.
Checking whether a transaction still exists in your SAP S/4HANA release: table PRGN_CORR2 (SE16N) lists old transactions and their successors, and the simplification list for your release explains why.
Orchestration
A close with hundreds of tasks across many company codes needs a plan that knows the dependencies, starts the jobs and shows who is late.
Task lists per period and organizational unit, with dependencies, background jobs, workflow notifications and an audit trail. Relaunched as part of the SAP S/4HANA core in release 1709.
FCLOCOFCLOCOC
A cloud application on SAP BTP that plans and runs the entity close across SAP S/4HANA Cloud, SAP S/4HANA and SAP ERP systems: closing templates, sequencing and dependencies, job scheduling, governance checks and critical-path monitoring. It sends triggers and parameters to the connected systems and does not copy financial data.
SAP BTPCross-system
Announced at SAP Sapphire in May 2026, with general availability planned for the second quarter of 2026. It coordinates several Joule agents across the close: posting, accruals, journal validation, error resolution and intercompany reconciliation.
SAP Fiori
The SAP Fiori apps that do period-end work in SAP S/4HANA, by step, with the app ID to find them in the launchpad and the SAP GUI transaction each one replaces. Some have no SAP GUI equivalent at all: they are new in SAP S/4HANA.
F2293Open and close FI posting periods by variant, account type and interval, including the special periods.
ReplacesOB52
F2581Create posting period variants and assign them to company codes, so several company codes open and close together.
No SAP GUI equivalent
The SAP S/4HANA Financial Closing cockpit in the launchpad: run and monitor the closing task lists.
ReplacesFCLOCO
F1927Job templates for foreign currency valuation, regrouping, automatic clearing and the GR/IR reclassification, scheduled and monitored in one place.
ReplacesFAGL_FCVFAGLF101F.13F.19
F1596Balance carryforward to the new fiscal year, for the general ledger and Asset Accounting together.
ReplacesFAGLGVTR
F0996ABalances by period with drill-down to line items, read straight from ACDOCA.
ReplacesS_ALR_87012277
F2217Line items with every Universal Journal field, filtered and saved as views.
ReplacesFBL3H
F0717Find, display and reverse journal entries; filter by intercompany transaction to check both sides.
ReplacesFB03FB08
F3302Worklists of purchase order items whose receipts and invoices differ, with status, priority, root cause and write-off. Optional machine learning proposals.
ReplacesMR11
F3303Open GR/IR items by age, supplier and company code, with the machine learning proposals on a card.
No SAP GUI equivalent
F5796Where reconciliation work gets stuck: bottlenecks, repeated work and processing time in days.
No SAP GUI equivalent
Transfer purchase orders to the Accrual Engine, propose the period amounts and post them, as jobs.
ReplacesACEPROPOSALRUNACEPOSTINGRUN
Planned, actual and accrued amounts per purchase order and month.
ReplacesPOACTREE03
Optional review of the proposed amounts by the controller, who can change them before posting.
ReplacesFACRARVWCO
Who reviews and who approves the proposals, and in which order.
No SAP GUI equivalent
F1914The depreciation run and the recalculation of depreciation, scheduled as jobs with their logs.
ReplacesAFABAFAR
F1616Planned and posted depreciation by asset and depreciation area.
ReplacesAR03
F1564Enter, display and check bank statements.
ReplacesFF67
F1520Clear the bank statement items that did not post automatically.
ReplacesFEBAN
The rules that pair intercompany documents between company codes.
No SAP GUI equivalent
Runs the matching methods on journal entries from ACDOCA.
No SAP GUI equivalent
Work the unmatched items, assign reasons and post adjustments.
No SAP GUI equivalent
Which company code pairs are reconciled for the period and which are not.
No SAP GUI equivalent
Balances of both sides per partner, with tolerances.
No SAP GUI equivalent
F3338Create and change allocation cycles: overhead allocation (assessment), distribution and more.
ReplacesKSU1KSV1
F3548Run the cycles for the period, in test mode first, and reverse them if needed.
ReplacesKSU5KSV5
F4363What each run moved, by sender and receiver.
No SAP GUI equivalent
F3915Enter the tracing factors the cycles use. Available from SAP S/4HANA 2020.
ReplacesKB31N
F0940Actual, plan and variance by cost center, to check what is left after the cycles.
ReplacesS_ALR_87013611
Prices and inventory values per material, in every currency and valuation of the material ledger.
No SAP GUI equivalent
Inventory value changes line by line, before and after the costing run.
No SAP GUI equivalent
We found no dedicated app for these steps on-premise. They run as SAP GUI transactions, which the Fiori launchpad can also open as tiles.
OKP1KSIIKSC5CO43KKAOKKS1CO88CKMLCPCJ8GKE28
SAP S/4HANA Cloud Public Edition has no SAP GUI, so it has apps where on-premise has transactions: for example Manage Posting Periods – Cost Accounting (since 2102) for the CO period lock, and Advanced Valuation job templates for foreign currency valuation.
App names and IDs from the SAP Fiori apps reference library and SAP Learning; they change between releases, so search the library by ID for your release.
Fiori first
For projects that run the close in SAP Fiori wherever they can. Every step in order, with the app to use, and the SAP GUI transaction only where no app does the job. Nothing is left out just because it has no app.
Month end: 40 steps · 19 in Fiori · 5 Fiori + SAP GUI · 16 only in SAP GUI
| # | Step | Area | When | How | Fiori app | SAP GUI | Note |
|---|---|---|---|---|---|---|---|
| 01 | Run the closing task list | Close | Every day | Fiori | Process Closing Tasks (Classic) | — | The SAP S/4HANA Financial Closing cockpit; templates are set up in FCLOCO |
| 02 | Post goods receipts | MM | Day −2 | Fiori + SAP GUI | Post Goods Receipt for Purchase OrderF0843 | MIGO | Goods issues to orders and transfers still use MIGO |
| 03 | Confirm production orders | PP | Day −2 | SAP GUI | — | CO11N | |
| 04 | Post supplier invoices | AP | Day −2 | Fiori | Create Supplier InvoiceF0859 | — | |
| 05 | Release blocked invoices | AP | Day −2 | Fiori + SAP GUI | Schedule Supplier Invoice Jobs – Advanced | MRBR | The app schedules the automatic release; MRBR for one-by-one release |
| 06 | Bill deliveries and post billing to accounting | SD | Day −1 | Fiori | Create Billing Documents – Billing Due List ItemsManage Billing Documents | — | Manage Billing Documents posts what did not reach accounting |
| 07 | Last payment run of the month | AP | Day −1 | Fiori | Manage Automatic PaymentsF0770 | — | |
| 08 | Import bank statements | Bank | Day −1 | Fiori + SAP GUI | Bank Statement MonitorF1734 | FF_5 | Import is usually automatic; FF_5 only for manual imports |
| 09 | Clear what the bank statements did not | Bank | Day −1 | Fiori | Reprocess Bank Statement ItemsF1520 | — | |
| 10 | Post recurring entries | GL | Day −1 | Fiori + SAP GUI | Manage Recurring Journal EntriesF1598 | F.14 | The app keeps the recurring documents (G/L accounts only); F.14 posts them |
| 11 | Post physical inventory differences | MM | Day −1 | SAP GUI | — | MI07 | |
| 12 | Open the new materials management period | MM | WD1 | SAP GUI | — | MMPV | Usually a scheduled job |
| 13 | Open the new FI period, keep the old one for closing postings | GL | WD1 | Fiori | Manage Posting PeriodsF2293 | — | |
| 14 | Open the new CO period | CO | WD1 | SAP GUI | — | OKP1 | Public cloud: Manage Posting Periods – Cost Accounting |
| 15 | Settle assets under construction | AA | WD1 | SAP GUI | — | AIBU | |
| 16 | Post depreciation | AA | WD1 | Fiori | Schedule Asset Accounting JobsF1914 | — | |
| 17 | Purchase order accruals: propose, review, post | AP | WD1–WD2 | Fiori | Schedule Accruals JobsReview Purchase Order Accruals – for Cost Accountant | — | Purchase order owners review in My Inbox |
| 18 | Manual accruals and deferrals | GL | WD2 | SAP GUI | — | FBS1 · F.81 | Fixed monthly amounts can be recurring journal entries instead |
| 19 | Reconcile GR/IR and write off old differences | AP | WD2 | Fiori | Reconcile GR/IR AccountsF3302Monitor GR/IR Account ReconciliationF3303 | — | |
| 20 | GR/IR reclassification, foreign currency valuation, regrouping, automatic clearing | GL | WD2 | Fiori | Schedule General Ledger JobsF1927 | — | One job template per step: F.19, FAGL_FCV, FAGLF101 and F.13 |
| 21 | Reconcile intercompany balances | GL | WD2 | Fiori | Schedule Matching RunsManage Assignments – By Matching MethodReconciliation Status Overview | — | Intercompany Matching and Reconciliation (ICMR) |
| 22 | Enter statistical key figures | CO-OM | WD2 | Fiori | Manage Statistical Key Figure ValuesF3915 | — | From SAP S/4HANA 2020; before that KB31N |
| 23 | Settle overhead orders to cost centers | CO-OM | WD3 | SAP GUI | — | KO8G | |
| 24 | Run distributions and assessments | CO-OM | WD3 | Fiori | Run AllocationsF3548 | — | Cycles are kept in Manage Allocations (F3338) |
| 25 | Indirect activity allocation | CO-OM | WD3 | Fiori | Run Indirect Activity Allocation Cost Centers – Actual | — | |
| 26 | Calculate actual activity prices | CO-OM | WD3 | SAP GUI | — | KSII | |
| 27 | Overhead on production orders | CO-PC | WD3 | SAP GUI | — | CO43 | |
| 28 | Work in process | CO-PC | WD3 | SAP GUI | — | KKAO | |
| 29 | Production variances | CO-PC | WD3 | SAP GUI | — | KKS1 | |
| 30 | Settle production orders | CO-PC | WD3 | SAP GUI | — | CO88 | |
| 31 | Distribute usage variances | ML | WD4 | SAP GUI | — | CKMDUVMAT | |
| 32 | Actual costing run | ML | WD4 | Fiori + SAP GUI | Manage Material Valuations | CKMLCP | Run in CKMLCP, check the new prices and values in the app |
| 33 | Results analysis and project settlement | PS | WD4 | SAP GUI | — | KKAJ · CJ8G | |
| 34 | Top-down distribution in margin analysis | CO-PA | WD4 | SAP GUI | — | KE28 | |
| 35 | Check what is left on cost centers | CO-OM | WD4 | Fiori | Cost Centers – Actual/Plan/VarianceF0940 | — | |
| 36 | Lock the CO period | CO | WD4 | SAP GUI | — | OKP1 | |
| 37 | Trial balance | GL | WD5 | Fiori | Trial BalanceF0996A | — | |
| 38 | Financial statements | GL | WD5 | Fiori | Balance Sheet/Income Statement – MultidimensionalF3084 | — | |
| 39 | Tax returns and statutory reports | Tax | WD5 | Fiori | Run Compliance Reports | — | Advanced Compliance Reporting, where it covers your country; otherwise S_ALR_87012357 |
| 40 | Close the FI period for operational postings | GL | WD5 | Fiori | Manage Posting PeriodsF2293 | — |
No month end step matches this filter.
Year end: 12 steps · 5 in Fiori · 0 Fiori + SAP GUI · 7 only in SAP GUI
| # | Step | Area | When | How | Fiori app | SAP GUI | Note |
|---|---|---|---|---|---|---|---|
| 01 | Copy number ranges to the new fiscal year | GL | Before year end | SAP GUI | — | OBH2 | |
| 02 | Plan activity prices for the new year | CO-OM | Before year end | SAP GUI | — | KP26 | |
| 03 | Costing run for the new standard costs | CO-PC | Before year end | SAP GUI | — | CK40N | |
| 04 | Balance confirmations to customers and suppliers | AR · AP | Year end | SAP GUI | — | F.17 · F.18 | Public cloud has an app for customers (F2834) |
| 05 | Physical inventory count and differences | MM | Year end | SAP GUI | — | MI07 | |
| 06 | Recalculate depreciation if rules changed | AA | Year end | Fiori | Schedule Asset Accounting JobsF1914 | — | |
| 07 | Month-end close for period 12 | Close | WD1–WD5 | Fiori | Process Closing Tasks (Classic) | — | Every step of the month-end list |
| 08 | Balance carryforward to the new year | GL | First days of the new year | Fiori | Carry Forward BalancesF1596 | — | Customers, suppliers and assets included; no AJRW in SAP S/4HANA |
| 09 | Release the new standard costs | CO-PC | First day of the new year | SAP GUI | — | CK24 | |
| 10 | Open special periods 13–16 for audit adjustments | GL | After period 12 | Fiori | Manage Posting PeriodsF2293 | — | Ideally with an authorization group, for the closing team only |
| 11 | Asset year-end closing | AA | After the last depreciation run | SAP GUI | — | AJAB | |
| 12 | Close the old fiscal year | GL | After the audit | Fiori | Manage Posting PeriodsF2293 | — | Late postings to the old year still update the new opening balances |
No year end step matches this filter.
Keep the SAP GUI steps in the launchpad. Add the transactions marked SAP GUI as tiles in the closing role, so the whole close runs from one place and nobody has to remember a transaction code.
Release matters. This list is for SAP S/4HANA on-premise and private cloud, 2020 or later. Public cloud has no SAP GUI and offers apps for most of the SAP GUI rows; older releases have fewer apps.
App names and IDs from the SAP Fiori apps reference library, SAP Learning and SAP Help; check the library for your release before you design the closing role.
A fast close is mostly work moved out of the close: reconciled during the month, automated in job chains and protected by clean master data.
GR/IR, bank and intercompany differences are cheaper to clear on the day they appear than on WD1, when everyone is waiting.
Cut-off times for logistics, a named owner and a deadline for every step, published before the month starts.
Collective transactions in job chains with dependencies, so the next step starts when the last one finishes, not when someone checks.
Settlement rules, released cost estimates, activity prices and tracing factors cause most CO errors. Check them in the last week of the month.
Product costing and the material ledger usually set the end date. Start them as soon as logistics and the cycles are done.
Fewer manual estimates in the monthly management close; the full set of adjustments at quarter and year end.
Troubleshooting
The same handful of problems stops most closes. Each one is quicker to prevent than to fix on WD3.
| Symptom | Usual cause | Fix |
|---|---|---|
| “Posting period … is not open” | The period is closed for that account type (+, A, D, K, M, S), or for CO postings that create FI documents | Open it in OB52 or the Manage Posting Periods app; for postings from CO, check interval 3 and OKP1 |
| An allocation cycle posts nothing | No tracing factor for the period, or the senders are already empty | Enter the statistical key figures (KB31N), run the cycle in test mode and check each segment’s senders and receivers |
| Under- or over-absorption left on cost centers | Activity prices not recalculated, or the activity type not set for actual prices | Run KSII after the cycles; check actual price indicator 5 on the activity type (KL02) and revaluation in the CO version (OKEQ) |
| Variances missing or in error | No released standard cost estimate for the material, or no variance key on the order | Release the cost estimate (CK40N or CK24) and check the order’s variance key before the close |
| Settlement fails | Missing settlement rule, or the period is locked for settlement | Generate or maintain the settlement rule and check the period lock in OKP1 |
| Costing run stops in Settlement | Orders not settled, the next MM period not opened, or materials with errors | Read the logs in CKMLCP, look for undistributed differences in CKMVFM, settle and run again |
| Balance carryforward stops on retained earnings | A profit and loss account has no retained earnings account assigned | Assign it in OB53 and run FAGLGVTR again |
| GR/IR balance keeps growing | Receipts and invoices out of step, old differences never cleared | Work the items in Reconcile GR/IR Accounts during the month; write off approved old differences with MR11 |
Transactions
The SAP GUI transactions you meet in a close, with where each one runs: SAP ERP 6.0 (ECC), SAP S/4HANA on-premise and private cloud, and the Fiori app that does the same job in SAP S/4HANA when there is one. Rows on a cream background exist only in SAP ECC.
78 transactions
| Transaction | What it does | Area | When | SAP ECC | SAP S/4HANA | Fiori app (SAP S/4HANA) |
|---|---|---|---|---|---|---|
MIGO | Goods movements | MM | Until cut-off | Yes | Yes | SAP GUI |
CO11N | Confirm production orders | PP | Until cut-off | Yes | Yes | SAP GUI |
MI07 | Post physical inventory differences | MM | Day −1 | Yes | Yes | SAP GUI |
VF04 | Billing due list | SD | Day −1 | Yes | Yes | SAP GUI |
VFX3 | Release billing documents to accounting | SD | Day −1 | Yes | Yes | SAP GUI |
MMPV | Open the next materials management period | MM | WD1 | Yes | Yes | SAP GUI |
OB52 | Open and close FI posting periods | FI-GL | WD1 and WD5 | Yes | Yes | Manage Posting PeriodsF2293 |
F.14 | Run recurring entries | FI-GL | Day −1 | Yes | Yes | SAP GUI |
FBS1 | Enter accrual or deferral document | FI-GL | WD2 | Yes | Yes | SAP GUI |
F.81 | Reverse accrual and deferral documents | FI-GL | Next period | Yes | Yes | SAP GUI |
FAGL_FCV | Foreign currency valuation | FI-GL | WD2 | Yes | Yes | Schedule General Ledger JobsF1927 |
FAGLF101 | Regroup receivables and payables | FI-GL | WD2 | Yes | Yes | Schedule General Ledger JobsF1927 |
F.5D · F.5E | Balance sheet adjustment by business area | FI-GL | WD2 | Classic G/L | RemovedDocument splitting builds these balance sheets | — |
F.50 | Profit and loss adjustment | FI-GL | WD2 | Classic G/L | RemovedDocument splitting builds these balance sheets | — |
F.13 | Automatic clearing | FI-GL | Day −1 to WD2 | Yes | Yes | Schedule General Ledger JobsF1927 |
FBL3H | G/L account line items | FI-GL | Any time | NoUse FBL3N | Yes | Display Line Items in General LedgerF2217 |
F.01 | Financial statements | FI-GL | WD5 | Yes | Yes | SAP GUI |
F110 | Payment run | FI-AP | Day −1 | Yes | Yes | SAP GUI |
MRBR | Release blocked invoices | FI-AP | Day −2 | Yes | Yes | SAP GUI |
MR11 | GR/IR account maintenance: write off differences | FI-AP | WD2 | Yes | Yes | Reconcile GR/IR AccountsF3302 |
F.19 | Analyze and reclassify GR/IR clearing accounts | FI-AP | WD2 | Yes | Yes | Schedule General Ledger JobsF1927 |
ACEPROPOSALRUN | Propose purchase order accrual amounts | FI-AP | WD1 | NoAccrue by hand (FBS1) | Yes | Schedule Accruals Jobs |
ACEPOSTINGRUN | Post purchase order accruals | FI-AP | WD2 | NoAccrue by hand (FBS1) | Yes | Schedule Accruals Jobs |
F150 | Dunning run | FI-AR | Weekly | Yes | Yes | SAP GUI |
F107 | Valuation run for doubtful receivables | FI-AR | WD2 | Yes | Yes | SAP GUI |
FF_5 | Import electronic bank statement | Bank | Daily | Yes | Yes | SAP GUI |
FEBAN | Post-process bank statements | Bank | Daily | Yes | Yes | Reprocess Bank Statement ItemsF1520 |
FBCJ | Cash journal | Bank | Day −1 | Yes | Yes | SAP GUI |
AIBU | Settle assets under construction | FI-AA | WD1 | Yes | Yes | SAP GUI |
AFAB | Post depreciation | FI-AA | WD1 | Yes | Yes | Schedule Asset Accounting JobsF1914 |
ASKB · ASKBN | Periodic posting of parallel depreciation areas | FI-AA | WD1 | Yes | RemovedEvery area posts in real time | — |
AW01N | Asset Explorer | FI-AA | Any time | Yes | Yes | SAP GUI |
S_ALR_87011990 | Asset history sheet | FI-AA | WD5 | Yes | Yes | SAP GUI |
S_ALR_87012357 | Advance return for tax on sales and purchases | Tax | WD5 | Yes | Yes | SAP GUI |
OKP1 | CO period lock | CO | WD1 and WD4 | Yes | Yes | SAP GUI |
KB31N | Enter statistical key figures | CO-OM | WD2 | Yes | Yes | Manage Statistical Key Figure ValuesF3915 |
KO8G | Settle internal orders, collective | CO-OM | WD3 | Yes | Yes | SAP GUI |
KO88 | Settle one order | CO-OM | WD3 | Yes | Yes | SAP GUI |
KSV5 | Run distribution cycles | CO-OM | WD3 | Yes | Yes | Run AllocationsF3548 |
KSU5 | Run assessment cycles | CO-OM | WD3 | Yes | Yes | Run AllocationsF3548 |
KSC5 | Indirect activity allocation | CO-OM | WD3 | Yes | Yes | SAP GUI |
KSII | Actual activity price calculation | CO-OM | WD3 | Yes | Yes | SAP GUI |
KSBT | Display activity prices | CO-OM | WD3 | Yes | Yes | SAP GUI |
S_ALR_87013611 | Cost centers: actual/plan/variance | CO-OM | WD3 | Yes | Yes | Cost Centers – Actual/Plan/VarianceF0940 |
KALC | CO-FI reconciliation posting (reconciliation ledger) | CO | WD4 | Classic G/LNew G/L: real-time integration instead | RemovedBlocked: CO already posts to the G/L | — |
1KEK | Transfer payables and receivables to profit center accounting | EC-PCA | WD2 | Classic G/LWith classic EC-PCA | Not neededProfit center on every journal line | — |
CO43 | Overhead on orders, collective | CO-PC | WD3 | Yes | Yes | SAP GUI |
KGI2 | Overhead on one order | CO-PC | WD3 | Yes | Yes | SAP GUI |
KKAO | Work in process, collective | CO-PC | WD3 | Yes | Yes | SAP GUI |
KKAX | Work in process, one order | CO-PC | WD3 | Yes | Yes | SAP GUI |
KKS1 | Variances, collective | CO-PC | WD3 | Yes | Yes | SAP GUI |
KKS2 | Variances, one order | CO-PC | WD3 | Yes | Yes | SAP GUI |
CO88 | Settle production orders, collective | CO-PC | WD3 | Yes | Yes | SAP GUI |
CKMDUVMAT | Distribute usage variances of materials | ML | WD4 | Yes | Yes | SAP GUI |
CKMDUVACT | Distribute usage variances of activities | ML | WD4 | Yes | Yes | SAP GUI |
CKMLCP | Actual costing cockpit (costing run) | ML | WD4 | YesEight steps | YesFive steps | SAP GUI |
CKM3 | Material price analysis | ML | WD4 | Yes | Yes | SAP GUI |
CKMVFM | Value flow monitor | ML | WD4 | Yes | Yes | SAP GUI |
CJ45 | Overhead on projects, collective | PS | WD4 | Yes | Yes | SAP GUI |
KKAJ | Results analysis, collective | PS | WD4 | Yes | Yes | SAP GUI |
CJ8G | Settle projects, collective | PS | WD4 | Yes | Yes | SAP GUI |
KE28 | Top-down distribution | CO-PA | WD4 | Yes | Yes | SAP GUI |
KE30 | Profitability reports | CO-PA | WD5 | Yes | Yes | SAP GUI |
OBH2 | Copy number ranges to the new fiscal year | FI-GL | Before year end | Yes | Yes | SAP GUI |
F.17 | Customer balance confirmation | FI-AR | Year end | Yes | Yes | SAP GUI |
F.18 | Supplier balance confirmation | FI-AP | Year end | Yes | Yes | SAP GUI |
AFAR | Recalculate depreciation | FI-AA | Year end | Yes | Yes | Schedule Asset Accounting JobsF1914 |
ABST2 | Reconcile Asset Accounting with the G/L | FI-AA | Before AJAB | Yes | RemovedAssets and G/L share one journal entry | — |
AJAB | Asset year-end closing | FI-AA | After the last depreciation run | Yes | Yes | SAP GUI |
AJRW | Asset fiscal year change | FI-AA | Start of new year | Yes | RemovedFAGLGVTR does it | — |
FAGLGVTR | Balance carryforward to the new year | FI-GL | Start of new year | YesNew G/L | YesAssets included | Carry Forward BalancesF1596 |
F.07 | Customer and supplier balance carryforward | FI-AP/AR | Start of new year | Yes | Yes | SAP GUI |
OB53 | Retained earnings account (configuration) | FI-GL | Before carryforward | Yes | Yes | SAP GUI |
KP26 | Plan activity prices for the new year | CO-OM | Before year end | Yes | Yes | SAP GUI |
CK40N | Costing run for new standard costs | CO-PC | Before year end | Yes | Yes | SAP GUI |
CK24 | Mark and release standard cost estimates | CO-PC | Start of new year | Yes | Yes | SAP GUI |
FCLOCO | Financial Closing cockpit | Tools | Every close | Add-onECC also has the Closing Cockpit (CLOCO) | YesIn the core from 1709 | Process Closing Tasks (Classic) |
SCMA | Schedule Manager | Tools | Every close | Yes | Yes | SAP GUI |
No transaction matches. Try a code such as AFAB or a word such as reconciliation.
App names and IDs as listed in the SAP Fiori apps reference library; they change between releases, and SAP S/4HANA Cloud Public Edition has its own set. Transactions without an app still run in SAP GUI, and the Fiori launchpad can open them as tiles.
Month-end closing finishes one period: postings, accruals, valuations, allocations, product costing and the period lock. Year-end closing runs the same steps for the last period and then closes the fiscal year: asset year-end closing (AJAB), balance carryforward to the new year (FAGLGVTR), retained earnings, number ranges and the special periods 13–16 for audit adjustments.
Statistical key figures, settlement of overhead orders, distributions and assessments, indirect activity allocation, actual price calculation, then on production orders overhead, work in process, variances and settlement. The material ledger costing run follows, and margin analysis comes last. Each step reads what the one before it posted.
No. FI and CO post to the same journal entry in the Universal Journal (ACDOCA), so the reconciliation ledger of SAP ERP is gone. You still check that cost centers are empty, orders are settled and the costing run has no errors before you lock the period.
Yes. Planned depreciation is recalculated with every asset transaction, but the depreciation run (AFAB, or the Schedule Asset Accounting Jobs app) still posts it to the general ledger each period. What disappeared is the separate periodic posting of parallel depreciation areas (ASKB) and the fiscal year change with AJRW.
MMPV moves the current materials management period forward for a company code. Materials management keeps the current and the previous period open, so after MMPV on WD1 goods movements can usually still be posted to the month being closed while the month before it is closed. The material ledger costing run needs the next period open.
A soft close produces management figures with fewer manual adjustments, accepting estimates where the effect is small. A hard close books every adjustment needed for statutory reporting, usually at quarter and year end.
A cloud application on SAP BTP for planning and running the entity close. It holds the task lists and dependencies, schedules jobs in the connected SAP S/4HANA Cloud, SAP S/4HANA and SAP ERP systems, and shows status and the critical path in one place.
Only if it is opened again in OB52, which should be controlled. A common setup keeps interval 1 for closing postings with an authorization group, so only the closing team can post while the period stays closed for everyone else.
Checked in October 2026.
Your vote could not be sent. Please try again.