Does FIS sell reconciliation software
Yes, but it is a separate product line from the core. FIS Data Integrity Manager, the platform formerly sold as IntelliMatch, covers enterprise, nostro, ATM and confirmation matching with payments investigation and exception management. Its showcase deal in May 2026 was the Commonwealth Bank of Australia, which moved it to SaaS on Microsoft Azure at more than 150 million transactions a day. FIS also runs an Optimized Reconciliation Service, a managed offering aimed at capital markets firms.
That tells you who Data Integrity Manager is built for: large institutions with a dedicated reconciliation function, a multi-year budget and a procurement process to match. A $3 billion bank on IBS or a community bank on Horizon has the same daily problem at a fraction of the volume. Its ACH clearing GL, Fedwire settlement, card settlement and due from accounts still need to tie to outside evidence every morning, usually in spreadsheets built from core reports. BankAutomation is priced and packaged for that bank.
9%
$1B to $150B
40+
$1,200
The 9 percent share is from the Federal Reserve Bank of Kansas City's March 2024 briefing on core providers, citing a 2022 ABA survey. The IBS figures are from FIS's IBS brochure. The price is ours.
FIS cores and what changes for reconciliation
The Kansas City Fed describes FIS as the core provider that mainly serves large and midsized banks, with a much smaller credit union base than Fiserv or Jack Henry. That shapes the work. An FIS bank tends to carry more commercial volume, more correspondents and more payment rails per accountant than a typical community bank, so reconciliation is less about one person's workbook and more about a queue of breaks that several people share.
| Core | Who runs it (FIS materials) | Where reconciliation time goes |
|---|---|---|
| IBS (Integrated Banking Solution) | Community to large regional banks; FIS calls it the platform of choice for banks between $1 billion and $150 billion in assets, with more than 40 clients above $10 billion | Commercial ACH origination with exposure limits, Fedwire volume, treasury management sweeps, several correspondents and a busy Fed account |
| Horizon | Community banks, positioned by FIS as a modern core for retail and commercial customers | ACH and debit card settlement, official checks, one or two due from accounts and a small team that also closes the month |
| Modern Banking Platform | FIS's cloud native, modular core for institutions that are modernizing | Two cores in parallel during migration, so every clearing account must be proven on both |
None of these cores needs an interface to be reconciled. If the core can write its daily GL detail and settlement reports to a file, that file is the ledger side of the match. Credit unions will find share drafts, shared branching and the corporate account covered on credit union reconciliation software.
The accounts an FIS bank proves every morning
The core posts to customers. The money settles somewhere else: on the Fed account, at the card networks, at a correspondent. Each of those leaves a clearing GL behind that someone has to prove against evidence the core did not produce.
| Account | Core side | Outside evidence | Break that shows up most |
|---|---|---|---|
| ACH origination | Originated batches debited to commercial customers and the ACH clearing GL | FedACH settlement entries by window on the Fed statement of account | A batch posted to the customer and held by exposure review, so it never reached the Fed |
| ACH receipt and returns | Received items, returns and NOCs posted to accounts | FedACH receipt and return settlement, Nacha files | A return settled today and posted tomorrow |
| Fedwire | Outgoing and incoming wires and the wire clearing GL | Fedwire Funds entries on the Fed statement and the wire system log | A wire released after the posting cutoff, booked on the next business day |
| Debit and credit card settlement | Card postings and the card settlement GL | Processor and network settlement reports, net settlement on the Fed or correspondent account | Interchange and network fees netted out of settlement |
| Federal Reserve account | Due from FRB GL | Statement of account, FIRD or the daily statement | Service charges, cash orders and adjustments booked on another day |
| Correspondents | Due from GL per correspondent | BAI2 or CSV statement from each correspondent | Sweeps, fees and returned items the correspondent posted first |
| Suspense and clearing | Suspense GLs | The items meant to clear them | Old items nobody owns |
Each row has its own page when it is the one that hurts: ACH reconciliation software, debit card reconciliation software, federal reserve account reconciliation software, correspondent bank reconciliation software and suspense account reconciliation software.
Commercial ACH and Fedwire are where IBS banks lose the morning
A bank in the IBS asset range usually originates ACH for hundreds of commercial customers: payroll, vendor payments, collections. Batches arrive all day, some are held for exposure or fraud review, and FedACH settles them in four windows. Forward items settle at 8:30 a.m. Eastern Time and Same Day ACH settles at 1:00, 5:00 and 6:00 p.m. Eastern Time. The core, meanwhile, posts the offset to the customer when the batch is accepted.
So the ACH clearing GL and the Fed account rarely agree at a glance. Most of the difference is timing and window grouping, and somewhere inside it sits the one batch that was posted to the customer and never sent, which is the item that becomes a loss if nobody sees it. Fedwire adds its own version of the same problem: a wire released after the core's posting cutoff appears on the Fed statement today and on the GL tomorrow.
BankAutomation groups originated batches by settlement window, matches each window to its Fed entry, and leaves only the batches with no settlement partner. Wires are matched by IMAD and amount, so a late wire is recognized as timing and closed when it posts. The Fed side of the match is described in detail on federal reserve account reconciliation software.
A worked example from an ACH origination day on IBS
Input
- Fed statement of account, FedACH origination settlement · 4 entries (8:30 a.m., 1:00, 5:00 and 6:00 p.m. ET) · 18,742,310.40 USD
- Core postings to the ACH origination clearing GL · 47 batches · 3,912 items · 18,754,810.40 USD
- ACH origination log · 47 batches accepted · 1 batch held for exposure review
Output
- Matched 46 batches grouped to the four FedACH settlement entries by window: the forward window at 8:30 a.m. and the three Same Day windows. No batch is compared to the GL one by one.
- Open 1 payroll batch of 38 items, 12,500.00 USD, debited to the customer on the core and held by exposure review, so it never reached the Fed. Assigned to ACH operations with an age of 0 days.
The figures tie: 18,754,810.40 less 18,742,310.40 is 12,500.00, the held batch. Without grouping, the analyst sees a difference of 12,500.00 mixed in with every timing item of the day. With grouping, it is one line with an owner before 9 a.m., and the customer's employees still get paid that day if the batch is released before the next window.
FIS Data Integrity Manager or a separate platform, compared
These are the routes we see at banks on FIS cores. Each one is the right answer for somebody.
| Route | Works well when | Where it runs out | Price signal |
|---|---|---|---|
| Core reports and spreadsheets | A handful of settlement GLs and one experienced person | No record of who matched what, rebuilt every day, stops when that person is out | Staff time |
| FIS Data Integrity Manager | A large bank with a reconciliation team, SWIFT and nostro volume and an existing FIS relationship | Sized and priced for enterprise programs, heavy for a bank that needs ACH, card and Fed matching | Quote only |
| Trintech ReconNET or Frontier | High volume matching and a long US bank reference base | Quoted per customer, cloud migration and re-quote at renewal | Quote only |
| SmartStream or Gresham | Global banks and capital markets workloads | Implementation scope and cost match that scale | Quote only |
| ReconArt | Bank, card and close modules from one vendor | Per user licensing grows with the team | Capterra lists from $300 per user a month |
| BankAutomation | Daily ACH, Fedwire, card, Fed and correspondent accounts in one queue with published pricing | Reads files and does not post back to the core; no SWIFT messaging or confirmation matching | $1,200, $3,900 or $9,500 a month |
If your bank already licenses Data Integrity Manager for nostro and securities, keep it there. The case for a separate platform is the daily domestic settlement work that the enterprise license prices on volume. Banks comparing the enterprise options will find them taken apart in intellimatch alternatives and smartstream tlm alternatives. Banks on other cores have sister pages: Fiserv reconciliation software and Jack Henry reconciliation software.
Core conversions to or from an FIS core
Banks move onto IBS and Horizon from other cores, and onto Modern Banking Platform from older FIS cores. Every conversion has the same accounting risk: for a few weeks, settlement GLs exist on two systems with different report layouts, and a clearing balance that does not move cleanly becomes a suspense item that outlives the project.
Because BankAutomation reads files, the old core and the new core are just two sources. You map both report layouts, run the same rules on each, and prove that every clearing account balance on the conversion date is explained by items that cleared afterward. When the old core is switched off, its source is retired and the rules stay.
Who buys reconciliation software on an FIS core
- Controllers at IBS banks whose commercial ACH and wire volume outgrew a workbook per settlement account.
- Deposit operations managers at Horizon banks who balance ACH, cards and official checks before starting their real job.
- Heads of payment operations who need held batches, late wires and unposted returns owned and aged, not found at month end.
- Banks in a core conversion that must prove every clearing account on both systems.
- Institutions that priced Data Integrity Manager for daily domestic settlement and found the scope too large.
Getting live without touching the core
There is no core interface to license and nothing for FIS to schedule. Your FIS contract does not change.
Step 01
Choose two accounts
Usually ACH origination and Fedwire, or ACH and card settlement, because they break every day.
Step 02
Save the evidence as files
Core GL detail and settlement reports, the Fed statement of account, processor and network reports, Nacha files and correspondent statements. CSV, fixed width and BAI2 all work.
Step 03
Approve the rules
FedACH windows, IMAD matching for wires, network fee netting, many to one grouping. One person proposes a rule and a second approves it.
Step 04
Run one month in parallel
Include a month end, compare against the current workbook, then retire it. Fed, correspondent and suspense accounts follow.
What it costs
Pricing is published and set per institution, not per user. Operations is $1,200 a month for 250,000 matched items, three source connections and up to 10 users, enough for ACH and card settlement at most community banks on Horizon. Platform is $3,900 a month for 2,000,000 items, unlimited sources, up to 50 users, SSO and maker-checker approvals, which is where most IBS banks with commercial volume land. Institution is $9,500 a month with unlimited items and users for multi-charter holding companies. Annual billing halves each monthly rate. Every limit is on the pricing page.
The resolver at the top of this page runs the matcher on sample USD card settlement data, so you can see grouping, fee netting and break classification before you talk to anyone. The rule types are described on transaction matching software.
BankAutomation is an independent product and is not affiliated with, endorsed by or certified by FIS. FIS, IBS, Horizon, Modern Banking Platform, Data Integrity Manager and IntelliMatch are trademarks of their owners and are named only to describe compatibility.
Questions about reconciliation software for banks on FIS cores
Does FIS have reconciliation software?
Yes. FIS sells Data Integrity Manager, formerly IntelliMatch, for enterprise, nostro, ATM and confirmation matching with exception management, and a managed Optimized Reconciliation Service for capital markets. Both are aimed at large institutions. Banks on FIS cores that need daily ACH, Fedwire, card and Fed matching at community or regional bank scale often use spreadsheets or a separate platform instead.
What reconciliation software works with FIS IBS?
Any platform that reads files works with IBS, because reconciliation needs the core's GL detail and settlement reports, not a live connection. Banks on IBS use spreadsheets, FIS Data Integrity Manager, Trintech ReconNET or Frontier, ReconArt and BankAutomation. BankAutomation reads saved report files and publishes its price, from $1,200 a month.
How do banks on FIS Horizon reconcile ACH and card settlement?
They tie the ACH and card postings on the core and the clearing GL balances to outside evidence each day: FedACH settlement entries on the Fed statement of account, and processor and network settlement reports for cards. Most breaks are timing or netted fees. Software groups postings by settlement window and nets fees by rule, so only real differences stay open.
Does BankAutomation integrate with FIS Code Connect?
It works from files, not from Code Connect APIs. You save the core GL detail and settlement reports your team already uses, with the Fed, network and correspondent files, and BankAutomation matches them. Nothing is installed on the core and nothing posts back, so there is no integration project and no change to your FIS contract.
Is FIS Data Integrity Manager the same as IntelliMatch?
Yes. Data Integrity Manager is the current name for the platform FIS sold as IntelliMatch, which originally came from SunGard. It is SWIFT accredited and is now offered as SaaS on Microsoft Azure, as in the Commonwealth Bank of Australia deal announced in May 2026.
How much does reconciliation software cost for a bank on an FIS core?
FIS Data Integrity Manager and Trintech ReconNET are quoted per customer, and Capterra lists ReconArt from $300 per user a month. BankAutomation publishes its prices: $1,200 a month for 250,000 matched items and three sources, $3,900 for 2,000,000 items with unlimited sources and maker-checker approvals, and $9,500 for unlimited volume. Annual billing halves each monthly rate.