No Plaid? No Problem: Automating Bank Feeds in Sage Intacct

For most finance teams, the day doesn't really get going until the bank activity is in the books. Sage Intacct's bank feeds make that almost effortless: transactions flow in automatically and match against what's already recorded, so reconciliation becomes a quick review instead of a daily chore.

But that convenience rests on one quiet assumption — that your bank connects through Plaid, the data network Sage Intacct uses to pull transactions automatically. So what happens when it doesn't?

The challenge: a bank Plaid doesn't support

Not every financial institution is on Plaid's supported list. We recently worked with a client whose bank wasn't — which meant the out-of-the-box automatic feed simply wasn't an option.

The fallback was the routine every controller knows too well: log into the bank, pull the day's activity, import or re-key it, and reconcile by hand. Every account, every day. It works, but it's slow, easy to fall behind on, and exactly the kind of repetitive task that automation was built to eliminate.

The solution: a file-based feed that behaves like the real thing

Here's the good news: even when a bank doesn't connect through Plaid, there's a good chance they will be able to deliver a daily BAI2 file — the banking industry's standard format for reporting transaction activity.

We built a lightweight integration that does the rest. It picks up that file, translates each transaction, and creates native bank feeds and reconciliations directly in Sage Intacct through its Web Services API. The end result looks and behaves just like a standard feed — transactions land in Intacct ready to auto-match — with no manual download, import, or data entry.

What it takes to set up

The integration has three prerequisites:

• A Sage Intacct Web Services developer license — this is what allows the integration to read accounts and create feeds programmatically.
• A matching rule set applied to every checking account in Intacct — without it, Intacct can't auto-match the incoming feed, and reconciliation setup will fail for that account. (The integration flags this clearly when it happens, so it's an easy fix rather than a mystery.)
• The ability for the bank to automate the delivery of a daily BAI2 transaction file to an SFTP server.

Rule sets are configured under Cash Management → Setup → Reconciliation rules → Rule sets. Each checking account needs one applied so Intacct can auto-match the incoming feed.

Built for the messy realities of month-end

Moving transactions is the easy part. The real engineering goes into handling everything that can go sideways in day-to-day operations — and this is where the integration earns its keep.

• Duplicate detection. Before creating a feed, it checks whether one already exists for that account on that date. If it does, the account is skipped — so re-runs or a re-sent file never produce duplicate transactions. (If finer control is ever needed, this can be extended to the individual transaction level.)

• End-of-month safeguard. Before importing, it checks for any reconciliations still open from the previous month on the accounts in the file. If one is still open, the whole file is held and left in place — protecting your close from new-month activity landing in the wrong period. Once those reconciliations are closed, the file processes itself automatically.

• Automatic retries. If a file errors out, it's automatically re-queued and retried on the next run — no babysitting required.

• Batch processing. Multiple bank files are handled in sequence in a single run, so a backlog clears itself.

• Email notifications. After every run, the team gets a summary email — how many feeds were created, total credits and debits, and a clear list of any errors that need attention.

The goal was simple: the integration should be something the finance team can trust to run quietly in the background, and only hear from when it genuinely needs them.

Visibility when something doesn't match

Automation should never feel like a black box. To keep reconciliation transparent, we also built an Unmatched Transaction Report — a Platform app that lives right inside Sage Intacct.

It lists unmatched bank and Intacct transactions side by side, with search, source filtering, and column sorting built in, plus one-click export to CSV. When something doesn't line up, the team can see exactly what and why in seconds — no exporting, no spreadsheets, no guesswork.

The Unmatched Transaction Report runs right inside Sage Intacct — searchable, sortable, and exportable, so nothing slips
through the cracks.

The takeaway

A bank that isn't supported by Plaid doesn't have to mean a lifetime of manual reconciliation. With the right file feed and a thoughtful integration, you can get the same hands-off, auto-matching experience Sage Intacct users expect — plus guardrails tuned to your close process.

If your organization is wrestling with a bank that won't connect, a clunky manual import, or any other gap between your systems, that's exactly the kind of problem we love to solve.

Looking for More on Sage Intacct?

For more helpful tips and tricks about Sage Intacct, subscribe to our blog and stay up-to-date with our latest tutorials. We're dedicated to providing valuable resources for businesses looking to optimize their financial management with Sage Intacct.

Check out these blogs to help get you started!

Sage Intacct R2 2026: What You Need to Know about the Latest Release
Why Nonprofits Choose Sage Intacct Over Oracle NetSuite: 8 Key Reasons
Create Expanded Columns and a Summary for Reports in Sage Intacct