1. Home
  2. Modules
  3. Period-end closing

SAP period-end closing: the FI and CO close, step by step

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.

  • FI-GL
  • AP and AR
  • Asset Accounting
  • CO-OM
  • CO-PC
  • Material Ledger
  • Margin Analysis
The close is a relay8 steps
  1. 01Logistics cut-offMM · SD · PP
  2. 02SubledgersAP · AR · AA
  3. 03Accruals and valuationFI-GL
  4. 04Overhead allocationsCO-OM
  5. 05Product costingCO-PC
  6. 06Actual costingML
  7. 07Projects and profitabilityPS · CO-PA
  8. 08Reporting and lockGL · Tax · Group

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.

What is period-end closing in SAP?

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

The close calendar: an example five-day close

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.

Example close calendar: which area works on which day, from two days before month end to the fifth working day.
Logistics cut-offDay −2 to WD1: Goods movements · billing · MMPV
Payables and receivablesDay −2 to WD2: Invoices · payments · PO accruals · GR/IR
Fixed assetsWD1: AIBU · AFAB
General ledgerDay −1 to WD2: Recurring · accruals · FX valuation
Overhead (CO-OM)WD2 to WD3: Key figures · cycles · KSII
Product costing (CO-PC)WD3: WIP · CO88
Material ledgerWD4: CKMLCP
Projects and CO-PAWD4: CJ8G · KE28
Reporting and lockWD4 to WD5: Lock · statements · tax · group
  • Logistics
  • Financial Accounting
  • Controlling
  • Reporting
  • Month end

Close checklist, day by day

Pick a day and tick the tasks as they finish. The ticks stay on this page only: nothing is saved.

Day

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.

Day −1

Last working day of the month

Billing, payments and bank statements bring receivables, payables and cash up to date.

Hands over: complete subledgers and bank balances.

WD1

First working day

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

Accruals and valuation

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

Controlling day

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

Actual costing and profitability

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

Report and lock

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

The FI close: make the balance sheet right

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.

FI area

General ledger

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.

Posting periods

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.

Recurring entries

F.14

Posts the recurring documents set up with FBD1, such as rents, leases or fixed fees.

Accruals and deferrals

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.

Foreign currency valuation

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.

Regrouping

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.

Automatic clearing

F.13

Clears open items that balance to zero on open-item-managed accounts, such as bank clearing and GR/IR accounts.

Trial balance and statements

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.

Payables

Every goods receipt and supplier invoice of the period is in, and whatever has been received but not invoiced is accrued.

Invoices and blocked invoices

MIROMRBR

Post the invoices received for the period and release those blocked for price or quantity once the difference is explained.

Payment run

F110

Pays due items and clears them. Schedule the last run of the month before the cut-off so bank and payables agree.

GR/IR reconciliation

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.

Purchase order accruals

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.

Supplier balance confirmation

F.18

Sends balance confirmations to suppliers, usually at year end or for the auditors.

Receivables

Revenue and receivables are complete, cash is applied, and receivables at risk are valued.

Billing to accounting

VF04VFX3

Bill every delivery of the period from the billing due list and release billing documents that did not reach accounting.

Incoming payments

FF_5FEBAN

Import the bank statements and post-process the items that did not clear automatically.

Dunning

F150

Runs dunning on overdue items, usually weekly, with a last run before the close.

Doubtful receivables

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.

Credit balances

FAGLF101

Customers with credit balances are shown as liabilities on the balance sheet.

Customer balance confirmation

F.17

Sends balance confirmations to customers, usually at year end.

Fixed assets

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.

Assets under construction

AIBU

Settles the capitalized costs of assets under construction to the final assets when they go into use.

Depreciation run

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.

Check the period

AW01NS_ALR_87011990

Asset Explorer for single assets and the asset history sheet for the movements of the period.

Year end

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.

Bank and cash

Cash is the first number auditors check. Every bank account agrees with its statement and every open item has an explanation.

Bank statements

FF_5FEBAN

Import electronic statements for all accounts up to the last day of the month and post-process what did not clear.

Cash journal

FBCJ

Close each cash journal for the period and agree it with the cash count.

Bank clearing accounts

F.13

Clear the bank clearing accounts automatically and investigate what is left.

Bank reconciliation

FBL3H

The G/L balance of each bank account equals the statement; outstanding items are listed and explained.

Tax

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.

Tax on sales and purchases

S_ALR_87012357

The classic advance return report for tax on sales and purchases (program RFUMSV00), by tax code and period.

Advanced Compliance Reporting

Generates statutory reports and electronic returns for many countries from the posted data, with a monitor for deadlines and submissions.

Brazil

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.

Intercompany

Both sides of every intercompany transaction must agree before group reporting can eliminate them.

Matching

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.

Solve differences

Assign reasons to unmatched items and post adjustments, with an approval workflow if needed.

SAP S/4HANA: Apps: Reconciliation Status Overview and Reconciliation Balances.

Line items by partner

FBL1HFBL5HFBL3H

Check intercompany supplier, customer and G/L items by trading partner.

Group reporting

After the entity close, the data goes to consolidation, for example in SAP S/4HANA Finance for group reporting.

Controlling

The CO close: move every cost to where it is explained

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.

CO area

Overhead (CO-OM)

Empty the service cost centers and overhead orders into the cost centers, orders and products that used them.

  1. Statistical key figures

    KB31N

    Enter the tracing factors the cycles use, such as headcount, floor space or kWh.

  2. Settle overhead orders

    KO8G

    Internal orders that collect overhead settle to their cost centers before the cycles run.

  3. Distribution

    KSV5

    Moves primary costs to the receivers and keeps the original cost element.

  4. Assessment

    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.

  5. Indirect activity allocation

    KSC5

    Allocates activity quantities that are not confirmed directly, based on tracing factors.

  6. Actual price calculation

    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.

  7. Check the cost centers

    S_ALR_87013611KSBT

    Actual, plan and variance by cost center, and the resulting activity prices. Anything left on a cost center should be explained.

Product costing (CO-PC)

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.

  1. Overhead

    CO43KGI2

    Applies the overhead rates of the costing sheet to production orders, collectively or one by one.

  2. Work in process

    KKAOKKAX

    Calculates WIP for orders not yet finally delivered. Product cost collectors value WIP at target cost.

  3. Variances

    KKS1KKS2

    Explains the order balance by variance category: input price, input quantity, resource usage, lot size, output price and others.

  4. Settlement

    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.

  5. Event-based alternative

    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.

Material ledger

With actual costing, the material ledger turns the price differences collected during the month into actual costs of inventory and cost of goods sold.

  1. Before the run

    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.

  2. Usage variances

    CKMDUVMATCKMDUVACT

    Distribute inventory and activity differences to the orders that consumed them.

  3. Costing run

    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.

  4. Post closing

    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.

  5. Analyze

    CKM3CKMVFM

    Material price analysis per material, and the value flow monitor for differences not yet distributed.

Projects and orders

Projects and investment orders carry costs and revenues until they are settled to their receivers.

  1. Overhead on projects

    CJ45CJ44

    Applies overhead rates to WBS elements and networks, collectively or one project at a time.

  2. Results analysis

    KKAJKKA2

    Calculates revenue, cost of sales, work in process or reserves for customer projects, collectively or one project at a time.

  3. Event-based revenue recognition

    Recognizes revenue with each cost, time or billing posting on customer projects, which leaves fewer adjustments for period end.

  4. Project settlement

    CJ8GCJ88

    Settles projects to assets under construction, fixed assets, cost centers or margin analysis.

  5. Investment and accrual orders

    KO8GKO88

    Settle after the overhead orders, to assets, cost centers or other receivers.

Margin analysis (CO-PA)

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.

  1. Check what has arrived

    Billing, cost of goods sold, settled production variances and project settlements must be in before margins are analyzed.

  2. Top-down distribution

    KE28

    Spreads amounts posted at a high level, such as freight or rebates by customer group, down to products and customers.

  3. Margin reports

    KE30

    Margins by product, customer and region. Fiori apps read the same data from ACDOCA.

Reconcile and lock

The last CO steps decide whether the period can really be locked.

  1. No FI–CO reconciliation

    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.

  2. Check what is left

    Cost centers with balances, orders not settled and materials with errors in the costing run are each a reason not to lock yet.

  3. Lock the CO period

    OKP1

    Locks business transactions for the period by controlling area, fiscal year and version.

  4. Close the FI period

    OB52

    Closes the period for operational postings. A closing interval with an authorization group keeps room for late adjustments.

Worked example

How actual price calculation empties a cost center

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.

Values in BRL
Price
Cost center 4100 and its production orders, plan price
ObjectCalculationBRL
Cost center 4100: costs of the monthPrimary and assessed costs120,000.00
Cost center 4100: credit for activity2,000 h × 50.00100,000.00
Balance left on the cost centerUnder-absorbed20,000.00
Production order 10011,200 h × 50.0060,000.00
Production order 1002800 h × 50.0040,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.

Cost center 4100 and its production orders, after ksii
ObjectCalculationBRL
Cost center 4100: costs of the monthPrimary and assessed costs120,000.00
Cost center 4100: credit for activity2,000 h × 60.00120,000.00
Balance left on the cost centerCost center empty0.00
Production order 10011,200 h × 60.0072,000.00
Production order 1002800 h × 60.0048,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

Year-end closing: what comes on top

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.

  • Before the year ends

    • Number ranges for the new year. Copy year-dependent document number ranges with OBH2.
    • Balance confirmations. Customers with F.17 and suppliers with F.18, usually for the auditors.
    • Physical inventory. Count, then post the differences with MI07 before the last costing run.
    • New year in CO. Plan activity prices (KP26) and release the new standard costs (CK40N or CK24).
  • Carry forward

    • Balance carryforward. FAGLGVTR carries forward G/L, customer, supplier and asset balances; F.07 can still carry forward customers and suppliers separately.
    • Retained earnings. Profit and loss accounts close to the retained earnings account set up in OB53.
    • Late postings. After the first carryforward, postings to the old year update the new opening balances automatically.
    • Special periods. Audit adjustments go to periods 13–16, opened in their own interval in OB52, ideally with an authorization group.
  • Asset Accounting

    • Recalculate if needed. AFAR recalculates planned depreciation when rules changed, before the carryforward.
    • Fiscal year change. In SAP S/4HANA it happens with the general ledger carryforward; AJRW is no longer used.
    • Close the old year. AJAB checks that depreciation is fully posted and locks the year for asset postings.
    • Two open years at most. If two years are open, close the earlier one before the next carryforward.

SAP ERP vs SAP S/4HANA

What changed from SAP ERP to 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.

Period-end closing in SAP ERP (ECC) and in SAP S/4HANA
AreaSAP ERP (ECC)SAP S/4HANA
FI and COSeparate 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/LOne Universal Journal (ACDOCA); FI and CO close together, with no reconciliation step; CO postings also check the FI posting periods
Asset AccountingParallel depreciation areas posted periodically (ASKB); fiscal year change with AJRWAll areas post in real time to their ledgers; planned depreciation recalculated with each asset transaction; fiscal year change with the balance carryforward
Material ledgerOptionalAlways active; actual costing optional; costing run reduced from eight steps to five
ProfitabilityCosting-based CO-PA common, kept in its own tables and reconciled with FI separatelyMargin analysis in the Universal Journal; market segment derived with each posting
Foreign currencyFAGL_FCVFAGL_FCV, or Advanced Valuation job templates in SAP S/4HANA Cloud
GR/IRF.19 and MR11, worked through at period endReconcile GR/IR Accounts and Monitor GR/IR Account Reconciliation apps, with optional machine learning proposals, used during the month
AccrualsManual accrual documents (FBS1)Accruals Management: purchase order accruals proposed from the order, reviewed, approved and posted by job
IntercompanyReconciliation with reports and spreadsheetsIntercompany Matching and Reconciliation (ICMR) on ACDOCA in near real time
AllocationsAssessment and distribution cycles (KSU5, KSV5)The same cycles, plus universal allocation: Manage Allocations and Run Allocations apps
Production accountingWIP and variances calculated at period endPeriod-end runs, or event-based WIP and variances in SAP S/4HANA Cloud (scope item 3F0)
OrchestrationSchedule Manager (SCMA), Financial Closing cockpit add-onFinancial Closing cockpit in the core from 1709 (FCLOCO), SAP Advanced Financial Closing on SAP BTP

SAP ECC

Only in SAP ECC: the steps SAP S/4HANA removed

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.

Which SAP ECC do you close?

7 steps that exist only in SAP ECC7 of 7 steps are part of a close with the classic G/L3 of 7 steps are part of a close with the new G/L

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

CO-FI reconciliation posting

Reconciliation · WD4, after the CO cycles

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

Transfer payables and receivables to profit centers

Transfer · WD2

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

Balance sheet adjustment

Adjustment · WD2

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

Profit and loss adjustment

Adjustment · WD2

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

Periodic posting of depreciation areas

Asset Accounting · WD1, with the depreciation run

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

Reconcile Asset Accounting with the G/L

Reconciliation · Year end, before AJAB

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

Asset fiscal year change

Year end · First days of the new year

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

Tools that run the close, and where AI comes in

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.

  • Financial Closing cockpit

    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

  • SAP Advanced Financial Closing

    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

  • Joule Financial Closing Assistant

    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.

    More on Joule

SAP Fiori

Fiori apps for the close

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.

Close step
  • Periods and tasksF2293

    Manage Posting Periods

    Open and close FI posting periods by variant, account type and interval, including the special periods.

    ReplacesOB52

  • Periods and tasksF2581

    Manage Posting Period Variants

    Create posting period variants and assign them to company codes, so several company codes open and close together.

    No SAP GUI equivalent

  • Periods and tasks

    Process Closing Tasks (Classic)

    The SAP S/4HANA Financial Closing cockpit in the launchpad: run and monitor the closing task lists.

    ReplacesFCLOCO

  • General ledgerF1927

    Schedule General Ledger Jobs

    Job templates for foreign currency valuation, regrouping, automatic clearing and the GR/IR reclassification, scheduled and monitored in one place.

    ReplacesFAGL_FCVFAGLF101F.13F.19

  • General ledgerF1596

    Carry Forward Balances

    Balance carryforward to the new fiscal year, for the general ledger and Asset Accounting together.

    ReplacesFAGLGVTR

  • General ledgerF0996A

    Trial Balance

    Balances by period with drill-down to line items, read straight from ACDOCA.

    ReplacesS_ALR_87012277

  • General ledgerF2217

    Display Line Items in General Ledger

    Line items with every Universal Journal field, filtered and saved as views.

    ReplacesFBL3H

  • General ledgerF0717

    Manage Journal Entries

    Find, display and reverse journal entries; filter by intercompany transaction to check both sides.

    ReplacesFB03FB08

  • GR/IRF3302

    Reconcile GR/IR Accounts

    Worklists of purchase order items whose receipts and invoices differ, with status, priority, root cause and write-off. Optional machine learning proposals.

    ReplacesMR11

  • GR/IRNew in S/4HANAF3303

    Monitor GR/IR Account Reconciliation

    Open GR/IR items by age, supplier and company code, with the machine learning proposals on a card.

    No SAP GUI equivalent

  • GR/IRNew in S/4HANAF5796

    GR/IR Process Insights

    Where reconciliation work gets stuck: bottlenecks, repeated work and processing time in days.

    No SAP GUI equivalent

  • Accruals

    Schedule Accruals Jobs

    Transfer purchase orders to the Accrual Engine, propose the period amounts and post them, as jobs.

    ReplacesACEPROPOSALRUNACEPOSTINGRUN

  • Accruals

    Display Purchase Order Accruals

    Planned, actual and accrued amounts per purchase order and month.

    ReplacesPOACTREE03

  • Accruals

    Review Purchase Order Accruals – for Cost Accountant

    Optional review of the proposed amounts by the controller, who can change them before posting.

    ReplacesFACRARVWCO

  • AccrualsNew in S/4HANA

    Manage Workflows for PO Accruals Review

    Who reviews and who approves the proposals, and in which order.

    No SAP GUI equivalent

  • Fixed assetsF1914

    Schedule Asset Accounting Jobs

    The depreciation run and the recalculation of depreciation, scheduled as jobs with their logs.

    ReplacesAFABAFAR

  • Fixed assetsF1616

    Depreciation Lists

    Planned and posted depreciation by asset and depreciation area.

    ReplacesAR03

  • BankF1564

    Manage Bank Statements

    Enter, display and check bank statements.

    ReplacesFF67

  • BankF1520

    Reprocess Bank Statement Items

    Clear the bank statement items that did not post automatically.

    ReplacesFEBAN

  • IntercompanyNew in S/4HANA

    Define Matching Methods

    The rules that pair intercompany documents between company codes.

    No SAP GUI equivalent

  • IntercompanyNew in S/4HANA

    Schedule Matching Runs

    Runs the matching methods on journal entries from ACDOCA.

    No SAP GUI equivalent

  • IntercompanyNew in S/4HANA

    Manage Assignments – By Matching Method

    Work the unmatched items, assign reasons and post adjustments.

    No SAP GUI equivalent

  • IntercompanyNew in S/4HANA

    Reconciliation Status Overview

    Which company code pairs are reconciled for the period and which are not.

    No SAP GUI equivalent

  • IntercompanyNew in S/4HANA

    Reconciliation Balances

    Balances of both sides per partner, with tolerances.

    No SAP GUI equivalent

  • OverheadF3338

    Manage Allocations

    Create and change allocation cycles: overhead allocation (assessment), distribution and more.

    ReplacesKSU1KSV1

  • OverheadF3548

    Run Allocations

    Run the cycles for the period, in test mode first, and reverse them if needed.

    ReplacesKSU5KSV5

  • OverheadF4363

    Allocation Results

    What each run moved, by sender and receiver.

    No SAP GUI equivalent

  • OverheadF3915

    Manage Statistical Key Figure Values

    Enter the tracing factors the cycles use. Available from SAP S/4HANA 2020.

    ReplacesKB31N

  • OverheadF0940

    Cost Centers – Actual/Plan/Variance

    Actual, plan and variance by cost center, to check what is left after the cycles.

    ReplacesS_ALR_87013611

  • Material ledger

    Manage Material Valuations

    Prices and inventory values per material, in every currency and valuation of the material ledger.

    No SAP GUI equivalent

  • Material ledger

    Material Inventory Values – Line Items

    Inventory value changes line by line, before and after the costing run.

    No SAP GUI equivalent

Still in SAP GUI

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

Public cloud is different

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

A Fiori-first close: month end and year end

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.

Close
How the step runs

Month end: 40 steps · 19 in Fiori · 5 Fiori + SAP GUI · 16 only in SAP GUI

  • Fiorian app does the whole step
  • Fiori + SAP GUIan app for most of it, a transaction for the rest
  • SAP GUIno app yet: do not skip it
Month end close step by step, with the Fiori app or the SAP GUI transaction for each step
#StepAreaWhenHowFiori appSAP GUINote
01Run the closing task listCloseEvery dayFioriProcess Closing Tasks (Classic)—The SAP S/4HANA Financial Closing cockpit; templates are set up in FCLOCO
02Post goods receiptsMMDay −2Fiori + SAP GUIPost Goods Receipt for Purchase OrderF0843MIGOGoods issues to orders and transfers still use MIGO
03Confirm production ordersPPDay −2SAP GUI—CO11N
04Post supplier invoicesAPDay −2FioriCreate Supplier InvoiceF0859—
05Release blocked invoicesAPDay −2Fiori + SAP GUISchedule Supplier Invoice Jobs – AdvancedMRBRThe app schedules the automatic release; MRBR for one-by-one release
06Bill deliveries and post billing to accountingSDDay −1FioriCreate Billing Documents – Billing Due List ItemsManage Billing Documents—Manage Billing Documents posts what did not reach accounting
07Last payment run of the monthAPDay −1FioriManage Automatic PaymentsF0770—
08Import bank statementsBankDay −1Fiori + SAP GUIBank Statement MonitorF1734FF_5Import is usually automatic; FF_5 only for manual imports
09Clear what the bank statements did notBankDay −1FioriReprocess Bank Statement ItemsF1520—
10Post recurring entriesGLDay −1Fiori + SAP GUIManage Recurring Journal EntriesF1598F.14The app keeps the recurring documents (G/L accounts only); F.14 posts them
11Post physical inventory differencesMMDay −1SAP GUI—MI07
12Open the new materials management periodMMWD1SAP GUI—MMPVUsually a scheduled job
13Open the new FI period, keep the old one for closing postingsGLWD1FioriManage Posting PeriodsF2293—
14Open the new CO periodCOWD1SAP GUI—OKP1Public cloud: Manage Posting Periods – Cost Accounting
15Settle assets under constructionAAWD1SAP GUI—AIBU
16Post depreciationAAWD1FioriSchedule Asset Accounting JobsF1914—
17Purchase order accruals: propose, review, postAPWD1–WD2FioriSchedule Accruals JobsReview Purchase Order Accruals – for Cost Accountant—Purchase order owners review in My Inbox
18Manual accruals and deferralsGLWD2SAP GUI—FBS1 · F.81Fixed monthly amounts can be recurring journal entries instead
19Reconcile GR/IR and write off old differencesAPWD2FioriReconcile GR/IR AccountsF3302Monitor GR/IR Account ReconciliationF3303—
20GR/IR reclassification, foreign currency valuation, regrouping, automatic clearingGLWD2FioriSchedule General Ledger JobsF1927—One job template per step: F.19, FAGL_FCV, FAGLF101 and F.13
21Reconcile intercompany balancesGLWD2FioriSchedule Matching RunsManage Assignments – By Matching MethodReconciliation Status Overview—Intercompany Matching and Reconciliation (ICMR)
22Enter statistical key figuresCO-OMWD2FioriManage Statistical Key Figure ValuesF3915—From SAP S/4HANA 2020; before that KB31N
23Settle overhead orders to cost centersCO-OMWD3SAP GUI—KO8G
24Run distributions and assessmentsCO-OMWD3FioriRun AllocationsF3548—Cycles are kept in Manage Allocations (F3338)
25Indirect activity allocationCO-OMWD3FioriRun Indirect Activity Allocation Cost Centers – Actual—
26Calculate actual activity pricesCO-OMWD3SAP GUI—KSII
27Overhead on production ordersCO-PCWD3SAP GUI—CO43
28Work in processCO-PCWD3SAP GUI—KKAO
29Production variancesCO-PCWD3SAP GUI—KKS1
30Settle production ordersCO-PCWD3SAP GUI—CO88
31Distribute usage variancesMLWD4SAP GUI—CKMDUVMAT
32Actual costing runMLWD4Fiori + SAP GUIManage Material ValuationsCKMLCPRun in CKMLCP, check the new prices and values in the app
33Results analysis and project settlementPSWD4SAP GUI—KKAJ · CJ8G
34Top-down distribution in margin analysisCO-PAWD4SAP GUI—KE28
35Check what is left on cost centersCO-OMWD4FioriCost Centers – Actual/Plan/VarianceF0940—
36Lock the CO periodCOWD4SAP GUI—OKP1
37Trial balanceGLWD5FioriTrial BalanceF0996A—
38Financial statementsGLWD5FioriBalance Sheet/Income Statement – MultidimensionalF3084—
39Tax returns and statutory reportsTaxWD5FioriRun Compliance Reports—Advanced Compliance Reporting, where it covers your country; otherwise S_ALR_87012357
40Close the FI period for operational postingsGLWD5FioriManage 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

  • Fiorian app does the whole step
  • Fiori + SAP GUIan app for most of it, a transaction for the rest
  • SAP GUIno app yet: do not skip it
Year end close step by step, with the Fiori app or the SAP GUI transaction for each step
#StepAreaWhenHowFiori appSAP GUINote
01Copy number ranges to the new fiscal yearGLBefore year endSAP GUI—OBH2
02Plan activity prices for the new yearCO-OMBefore year endSAP GUI—KP26
03Costing run for the new standard costsCO-PCBefore year endSAP GUI—CK40N
04Balance confirmations to customers and suppliersAR · APYear endSAP GUI—F.17 · F.18Public cloud has an app for customers (F2834)
05Physical inventory count and differencesMMYear endSAP GUI—MI07
06Recalculate depreciation if rules changedAAYear endFioriSchedule Asset Accounting JobsF1914—
07Month-end close for period 12CloseWD1–WD5FioriProcess Closing Tasks (Classic)—Every step of the month-end list
08Balance carryforward to the new yearGLFirst days of the new yearFioriCarry Forward BalancesF1596—Customers, suppliers and assets included; no AJRW in SAP S/4HANA
09Release the new standard costsCO-PCFirst day of the new yearSAP GUI—CK24
10Open special periods 13–16 for audit adjustmentsGLAfter period 12FioriManage Posting PeriodsF2293—Ideally with an authorization group, for the closing team only
11Asset year-end closingAAAfter the last depreciation runSAP GUI—AJAB
12Close the old fiscal yearGLAfter the auditFioriManage 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.

Six habits of a fast close

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.

Days to close the month · APQC, 2017
  • Top performers4.8
  • Median6.4
  • Bottom performers10
  1. 01

    Reconcile during the month

    GR/IR, bank and intercompany differences are cheaper to clear on the day they appear than on WD1, when everyone is waiting.

  2. 02

    One calendar, one owner per task

    Cut-off times for logistics, a named owner and a deadline for every step, published before the month starts.

  3. 03

    Automate the batch

    Collective transactions in job chains with dependencies, so the next step starts when the last one finishes, not when someone checks.

  4. 04

    Fix master data before the close

    Settlement rules, released cost estimates, activity prices and tracing factors cause most CO errors. Check them in the last week of the month.

  5. 05

    Watch the critical path

    Product costing and the material ledger usually set the end date. Start them as soon as logistics and the cycles are done.

  6. 06

    Soft close monthly, hard close quarterly

    Fewer manual estimates in the monthly management close; the full set of adjustments at quarter and year end.

Troubleshooting

When the close stops: common causes

The same handful of problems stops most closes. Each one is quicker to prevent than to fix on WD3.

Common period-end closing problems, their usual cause and the fix
SymptomUsual causeFix
“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 documentsOpen it in OB52 or the Manage Posting Periods app; for postings from CO, check interval 3 and OKP1
An allocation cycle posts nothingNo tracing factor for the period, or the senders are already emptyEnter 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 centersActivity prices not recalculated, or the activity type not set for actual pricesRun 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 errorNo released standard cost estimate for the material, or no variance key on the orderRelease the cost estimate (CK40N or CK24) and check the order’s variance key before the close
Settlement failsMissing settlement rule, or the period is locked for settlementGenerate or maintain the settlement rule and check the period lock in OKP1
Costing run stops in SettlementOrders not settled, the next MM period not opened, or materials with errorsRead the logs in CKMLCP, look for undistributed differences in CKMVFM, settle and run again
Balance carryforward stops on retained earningsA profit and loss account has no retained earnings account assignedAssign it in OB53 and run FAGLGVTR again
GR/IR balance keeps growingReceipts and invoices out of step, old differences never clearedWork the items in Reconcile GR/IR Accounts during the month; write off approved old differences with MR11

Transactions

Transactions for period-end closing

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.

  • Yesruns there
  • Classic G/Lonly with the classic general ledger
  • Add-onseparate add-on
  • Nodoes not exist there
  • Removedgone in SAP S/4HANA
  • Not neededno longer part of the close
SAP transactions used in period-end closing, in SAP ECC and SAP S/4HANA, with the Fiori app
TransactionWhat it doesAreaWhenSAP ECCSAP S/4HANAFiori app (SAP S/4HANA)
MIGOGoods movementsMMUntil cut-offYesYesSAP GUI
CO11NConfirm production ordersPPUntil cut-offYesYesSAP GUI
MI07Post physical inventory differencesMMDay −1YesYesSAP GUI
VF04Billing due listSDDay −1YesYesSAP GUI
VFX3Release billing documents to accountingSDDay −1YesYesSAP GUI
MMPVOpen the next materials management periodMMWD1YesYesSAP GUI
OB52Open and close FI posting periodsFI-GLWD1 and WD5YesYesManage Posting PeriodsF2293
F.14Run recurring entriesFI-GLDay −1YesYesSAP GUI
FBS1Enter accrual or deferral documentFI-GLWD2YesYesSAP GUI
F.81Reverse accrual and deferral documentsFI-GLNext periodYesYesSAP GUI
FAGL_FCVForeign currency valuationFI-GLWD2YesYesSchedule General Ledger JobsF1927
FAGLF101Regroup receivables and payablesFI-GLWD2YesYesSchedule General Ledger JobsF1927
F.5D · F.5EBalance sheet adjustment by business areaFI-GLWD2Classic G/LRemovedDocument splitting builds these balance sheets—
F.50Profit and loss adjustmentFI-GLWD2Classic G/LRemovedDocument splitting builds these balance sheets—
F.13Automatic clearingFI-GLDay −1 to WD2YesYesSchedule General Ledger JobsF1927
FBL3HG/L account line itemsFI-GLAny timeNoUse FBL3NYesDisplay Line Items in General LedgerF2217
F.01Financial statementsFI-GLWD5YesYesSAP GUI
F110Payment runFI-APDay −1YesYesSAP GUI
MRBRRelease blocked invoicesFI-APDay −2YesYesSAP GUI
MR11GR/IR account maintenance: write off differencesFI-APWD2YesYesReconcile GR/IR AccountsF3302
F.19Analyze and reclassify GR/IR clearing accountsFI-APWD2YesYesSchedule General Ledger JobsF1927
ACEPROPOSALRUNPropose purchase order accrual amountsFI-APWD1NoAccrue by hand (FBS1)YesSchedule Accruals Jobs
ACEPOSTINGRUNPost purchase order accrualsFI-APWD2NoAccrue by hand (FBS1)YesSchedule Accruals Jobs
F150Dunning runFI-ARWeeklyYesYesSAP GUI
F107Valuation run for doubtful receivablesFI-ARWD2YesYesSAP GUI
FF_5Import electronic bank statementBankDailyYesYesSAP GUI
FEBANPost-process bank statementsBankDailyYesYesReprocess Bank Statement ItemsF1520
FBCJCash journalBankDay −1YesYesSAP GUI
AIBUSettle assets under constructionFI-AAWD1YesYesSAP GUI
AFABPost depreciationFI-AAWD1YesYesSchedule Asset Accounting JobsF1914
ASKB · ASKBNPeriodic posting of parallel depreciation areasFI-AAWD1YesRemovedEvery area posts in real time—
AW01NAsset ExplorerFI-AAAny timeYesYesSAP GUI
S_ALR_87011990Asset history sheetFI-AAWD5YesYesSAP GUI
S_ALR_87012357Advance return for tax on sales and purchasesTaxWD5YesYesSAP GUI
OKP1CO period lockCOWD1 and WD4YesYesSAP GUI
KB31NEnter statistical key figuresCO-OMWD2YesYesManage Statistical Key Figure ValuesF3915
KO8GSettle internal orders, collectiveCO-OMWD3YesYesSAP GUI
KO88Settle one orderCO-OMWD3YesYesSAP GUI
KSV5Run distribution cyclesCO-OMWD3YesYesRun AllocationsF3548
KSU5Run assessment cyclesCO-OMWD3YesYesRun AllocationsF3548
KSC5Indirect activity allocationCO-OMWD3YesYesSAP GUI
KSIIActual activity price calculationCO-OMWD3YesYesSAP GUI
KSBTDisplay activity pricesCO-OMWD3YesYesSAP GUI
S_ALR_87013611Cost centers: actual/plan/varianceCO-OMWD3YesYesCost Centers – Actual/Plan/VarianceF0940
KALCCO-FI reconciliation posting (reconciliation ledger)COWD4Classic G/LNew G/L: real-time integration insteadRemovedBlocked: CO already posts to the G/L—
1KEKTransfer payables and receivables to profit center accountingEC-PCAWD2Classic G/LWith classic EC-PCANot neededProfit center on every journal line—
CO43Overhead on orders, collectiveCO-PCWD3YesYesSAP GUI
KGI2Overhead on one orderCO-PCWD3YesYesSAP GUI
KKAOWork in process, collectiveCO-PCWD3YesYesSAP GUI
KKAXWork in process, one orderCO-PCWD3YesYesSAP GUI
KKS1Variances, collectiveCO-PCWD3YesYesSAP GUI
KKS2Variances, one orderCO-PCWD3YesYesSAP GUI
CO88Settle production orders, collectiveCO-PCWD3YesYesSAP GUI
CKMDUVMATDistribute usage variances of materialsMLWD4YesYesSAP GUI
CKMDUVACTDistribute usage variances of activitiesMLWD4YesYesSAP GUI
CKMLCPActual costing cockpit (costing run)MLWD4YesEight stepsYesFive stepsSAP GUI
CKM3Material price analysisMLWD4YesYesSAP GUI
CKMVFMValue flow monitorMLWD4YesYesSAP GUI
CJ45Overhead on projects, collectivePSWD4YesYesSAP GUI
KKAJResults analysis, collectivePSWD4YesYesSAP GUI
CJ8GSettle projects, collectivePSWD4YesYesSAP GUI
KE28Top-down distributionCO-PAWD4YesYesSAP GUI
KE30Profitability reportsCO-PAWD5YesYesSAP GUI
OBH2Copy number ranges to the new fiscal yearFI-GLBefore year endYesYesSAP GUI
F.17Customer balance confirmationFI-ARYear endYesYesSAP GUI
F.18Supplier balance confirmationFI-APYear endYesYesSAP GUI
AFARRecalculate depreciationFI-AAYear endYesYesSchedule Asset Accounting JobsF1914
ABST2Reconcile Asset Accounting with the G/LFI-AABefore AJABYesRemovedAssets and G/L share one journal entry—
AJABAsset year-end closingFI-AAAfter the last depreciation runYesYesSAP GUI
AJRWAsset fiscal year changeFI-AAStart of new yearYesRemovedFAGLGVTR does it—
FAGLGVTRBalance carryforward to the new yearFI-GLStart of new yearYesNew G/LYesAssets includedCarry Forward BalancesF1596
F.07Customer and supplier balance carryforwardFI-AP/ARStart of new yearYesYesSAP GUI
OB53Retained earnings account (configuration)FI-GLBefore carryforwardYesYesSAP GUI
KP26Plan activity prices for the new yearCO-OMBefore year endYesYesSAP GUI
CK40NCosting run for new standard costsCO-PCBefore year endYesYesSAP GUI
CK24Mark and release standard cost estimatesCO-PCStart of new yearYesYesSAP GUI
FCLOCOFinancial Closing cockpitToolsEvery closeAdd-onECC also has the Closing Cockpit (CLOCO)YesIn the core from 1709Process Closing Tasks (Classic)
SCMASchedule ManagerToolsEvery closeYesYesSAP GUI

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.

Frequently asked questions

What is the difference between month-end and year-end closing in SAP?

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.

In what order should the CO period-end steps run?

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.

Do I still have to reconcile FI and CO in SAP S/4HANA?

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.

Is the depreciation run still needed in SAP S/4HANA?

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.

What does MMPV do, and when do I run it?

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.

What is the difference between a soft close and a hard close?

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.

What is SAP Advanced Financial Closing?

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.

Can I post to a period that is already closed?

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.

References

Checked in October 2026.