FB01FI

SAP FB01Post Document

Everything that happens to money in SAP ends up as an accounting document. Not a PDF — a record with a header (when, which company, what type) and two or more line items that must add up to zero. Debits on one side, credits on the other, balance nil. If it does not balance, SAP will not post it.

FB01 is the raw, unassisted way to create one. You choose the accounts, you choose whether each line is a debit or a credit, you type the amounts. Nothing is pre-filled and nothing is inferred.

That is why beginners rarely start here, and why it is worth understanding first. Friendlier transactions like FB50 (journal entries), FB60 (vendor invoices) and FB70 (customer invoices) are wrappers that build the same document with some of the decisions made for you. Learn what FB01 is doing and the others stop being magic.

When you would actually use FB01

What the screen looks like

Enter Company Code Document: Header Data
FB01

Document header

Document Date15.07.2026
Posting Date31.07.2026
Document TypeSA
Period7
Company Code1000
Currency/RateEUR
ReferenceACCR-07-2026
Doc.Header TextJuly rent accrual

First line item

Posting Key40
Account470000
Enter the first line item, then press Enter to continue to the next.
Client 100 | S/4HANA | Company Code 1000
Illustrative recreation.FB01 header screen — you build the document one line at a time — Drawn for training with invented data; not a capture of a real SAP system. Fields with a blue border are required. SAP is a trademark of SAP SE.

The fields, in plain English

Document DateBKPF-BLDAT

The date printed on the source paperwork — the invoice date, the contract date. It is what the outside world would call the date of the transaction.

Watch out: This does NOT decide which accounting period the entry lands in. Posting Date does.

Posting DateBKPF-BUDAT

The date the entry hits the books, and therefore which fiscal period and which month-end it belongs to. An invoice dated 15 July but posted with a posting date of 31 July counts in July.

Watch out: If the period is closed you get error F5201. This is the single most common FB01 failure.

Document TypeBKPF-BLART

A two-character code classifying the document, which also controls which number range it takes and which account types it may post to. SA is a general G/L document, KR a vendor invoice, DR a customer invoice, AB a general one that allows all account types.

Watch out: Document type restricts allowed account types. Choosing SA and then trying to post to a vendor will be rejected.

Company CodeBKPF-BUKRS

The legal entity that produces its own balance sheet and P&L. This is the fundamental FI organisational unit — a document always belongs to exactly one company code.

Posting KeyBSEG-BSCHL

A two-digit code doing two jobs at once: it says whether the line is a debit or a credit, and it says what kind of account the line posts to. 40 = debit a G/L account, 50 = credit a G/L account, 31 = credit a vendor, 01 = debit a customer.

Watch out: The number you memorise first is 40/50. Getting them the wrong way round produces a document that balances but is economically backwards.

ReferenceBKPF-XBLNR

A free-text field for the external document number — the supplier invoice number, for example. Searchable later, so a consistent convention here saves hours.

Step by step

  1. 1Enter the header: dates, document type, company code, currency.Posting date determines the period; document date is only informational.
  2. 2Enter posting key and account for the first line, then press Enter.
  3. 3Fill in the amount and any required fields (cost centre, tax code) on the line item screen.
  4. 4Repeat posting key and account for each further line.
  5. 5Check the balance display — it must show 0.00 before SAP will let you post.Menu: Document → Simulate shows the finished entry before you commit.
  6. 6Post with Ctrl+S. SAP returns the new document number.

Errors you will hit, and what they mean

F5201 — Posting period 006 2026 is not open

Why: The posting date falls in a period that has been closed for the account type you are posting to.

Fix: Either change the posting date into an open period, or ask whoever owns the close to open the period in OB52. Do not simply backdate to force it through — you will distort a closed month.

F5702 — Debits do not equal credits

Why: The line items do not sum to zero, usually a typo in an amount or a missing line.

Fix: Use Document → Simulate to see all lines with the running balance and find the difference.

F5808 — Field Cost Center is a required field for G/L account 470000

Why: The field status group on the account (or on the posting key) makes cost centre mandatory, and it was left blank.

Fix: Fill the cost centre. If it genuinely should not be required, the field status group needs changing in configuration — that is a change to make deliberately, not to work around.

Common questions

What is the difference between FB01 and FB50?

They create the same kind of document. FB50 is a single-screen entry for G/L postings that infers the posting key from whether you type the amount in the debit or the credit column. FB01 makes you state the posting key explicitly and can post to any account type. FB50 is faster day-to-day; FB01 is more general.

Can I delete a document posted with FB01?

No. Posted FI documents are never deleted — that is the point of an audit trail. You reverse them with FB08, which creates an equal and opposite document and links the two.

What does "parking" a document mean?

Parking (FV50/FV60) saves an incomplete document without updating any balances, so someone else can review and post it. FB01 posts immediately.

Transactions that go with FB01

Reading about it only gets you so far

Click through this transaction in a simulated SAP screen — no account needed, nothing to break.

Practise SAP transactions hands-on

Interactive modules, games, and an AI tutor — free to start.

Get started free →