The new Apideck developer docs are live. See what’s new →

Bank feeds for business accounts in 2026: Plaid Core Exchange, FDX and the ledgers beyond QuickBooks

Plaid Exchange is closed to new integrations and QuickBooks Australia drops legacy feeds by 3 December 2026. What to build next: Core Exchange, FDX, push feeds.

Kateryna PoryvayKateryna Poryvay

Kateryna Poryvay · Growth Marketer, Apideck

11 min readView as .md
Bank feeds for business accounts in 2026: Plaid Core Exchange, FDX and the ledgers beyond QuickBooks

Plaid has closed Plaid Exchange to new integrations, and Intuit is switching off every legacy bank feed in QuickBooks Online Australia by 3 December 2026. If you run business accounts, cards or treasury, you have probably shipped a QuickBooks and Xero integration already, with NetSuite likely next, and these changes affect what you build after that. In the Embedded Finance Index (EFI, which Apideck publishes), QuickBooks, Xero and NetSuite are the accounting integrations fintechs disclose most often, and past them the ledgers change from market to market.

What's changing, in short:

  • Plaid: new data providers build to Plaid Core Exchange, an FDX-aligned spec that replaces Plaid Exchange, Plaid's older proprietary one.
  • QuickBooks Australia: Intuit is replacing legacy feeds with open banking feeds, bank by bank, on a schedule that ends on 3 December 2026.
  • FDX: Plaid and Intuit both work with FDX for these feeds. The US Section 1033 rule that put FDX at the center of financial data sharing is being rewritten, but it covers consumer accounts, so it doesn't decide how business feeds work.

Your customers' accountants reconcile from the bank feed. Arc, an Apideck customer offering startups deposit accounts and treasury management, puts it this way: "It's critical for our customers to sync that data to their accounting systems."

Business-account and card providers will get the most from the pull-side changes and the checklist. Payments providers should start with the section on payouts and fees.

Where your customers' books are

Which ledger comes after the first three depends on where your customers are. In EFI's November 2026 data, Xero ranks above QuickBooks in the UK and APAC, and DATEV is in the EU top five. The Benelux and French ledgers that European businesses run don't make any regional top five. EFI counts publicly disclosed relationships, from companies' own disclosures and providers' customer lists, so read it as a measure of disclosure rather than market share.

A provider expanding out of the US meets ledgers its first integrations don't cover, and most of them can't be reached through the US networks. Our ledger map 2026 has the full order by market and what each ledger takes to go live.

Two routes into the ledger

Transactions reach small-business accounting software in one of two ways, and most providers need both. On the pull route, your platform is a data source: you, or a provider acting for you, host an API, and a network such as Intuit's or Plaid's collects your customers' transactions from it for the ledgers it serves. On the push route, you post statements into each ledger yourself.

PullPush
Who moves the dataThe ledger, or a network acting for it, fetches from an API you hostYou post statements into the ledger's bank feed API
FormatFDX (US and Canada)Each ledger's own API
Where it appliesQuickBooks Online through Intuit; ledgers on Plaid's bank-feed networkXero, NetSuite, Sage Intacct, Exact Online, Zoho Books, Moneybird, Pennylane, Rillet, Snelstart, Twinfield
When data landsOn the network's scheduleWhen you post (NetSuite: on its next import, on a schedule the admin sets or on demand)
Who decides if you're inIntuit or Plaid onboardingXero requires a partnership; other ledgers set their own API access rules, then the customer authorizes

Bank feeds for business accounts in 2026: Plaid Core Exchange, FDX and the ledgers beyond QuickBooks inside article

For most US providers the pull route comes first, because of QuickBooks: QuickBooks Online doesn't take pushed bank transactions, and pulls from data providers on Intuit's network on Intuit's schedule. The push route covers what those networks stop short of, which is mid-market and most non-US ledgers.

What's changing on the pull side

Plaid Core Exchange replaces Plaid Exchange

Plaid's program for data providers is now Core Exchange, an API you host and Plaid calls. It is an FDX-aligned API specification, and the older Plaid Exchange is closed to new integrations. If you build direct, this is what you take on, and most of it concerns authentication:

  1. Build to a supported FDX version. Core Exchange covers FDX 4.6 to 6.4, and 6.4 is the latest.
  2. Run your own OAuth 2.0 server. Users log in on your domain, and Plaid receives a token, not their credentials.
  3. Require a second factor. Plaid requires 2FA for every Core Exchange connection, handled inside your own login flow.
  4. Keep access tokens short-lived (Plaid's docs describe 15 minutes). Rotate refresh tokens on each use, which Plaid prefers, or let them last 13 months or more to meet reauthorization requirements.

Plaid says a new integration can take six to eight weeks once build work starts. If you're already on Plaid Exchange, Plaid puts a typical migration at about 90 days, with customers re-authenticating; in select cases a backend token exchange moves connections without that step.

Apideck's route, in early access, changes that split: you still provide the login with MFA, but Apideck runs the FDX data provider and onboards your brand with Plaid, so you don't build or certify the API yourself.

What your FDX endpoint serves

If you build direct, Core Exchange asks for a small set of read endpoints: the customer's accounts, each account's details and balances, its transactions, its statements, and the account and routing numbers. Plaid requests transactions for a date range and filters on the posted date. A posted deposit transaction looks like this (field names from Plaid's Core Exchange 6.4 reference, values illustrative):

{
  "page": { "nextPageKey": "B47D80MVP23T" },
  "transactions": [
    {
      "accountCategory": "DEPOSIT_ACCOUNT",
      "transactionId": "txn_000481",
      "postedTimestamp": "2026-10-03T00:00:00.000Z",
      "transactionTimestamp": "2026-10-02T14:12:09.000Z",
      "description": "Wire from Acme Ltd, INV-2291",
      "debitCreditMemo": "CREDIT",
      "status": "POSTED",
      "amount": 657.65
    }
  ]
}

The amount is an absolute value, and debitCreditMemo carries the direction. A pending transaction and its posted version need different transactionIds, linked through referenceTransactionId. And postedTimestamp belongs on posted transactions only.

QuickBooks: Intuit's network, and Australia's switch

For QuickBooks Online in the US and Canada, Intuit runs the Financial Data Platform (FDP), its network of data providers. QuickBooks Online data providers go through its Direct Connectivity track, which accepts API standards including FDX, while OFX's Direct Connect and Web Connect serve QuickBooks Desktop and Quicken. In the US, only a QuickBooks company user can connect the feed (an accountant can't connect it for a client), so your onboarding has to reach the business owner.

In Australia the change is already under way. Intuit is progressively disconnecting all legacy bank feeds in QuickBooks Online Australia between 18 August and 3 December 2026 and replacing them with Consumer Data Right feeds. On Intuit's current schedule, which it says may change, Westpac goes on 18 November, ANZ on 24 November and CBA on 3 December.

QuickBooks Australia's bank list now labels each institution by connection type (Open Banking, Direct Feed or App connection), and accounts that aren't supported fall back to CSV upload. If you serve Australian businesses, check how your accounts are listed before your customers' feeds stop.

Why FDX is the format to build to

In the US and Canada, the shared format for the pull route is FDX, the Financial Data Exchange standard. FDX has over 200 member organizations, including Apideck, which sits on FDX's Corporate and Treasury API Task Force. Plaid's Core Exchange is FDX-aligned, and Intuit accepts FDX for QuickBooks Online alongside other API standards.

The CFPB approved FDX as a standard-setting body under its Section 1033 open banking rule in January 2025. A federal court stayed the rule's compliance dates in October 2025, and a reconsideration proposal went to the White House's regulatory review office (OIRA) in August 2026. The rule covers consumer accounts, so none of this changes the case for FDX on business feeds.

Push: the ledgers the networks don't reach

Plaid's bank-feed network covers a short list of ledgers, mostly in the US and Canada. NetSuite, Sage Intacct and the European ledgers are outside it, so for those you post statements into each ledger yourself. Xero is the exception: Xero's Bank Feeds API specification says the API is only available to financial institutions that have an established financial services partnership with Xero. Our bank feeds API integration guide covers how each ledger takes statements, with code, and the statement rules behind most rejected feeds.

For payments companies: payouts and fees in the books

Merchants of a payments provider have a different reconciliation problem. Their bank receives one payout, net of fees and refunds, while their books need sales, fees and refunds as separate entries. Accountants commonly handle this by keeping the processor balance as its own account in the ledger: every charge and deduction posts against it, and each payout is a transfer out of it that matches a deposit in the business's bank feed.

A bank feed fits that model. Register the merchant's processor balance as a feed account (account type bank), then post each statement with:

  • sales, refunds and fees as separate lines, told apart by description and reference
  • each payout as a transfer whose reference matches the deposit the merchant's bank shows

Apideck's statement lines also carry a transaction type (credit, debit, deposit, transfer, payment or other) and a counterparty. Statements have to balance, with the start balance plus every line equal to the end balance, so Xero rejects a statement that doesn't add up before an accountant has to find the gap. Apideck's Intuit route lists this case directly: sellers reconcile payouts and fees in QuickBooks next to their other bank accounts.

What to ask any bank-feed provider

Whether you build a bank feed integration yourself or buy one, ask these questions before you commit:

  1. Which ledgers get a native feed, and which get journal entries? Journal entries land in the general ledger without passing through the reconciliation screen, and accountants trust them less.
  2. How does QuickBooks Online get the data? Is that route live or in early access, and in which countries?
  3. If Plaid is involved, is it Core Exchange, and how do existing Plaid Exchange connections move over?
  4. Whose name appears in the ledger's bank list, yours or the provider's? Can each of your brands have its own listing?
  5. Whose Xero partnership does the Xero feed run under?
  6. Can you read back what each ledger accepted, and how do you learn about a rejected statement?
  7. How are duplicates prevented when a request is retried?
  8. Can a processor balance carry sales, refunds, fees and payouts as separate lines?
  9. Where does transaction data sit in transit? Pull routes have to hold statements somewhere until the network collects them.
  10. How far back can you backfill on each ledger?

How Apideck covers both routes

Apideck's Bank Feeds API puts both routes behind one set of endpoints. You register a feed account for each card, wallet or processor balance, then post statements with a start and end balance, and the same call reaches every ledger.

  • Push: ten ledgers take native feeds today and another 23 get journal entries, so customers on Business Central or MYOB are covered without a second integration. On NetSuite, the admin setup takes 10 to 15 minutes. Our bank feeds guide lists which ledger gets which.
  • QuickBooks Online: Apideck runs FDX Connect, its own FDX data provider. Through Intuit Bank Feeds, in early access in the US and Canada, your platform appears in the QuickBooks bank list under your own name, with one listing per brand. Statements wait in an encrypted store until Intuit collects them. A statement holds up to 1,000 transactions, each feed account carries one currency, and a rejected statement returns every violation at once.
  • Plaid: a Plaid route on Core Exchange is open for early-access requests, with no launch date yet.

Both pull routes are early, so check their status with us before you plan a launch around them. Customers connect their ledger through Vault, Apideck's white-label connection flow, which also covers the 55+ accounting and ERP connectors behind the rest of the Accounting API. You still own the Xero partnership and the decision about which brands and accounts to list.

Start the Xero and Intuit approvals now, because approval usually takes longer than the build; our bank feeds partnership guide covers what each ledger requires. Teams on Plaid Exchange should plan the move to Core Exchange, and anyone serving Australian businesses should check their QuickBooks listing before 3 December. If you want a second opinion, send us a count of your customers per ledger and we'll show whether each ledger gets a native feed, journal entries or Intuit's pull route, and where your coverage has gaps.

Trusted by fast-moving product & engineering teams

Bonsai by Zoom
JobNimbus
Blue Zinc
Exact
Drata