A manual journal against the account
How you'll know: SAP rejects the GL entry and says the account can't be posted to directly.
Fix: Post against the customer, vendor or asset instead. If the subledger is wrong, correct it there and the GL follows.
Post a customer invoice in SAP and two things happen at once: a line on that customer's account, and the same amount on a general ledger account you never typed in. That GL account is the reconciliation account. It's named on the customer or vendor master, and SAP posts to it on every transaction. If you've just been stopped from posting to one by hand, that's the control doing its job.
A reconciliation account is a general ledger account linked to a subledger: customers (accounts receivable), vendors (accounts payable) or fixed assets.
Each posting to a customer, vendor or asset also lands on its reconciliation account automatically, so the subledger total and the GL balance stay in agreement by design.
You can't post to it directly with a GL journal entry. Corrections go through the customer, vendor or asset itself.
It's marked on the GL account's company code data, with D for customers, K for vendors or A for assets.
FS00 › Control Data › Recon. account for acct typeThe same steps cover SAP FICO on ECC and S/4HANA. The screens differ a little.
Create it as a balance sheet account in your chart of accounts, then set the reconciliation account type in its company code data. On S/4HANA the Manage G/L Account Master Data app does the same job.
On S/4HANA that's the Business Partner transaction, in the FI customer or FI vendor role. On ECC it's the customer or vendor master (FD01, FK01). From then on, every invoice and payment for that partner also posts to this GL account.
For fixed assets the link runs through account determination. The acquisition and production cost account set there is a reconciliation account for assets, and every asset in the class posts to it.
Down payments, guarantees and similar special G/L transactions post to an alternative reconciliation account tied to a special G/L indicator. That keeps them apart from ordinary receivables and payables on the balance sheet.
How you'll know: SAP rejects the GL entry and says the account can't be posted to directly.
Fix: Post against the customer, vendor or asset instead. If the subledger is wrong, correct it there and the GL follows.
How you'll know: Items posted before the change still sit on the old reconciliation account, so the GL split no longer looks the way you expected.
Fix: Plan the change with whoever owns your FI configuration, including what happens to open items already on the old account.
How you'll know: Trade, intercompany and employee receivables all land on one GL line, and finance splits them by hand for the balance sheet.
Fix: Create separate reconciliation accounts for each group and assign the right one on each master record.
How you'll know: A customer balance list and the reconciliation account show different totals at month end.
Fix: Check the selection first: special G/L items on alternative accounts, currency valuation and posting periods explain most gaps. SAP's comparison reports confirm it before close.
The other reconciliation SAP finance teams talk about is matching the bank. Electronic bank statement processing imports a statement file, in formats such as MT940, camt.053 or BAI2, and clears what it can against open items using configured rules. In classic SAP that's FF_5 to import and FEBAN to work through what's left. S/4HANA adds Fiori apps for the same work, and SAP Multi-Bank Connectivity brings statements in directly from banks that support it.
It stalls when a bank only offers a CSV download or a PDF, or when customers send remittance details separately from the payment. Then someone builds the statement by hand, or clears items one at a time. With several company codes and house banks, that repeats for each one.
A GL account tied to a subledger (accounts receivable, accounts payable or asset accounting) that receives postings automatically whenever a subledger transaction happens, instead of accepting manual entries.
No. SAP blocks direct postings on purpose, because the account exists to stay in step with its subledger. Any correction goes through the customer, vendor or asset record.
Create a balance sheet GL account in FS00, set the reconciliation account type for customers, vendors or assets in its company code data, then assign it on the customer or vendor master, or in the asset class's account determination.
Mostly through electronic bank statement processing. SAP imports a structured statement file and matches its lines against open items using configured rules, then leaves the rest for post-processing. If a bank can't deliver a file SAP reads, someone has to bring the statement in by hand first.
The idea is the same, but the names and screens differ. Business One calls it a control account, set on the business partner's accounting data, and it has its own bank statement import and internal reconciliation tools.
n-frames builds converters that take a bank's CSV export and produce a statement file SAP's import accepts, so the same matching rules run on every account. Documents created through interfaces can count toward SAP licensing, so confirm with your SAP account team before anything goes live.