Bank Feed Extensions

Admin 5 min read Updated July 2026

Bank statements can arrive two ways: someone downloads and imports a file, or they simply appear — delivered by a bank feed. REDA Financials’ feed extension point makes the second way possible, with aggregation providers (the Plaid-style services) supplying the pipes.

What the core provides

Feed setup per bank account: which provider serves this account and its connection state — the socket a provider extension fills.
A provider-agnostic landing zone: fed transactions arrive as ordinary bank statements and lines — identical to a CSV import, just automatic. Everything downstream (matching, reconciliation) is unchanged.

Manual import vs bank feed

The cleanest way to understand what a feed buys you is a side-by-side of the two arrival paths — because everything after arrival is identical:

	Manual CSV import	Bank feed
How statements arrive	Someone downloads a file from the bank portal and imports it	They appear on their own schedule, delivered by the provider
Human effort	A recurring chore per account, per period	None once connected
What lands in the system	Bank statements and lines	Exactly the same bank statements and lines
Matching & reconciliation	Identical — everything downstream of arrival is unchanged
Coverage	Every bank on earth	By provider and region — ask REDA about your banks
When the other path is needed	—	CSV remains the fallback; the two coexist safely on the same account

What changes for the team

Only the arrival. With a feed connected, statements appear on their own schedule and reconciliation starts from “data’s already here” — the import step of the manual workflow simply disappears. If a feed hiccups, CSV import remains as the manual fallback; the two coexist safely on the same account.

Per account, not per org. The feed setup lives on each bank account: which provider serves it and the connection's state. One entity can run a fed operating account and a manually imported savings account side by side — each account decides its own arrival path.

A worked example — Meridian's mixed estate

Meridian Properties Group banks in four countries, and its accounts show both paths coexisting:

Account	Arrival path	What reconciliation looks like
US operating account	Feed — a provider extension is installed and registered on the account's feed setup	Statements are simply there each morning; the reconciler starts from "data's already here"
UK operating account	Manual — no feed provider connected for this bank yet	The clerk downloads and imports the CSV, then reconciles — the statements and lines are indistinguishable from the fed ones
US operating account, the week the feed hiccups	CSV fallback	The clerk imports manually for the gap; feed and fallback coexist safely on the same account

The reconciliation training is written once, because the workflow is one workflow — only the arrival differs.

Common mistakes to avoid

Mistake	Why it hurts	Do this instead
Waiting for feeds before starting banking work	Reconciliation is delayed for a convenience feature	Start with CSV import today — it covers every bank; feeds remove the chore later
Treating a feed hiccup as a reconciliation blocker	The close waits on a pipe, unnecessarily	Import the gap manually — CSV remains the fallback on the same account
Expecting the feed to reconcile for you	Feeds deliver data; matching and reconciliation are the same downstream work either way	Keep the reconciliation discipline unchanged; celebrate only the vanished import step
Assuming one provider covers all your banks and regions	Coverage is by provider and region	Check availability bank by bank with REDA before planning a rollout
Forgetting the feed setup is per bank account	Connecting one account tells you nothing about the others	Review each account's feed setup and connection state individually

Roll out feeds account by account. Because fed statements are identical to imported ones, there's no big-bang moment: connect the busiest account first, watch a cycle of statements arrive, and extend to the next. The fallback is always one CSV away.

Availability: feed extensions ship separately, by provider and region — ask REDA what’s available for your banks. Until then, CSV import covers every bank on earth.

Where to go next

Importing Bank Statements — the workflow feeds automate.
Extension Architecture — the pattern.

Frequently asked questions

No — fed transactions arrive as ordinary bank statements and lines, identical to a CSV import, just automatic. Everything downstream (matching, reconciliation) is unchanged.

No — CSV import remains as the manual fallback, and the two coexist safely on the same account. Import the gap by hand and carry on; reconnect the feed when it recovers.

It delivers the data; the matching and reconciliation workflows are exactly the ones you already know. What disappears is the download-and-import chore, nothing else.

Per bank account — each account's feed setup names its provider and connection state. Fed and manual accounts happily coexist, even within one entity.

Feed extensions ship separately, by provider and region — ask REDA what's available for your banks. Until a feed exists for a bank, CSV import covers it completely.

Was this article helpful?