Write bank transactions from Codat to QuickBooks Online

Learn how to write your SMB users' bank transactions via our QuickBooks Online Bank Feeds integration

When an SMB user has connected their bank accounts, you're ready to write bank transactions from a source bank account to QuickBooks Online (QBO). You can write transactions from any account that has a status of connected when you retrieve bank account status and information.

Note the following requirements before writing bank transactions to QBO.

Ordered by cleared on date

To be written successfully, bank transactions must be cleared (not pending) and have a clearedOnDate of the current or prior day. In the Create bank transactions endpoint, the clearedOnDate is set in the date field.

Bank transactions must be ordered chronologically (from earliest to latest) by the clearedOnDate.

Cleared on date field names

The clearedOnDate is returned by the List bank transactions for a bank account endpoint. However, when writing transactions with Create bank transactions, you must supply the value of the clearedOnDate in the date field.

Historic transactions

You can write historic transactions of up to seven days based on the feed start date, as chosen by the SMB user in the QBO UI.

Codat sends bank transactions to QBO for a maximum of the past seven days.

Future bank feeds not supported

Writing future (future-dated) bank transactions to QBO is not supported.

Other requirements

Note the following requirements for writing bank transactions to QBO.

• You can only write bank transactions from one source bank account at a time.
• Bank transactions must be written in chronological order.
• A bank transaction can't be older than the most recent transaction available in the target bank account.
• Up to 1000 bank transactions can be written at a time.

How often to write transactions

QBO requires that bank transactions are sent from Codat in chronological order. Therefore, we recommend you post seven days of historic transactions on the initial write operation. For subsequent write operations, we recommend you post daily transaction data, which will be sent to QBO on a daily schedule.

Write bank transactions to QuickBooks Online

Make the following requests to the Codat API. All write requests are asynchronous.

1. Write bank transactions from an SMB user's connected source bank account using the Create bank transactions endpoint.

   POST https://api.codat.io/companies/COMPANY_ID/connections/CONNECTION_ID/push/bankAccounts/ACCOUNT_ID/bankTransactions
   Example request body (all fields are mandatory)

   {
     "accountId": "482342-acc-001",
     "transactions": [
       {
         "id": "7832323211-GIF",
         "amount": 450,
         "balance": 2000,
         "date": "2022-08-30T17:05:12.191Z", // clearedOnDate, time is optional
         "description": "events-hospitality"
       },
       {
         "id": "7832323211-SDC",
         "amount": 730,
         "balance": 2730,
         "date": "2022-08-31T11:06:49.191Z", // clearedOnDate, time is optional
         "description": "corporate-training"
       }
     ]
   }

   The balance of the last bank transaction in the array is used to update the balance of the specified bank account.

2. If the data is valid, the endpoint returns a write operation with a status of Pending (202). If the write completes successfully, this changes to Success.

3. Repeat the request for the remainder of the SMB user's source bank accounts.

Transactions reference

The following table details how each property in the transactions array is handled when writing bank transactions to QBO. For more details, see the Bank account transactions data type.

Property in the transactions array	Status
id	Required
date	Required
description	Required
counterparty	Not supported; ignored if written
reference	Not supported; ignored if written
reconciled	Not supported; ignored if written
amount	Required
balance	Required
transactionType	Optional, either Credit, Debit, or Unknown
modifiedDate	Populated automatically on write
sourceModifiedDate	Populated automatically on write