Ask a finance team how they reconcile the bank and the honest answer is often a spreadsheet. The functionality to import statements and match them automatically exists, but it requires configuration that rarely fits into an initial implementation timeline, so it gets deferred and then forgotten. Two years later reconciliation is a multi-day monthly exercise and an audit comment.
This page explains how the automated path works, what setting it up genuinely involves, and the reconciliation problems that show up in practice. Available statement formats, matching behavior, and automatic entry generation vary by Sage X3 version, patch level, and localization, so treat the specifics here as the shape of the process and confirm the detail against your own environment.
Where teams usually are
- Reconciliation performed in Excel outside the system entirely
- Statement imports failing, or importing with wrong amounts or dates
- Nothing ever auto-matches, so every line is handled manually
- The reconciled balance not tying to the general ledger bank account
- Multi-currency accounts — a local currency account alongside a USD account, for example — reconciling with differences nobody can explain
- Bank fees, interest, and unidentified items with no defined route into the ledger
How the process works
Bank accounts, GL accounts, and currency
Each bank account is linked to a general ledger account and a currency, and carries its own statement history and reconciliation position. That linkage is the reason manual journals posted straight to the GL bank account cause reconciliation differences the bank module cannot see.
Statement import through a format definition
Imports use a bank file format definition mapped through an import template to the statement structure. Commonly used formats include MT940 or SWIFT, BAI2, and CAMT.053, subject to version and configuration. The definition has to match what the bank actually transmits — including bank-specific transaction codes, which are rarely documented the way the format specification suggests.
Matching rules
Matching works on amount, a date window, reference or check number, and counterpart text. Statement lines that find no match can generate journal entries for items such as fees and interest through defined entry types, so recurring bank charges do not need manual entry every month.
Closing the reconciliation
The reconciliation closes on a statement balance that must equal the general ledger bank balance plus or minus outstanding items. If that equation does not hold, the cause lies in one of the two ledgers rather than in the matching.
What implementing it actually involves
- 1. Get real statement files from the bank first
Obtain production sample files for every account before configuring anything. Files taken from format documentation almost never match what a specific bank sends.
- 2. Decide what posts automatically
Agree with finance which transaction types generate entries without review — typically fees, interest, and FX adjustments — and which are always treated as exceptions.
- 3. Align the posting grain with the statement
Payment and receipt processes must hit the bank GL account at the same level of detail as the statement. If deposits post as a batch in Sage X3 while the bank reports individual items, matching will remain manual no matter how the rules are tuned.
- 4. Work through multi-currency deliberately
The bank account currency, the currency setting on the GL account, and the rate policy applied to payments together determine whether exchange differences appear inside reconciliation or elsewhere. Decide it before the first import rather than diagnosing it afterwards.
- 5. Reconcile the opening position
Establish the starting balance and the outstanding items before go-live. An unreconciled opening position contaminates every subsequent period.
- 6. Document the monthly procedure and pilot it
The process is unforgiving of skipped statements, so users need a written monthly routine and a pilot period where they run it with support available.
Why reconciliation breaks
- Format definition mismatches — line types, field positions, date formats, or sign conventions differing from the live file
- Deposits posted as a batch in Sage X3 while the bank statement lists each item separately
- The same statement imported twice
- Payments posted directly to the general ledger, bypassing the bank module altogether
- Manual journals against the bank GL account, creating entries reconciliation has no visibility of
Notice how many of these are process problems rather than software problems. Matching rules are usually the last thing that needs adjusting, not the first.
When to bring in help
- The bank module was never implemented and reconciliation lives in spreadsheets
- Several banks, several accounts, or several currencies are in scope
- The import format was attempted once and never made to work
- Auditors have raised findings on bank reconciliation
- The person who knew the monthly routine has left
PRH has implemented bank reconciliation including MT940 and SWIFT statement import for multi-currency accounts, piloted the monthly process alongside client finance teams, and written the end-user guides that keep it running after go-live. The work is as much about matching the posting process to the bank's behavior as it is about configuration.
Bank reconciliation questions
Does Sage X3 have automatic bank reconciliation?
Yes — through bank statement import and matching rules. It is not automatic out of the box; it has to be configured per bank account and per file format.
What bank statement formats does Sage X3 support?
Formats are defined through configurable definitions. MT940 or SWIFT, BAI2, and CAMT.053 are commonly used, with availability depending on version and setup.
Why do my bank transactions not auto-match?
Usually a posting grain mismatch between batch entries and individual bank items, matching rule tolerances that are too tight, or payment references that were never carried through to the bank.
Why doesn't the reconciled balance match my GL bank account?
Manual journals against the bank account, transactions posted outside the bank module, or prior periods that were never reconciled.
Can Sage X3 reconcile foreign-currency bank accounts?
Yes. How exchange differences behave depends on the currency setup on the bank and GL accounts and the rate policy applied to payments.
How long does it take to implement bank reconciliation?
It scales with the number of banks and formats. The critical path is obtaining real statement files and aligning the payment and receipt posting process with what those files contain.
Related finance and automation pages
- Finance and accounting consulting
Close, controls, and multi-entity accounting work.
- Bank automation services
Payment files, statement import, and treasury automation.
- Failed bank file imports
Troubleshooting guide for import failures at the file level.
- Sage X3 bank automation
Background reading on automating the cash cycle.
- Beverage manufacturer bank automation case study
A full cash cycle rebuilt end-to-end in Sage X3.
- Sage X3 Purchase Invoice Errors and Matching Problems
The payables side that feeds the bank.
- Sage X3 Fixed Assets Implementation
Another finance module often added after the original go-live.
- Sage X3 implementation consulting
Senior-led implementation of finance modules, including phased additions.