Post statements from your platform through the Bank Feeds API and Apideck creates a bank feed on the matching checking, savings or credit card account in Sage Intacct. The transactions are then available to match in Intacct’s bank reconciliation, on both the XML and the REST API.
x-apideck-service-id: sage-intacct{ "bank_feed_account_id": "BOA-OPERATING", "start_date": "2026-10-05T00:00:00Z", "end_date": "2026-10-11T23:59:59Z", "start_balance": 120400.00, "start_balance_credit_or_debit": "credit", "end_balance": 131890.50, "end_balance_credit_or_debit": "credit", "transactions": [ { "source_transaction_id": "po_77310", "posted_date": "2026-10-06T12:00:00Z", "description": "Payout, marketplace sales", "counterparty": "Northwind Marketplace", "reference": "PO-77310", "amount": 14250.00, "credit_or_debit": "credit", "transaction_type": "deposit" }, { "source_transaction_id": "po_77322", "posted_date": "2026-10-09T12:00:00Z", "description": "Platform fees, October", "counterparty": "Northwind Marketplace", "reference": "FEE-1009", "amount": 2759.50, "credit_or_debit": "debit", "transaction_type": "debit" } ]}
01How it works
Sage Intacct records bank data as bank feeds attached to a cash account: a checking, savings or credit card account. Each feed carries a batch of transactions with a posting date, type, document number, payee, amount and description. Intacct can fill feeds itself from connected banks through Sage Cloud Services, or accept them as data sent through its API.
Apideck uses the second route. A statement you post becomes an API-sent bank feed on the account you name, and its transactions join Intacct’s bank reconciliation, where the bookkeeper matches them to what is already in the books. There is no separate feed account to register: you post against a cash account that already exists in Intacct.
01 · Your platform
GET /accounting/bank-accounts to find the Intacct account
02 · Your platform
POST /accounting/bank-feed-statements with that account’s ID
03 · Apideck
Creates a bank feed on the account, XML or REST API
04 · Bank reconciliation
Transactions are available to match in Intacct
02Setup
There is nothing to install in Intacct beyond the Apideck Sage Intacct connection itself. The work is choosing the right account for each feed.
Your customer connects Intacct through Apideck Vault, on the XML (Web Services) connector or the REST connector.
List bank accounts with GET /accounting/bank-accounts and pick the checking, savings or credit card account your platform’s account maps to.
Send that account’s ID as bank_feed_account_id on each statement. Apideck creates the bank feed on that account.
The bookkeeper matches the fed transactions in Intacct’s bank reconciliation, the same place feeds from banks arrive.
Full step-by-step instructions: Bank feeds developer guide.
03Fields
Each transaction in your statement becomes a line on the Intacct bank feed. The feed itself takes the account and the statement date.
| Intacct bank feed | From your statement | |
|---|---|---|
| Account (FINANCIALENTITY) | bank_feed_account_id | The cash account ID |
| Feed date | start_date | |
| Posting date | transactions[].posted_date | |
| Transaction type | transactions[].transaction_type | Mapped to Intacct types |
| Document number | transactions[].reference | |
| Payee | transactions[].counterparty | |
| Amount | transactions[].amount, signed by credit_or_debit | |
| Description | transactions[].description | |
| Transaction ID | transactions[].source_transaction_id |
In Intacct the statement ending balance belongs to the bank reconciliation, not to the feed. Keep sending reconciling start and end balances, which the Bank Feeds API and other ledgers expect, and treat Intacct’s reconciliation as the place the balance is confirmed.
04In production
Both Sage Intacct connectors post bank feeds. Listing bank accounts works on both; creating a bank account through the API is on the XML connector.
Statements post against an existing cash account. There is no bank-feed-accounts resource on Intacct.
Apideck creates API-sent feeds (feed type xml). Intacct’s own bank connections through Sage Cloud Services use a separate feed type.
Creating the feed does not reconcile it. Matching happens in Intacct’s bank reconciliation, where the bookkeeper reviews or confirms the matches.
05FAQ
Yes. Intacct’s API can create bank feeds on checking, savings and credit card accounts, with the transactions sent in the request. Apideck uses this on both the XML and REST APIs, so you post one unified statement and Apideck creates the Intacct bank feed.
No. On Intacct you post statements against an existing checking, savings or credit card account. Find its ID with GET /accounting/bank-accounts and send it as bank_feed_account_id.
In bank reconciliation for that account, where they are available to match against transactions already in the books, alongside any feeds Intacct receives from banks.
Yes. Apideck has a Sage Intacct REST connector alongside the XML Web Services connector, and both post bank feed statements.
Intacct keeps the statement ending balance on the bank reconciliation rather than on the feed. Send reconciling balances anyway; they keep your statements valid across every ledger on the Bank Feeds API.
One Bank Feeds API, every ledger
The statement you send to Sage Intacct is the same one that reaches Xero, Exact Online, Moneybird and the other native ledgers, and QuickBooks Online through Intuit.