Reconcile your SAP GL cash account against your bank statement offline. Pre-labeled fields for company code, house bank, and clearing documents. Download in Excel, Word, or PDF.
Fill in the SAP-specific fields below and watch the live preview update. Download the completed statement when you are done.
Pick Excel, Word, or PDF. Each has SAP-specific fields pre-labeled for company code, house bank, and GL account.
Fill in your SAP company code, house bank key, account ID, GL account number, and the period you are reconciling.
Enter the bank statement closing balance and GL cash balance. Add deposits in transit, outstanding payments, bank charges, and clearing differences.
If both adjusted balances match, save a copy for your records. Reference clearing document numbers for audit trail back to SAP.
Grab a blank template in the format that fits your workflow. Every version follows the same two-sided layout with SAP fields pre-labeled.
Spreadsheet with formulas. Best for SAP teams that reconcile in Excel alongside transaction reports.
Pre-formatted document with tables. Best for teams that need a sign-off copy alongside SAP clearing documents.
Print-ready layout. Best for physical sign-off and audit binders referencing SAP clearing documents.
Stop matching bank statements to GL entries manually. Let Bluecopa auto-reconcile across all your SAP company codes and flag exceptions.
SAP handles bank reconciliation through electronic bank statements (EBS) imported via FF.5 or processed manually through FEBAN. The goal stays the same: the GL cash account must match the bank statement after adjustments.
Upload an MT940, BAI2, or CAMT.053 file into SAP using transaction FF.5. SAP parses the statement into individual line items and creates a bank statement document.
SAP compares bank statement line items against open GL items using matching rules (amount, reference, date). Matched items get clearing documents assigned automatically.
Use FEBAN to review items SAP could not match. These are typically timing differences: deposits in transit, outstanding vendor payments, or bank charges not yet posted.
Create journal entries for bank charges, interest, and errors. Each posting creates a clearing document that links the GL entry to the bank statement line.
Run report FF67 to confirm no open items remain. The adjusted GL balance must equal the bank statement closing balance. Archive the reconciliation for audit trail.
Common SAP bank reconciliation mistakes stem from misconfigured house banks, skipped clearing runs, or ignoring small differences that compound over periods.
Use transaction FF.5 or FEBAN in SAP to compare your bank statement with the GL cash account. Import the electronic bank statement (MT940 or BAI2 format), run automatic matching, and manually clear any remaining open items. This template mirrors that two-sided layout so you can reconcile offline or validate SAP output.
FF.5 is the SAP transaction code for electronic bank reconciliation. It imports bank statement data, matches it against posted GL entries, and creates clearing documents for matched items automatically.
SAP supports MT940 (SWIFT), BAI2 (US standard), CAMT.053 (ISO 20022), and custom flat-file formats. The format is configured in the house bank and account ID setup within SAP.
Yes. There is no cost, no account creation, and no watermark. The interactive tool runs in your browser and the downloadable files are yours to keep.
Yes. While the fields are labeled for SAP terminology (company code, house bank), the reconciliation logic is standard. You can use this template with any ERP and simply relabel the fields.
FEBAN is the SAP transaction for manual bank statement processing. Unlike FF.5 which runs automatic matching, FEBAN lets you process and post bank statement line items one at a time, giving more control over complex reconciling items.
Templates work well for a handful of bank accounts. When you are reconciling across multiple company codes, handling hundreds of line items per statement, or spending days each month on manual matching in SAP, automation tools like Bluecopa can auto-match transactions and flag exceptions.