---
title: "Bank Feeds Partnership Guide: Xero, QuickBooks, NetSuite and More"
description: "Which ledgers need a partnership before you can offer bank feeds: Xero's financial services program, Intuit's FDP, Plaid, NetSuite, Sage Intacct and more."
author: "Bernard Willems"
published: "2026-11-12T00:00+02:00"
updated: "2026-11-12T11:06:18.128Z"
url: "https://www.apideck.com/blog/bank-feeds-partnership-guide"
tags: ["Unified API", "Guides & Tutorials"]
---

# Bank Feeds Partnership Guide: Xero, QuickBooks, NetSuite and More

A card program can push the same transactions into Xero and NetSuite, and the approvals behind the two have almost nothing in common. Xero won't open its Bank Feeds API until you hold a financial services partnership. For NetSuite, the customer's administrator installs two bundles, and that is the whole approval. QuickBooks Online only pulls from data providers on Intuit's network, and Apideck's Intuit Bank Feeds route gets your brand listed there during onboarding. Sage Intacct, Exact Online, Pennylane, Snelstart and Twinfield take statements through their accounting APIs with no separate bank feed program, but you still register for those APIs. These approvals take longer than the code, so they set the roadmap. For the technical side (posting statements, field mapping, rejected statements), see our [bank feeds API integration guide](https://www.apideck.com/blog/bank-feeds-api-integration).

## Bank feeds can need two approvals

The first approval comes from the ledger's bank feed program, such as Xero's financial services partnership or Intuit's Financial Data Platform. It decides whether your transactions appear in the customer's bank reconciliation screen under your brand. Then there's access to the ledger's accounting API, which you need before any customer can connect. Our [accounting and ERP partnership guide](https://www.apideck.com/blog/accounting-and-erp-partnership-guide) covers that layer for 55+ connectors. Most ledgers ask for one of the two, a few ask for neither, and Xero asks for both.

### 🔴 Your own bank feed partnership

The ledger opens its bank feed API only to providers it has approved, and the approval is between you and the ledger.

| Ledger | Bank feed program | Accounting API access |
| --- | --- | --- |
| Xero | Financial services partnership with Xero | Your own Xero app |

### 🔵 A network listing through Apideck

The ledger pulls bank data from a data network. Apideck runs the data provider and takes your brand through onboarding, so you don't build or certify a data provider yourself. Both routes are in early access, so you request them from Apideck's sales team.

| Ledger | Network | What you provide |
| --- | --- | --- |
| QuickBooks Online | Intuit Financial Data Platform | Brand name and logo, a hosted login with MFA, a help article |
| Ledgers on the Plaid network | Plaid Core Exchange | A hosted login with MFA |

### 🟢 No separate bank feed program

The ledger takes statements through its regular API. You may still need access to that API, which our [accounting partnership guide](https://www.apideck.com/blog/accounting-and-erp-partnership-guide) covers per connector.

| Ledger | Accounting API access |
| --- | --- |
| NetSuite | No partnership; the customer's admin installs two bundles |
| Sage Intacct | Web Services developer license with a Sender ID |
| Exact Online | Exact developer subscription and your own app |
| Pennylane | OAuth credentials from Pennylane's partnerships team |
| Snelstart | SnelStart certifies your integration before issuing a key |
| Twinfield | Certification under a paid Twinfield API subscription |
| Zoho Books, Moneybird | Self-service, or Apideck's credentials |
| Rillet | The customer's own API key |

## Xero: the financial services partnership

Xero's Bank Feeds API is closed. [Xero's own API specification](https://github.com/XeroAPI/Xero-OpenAPI/blob/master/xero_bankfeeds.yaml) says it is "only available to financial institutions that have an established financial services partnership with Xero." Existing partners request access from their Partner Manager, and everyone else contacts Xero to apply. Xero reviews the application, and your app is certified for bank feeds before customers can use it.

Xero sets the commercial terms of a financial services partnership in its own agreement with each partner. Its [developer pricing tiers](https://developer.xero.com/pricing) (a free Starter tier up to Enterprise, with the paid tiers priced in Australian dollars) don't apply here: [Xero's pricing FAQ](https://developer.xero.com/faq/pricing-and-policy-updates) excludes "Financial Services applications in banking, credit and payments that operate on different commercial contracts." Bank feed access doesn't depend on the Advanced tier either. That tier gates the Journals endpoint, Xero Practice Manager and Bulk Connections, while bank feeds come through the partnership.

Fintechs that aren't banks have a second option to watch. A [newer version of the specification](https://github.com/XeroAPI/Xero-OpenAPI/blob/master/xero_bankfeeds_v2.yaml), which covers feed connections (statements still use version 1), says the API is available to "financial institutions with a Xero partnership and approved app partners." For non-bank apps, Xero writes, "it automates statement imports into Xero bank and credit card accounts; it does not create a direct bank feed."

Once Xero approves you, Apideck's Xero connector posts statements through your certified app, and Vault handles each customer's OAuth connection. Xero checks the arithmetic on every statement (the start balance plus the lines must equal the end balance) and rejects duplicates. The opening balance can't be more than a year old, and the API has no endpoint to update or delete a posted statement, so you correct a mistake with a new one. The [Xero bank feeds developer guide](https://developers.apideck.com/guides/bank-feeds-xero) walks through the setup.

## QuickBooks Online: Intuit's Financial Data Platform

QuickBooks Online doesn't accept pushed bank statements. Intuit pulls bank data on its own schedule from data providers on its network, the Intuit Financial Data Platform (FDP). An institution that wants its own direct connection contacts Intuit's [Direct Connectivity team](https://www.intuit.com/partners/fdp/implementation-support/). Intuit doesn't publish fees or timelines for this track.

Apideck's [Intuit Bank Feeds route](https://www.apideck.com/intuit-bank-feeds), in early access, makes Apideck the data provider. Apideck runs an FDX data provider, and during onboarding your platform is filed with Intuit as its own institution. Each brand you power gets its own listing, and your customers find it by searching for your name in QuickBooks. You post statements to the same Bank Feeds API you use for every other ledger, and Intuit collects them on its next pull.

Before launch, you prepare:

- a sign-in on your existing customer login, with multi-factor authentication
- a login page Intuit can send users to, with its login URL and JWKS URL added in Apideck
- your brand name and logo for the QuickBooks listing
- one feed account per currency
- a help article that shows customers how to connect

The route covers QuickBooks Online in the US and Canada. A statement can hold up to 1,000 posted transactions, and pending ones aren't accepted. QuickBooks caps bank connections on its entry plans (one account on QuickBooks Free in the US, two on QuickBooks Lite in Canada), and in the US an accountant can't connect a bank account on a client's behalf. There's no sandbox for bank feeds; Intuit tests end to end in pre-production during onboarding. Your existing QuickBooks app connection doesn't carry over, since Intuit runs bank feeds as a separate program. Statements wait in an encrypted store on Apideck's side until Intuit collects them, which is why Apideck's zero data retention default doesn't apply to this route.

## The Plaid network

Some ledgers take bank data from Plaid. When the two companies [announced their partnership](https://www.xero.com/us/media-releases/xero-plaid-partnership/) in July 2025, Xero said "Plaid will power an increasing portion of Xero's US bank feed sources." A provider reaches that network through [Plaid Core Exchange](https://plaid.com/core-exchange/docs/), Plaid's free, FDX-aligned API specification, because Plaid has closed its older program, Plaid Exchange, to new integrations. Plaid's [onboarding guide](https://plaid.com/core-exchange/docs/onboarding-guide/) says some partners launch "in as little as one week," and that integrations "can take six to eight weeks once build work begins." Your OAuth flow has to include multi-factor authentication.

Apideck's Plaid route is in early access. You can write accounts and statements today, and delivery to Plaid follows Plaid's validation, with no launch date yet. Apideck's [Plaid bank feeds page](https://www.apideck.com/plaid-bank-feeds) lists the ledgers whose own help docs name Plaid as a source, including Xero in the US and Zoho Books.

## NetSuite: an admin install, no partnership

Oracle's Bank Feeds SuiteApp connects to a fixed list of banks, and [Oracle's help](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_159010939426.html) says "there is no way to add a new bank" to it. Providers outside that list deliver data through a Financial Institution Connectivity plug-in instead. Listing your own plug-in on the SuiteApp Marketplace takes a SuiteCloud Developer Network listing review and a completed Built for NetSuite review.

Through Apideck there's no Oracle agreement to sign. The customer's NetSuite administrator installs Oracle's free Bank Statement Parsers SuiteApp and Apideck's bundle, then sets up a format profile for the bank accounts. Apideck's [NetSuite setup guide](https://developers.apideck.com/guides/bank-feeds-netsuite) puts that at 10 to 15 minutes. NetSuite then picks up the staged statements on its next import, and the lines appear in Match Bank Data.

## Sage Intacct: approval sits on the accounting API

Sage Intacct accepts bank transactions sent through its API against a checking account that already exists in the customer's company, and the feed itself needs nothing extra installed. [Intacct's API reference](https://developer.intacct.com/api/cash-management/bank-feeds/) says "Bank feeds are currently supported for checking account reconciliation." The approval sits on the accounting side. Intacct's Web Services need a developer license, which includes a Sender ID. Software vendors can get one through Sage Intacct's Marketplace Partner Program or from a Sage account manager, and Sage doesn't publish the fees. You add your Sender ID to Apideck once, and each customer authorizes it in their Intacct company.

## European ledgers

None of the European ledgers Apideck supports for bank feeds needs a separate bank feed program before you can post statements. Access to their accounting APIs is where they differ:

- Exact Online: you register your own app, which needs an Exact Online developer subscription in each country (€15 a month in the Netherlands). Apideck has test credentials for the Netherlands only.
- Pennylane: its partnerships team issues OAuth credentials after reviewing your application. Pennylane takes statements against an existing account.
- Snelstart: SnelStart issues a permanent key only after it certifies your finished integration. Statements are create-only, so keep your own record of what you sent.
- Twinfield: Wolters Kluwer requires every API integration to be certified, as part of an ongoing paid Twinfield API subscription. Statements are create-only here too.
- Zoho Books and Moneybird: no partner approval is needed. Register an OAuth app yourself or use Apideck's credentials.
- Rillet: no partnership. Each customer creates an API key once Rillet turns on API access for their organization.

## Ledgers without a bank feed route

Some ledgers accept bank feeds only from financial institutions. [MYOB's Transactions API](https://developer.myob.com/api/myob-transactions-api/) "enables trusted Financial Institutions to directly integrate with MYOB to become bank feed providers," and access starts with an expression of interest. For MYOB Business and other ledgers that Apideck can't post a feed to, Apideck writes [journal entries](https://developers.apideck.com/guides/bank-feeds-journal-entries-workaround) instead. Those land in the books but skip the bank reconciliation queue, so check with your customers' accountants before you rely on them.

## Testing before a ledger approves you

Approval usually takes longer than the build, so most teams build first. Apideck's [interactive bank feeds demo](https://demos.apideck.com/banks) and the [sample app on GitHub](https://github.com/apideck-samples/bank-feeds-sync) run the whole flow on mock data. Several connectors have their own sandboxes, including Exact Online, and NetSuite offers partner trial accounts for extended testing. Xero and QuickBooks Online are the exceptions. Xero's Bank Feeds API opens only after Xero approves your own app, so you can't test bank feeds on Apideck's shared Xero credentials, though Apideck can demo the Xero flow in the meantime. QuickBooks Online has no bank feeds sandbox, and testing happens in Intuit's pre-production run during onboarding.

## How long each route takes

| Route | Time | Source |
| --- | --- | --- |
| Xero financial services partnership | Not published | Xero |
| Intuit direct listing | Not published | Intuit |
| Intuit Bank Feeds through Apideck | Set by Intuit's onboarding | Apideck |
| Plaid Core Exchange | As little as one week; six to eight weeks once build work begins | Plaid |
| NetSuite setup through Apideck | 10 to 15 minutes per customer | Apideck |

Where a vendor publishes no number, plan around that vendor's review, which usually runs longer than your build.

## Getting started

Arc, which offers startups deposit accounts and treasury management, puts it this way: "It's critical for our customers to sync that data to their accounting systems." Bank feeds are included in every Apideck plan on the connectors that support them, and any fees a ledger charges for API access are separate. Start a [30-day free trial](https://www.apideck.com/signup) to build against the demo and the sandboxes, or [book a demo](https://www.apideck.com/demo-request) to map your ledgers to the approvals above. If you need an introduction to a ledger's partnership team, contact [partners@apideck.com](mailto:partners@apideck.com). For QuickBooks Online, [request early access to Intuit Bank Feeds](https://www.apideck.com/intuit-bank-feeds).
