SAP FI explained: finance in SAP

Written by an SAP Finance & Treasury practitioner working with SAP since 2008 · how the guides are written · Updated 10 October 2026

SAP FI (Financial Accounting) is the SAP area that keeps a company's statutory books — general ledger, payables, receivables, fixed assets, bank accounting, tax — and runs the record to report close that turns daily postings into financial statements. It is the view auditors and tax authorities read, as distinct from Controlling, which cuts the same postings for management.

Many projects staff both halves with one person, the FICO consultant.

Which FI design decisions cannot be undone later?

Currencies, ledgers and document splitting: each costs a project to change once postings exist. A company code carries a chart of accounts, a fiscal year variant and a set of currencies fixed when it is created: the local currency the books are kept in, the group currency consolidation reads, and sometimes a hard or index currency for a high-inflation country. Adding a currency afterwards is a conversion project, not a switch.

The leading ledger carries the group accounting principle; non-leading ledgers carry local GAAP, and can run their own fiscal year variant where a subsidiary's statutory year differs. Most documents post to every assigned ledger at once, and only valuation postings are written to one ledger deliberately. Document splitting sits underneath all of it: pick the splitting characteristics — profit centre, segment, business area — and the system will produce a balance sheet below company code level, at the price of every document needing a characteristic it can inherit or derive. Splitting is the single choice new FI consultants underestimate, because changing it after the first close means rebuilding the ledger.

How does an auditor follow an FI document trail?

By document type and number range first, then from original document to follow-on document to clearing document. Every posting is a document with a type, and the type is doing more work than it looks: it fixes the account types allowed, the number range, and whether that range restarts each fiscal year or runs continuously. Journal entries, vendor invoices, invoices arriving from invoice verification, customer invoices, incoming and outgoing payments and clearing documents each get their own, so a range gap is a question an auditor is entitled to ask. Who was allowed to post those documents in the first place is the other half of the audit, and it belongs to SAP GRC and its access risk analysis.

Underneath, posting keys decide debit or credit and which account type a line addresses, and the field status group on the account decides what the person posting must fill in — which is where the assignment and reference fields come from, the fields automatic clearing later matches on. Reversals are their own small discipline: the reversal reason decides whether the reversal lands in the original period or the current one, and a period already closed forces the second. The trail runs original document, follow-on document, clearing document, and being able to walk it backwards from a bank line to the invoice is the working skill.

How do postings from other modules reach the general ledger?

Through account determination: most FI postings are not typed by an accountant but arrive from another area, and a table decides which account they hit.

Goods movements

Procurement resolves accounts through transaction keys — stock, the GR/IR clearing account, consumption with its general modifiers, price differences — read by valuation class and valuation grouping code, all maintained in OBYC.

Billing

Sales resolves revenue, discount and accrual accounts from a key built out of the selling organisation and an assignment group carried on both the customer record and the material, maintained in VKOA.

Payroll

Payroll results post through symbolic accounts, so the mapping is owned jointly and understood by neither side until the first run.

Asset accounting

The asset class carries the account determination (AO90), so one wrong class on one asset misposts every acquisition and every depreciation run after it.

A missing row in one of those tables surfaces as a document that will not post, days after the configuration that caused it. Reading that error back to the table it came from is the quiet centre of the job.

What actually happens during a period close?

A close is an ordered list of programs, and the order matters more than any one of them. Goods receipt and invoice receipt balances are regrouped so the account splits into other receivables and other payables; open items and balances in foreign currency are valued, usually as a reversing posting; accruals and recurring entries run; depreciation posts per depreciation area; intercompany balances are reconciled and the differences chased by people, not programs; then the period is closed in the posting period variant, which can hold one account interval open for the closing team while everyone else is locked out. At year end, balances carry forward and the retained earnings account takes the profit and loss accounts.

An FI consultant's month is shaped by that calendar: quiet in the middle, then every question at once on working days one to five — and a good share of those questions arrive from the analytics stack, when a management report and the ledger disagree by a rounding.

How do clearing and the payment run work?

Clearing closes open items by matching them against each other, and the payment program creates the outgoing payments that clear supplier invoices. Payables and receivables are sub-ledgers that summarise into reconciliation accounts, so a reconciliation account is never posted to directly and never agrees with the sub-ledger by accident. Clearing is what keeps them readable: automatic clearing matches on criteria you configure per account, which is why the assignment field on the document is a design decision rather than a free-text box.

The payment program is the busiest thing FI owns. It proposes items by payment method and house bank, produces exceptions someone must read, and hands a file to the bank in a format built from a format tree or a standard payment medium. On the receivables side the electronic bank statement runs interpretation algorithms against incoming lines, and the ones it cannot match land in a clarification queue. Dunning runs on levels and areas, and every business argues about level three. Treasury picks up where bank accounting stops.

Practitioners name this work by transaction code, and S/4HANA has added a Fiori app for much of it without retiring the codes. The everyday set:

A dash means most teams still use the transaction for that task, not that no app exists. Configuration has no Fiori equivalent at all: it stays in the Implementation Guide, with OBYC, OB52 and the payment program's own settings in FBZP among the screens an FI consultant opens weekly.

How does FI handle tax and e-invoicing mandates?

With a tax procedure per country, tax codes that carry the rate and the account key, and localisation projects for each country's electronic invoicing rules. A long tail of cases breaks the simple picture: reverse charge, EU triangulation, plants abroad, withholding tax deducted at invoice in one country and at payment in another. None of it is negotiable, and all of it has an external deadline.

The growth area is continuous transaction controls: country by country, tax authorities now want invoices cleared or reported electronically in their own format, on their own schedule. That work arrives as localisation projects with a legal go-live date attached, which is the one kind of SAP deadline nobody can move.

How does asset accounting work in SAP FI?

Asset accounting is a sub-ledger with its own vocabulary. The asset class defaults the number range, the screen layout and the account determination; a depreciation area exists per accounting principle and is tied to a ledger, so an asset can depreciate over fifteen years for the group and over a different life for the local tax authority. Assets under construction collect cost and settle to the finished asset by line item.

At cutover the asset register is loaded with acquisition values and accumulated depreciation as at the takeover date, and reconciled class by class against the legacy register before anyone opens a period. Balances and open items follow. Being the person who reconciled that load is worth more on a CV than any amount of vocabulary.

What is SAP Group Reporting?

SAP Group Reporting, in full SAP S/4HANA Finance for group reporting, is the consolidation component of S/4HANA. It turns the books of many companies into one set of group financial statements. It reads the same data FI posts. As postings reach the general ledger they are stored in the Universal Journal table, ACDOCA. The fields group reporting needs are derived from mappings. A task in the Data Monitor, Release Universal Journal, then transfers the validated data into the group reporting table, ACDOCU.

The reporting entity is the consolidation unit. It is usually one company, and it can also be derived from a company and a profit centre together. Validation rules check the data before any consolidation task runs on it. For an FI consultant this is the specialism nearest the close. It suits people who have run a group close themselves.

Who moves into FI, and what do interviewers check?

Accountants and auditors who already own the rules (the domain route), finance key users (the key-user route), logistics consultants who already maintain half of account determination, and people who reconciled open items in the migration stream. Interviews go straight at document splitting and at walking a GR/IR difference to the account it sits on; the FI interview guide runs those scenarios. Since the universal journal merged FI and Controlling postings, "FI only" is a narrower position than it was.