SAP FD10N — Customer Balance Display
Where FBL5N lists every individual line item, FD10N summarises. It gives you one row per period showing what was debited, what was credited and where the balance ended up.
That makes it the natural starting point for "something moved and I do not know what". Find the period that changed in FD10N, then drill into it rather than scrolling through thousands of line items.
FK10N is the identical transaction for vendors. Both are read-only.
When you would actually use FD10N
- A receivables balance changed and you need to find which period moved.
- Getting a quick year-on-year comparison for one customer.
- Checking a customer's total exposure before approving an order.
- Starting an investigation before narrowing down with FBL5N.
What the screen looks like
| Period | Debit EUR | Credit EUR | Balance EUR | Cumulative EUR |
|---|---|---|---|---|
| Bal. c/f | 2,150.00 | |||
| 5 | 4,300.00 | 2,150.00 | 2,150.00 | 4,300.00 |
| 6 | 910.00 | 4,300.00 | 3,390.00- | 910.00 |
| 7 | 3,600.00 | 3,600.00 | 0.00 | 910.00 |
The fields, in plain English
KNA1-KUNNRThe customer account number. Ranges are allowed, though the report is most readable for one account at a time.
BSID/BSAD-GJAHRWhich financial year to display. The report shows all periods of that year, so choosing the year is choosing the window.
Watch out: A non-calendar fiscal year shifts the period numbers. Period 1 is not necessarily January.
The opening balance brought in from the prior year, shown as the first row. If this looks wrong, the balance carry-forward may not have been run.
The running total after each period — what the customer owed at each period end. This is the column to compare against a reported figure.
Step by step
- 1Enter the customer, company code and fiscal year.
- 2Execute. The balance table appears with one row per period.
- 3Scan the balance column for the period that moved unexpectedly.
- 4Double-click that period's debit or credit figure to drill into the line items.
- 5From a line item, double-click again to open the full document in FB03.
- 6Use the special G/L view if down payments are involved — they are reported separately.
Errors you will hit, and what they mean
Customer 200417 not created in company code 1000
Why: The customer exists centrally but is not extended to that entity.
Fix: Check which company codes the customer is set up in before assuming the account is wrong.
Balance carried forward is zero but prior year had a balance
Why: The year-end balance carry-forward program has not been run for the new fiscal year.
Fix: This is a period-end task owned by the close team. Do not post a manual entry to compensate.
Figures do not agree with the balance sheet
Why: Usually special G/L transactions, which sit on separate reconciliation accounts and are shown separately here.
Fix: Include the special G/L view and compare again before assuming a reconciliation problem.
Common questions
What is the difference between FD10N and FBL5N?
FD10N shows BALANCES by period. FBL5N shows individual LINE ITEMS. Use FD10N to find which period moved, FBL5N to see exactly which documents moved it.
What is the vendor equivalent?
FK10N, Vendor Balance Display. Same layout, same drill-down.
Can I see several company codes at once?
Yes — enter a company code range and the report totals across them, which is useful for a customer trading with more than one of your entities.
Transactions that go with FD10N
Reading about it only gets you so far
Practise SAP transactions in a safe simulated environment and keep what you learn.
Practise SAP transactions hands-on
Interactive modules, games, and an AI tutor — free to start.
Get started free →