Skip to main content

Import bank transactions

Learn how to import bank transaction data from your application to your customer's accounting platform

Once a company has mapped their source account to a target account, you can begin creating bank transactions in their accounting platform using the established

The fallback content to display on prerendering
.

Generate transactions

Before you can record your customer's bank transactions in their accounting platform, you need to generate a transactions object for each transaction that has been made from their account.

Collect transaction data within your own application and map it to Codat's Bank transactions schema. Add this to Create bank transactions, including the sourceAccount id that the transactions should be associated with at the top level.

Transaction signs

Make sure the transaction amount signs align with the transactionType. Codat issues a warning for inconsistencies, such as a Debit transaction with a positive amount.

Push bank transactions

In Codat, creating a bank transaction is a two-step process (learn more about it here). It requires you to check the data model of the data type you want to create first to ensure all required properties are included in your request.

Next, you are ready to create the bank transaction. You will receive pushOperation key in return. You can then use it to monitor the status of the operation, or display its results.

Create bank transactions

We recommend regularly uploading transactions throughout the day so that your customers' bank feed balances are close to real-time. This enhanced accuracy helps companies with their planning and forecasting.

Use our Create bank transactions endpoint to create bank transactions. In response, you will receive a pushOperation object with a Pending status.

Quantity limit

A maximum of 1000 bank transactions can be pushed at a time.

const transactionsResponse = bankFeedsClient.transactions.create({
createBankTransactions: {
accountId: sourceAccountResponse.sourceAccount.id,
transactions: [
{
id: "63e2b848-951a-4657-a889-ded00f0e616a",
amount: 100.0,
balance: 100.0,
date: "2023-08-22T10:21:00.000Z",
description: "Repayment of Credit Card",
transactionType: BankTransactionType.Credit
},
{
id: "710ed9f9-feb6-4ab7-9055-05a26d31718c",
amount: -75.0,
balance: 25.00,
date: "2023-08-22T10:22:00.000Z",
description: "Amazon US | $1.25 | PXDFGSDTR | c2dddf4c-eece-4a9b-a392-8c8e65b59e47",
transactionType: BankTransactionType.Debit
}
],
},
accountId: sourceAccountResponse.sourceAccount.id,
companyId: companyResponse.company.id,
connectionId: connectionResponse.connection.id
});
QuickBooks Online bank feeds syncing info

Transactions pushed to QuickBooks Online bank feeds will show a Success status when they validated and saved by Codat. However, they will only become available in their accounting software after synchronization between QBO and Codat.

QBO automatically polls Codat daily for updates, and users can also manually trigger that sync from the QBO interface.

Monitor request status

After you submit your request to create bank transactions to our API, it will have a status of Pending. Use the PushOperationStatusChanged webhook to track when the status of your push operation changes to Success or Failed.

If the request is successful, you will receive a webhook like this:

{
"CompanyId":"c2dddf4c-eece-4a9b-a392-8c8e65b59e47",
"RuleId":"5a6f112d-b0fa-4c0b-9ea4-7dd4075bc43d",
"Type":"Push Operation Status Changed",
"AlertId":"a6bb69d5-631c-4732-8e4e-18bea36aea20",
"Message":"bankTransactions triggered notification for PushOperationStatusChanged at 2023-09-12T18:19:42.742Z",
"Data":{
"dataType":"bankTransactions",
"status":"Success",
"pushOperationKey":"e881111f-b6a4-4740-b125-340a6c300cd3"
}
}

If you want to see a history of all push operations for a specific company, retrieve these by calling the List create operations endpoint.


Was this page useful?
❤️
👍
🤔
👎
😭