Transfer logs

Transfer Logs are the "shipping manifest" for your financial data. They provide a detailed record of every attempt Synci makes to move a transaction from your bank to your destination, allowing you to track its journey and troubleshoot any delivery issues.

Written By Matias

Last updated About 4 hours ago

What are transfer logs?

Whenever Synci transfers a bank transaction, it creates a Transfer Log. Because a single bank account can be connected to multiple destinations via different Transfer links, a separate log is generated for each link.

These logs allow you to verify if a transaction was successfully delivered, why it might have been skipped, or exactly what error occurred if a transfer failed.

Information captured in a log

Each log entry provides key details about the transfer attempt:

Transfer Link: The specific connection (source bank to destination account) used for the transfer.
Bank Transaction: A reference to the original transaction received from your bank.
Destination Transaction ID: The unique ID assigned to the transaction by the destination service (e.g., the YNAB Transaction ID) once it is successfully created.
Status: The current state of the transfer attempt.
Message: A human-readable description of what happened, often including specific error messages from external APIs.
Timestamps: When the transfer was first attempted and when it was last updated.

Log statuses & their meaning

Transfer logs move through several statuses during their lifecycle:

Status	Meaning
Scheduled	Synci has identified the transaction and is preparing to send it to the destination.
Transferred	The transaction was successfully created in your destination.
Updated	An existing transaction was modified (e.g., when a "Pending" transaction becomes "Booked" at your bank).
Failed	An error occurred (e.g., the destination API was down or the account was disconnected).
Skipped	The transaction was intentionally not sent, usually because a Rule with a "Stop Transfer" action was triggered.
Retrying	Synci encountered a temporary issue and will attempt the transfer again automatically.

Undoing a transfer

If a transaction was sent to the wrong place or you simply want to remove it, Synci provides a powerful Undo feature directly from the Transfer Logs.

How it works

When you trigger an Undo:

Deletion: Synci connects to the destination API (YNAB/Lunch Money) and deletes the transaction using the stored Destination Transaction ID.
Audit Trail: A new log entry is created to record the undo action, and the original log is marked as undone.
Re-syncing: Once undone, the transaction becomes eligible to be transferred again (unless rules or filters prevent it).

Constraints

Only logs with a TRANSFERRED status can be undone.
A transfer cannot be undone if it has already been undone previously.
The log must contain a valid Destination Transaction ID to know what to delete.

Troubleshooting with transfer logs

Transfer logs are your first stop when "missing" transactions occur:

Check for SKIPPED: If a transaction isn't showing up in YNAB, check if a rule accidentally marked it as SKIPPED.
API Errors: If a log is FAILED, the message field will contain the exact error from the destination. This is often related to expired API tokens or changed account names.
Bulk Actions: If a large batch of transactions was sent incorrectly, you can use Bulk Undo to remove them all at once rather than one by one.

Pro tip: Using filters

You can filter logs by Transfer links to see the history of a specific connection, or by Bank Transaction ID to see every destination a single transaction was sent to.