# Intuit Bank Feeds — Accounting API: gotchas

> Canonical URL: https://developers.apideck.com/apis/accounting/intuit-bank-feeds/gotchas

## GET /accounting/bank-feed-accounts

`feed_status` reads back as `pending` for every account in this release — it does not yet reflect
whether QuickBooks has picked the feed up. `status` is returned for every account, including
revoked ones.

## POST /accounting/bank-feed-accounts

**No QuickBooks OAuth connection is required or used.** `intuit-bank-feeds` is a separate connector
with its own connection lifecycle, so a bank-feeds-only integration never authenticates to
QuickBooks: connecting `quickbooks` does nothing for this connector, and this connector needs
nothing from it.

**QuickBooks requires holder contact data on every account.** It reads the holders' names,
emails, addresses and phones with each account, so `account_holders`, `emails`, `addresses` and
`phone_numbers` must each carry at least one entry, or the account is rejected with one
`contact_required` violation per missing list. Each list holds at most 10 items, and only the
fields the bank-feed provider stores are forwarded: an address keeps `type`, `line1`–`line3`,
`city`, `state`, `postal_code` and `country`, and `id` is dropped from every item.

- Each holder needs `first_name` and `last_name`, or `business_name` when `type` or
  `relationship` marks it as a business.
- At least one phone must be servable: `type` one of `mobile`, `home`, `work`, `office`,
  `personal` or `fax`, at most 15 digits across `area_code` and `number`, and the country code in
  `country_code` rather than a leading `+` in `number`.
- Each address needs `line1`, `city` and `country` as an uppercase ISO 3166 alpha-2 code. Address
  lines, `city` and `state` are limited to 64 characters and `postal_code` to 10. Each email must
  be a valid address.

An address that carries only fields the bank-feed provider does not store (for example only
`string`) is dropped, and the account is then rejected as if the list were empty.

A connection only becomes callable once it reports ready, so a newly created one can briefly stay
in the `added` state. Re-check it and retry rather than reading `added` as a failure.

Field handling is stricter than the unified contract: `null` is rejected rather than ignored, so
omit an optional field instead of sending `null` for it. `feed_status` is not returned on this
create response — read the account back to see it.

`balance_as_of` is when `balance` was true; when `balance` is sent without it, the time the
balance was received is recorded instead. A value without a timezone offset (`Z` or `±hh:mm`), or
one that is not a valid date-time, is rejected with `timezone_offset`.

Posting the same `source_account_id` again updates that account rather than creating another,
and returns the same `id`, so retrying a create that timed out is safe. The update replaces the
account: fields left out of it are cleared.

`status` sets a new account's consent: send `revoked` to create it without sharing it with the
data consumer. Omitted, it defaults to `active`. When the `source_account_id` already exists,
`status` is ignored and the account keeps its current status; change it with an update.

## GET /accounting/bank-feed-accounts/{id}

`feed_status` reads back as `pending` for every account in this release — it does not yet reflect
whether QuickBooks has picked the feed up.

`status` is the consent for this account: `revoked` means QuickBooks no longer receives it.

## PATCH /accounting/bank-feed-accounts/{id}

Only `status` is changed: set it to `revoked` to stop the data consumer receiving this account,
and to `active` to restore it. Nothing is deleted. Other fields in the request are ignored, and a
request without `status` is rejected by the provider.

## GET /accounting/bank-feed-statements

List responses carry statement metadata only — `transactions` is never included, however many
statements the page holds. Fetch a single statement by id to read its transactions.

## POST /accounting/bank-feed-statements

A successful create does **not** mean QuickBooks has the statement. This connector is pull-based:
the statement is stored on the Apideck side and waits there for Intuit's scheduled pull. That is a
fundamental difference from `xero`, where a successful push means Xero already holds the data.
Because delivery happens later and out of band, `status` reads back as `pending` and does not
advance to `success` in this release; a `status` other than `pending` sent on write is rejected.

Statements are validated on the way in, and a violation is **rejected** — never silently dropped:

- At most 1000 entries in `transactions`.
- Every `source_transaction_id` must be unique, both within the statement and against transactions
  already submitted for the same bank feed.
- Transactions must be in chronological order: `posted_date` must be non-decreasing across the
  array.
- Posted transactions only — pending or authorization-hold transactions are not accepted.
- `description` is limited to 255 characters.
- Every timestamp needs an explicit timezone offset: `start_date`, `end_date` and each
  transaction's `posted_date` must end in `Z` or `±hh:mm`. A bare local datetime such as
  `2026-01-15T12:00:00` is rejected, even though the unified `date-time` format permits it.
- `null` is rejected rather than ignored. Omit an optional field instead of sending `null` for it.

A rejected statement comes back with every violation at once, each naming the rule it broke, so a
single round trip shows all of them.

Each transaction's `transaction_type` reaches QuickBooks as its transaction type; when it
contradicts `credit_or_debit` (for example `deposit` on a `debit` line), `credit_or_debit` decides.
`merchant_category_code` is sent as the merchant category, and `counterparty` as the payee on
`bank` accounts only — it is not sent for `credit_card` accounts.

## GET /accounting/bank-feed-statements/{id}

`transactions` **is** returned here, unlike the list operation, which carries statement metadata
only. Fetching a statement by id is the only way to read its transactions.

`status` reads back as `pending`. See the create operation for why it does not advance to
`success` in this release.


[API reference](https://developers.apideck.com/apis/accounting/reference.md) · [Coverage matrix](https://developers.apideck.com/apis/accounting/coverage)
