When a new client walks in clutching a bank statement from a mutual building society or a regional credit union, most bookkeepers know the routine: check the format, start the import. What's less obvious is how the institution type affects everything from the statement export formats you'll be working with to how transactions are categorised and reconciled. Understanding these differences will save you hours of troubleshooting and set clearer expectations with clients from day one.
The Three Institution Types and What They Mean for Data Access
Australia's financial system broadly divides into authorised deposit-taking institutions (ADIs) — which includes the Big Four banks, regional banks, building societies, and credit unions — and non-ADI lenders. All three types your clients are likely to use fall under ADI supervision by APRA, but their participation in the Consumer Data Right (CDR) framework varies considerably.
The Big Four (ANZ, CBA, NAB, Westpac) and several major regional banks have been CDR-obligated since 2020–2021 and offer reliable, real-time bank feeds via accredited data recipients like Basiq. Larger building societies such as Newcastle Permanent and Greater Bank have progressively joined the CDR regime as obligations expanded, but many smaller mutuals and credit unions are still working through implementation or have applied for extensions. The Australian Competition and Consumer Commission (ACCC) publishes an up-to-date register of CDR participants — worth bookmarking.
In practical terms, whichever institution your client banks with, you'll be importing their statements rather than connecting a live feed: ReconLink ingests CSV, Excel and PDF bank statements (or your client forwards them to a per-client email inbox). Some institutions export cleaner files than others — a non-participating credit union may only offer a basic CSV — which can mean more time, more potential for transcription errors, and a higher chance of a reconciliation headache at BAS time.
Reconciliation Differences to Watch For
Whatever the export format, institution type introduces subtle differences in how transactions appear.
Building societies and credit unions often use non-standard transaction description formats. Where a major bank might label a direct debit as "EFTPOS WOOLWORTHS SUPERMARKETS SYDNEY", a credit union might produce "DD 0042938 SUPPLIER REF" — a reference code rather than a vendor name. This breaks pattern-matching coding rules that rely on merchant names and forces you to build custom rules or intervene manually far more often than you would with a Big Four client.
Interest calculations also differ. Credit unions frequently compound interest daily but credit it monthly, sometimes on the last business day of the month. If your client has a business savings or offset account with a credit union, make sure you're not accidentally coding those interest credits as trading income. They're typically coded to a "Bank interest received" account — not subject to GST (N-T) — but the timing and description format can trip up automated rules.
Loan offset accounts at mutuals are another edge case. These appear as separate account entries but functionally reduce the loan balance. They need to be set up as contra accounts in your chart of accounts and excluded from standard reconciliation runs.
Institutions With Messier Exports: Your Practical Workflow
If a client is firmly attached to their community credit union — and many are, for genuinely good reasons — don't fight it. Set up a reliable manual import workflow instead.
First, confirm what export formats the institution supports. Most credit unions and building societies provide CSV or OFX exports from online banking. OFX is generally cleaner because it includes a structured transaction ID that prevents duplicate imports. CSV formats vary wildly: some include running balances, some don't; some use DD/MM/YYYY, others use ISO 8601.
Second, establish a regular cadence. The biggest risk with manual imports is gaps — a client forgets to download for six weeks and you end up with two months of transactions to code under BAS pressure. Set a calendar reminder for your client to export and email their statement fortnightly, or use a tool like ReconLink's email inbox feature: your client forwards the downloaded statement to their unique inbox address and it's automatically ingested, parsed, and queued for coding.
Third, document the institution's quirks in your client file. Note the date format, whether transaction descriptions are truncated, and any known issues with the export (some institutions omit pending transactions from CSV exports, for instance). Future you — or a colleague covering your leave — will thank you.
When to Flag a Change of Institution
Occasionally the right advice is simply to suggest your client consider moving their business banking to a CDR-participating institution. This isn't a decision to push lightly — credit unions often offer genuinely better interest rates and lower fees — but if a client is spending $50 a month in bookkeeping time on manual statement wrangling, the maths can favour a switch.
Frame it as a workflow conversation rather than a product recommendation, and be careful not to provide financial product advice if you're not licensed to do so. Something like: "It's worth comparing what your current bank costs you in admin time versus what a CDR-connected account might save — that's a question worth putting to your financial adviser."
Setting Client Expectations from the Onboarding Call
The simplest fix is setting expectations early. During your onboarding checklist, ask every new client which institution they bank with and look it up on the ACCC's CDR register before the first meeting. If they're with a non-participating institution, tell them upfront: "We'll need to do manual imports for now — here's how that works, and here's roughly how long it adds to your monthly process."
Clients who understand the reason for extra steps are far more likely to co-operate with the workaround. Those who don't are the ones who forget to send statements, delay BAS lodgements, and end up frustrated with a bookkeeper who "takes forever."
Knowing the institution landscape isn't glamorous knowledge, but it's the kind of operational detail that separates bookkeepers who run tight, predictable practices from those perpetually firefighting at quarter-end.