Transactions

Formerly "bank transactions": Synci now fetches activity from banks, brokerages, and crypto exchanges alike, so these are simply called transactions. For investment accounts, transactions represent account activity: trades, dividends, contributions, withdrawals, fees, and so on.

Transactions are synced automatically on each account's Sync frequency: every 6 hours by default, as often as every 2 hours on Pro, and as rarely as once a day if you choose. This happens if the following conditions are met:

• The account's Sync frequency isn't set to Never. New accounts sync automatically.

• The account and its connection are healthy (otherwise Synci retries once a day until they recover).

Banks that cap how many requests a day they accept may sync less often: Synci slows such an account down to every 6 hours, and further (up to once a day) if the bank keeps refusing.

Investment and crypto accounts sync once per day, since brokerages typically make activity available with a one-day delay.

Transactions are stored in Synci for as long as your Data retention settings allow.

Pending vs. booked

Bank transactions come in two states:

• Pending: The transaction has been authorized but not yet settled by your bank. Details like the amount, payee, or date may still change.

• Booked: The transaction has settled and its details are final.

Whether pending transactions are synced at all is controlled per account with Sync pending transactions in its Sync settings. When a pending transaction later becomes booked, Synci recognizes it as the same transaction and updates it in place, without creating a duplicate. Two settings under Settings > Advanced help with this, and both are on by default:

• Match settlements with changed amounts: Catches card pre-authorizations (like a fuel station hold) that book at a different amount.

• Match re-worded counterparty names: Catches counterparties the bank re-words when the transaction settles, for example RYANAIR.COM settling as RYANAIR.C 2833094798.

If the transaction was already transferred to a destination, your linked account settings (under When transactions become booked) decide which changes (status, payee, description, amount) are pushed through to the destination.

Available data

We fetch and store every available transaction field. For a full list, we recommend reading our API documentation for transactions.

In the Synci dashboard, click a transaction (or the three dots at the end of its row) to open its details. The Fields tab shows all non-empty fields, and the Transfer Logs, Rule Logs and Account tabs show its transfer logs, rule logs, and account details.

Mapped fields

Mapped fields are user-friendly fields Synci generates based on your account's Map fields settings. They make it easy to get the most commonly used values, without building your own logic around which raw transaction fields to use. They are also the fields Synci uses when transferring transactions to destinations like YNAB, Lunch Money, Google Sheets, Notion, and Actual Budget (through SimpleFIN).

For instance, many banks provide the transaction description in the "Remittance Information Unstructured" field, but other banks put it elsewhere. Mapped fields solve this headache for you.

Synci provides the following mapped fields:

• Date

• Payee

• Description

By default, each one uses Automatic mapping: Synci picks the best available field for your bank, with its own fallbacks when a bank leaves it empty. To override it, open the account's Settings > Map fields, turn off Automatic mapping for that field, and add the fields you want in order of preference. Synci tries them from top to bottom and uses the first one with a value.

• Payee and Description can use any raw transaction field, plus AI-enriched counterparty name and the options Creditor when negative, debtor when positive and Debtor when negative, creditor when positive. If none of your chosen fields has a value, the field is left empty.

• Date can use the Booking date or the Value date, for example to always use the value date instead of the booking date. If neither has a value, the automatic rule applies.

You can also check and adjust the mapping on your real transactions in the Transaction preview step right after connecting.

Enriched fields

If enrichment is enabled for an account, Synci adds cleaned-up data on top of the raw transaction: a normalized counterparty name and logo, a category, location details, and whether the transaction looks like a recurring subscription. Enrichment applies to bank accounts only, needs a plan with AI features (Pro), and covers transactions from the last 3 months. Pending transactions aren't enriched until they book.

Investment activity

Transactions on investment and crypto accounts carry additional trade details:

• Activity type: Buy, Sell, Dividend, Interest, Contribution, Withdrawal, Transfer, Fee, Tax, Stock Dividend, Stock Split, or Other.

• Instrument: The security involved: symbol, name, exchange, and asset class (stock, ETF, option, cryptocurrency, fixed income, mutual fund).

• Trade figures: Units, price per unit, fees, and the FX rate where applicable.

• Options: For option trades: ticker, call/put, strike price, expiration, and the underlying symbol.

Duplicate detection

Synci automatically detects and skips duplicates during syncing, using several layers of matching, from exact provider transaction IDs down to careful comparison of dates, amounts, and references. This keeps your data clean even when a bank re-delivers the same transactions or a pending transaction is replaced by its booked version.

For special cases, you can customize which fields are used for duplicate filtering with Fields for duplicate filtering under the account's Settings > Advanced.

Rules

Rules let you automatically transform or act on transactions using conditions and actions. When you create a rule for an account, you choose how it applies:

• Change my data in Synci: Attached to one or more accounts and applied as transactions are fetched. The changes are saved in Synci and apply everywhere the transaction is sent.

• Only on the way out: Shapes transactions as they leave Synci, while the transaction stored in Synci stays untouched. Attach it to a linked account to shape what one destination receives, or to a bank account as an output rule to shape everything it sends out (its destinations, the API, and webhooks).

Rules aren't available for brokerage and crypto accounts.

Every rule that fires leaves a rule log, so you can always see exactly what was changed and why.

Logs

Transfer logs

Every time a transaction is transferred to a destination, Transfer logs are created recording the outcome. Failed transfers can be retried, and completed transfers can be undone from the transfer log.

Rule logs

Every time a rule is triggered for a transaction, Rule logs are created detailing the exact action that was performed.