--- title: "Turn a bank statement export into a reconciliation queue | R&D COPILOT" lang: en canonical: https://rdcopilot.com/insights/bank-statement-import-reconciliation/ content_version: 5db1a1790cfa9e25a0fc05401075466f0eaa5b82bd151c50758ddcea89ffda84 contact: https://rdcopilot.com/contact/ --- [RDC](https://rdcopilot.com/) [Insights](https://rdcopilot.com/insights/)Banking BankingDecision guide # Turn a bank statement export into a reconciliation queue Bank reconciliation becomes easier when imported transactions stay connected to their original statement lines. Finance should be able to review proposed invoice matches, inspect unexplained movements and see exactly which transactions remain open. The first implementation should begin with a real supported export format. By R&D COPILOT6 October 20265 min read In this guide 1. [Start with the statement your bank actually exports](https://rdcopilot.com/insights/bank-statement-import-reconciliation/#guide-section-1) 2. [Keep an untouched import record](https://rdcopilot.com/insights/bank-statement-import-reconciliation/#guide-section-2) 3. [Build proposals from explicit matching rules](https://rdcopilot.com/insights/bank-statement-import-reconciliation/#guide-section-3) 4. [Give unmatched movements a useful workspace](https://rdcopilot.com/insights/bank-statement-import-reconciliation/#guide-section-4) 5. [Bound access and the banking role](https://rdcopilot.com/insights/bank-statement-import-reconciliation/#guide-section-5) 6. [Reconcile the process before trusting the matches](https://rdcopilot.com/insights/bank-statement-import-reconciliation/#guide-section-6) 7. [Define the import balance checks](https://rdcopilot.com/insights/bank-statement-import-reconciliation/#guide-section-7) 8. [Build one supported path first](https://rdcopilot.com/insights/bank-statement-import-reconciliation/#guide-section-8) [Sources & inspiration](https://rdcopilot.com/insights/bank-statement-import-reconciliation/#guide-sources) ## Start with the statement your bank actually exports Ask which accounts, currencies and periods are included, and how the bank represents reversals, fees and references. A column name such as date may mean booking date or value date. Preserve both when supplied. The meaning of the data matters more than whether the file opens successfully. ## Keep an untouched import record Retain the original file and an import identifier before normalizing columns. Record account context, period and the operator. Normalized transactions should retain a reference to the original row so that a reviewer can resolve a parsing question without searching for the attachment. Check encoding, decimal separators, signs and currency before matching. A debit interpreted as a credit creates a plausible-looking but wrong reconciliation. Reject an ambiguous format with a useful explanation rather than guessing. Establish whether the export contains opening and closing balances and how those can help verify completeness. ## Build proposals from explicit matching rules Start with predictable evidence: transaction references, amounts, counterparties and invoice identifiers. Show which evidence supports each proposed match. A reviewer should understand why the suggestion appeared and where another candidate exists. Separate exact rules from less certain suggestions. Text assistance can help explain an unusual reference, but calculations and allocation totals should follow explicit rules. Do not let a fluent explanation override a currency difference or allocate more than the available amount. Keep the original bank description visible alongside any normalized name. ## Give unmatched movements a useful workspace An unmatched transaction is not necessarily an error. It may represent a fee, a transfer, a partial settlement or an invoice not yet received. Provide categories for investigation and a place to record evidence, without forcing the first plausible explanation. Assign unresolved items to someone who can obtain the missing information. Keep proposal, approval and accounting outcome distinct. When a match is rejected, retain the reason to improve the rules and avoid presenting the same unhelpful suggestion repeatedly. Changes to a matched invoice should trigger a targeted review of the affected allocation. ## Bound access and the banking role A statement can reveal counterparties and personal payment details. Limit account visibility to the finance users who need it and make exports deliberate. Support notifications should identify the unresolved item without reproducing the full statement. This workflow can operate on exports supplied by authorized staff. Direct bank connectivity is a separate scope with its own provider, authorization and supported account questions. Importing records does not authorize initiating payments. Keep those capabilities and their permissions separate in both the proposal and the interface. ## Reconcile the process before trusting the matches Test totals and counts from the original file through normalized transactions to the reconciliation queue. Include negative values, multiple currencies, repeated imports and an interrupted upload. Confirm that no row disappears simply because parsing or matching failed. Measure automatic proposals accepted without correction, rejected suggestions, unresolved items and reviewer time. Report these by transaction type so easy internal transfers do not hide difficult customer payments. A useful acceptance check is that the finance team can reconstruct every allocation and account for the original statement totals. ## Define the import balance checks Before considering invoice matches, establish the checks that can be performed using the supplied statement. Where opening and closing balances are present, agree how transaction amounts relate to them. Where they are absent, use the available row counts and totals and record the limits of that check. Keep booking and value dates distinct when both appear. A filter using the wrong date can exclude a payment from the comparison period while leaving the source file apparently complete. Make the selected period basis visible to finance and keep it with the import configuration. The importer should also explain unrecognized transaction types. A row that is not a customer receipt may still be necessary to reconcile the statement. Preserve it and route it to the appropriate classification rather than dropping it because no invoice candidate exists. This gives the accountant a complete financial input while allowing different matching rules for receipts, transfers and charges. Evaluate each group separately before extending automated suggestions. - A reviewer can identify the account, currency, source row and date basis for every normalized transaction before evaluating invoice suggestions. - The import accounts for transaction types without invoice matches rather than omitting them from the finance team's reconciliation input. - Where balance information exists, the agreed calculation is checked independently of any AI-generated explanation or proposed counterparty match. - The report distinguishes accepted suggestions, rejected suggestions and unresolved records so the team can evaluate each transaction group on its own terms. ## Build one supported path first RDC can implement a statement importer, explainable matching proposals and an exception workspace connected to your accounting records. Start with one export format and a clearly defined account scope, then evaluate additional formats individually. For a quote, bring redacted statements, relevant invoice exports and examples of transactions that currently require manual investigation. We agree parsing rules, approval responsibilities and the evidence retained after reconciliation. The aim is a workflow finance can inspect and operate, with supported integrations documented rather than assumed. Inside the product ## Banking [![Bank and ledger entries with an exact match proposed.](https://banking.rdcopilot.com/product-demos/banking/gallery-overview-en.png)View full size](https://banking.rdcopilot.com/product-demos/banking/gallery-overview-en.png) Bank and ledger entries with an exact match proposed. [![Accepted receipt match and a bank-fee difference set aside for review.](https://banking.rdcopilot.com/product-demos/banking/gallery-detail-en.png)View full size](https://banking.rdcopilot.com/product-demos/banking/gallery-detail-en.png) Accepted receipt match and a bank-fee difference set aside for review. Swipe or use the arrows to explore. Image 1 of 2 Follow the references ## Sources & inspiration ### [ReconFlow](https://devpost.com/software/reconflow) Devpost project by Aditya Jain, Rachit Bhatia, Nisarg Gandhi Reconciliation with review of exceptions. This independently created project is credited as inspiration. The workflow and implementation guidance in this article are RDC’s analysis. - [EDPB data protection guide for small business](https://www.edpb.europa.eu/sme_en) Put the guide to work ## Start with your workflow. Tell us what your team needs to do, which systems are involved and where the current process slows down. [Discuss your project](https://rdcopilot.com/contact/?product=banking) [Explore Banking](https://banking.rdcopilot.com/en/products/banking/) Banking ## Keep exploring. [All guides](https://rdcopilot.com/insights/) Workflow ### [Import the same bank statement twice without doubling the work](https://rdcopilot.com/insights/banking-duplicate-statement-import/) Prevent repeated bank imports from creating duplicate work while preserving legitimate equal-valued payments, original source rows and finance review decisions. [Read guide](https://rdcopilot.com/insights/banking-duplicate-statement-import/) How-to guide ### [Why a payment does not always match one invoice](https://rdcopilot.com/insights/banking-partial-payments-fees/) Review partial payments, grouped settlements and fees through explicit allocations, supporting evidence and remaining balances the accountant can inspect. [Read guide](https://rdcopilot.com/insights/banking-partial-payments-fees/)