Build native integrations through our scalable Unified APIs
Showcase integrations, partners, and apps to your customers
Intuit Bank Feeds, in early access
Get your platform into QuickBooks Online
QuickBooks doesn’t accept pushed bank statements; Intuit pulls them from an FDX data provider. Apideck runs that provider, so you post to the same Bank Feeds API you use for Xero, and your customers link you from QuickBooks.
Banking
Your Application
Business account ••4821
Bank balance
$45,812.40
- 6 OctCard, office suppliesCategory: Supplies−470.55Add
- 4 OctCustomer refundMatch: CN-208+96.00Match
- 3 OctAd spendCategory: Advertising−612.00Add
- 2 OctContractor paymentCategory: Contractors−1,250.00Add
Your Application’s account in QuickBooks Online. Sample data, simplified mock-up.
What is Intuit Bank Feeds?
Intuit Bank Feeds is how a financial platform gets its customers’ transactions into QuickBooks Online as a bank feed. Unlike Xero or NetSuite, QuickBooks does not accept statements you push. Intuit pulls accounts and transactions from an FDX data provider on its own schedule. Apideck runs that provider, FDX Connect, and lists your platform as its own institution in QuickBooks’ bank list.
QuickBooks is one route. Your integration serves them all.
Each customer’s transactions go to the ledger that customer uses: QuickBooks through Intuit, Xero and the others natively, Plaid-powered apps next. Type your name and watch it route.
Your Application
Your customers’ accounts
- Harbor Bakery
- Atlas Freight
- Lumen Studio
Select a transaction to inspect its payload
Lumen Studio’s cash-flow app
On the Plaid network
Balance at Your Application
$9,623.10
Atlas Freight’s QuickBooks Online
Through Intuit Bank Feeds
Latest for review
Freight invoice paid
Harbor Bakery’s Xero
Native bank feed
- Flour supplier−470.55Match Bill FLR-311
- Card sales, daily settlement+1,832.40Match INV-1043
- Routed this session
- 0
- To Plaid apps
- 0
- To QuickBooks via Intuit
- 0
- To native feeds
- 0
Simulated data and sample customers. Each customer’s transactions go to the system that customer uses; Plaid and Intuit request them on their own schedule, native feeds receive statements as you post them. One integration on your side serves all of them.
Already on Xero?
Change one header.
QuickBooks uses the same statement call. Point it at intuit-bank-feeds instead of xero and keep the payload. On top, you add one endpoint to your login for the signed handoff.
Xero, native feed
Authorization: Bearer <APIDECK_API_KEY>x-apideck-app-id: <APP_ID>x-apideck-consumer-id: <CUSTOMER_ID>x-apideck-service-id: xero// statement body: identical
QuickBooks Online, Intuit Bank Feeds
Authorization: Bearer <APIDECK_API_KEY>x-apideck-app-id: <APP_ID>x-apideck-consumer-id: <CUSTOMER_ID>x-apideck-service-id: intuit-bank-feeds// statement body: identical
The statement body both receive
{ "bank_feed_account_id": "bfa_01H8X9Y2A3B4C5D6E7F8G9H0J1", "start_date": "2026-10-01T00:00:00Z", "end_date": "2026-10-07T23:59:59Z", "start_balance": 45812.40, "start_balance_credit_or_debit": "credit", "end_balance": 48212.40, "end_balance_credit_or_debit": "credit", "transactions": [ { "source_transaction_id": "txn_01H9A2B3C4D5E6F7G8H9J0K1L2", "posted_date": "2026-10-07T09:12:00Z", "description": "Payout to seller account", "amount": 2400.00, "credit_or_debit": "credit" } ]}
You push, Intuit pulls, Apideck sits in between
The one real difference from other ledgers: timing. Transactions reach QuickBooks after Intuit’s next pull, not the moment you post.
- 1You
Post statements
Same Bank Feeds API call as every other ledger, as transactions settle.
- 2Apideck
Hold them for Intuit
FDX Connect keeps each statement in an encrypted store until Intuit collects it.
- 3Intuit
Pull on its schedule
Intuit reads accounts and transactions over FDX, on its own schedule.
- 4Customer
Match in For review
Lines land in QuickBooks’ bank feed, ready to match to invoices and bills.
What is FDX Connect?
The provider Intuit pulls from.
FDX Connect is Apideck’s data provider built on FDX, the open banking standard Intuit reads. You never call it: you post to the Bank Feeds API, and FDX Connect serves the data to Intuit when it pulls.
- An OAuth and OpenID Connect sign-in server, with one issuer per listing, so each platform is its own institution in QuickBooks
- A signed handoff to your existing login and MFA; it never sees a password
- The FDX read endpoints Intuit calls: accounts, balances and transactions, scoped to what each customer chose
- The same provider serves Plaid Core Exchange, so one sign-in contract covers QuickBooks and the Plaid network
Embedded or direct, the same architecture
Whether you power accounts inside other platforms or serve your own customers, the planes do not change. Only who owns the sign-in does. QuickBooks is the Intuit lane.
Your Application powers accounts inside partner platforms, such as marketplaces or vertical software. Each partner owns the login and the brand, so its customers find the partner’s name in the bank list. Your Application sends data once; nothing changes for it per partner.
Apideck is never in the money path. A bank feed carries data; money stays with Your Application.
Found in QuickBooks, signed in on your login
Your customer starts in QuickBooks Online and ends on the Your Application login they already trust. Step through it.
A business customer of Your Application links their account from inside QuickBooks Online. The sign-in is Your Application’s own, Intuit pulls the data from FDX Connect, and the transactions land in QuickBooks’ bank feed.
Link account
Your Application
yourapplication.example
Harbor Savings
harborsavings.example
Step 1 of 7
Early accessThe customer links an account in QuickBooks
QuickBooks
Intuit
ApideckIn Banking, the customer searches QuickBooks’ bank list. Your Application is listed as its own institution, filed with Intuit during onboarding.
Illustrative walkthrough with sample data. Screens are simplified mock-ups, not Plaid’s, Intuit’s, Xero’s or any app’s actual interface.
Intuit’s rules for every statement
These come from Intuit, not from us, so they apply through any provider. Build to them and statements go through first time.
- 1,000
- transactions per statement, at most
- Unique
- source_transaction_id on every line, never reused
- By date
- transactions in posted-date order
- Posted
- lines only, no pending transactions
- 255
- characters per description, at most
- 1 currency
- per feed account, matching the linked QuickBooks account
What works in early access
Straight answers, so you can plan your launch.
- Create, list and read feed accounts and statements, Works todayThe full flow from your side: register accounts, post statements, read them back
- Knowing Intuit has collected a statement, Not yetStatements read back as pending; a collected signal is not exposed yet
- Retrying a post, Good to knowNo idempotency key yet. A reused transaction ID rejects the whole statement and names the rule, so read back before retrying
- Your listing in QuickBooks’ bank list, Good to knowFiled with Intuit during onboarding; Intuit’s process sets the timing
Works todayNot yetGood to know
Two calls you already make, one endpoint you add
Register each account once, then post statements as transactions settle, with the service set to intuit-bank-feeds. The only new code lives on your login: accept the signed handoff and send back a signed result.
Every statement:
- Reconciles to the cent: start balance + credits − debits = end balance
- Unsigned amounts: the direction lives in credit_or_debit
- A unique source_transaction_id: one per line, never reused; QuickBooks rejects the statement otherwise
Authorization: Bearer <APIDECK_API_KEY>x-apideck-app-id: <APP_ID>x-apideck-consumer-id: <CUSTOMER_ID>x-apideck-service-id: intuit-bank-feeds{ "bank_feed_account_id": "bfa_01H8X9Y2A3B4C5D6E7F8G9H0J1", "start_date": "2026-10-01T00:00:00Z", "end_date": "2026-10-07T23:59:59Z", "start_balance": 45812.40, "start_balance_credit_or_debit": "credit", "end_balance": 48212.40, "end_balance_credit_or_debit": "credit", "transactions": [ { "source_transaction_id": "txn_01H9A2B3C4D5E6F7G8H9J0K1L2", "posted_date": "2026-10-07T09:12:00Z", "description": "Payout to seller account", "amount": 2400.00, "credit_or_debit": "credit" } ]}
Built for platforms that hold the money
- Corporate card issuers
- Card spend lands in QuickBooks’ For review, ready to code, instead of a monthly CSV import.
- Embedded banking and treasury
- Accounts you hold for businesses show up in QuickBooks’ bank list by name, like any bank.
- BaaS and multi-brand platforms
- One institution per brand you power, each under its own name and login, from one integration.
- Payouts and marketplaces
- Sellers reconcile payouts and fees in QuickBooks, next to their other bank accounts.
What Intuit receives
- Accounts, with name, type and currency
- Current and available balances
- Posted transactions, with date, description and amount
- Only the accounts each customer chose to share
What it does not
- Money. A feed carries data. Nothing moves between accounts.
- Passwords. Customers sign in on your login. Intuit and Apideck never see credentials.
- Pending transactions. QuickBooks takes posted lines only.
Before you go live
Tick what you already have. None of it is new infrastructure. Finish the list and book a call to plan your QuickBooks listing.
QuickBooks, without becoming a data provider
Intuit only pulls from FDX data providers. Here is what you get by not building one.
No data provider to build
QuickBooks only pulls from FDX data providers. Apideck runs one, FDX Connect, so you never build, host or certify it.
The API you already use
Same Bank Feeds endpoints and payload as Xero and NetSuite. QuickBooks is one header away.
Your name, your login
Your platform is its own institution in QuickBooks’ bank list, and customers sign in on your login with your MFA.
One provider, two networks
The FDX Connect provider that serves Intuit also serves Plaid Core Exchange, next. One sign-in contract for both.
Europe included
QuickBooks is strongest in North America. The same API posts statements into Exact Online, Moneybird, Pennylane, Snelstart and Twinfield.
A member of FDX
Apideck is a member of the Financial Data Exchange, the standards body behind the specification Intuit reads.
Questions to ask any QuickBooks bank feed provider, including us
Getting into QuickBooks’ bank list is the start. These separate a listing your customers trust from one they have to be talked through.
- Is my platform listed under its own name?
- Customers search QuickBooks’ bank list for the name on their card or statement. A shared listing puts someone else’s name in between.
- Where does my customer sign in?
- On your login, with your MFA? Or on a screen the provider hosts, which your customers have never seen?
- Who runs the FDX server Intuit pulls from?
- QuickBooks pulls over FDX. Ask who hosts the provider, keeps it conformant and answers Intuit when something breaks.
- Where does data wait before Intuit pulls it?
- A pull model means storage. Ask where statements are held, how they are encrypted, and who can read them.
- What happens when a post is retried?
- Ask how duplicates are caught. Ours today: a reused transaction ID rejects the whole statement and names the rule.
- What else does the same integration reach?
- QuickBooks is one ledger. Ask whether Xero, NetSuite and the Plaid network come with it or need another project.
QuickBooks is one route. The same API reaches the rest.
Put your application in QuickBooks Online
Early access is open to platforms that hold account and transaction data. We take you through onboarding and file your listing with Intuit.
Your own listing
Customers find your name in QuickBooks’ bank list and sign in on your login.
No new integration
The Bank Feeds API you use for Xero, with one header changed.
Prefer to talk it through?
Questions
What is Intuit Bank Feeds?
Intuit Bank Feeds is how a financial platform gets its customers’ transactions into QuickBooks Online as a bank feed. QuickBooks does not accept pushed statements: Intuit pulls account and transaction data from an FDX data provider on its own schedule. Apideck runs that provider, FDX Connect, so a platform posts statements to the same Bank Feeds API it uses for Xero or NetSuite, and its customers link the platform from QuickBooks’ own bank list. It is in early access.
Why can’t I push statements into QuickBooks like I do into Xero?
Because QuickBooks Online only ingests bank data by pulling it from a data provider. Xero and most other ledgers accept statements you push. Apideck hides that difference: you keep posting to POST /accounting/bank-feed-statements, and FDX Connect holds the statement until Intuit collects it.
I already send bank feeds to Xero through Apideck. What changes?
The request stays the same. You point it at QuickBooks by changing the x-apideck-service-id header to intuit-bank-feeds, keep posting the same statement payload, and add one endpoint to your login for the signed sign-in handoff. Plan for one feed account per currency, since QuickBooks rejects statements whose currency differs from the linked bank account.
How quickly do transactions appear in QuickBooks?
After Intuit’s next pull, not the moment you post. Intuit sets its own schedule. Until it collects a statement, the statement reads back as pending.
Is QuickBooks Online on Plaid’s network?
No. Intuit runs its own aggregation and takes institution data directly from data providers under its own program, not through Plaid. That is why QuickBooks has its own route, Intuit Bank Feeds. The same FDX Connect provider also serves Plaid Core Exchange, so one sign-in contract covers both.
Does Apideck store my customers’ data on this route?
Yes, unlike Apideck’s usual pass-through. Because Intuit pulls rather than receives, statements wait in an encrypted store on Apideck’s side until Intuit collects them. Zero data retention does not apply to this route.
Do I need my own agreement with Intuit?
You do not build or certify a data provider yourself: Apideck operates FDX Connect and files your platform as its own institution with Intuit during onboarding. Intuit’s process sets the timing of that listing.
What works in early access?
Creating, listing and reading feed accounts and statements. Statements read back as pending, without a signal yet that Intuit has collected them. Request early access and we will take you through onboarding and your listing with Intuit.