Skip to main content
Redbark syncs posted transactions by default. Pending transactions are temporary records and can change when they settle. Banks can assign a new transaction ID at settlement. The amount or description can also change. If both versions were synced, the pending and posted records could appear as separate transactions because there is no reliable identifier linking them. Waiting for settlement means destination records are final and can be deduplicated by their posted transaction ID.

​
Card holds

Some banks, such as UBank and Bank Australia, share card holds as completed transactions, so Redbark treats those holds as pending and, with pending transactions off, each purchase appears once it settles. Duplicates written before this change stay in your destination until you remove them.

​
Include pending transactions

You can opt in for an individual sync, except a budget spreadsheet, which always excludes pending transactions:
  1. Open the sync.
  2. Select Settings.
  3. Enable Include pending transactions under Experimental.
This setting is likely to create duplicates when pending transactions settle with new IDs. You will need to remove those duplicates manually from the destination.
If a transaction has already posted but remains absent, follow Transactions are late or missing.