> ## Documentation Index
> Fetch the complete documentation index at: https://docs.finta.io/llms.txt
> Use this file to discover all available pages before exploring further.

# How Finta syncs your data

> Learn how often Plaid, GoCardless, Mercury, and Stripe data syncs to Finta, when to run a manual sync, and why updates can be delayed.

## Short answer

Finta keeps your data up to date automatically. The timing depends on how your account is connected.

* Plaid syncs when the bank reports new activity.
* GoCardless follows a bank-specific schedule, with no scheduled gap longer than 24 hours.
* Mercury syncs from webhooks when enabled and hourly otherwise.
* Stripe syncs after supported Stripe events.

You can also start a manual sync from most destination pages.

## Sync frequency by provider

The table below covers transaction and provider-record updates. Finta also refreshes account balances once per day; see [Daily balance snapshots](#daily-balance-snapshots).

*On a phone, swipe the table sideways to see all timing details.*

| Provider                                                     | Normal cadence                                                               | What to expect                                                                                                                                                                                                  |
| ------------------------------------------------------------ | ---------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Plaid](/bank-connections/plaid/manage-connection)           | Triggered when Plaid reports new activity from the institution               | Timing varies by bank. Posted transactions often arrive shortly after the bank sends the update, but Finta cannot promise a fixed interval.                                                                     |
| [GoCardless](/bank-connections/gocardless/manage-connection) | Scheduled per connection using the bank's available request window           | Timing varies by bank. Finta schedules the next request from the rate-limit window reported by the bank, with no scheduled gap longer than 24 hours.                                                            |
| [Mercury](/bank-connections/mercury/manage-connection)       | Webhook-triggered when Finta has an active Mercury webhook; hourly otherwise | With an active webhook, new activity normally reaches Finta within minutes. Connections without an active webhook receive a scheduled hourly sync.                                                              |
| [Stripe](/bank-connections/stripe/manage-connection)         | Webhook-triggered for supported Stripe events                                | Customer, product, price, subscription, and invoice records arrive after supported events. Charge transactions refresh after Stripe reports an available-balance update, which may occur later than the charge. |

## Daily balance snapshots

Finta refreshes account balances once per day for active connections, regardless of provider. If a destination includes a Balance History table, Finta starts a destination sync after storing that day's balance snapshot. This balance job is separate from the transaction and provider-record cadences above.

## Your first sync

Finta begins pulling account data after you authorize a bank connection. After you finish setting up a destination, Finta starts that destination's first sync.

The first sync may take longer than later updates. The provider may still be preparing or returning historical data, especially when you requested a long history or connected several accounts. There is no fixed completion time.

## Manual syncs

You can start a manual sync from most destination pages. A manual sync is useful after you:

* Change a destination's table configuration
* Repair its credentials
* Change its sync start date
* Fix a setup issue and want to retry

In pass-through mode, a manual destination sync requests fresh data from the bank or provider. Once [Storage Mode](/getting-started/storage-mode) is fully active, manual syncs serve accounts, transactions, holdings, and investment transactions from Finta's stored data instead. Neither mode can force a bank or provider to publish data that the provider has not made available yet.

## Coda syncs

Coda uses [Finta Pack sync tables](https://coda.io/packs/finta). Start those table syncs from inside your Coda document, not from a Finta destination page.

## Why data may appear later

An update can arrive later than expected when:

* The transaction is still pending or the bank has not reported it
* The provider has not sent an update yet
* The bank connection needs [re-authorization](/bank-connections/reconnect)
* The destination is disabled, has no configured table, or has invalid credentials
* An initial historical pull or backfill is still running

Check the [Syncs page in your Finta dashboard](https://app.finta.io/syncs) for run history and errors. You can also open the affected connection from the **Accounts** page or the affected destination from the dashboard to check its status and settings.