This guide explains how Synder imports your transactions from connected integrations and compiles them into summaries in Summary Sync, what statuses you will see on the Summaries List, and how the process differs between daily and per-payout aggregation.
Use this guide if you:
- just connected an integration and want to know what to expect during the first import
- see summaries on Fetching or Not Ready and want to understand why
- are deciding between daily and per-payout aggregation and want to see how data is collected for each
How the import process works
When an integration is connected, Synder continuously imports data through automated background processes. You can review every import in Summaries > Import Activity Log. For details on the different import request types, see Import Activity Log: Types of Import Requests for Connected Integrations.
The import process begins from the earliest import start date selected on the historical data import page — usually the start date of your first import after creating the organization. Once data is imported, Synder compiles it into summaries based on your summary period settings. The timing of synchronization then depends on the frequency you selected (daily auto-sync, fully fetched auto-sync, or manual sync). More on that in Summary Sync: Aggregating Data by Day, Payout, Month, or Custom Periods.
Example 1: Daily synchronization
If you have Stripe connected and the synchronization frequency is set to daily, all summaries during the first import will be labeled as Fetching and Not Ready (previously called Pending) on the Summaries List. This means Synder is still collecting transactions from the selected start date and compiling them into daily summaries. Once all transactions are processed, the summaries are finalized and move to Ready to Sync. Synchronization is then automatic or manual, depending on your settings.
Summaries that cover the current day (the day you are viewing the list) usually remain on Fetching and Not Ready until the next day. This is expected: Synder waits for the full day to close so it can capture every transaction that belongs to that period.
If a summary stays on Not Ready longer than expected, see Why is my summary on Not Ready status in Summary Sync? for the most common reasons (current period, unverified transactions on the processor side, draft invoices, or per-payout mode awaiting the payout) and what to do about each.
Example 2: Synchronization per payout
If your synchronization period is set to per payout, a summary will not appear until the payout is issued by the integration and fetched by Synder. Once the payout and its transactions are fetched, a summary is generated and added to the Summaries List. The summary will cover the appropriate date range — since payouts typically occur every few days, the summary reflects that period.
Note that in Per Payout mode, summaries can stay on Not Ready until the payout actually lands at the bank, even after it has been opened on the processor side. This is normal — the summary will move to Ready to Sync once the payout closes and the final amounts (sales, fees, refunds, adjustments) are confirmed.
In some cases, if a payout within the import date range includes transactions that occurred before the selected import start date, Synder will also import those earlier transactions. This ensures the summary fully reflects every transaction associated with the payout, giving you complete and precise entries.
Related guides
- Why is my summary on Not Ready status in Summary Sync?
- Summary Sync: Aggregating Data by Day, Payout, Month, or Custom Periods
- Import Activity Log: Types of Import Requests for Connected Integrations
- Summary Sync Transaction Reconciliation: How to Verify Your Data Before You Sync
- Summary Sync for Ecommerce: Things You Need to Know
