SAP FI explained: finance in SAP

SAP FI (Financial Accounting) is the SAP area that holds a company's books of record: the general ledger, payables and receivables, fixed assets, bank accounting and tax, plus the period-end close that turns daily postings into statutory financial statements. It is the external, statutory view of the money — what auditors and tax authorities see — as distinct from CO (Controlling), which holds the internal view of the same postings.

What the area covers

General ledger (FI-GL) — chart of accounts, company codes, parallel ledgers for local and group valuation, document splitting.
Accounts payable (FI-AP) — vendor invoices, the hand-off from invoice verification, the automatic payment run and payment media.
Accounts receivable (FI-AR) — invoices from billing, incoming payments, clearing, dunning and collections.
Asset accounting (FI-AA) — capitalisation, a depreciation area per ledger, the depreciation run, transfers and retirements.
Bank accounting (FI-BL) — house banks, electronic bank statement import and its posting rules, the border with Treasury.
Tax — tax on sales and purchases, withholding tax, statutory reporting, and country-specific e-invoicing rules.
Closing — foreign-currency valuation, accruals, intercompany reconciliation, period open/close, the hand-off to group reporting.
Account determination — which account a goods movement, a billing document or a payroll run hits — the quiet centre of the job, and where most FI defects live.

What does an SAP Finance consultant actually do?

The artefacts are concrete: design documents from fit-to-standard workshops, configuration in the IMG (company codes, document types, tax codes, depreciation areas, account determination), functional specs for payment and tax file formats, and migration templates for open items and asset histories.

Meetings are with the group accountant and the controller as often as with IT: fit-gap sessions on ledgers and the chart of accounts, integration sessions with MM and SD over goods-receipt/invoice-receipt clearing and revenue accounts, and the audit question of who may post what.

Design and build weeks — workshops, the write-up, then configuration, developer specs and test data; a wrong ledger or currency choice is expensive later.
Test weeks — sitting behind key users, tracing a failed posting back to its source document.
Cutover — loading balances and open items, reconciling to the legacy trial balance, opening the first period.
Hypercare and AMS — the first close in the new system, then a rhythm the month-end sets.

How do people get into SAP Finance?

From accounting — bookkeepers, GL and AP/AR accountants and auditors converting into consulting; the classic domain route into SAP.
From a live system — the finance person colleagues ask before they raise a ticket (the key-user route).
From an adjacent area — CO consultants widening outward; MM or SD consultants who already own half of account determination.
From the technical side — developers and migration people who have debugged posting logic long enough to read the accounting behind it.

What gets someone hired is evidence, not vocabulary: a close you supported end to end, a rollout where you configured tax and company codes, an open-item migration you reconciled. Interviewers probe exactly there — explain document splitting, or how a goods-receipt/invoice-receipt difference clears (what interviews test).

What it pairs with

CO is the default second area — same postings, internal lens. Treasury grows out of bank accounting; MM and SD pair with FI because procure-to-pay and order-to-cash both end in a posting; and GRC because segregation of duties around payments is an annual audit topic (which combinations work).

Where it is going

The Universal Journal removed the reconciliation seam between FI and CO, so "FI only" narrows while FICO breadth becomes the assumption. E-invoicing and digital reporting mandates arrive country by country, each a localisation project with a legal deadline attached. And as classic Business Suite installations run out of mainstream maintenance, their finance conversions — ledger design, custom-code clean-up, balance migration — keep project work flowing (the wider career effect).