Skip to main content

The Movement object

A Movement represents a single transaction in a bank account, such as a transfer, a check, or another debit or credit. It is retrieved from an institution for an account under a Link and is returned when you list or fetch movements.
Movement Object
Post date and transaction dateAs you probably noticed, each movement includes two different dates: a post_date and a transaction_date 🧐. This is because the bank uses accounting dates internally. Some bank even create movements in the future. For example, if you make a transaction on a Saturday, this transaction will appear to have Monday as its date. In this example, Saturday corresponds to the transaction_date, and Monday corresponds to the post_date.
Pending checksChecks take some time to be confirmed by the bank. This can take as long as 48 business hours. Pending checks can be reversed for several reasons (for example, lack of funds). Fintoc marks pending checks with the pending flag so you know that the movement isn’t yet confirmed by the bank.

Movement Status

The status field indicates the current state of a movement. Movements are initially confirmed, but may transition to other statuses as bank data is processed and validated.

The Transfer Account object (within the Movement object)

The Transfer Account object identifies the account on the other side of a transfer, and it appears in the sender_account and recipient_account fields of a Movement.
Transfer data problemsTransfer data can sometimes be null or wrong. This can be due to the movement not being a transfer or because of matching problems with the banks statements. Always double check the transfer data before reconciliating your movements. On the other hand, movement data is always reliable. The transfer data can change up to 5 days after the movement was created.