SAP S/4HANA FI cheat sheet

Transaction OBA7 defines document types; the SPRO path is Financial Accounting Global Settings > Document > Document Types > Define Document Types.

A document type controls the number range, permitted account types, field status group, posting keys, and reversal document type.

Account type indicators are A for assets, D for customers, K for vendors, S for G/L accounts, and M for material.

Transaction FBN1 creates number range intervals; document number ranges can be year-dependent and are assigned per company code.

Field status settings from the document type and the G/L account combine; suppressed fields override optional and required fields.

Standard document types include SA for G/L, KR for vendor invoice, KZ for vendor payment, DR for customer invoice, DZ for customer payment, and AA for asset postings.

The reversal document type is specified in the source document type; a dedicated reversal type can have its own number range.

A document type already used in postings cannot be deleted; it can be blocked or marked for deletion instead.

Vendor master data is stored in LFA1 for general data, LFB1 for company code data, and LFM1 for purchasing data; maintain it with BP or FK01/FK02/FK03.

Transaction FB60 posts vendor invoices, FB65 posts vendor credit memos, and F-53 posts manual outgoing payments.

The vendor reconciliation account is defined in the company code segment and is updated automatically; it cannot be posted directly.

Special G/L transactions include down payments, guarantees, bills of exchange, and noted items, and they use special G/L indicators.

Payment terms determine the baseline date, cash discount days, and net due date; the baseline date defaults from the invoice date or posting date.

Transaction FBL1N displays vendor line items; open items can be cleared automatically with F.13 or manually with F-44.

Logistics invoice verification with MIRO posts vendor liabilities with a purchase order reference and updates the vendor account.

Payment blocks and reason codes can exclude individual vendor items from an automatic payment run.

Transaction F104 performs valuation of open customer receivables, calculates adjustments for overdue items, and creates adjustment postings.

Valuation methods and aging intervals are defined in Customizing under Accounts Receivable periodic processing and closing valuation.

The adjustment amount is based on days overdue relative to the net due date derived from the customer payment terms.

A value adjustment posts to separate adjustment accounts rather than directly to the customer reconciliation account.

Adjusted open items remain open; the adjustment is an additional line item carrying a value-adjustment indicator.

Valuation methods can calculate adjustments as a percentage, a flat rate, or a formula applied to defined aging intervals.

F104 can be executed as a test run to review calculated adjustments before the productive update run.

Manual individual value adjustments can be posted for specific receivables and reversed or released when the item is settled.

Customer master data is stored in KNA1 for general data, KNB1 for company code data, and KNVV for sales data; maintain it with BP or FD01/FD02/FD03.

Transaction FB70 posts customer invoices, FB75 posts customer credit memos, and F-28 posts incoming payments.

The customer reconciliation account is defined in the company code segment and is updated automatically from customer postings.

Transaction F150 runs dunning for overdue customer items according to a dunning procedure with levels, days, and charges.

Transaction FBL5N displays customer line items by company code, account, and status, including open, cleared, and special G/L items.

Payment terms determine the baseline date and net due date; the baseline date defaults from the invoice date or posting date.

Special G/L indicators in Accounts Receivable include down payments, guarantees, bills of exchange, and noted items.

Credit management in SAP S/4HANA uses credit limits, credit exposure, and credit control areas to block or release sales orders.

Transaction FI12 creates house banks; a house bank ID is up to five characters and is assigned to a bank country and bank key.

The bank key identifies the bank: in Germany it is the Bankleitzahl, and in the United States it is the routing number.

A house bank can have multiple bank accounts; the account ID is up to five characters and links the bank account number, currency, and G/L account.

The payment program uses the house bank and account ID to determine the paying bank account during bank determination.

Bank master data is maintained per bank country and bank key and is shared across company codes.

House banks are created per company code, while the underlying bank master data is country-wide.

Check lots and check number ranges are maintained per house bank account for check payment methods.

Bank determination can select an alternative bank account for a house bank when the main account is not suitable.

Transaction F110 executes the automatic payment program in the sequence parameters, proposal run, payment run, and payment media generation.

The proposal run selects open items and creates a proposal list that can be reviewed and edited before the payment run is executed.

Transaction FBZP configures the payment program, including paying company codes, payment methods per country, bank determination, and house bank selection.

Parameters for F110 include the run date, identification, company codes, payment methods, and next payment date.

A payment run clears selected open items and generates payment documents for vendors or customers.

The payment medium workbench creates payment files and forms, such as DME files or checks, using payment medium formats assigned to payment methods.

Bank determination uses ranking order and available amounts to choose the bank account and payment method.

Items with a payment block, a future due date, or an excluded payment method are not included in the payment run.

An asset class defines account determination, screen layout, depreciation areas, and default useful life for asset master records.

The chart of depreciation is assigned to the company code and contains the depreciation areas used for asset valuation.

Transaction AS01 creates an asset master record; the asset class determines the account determination and default depreciation rules.

Transaction ABZON posts an external acquisition with an automatic offsetting entry to a specified G/L account.

Transaction AFAB calculates and posts periodic depreciation; it is normally run first as a test run and then as an update run.

Depreciation keys define the calculation method and useful life and are assigned in the asset master or proposed by the asset class.

The capitalization date determines the depreciation start date according to the depreciation rule, such as mid-month or beginning of month.

Transaction ABAVN posts asset retirements, and ABUMN posts transfers of asset values between asset master records.

A chart of depreciation is a country-specific set of depreciation areas assigned to a company code for asset valuation.

A depreciation area represents a valuation view, such as book or tax, with its own depreciation key, useful life, and posting rules.

Asset classes group assets for account determination, screen layout, and default depreciation area settings.

The asset master record contains the asset class, capitalization date, useful life, depreciation key, and depreciation area values.

Transaction AW01N displays asset master data, depreciation areas, planned depreciation, posted values, and transaction history.

Acquisition and production costs are managed per depreciation area; each area can post to different G/L accounts.

Asset reconciliation accounts are updated automatically from asset postings and cannot be posted directly.

Low-value assets and assets under construction use specific asset classes and depreciation rules for capitalization and depreciation.

Transaction OX02 defines a company code with a four-character ID, country, currency, chart of accounts, and fiscal year variant.

Transaction EC01 copies a reference company code and its customizing settings to create a new company code, which is then adjusted.

The company code must be assigned to a company defined with OX15; the company is the legal entity for consolidation.

A fiscal year variant defines the number of posting periods and special periods and is assigned to the company code.

A posting period variant controls which posting periods are open for posting and is assigned to the company code.

Transaction OB62 assigns the chart of accounts to the company code; the chart must exist before assignment.

Document number ranges are maintained per company code with FBN1 and assigned to document types.

Parallel ledgers and accounting principles are assigned to the company code for parallel valuation and reporting.

Transaction OB13 defines charts of accounts; the operative chart of accounts is assigned to each company code.

Transaction FS00 creates and changes G/L accounts; the chart of accounts segment is stored in SKA1 and the company code segment in SKB1.

Account groups control the number range interval and field status for G/L account master records.

Posting key 40 is the standard debit posting key and posting key 50 is the standard credit posting key for G/L account postings.

Transaction FB50 posts G/L account documents, FB01 posts general documents, and FB03 displays posted documents.

Reconciliation accounts for vendors, customers, and assets cannot be posted directly; they are updated from subledger postings.

Open item management and line item display are set in the G/L account company code segment and affect clearing and reporting.

Document splitting and parallel ledgers can create additional ledger-specific postings for segment reporting and valuation.