Summary Sync: Aggregating Data by Day, Payout, Month, or Custom Periods

This guide explains the available summary aggregation modes in Synder and how they affect accounting records.

Use this guide to understand:

  • How each summary mode works
  • When to use daily, monthly, per-payout, or manual summaries
  • What happens when you switch modes

When you sign up for Synder Summary sync mode, Synder prompts you to choose the summary aggregation mode. All modes combine sales, fees, refunds, taxes, and discounts into a single summarized record. They differ in timing, structure, and reconciliation logic. 

Daily Aggregation

Daily aggregation creates one summary per calendar day. This mode is suitable for businesses that want to get a quick, summarized view of all financial data for a day. 

How it works

  • Synder summarizes all transactions for a calendar day.
  • Synder creates one summary per day.
  • The current day’s summary remains in Fetching/Pending status until the next day to capture all transactions.

Use daily summaries if you need accounting data available daily or if you reconcile within the first few days of the next month. 

Note: Daily summaries are available for all accounting platforms.

Per Payout Aggregation

Per-payout aggregation creates one summary per finalized payout. Use the per-payout aggregation mode if you want summaries to match payout deposits exactly, or if you reconcile based on payout (settlement) reports.

How it works

  • One summary is created per finalized payout.
  • The summary becomes ready to sync after the corresponding payout completes.
  • Aggregation may take days or weeks, depending on payout timing.


Note: Per-payout mode is currently available for Amazon, eBay, Shopify, and Stripe integrations, and it drastically improves the reconciliation process of these integrations.

Only QuickBooks Online, Sage Intacct, and Oracle NetSuite support this aggregation mode.

Monthly aggregation

Monthly aggregation creates one summary per calendar month. Consider using monthly summaries if you prefer fewer records in your books. This aggregation mode is particularly helpful if you reconcile on a monthly basis and don’t need the data synchronized to the books daily.

How it works

  • One summary is created per calendar month.
  • The summary remains in Fetching/Pending status during the month.
  • It finalizes automatically on the first day of the following month.

Note: Monthly summaries are available for all accounting platforms.

Manual (Custom Period) Summaries

Manual summaries allow custom date ranges. Consider using manual (custom period) summaries if you have non-standard accounting periods or if you reconcile specific date ranges for audits. 

How it works

  • You can generate summaries manually for periods up to 31 days.
  • You can also stop automatic summary period creation and control how Synder aggregates your data. Choose “None” in the integration summary aggregation mode to stop the automatic summary creation.
  • Manually generated summaries remain in Ready to sync status until synced manually.


Note: Manual summaries are available for all accounting platforms.

Generate a Manual Summary

  • Go to the Summaries list from the left-side menu.
  • Click Generate Summary.
  • Select the integration you want to generate the summary for.
  • Choose the date range.
  • Click Generate.
  • Review the summary data.
  • Click Save to summaries.

Changing Summary Modes

Changing aggregation modes requires manual review to prevent duplicate or missing data.

When you change the mode (for example, Daily to Monthly), the existing summaries in any status are finalized in their original mode. The next period is generated in a new mode. 

You must manually adjust overlapping periods.

Example: Missing Data

If you switch from Daily → Monthly on May 20:

  • Daily summaries exist until May 20
  • The next automatic monthly summary will cover June
  • The summaries for May 21–31 period will NOT be created automatically

Generate the summary for May 21-31 manually to avoid missing data. 

Example: Duplicate Data

If you switch from Monthly → Daily on May 20:

  • The entire monthly summary for May still gets finalized for the full May period.
  • Starting May 21, daily summaries will be generated for the rest of the month.
  • Data for May 21–31 will appear in both the monthly and daily summaries

To fix this:

  1. Delete the May monthly summary
  2. Manually generate summaries for May 1–20
  3. Keep daily summaries for May 21 onward

Note: The Per-payout mode is a complex process of gathering transactions based on the payout they relate to. Per-payout summaries cannot be generated manually. Contact support for assistance when switching to or from per-payout mode.

Verify That Transactions Are Not Missing or Duplicated

If you’d like to double-check that each transaction is linked to only one summary, you can download the Register report. It shows how individual transactions are connected to specific summaries. 

Steps

  1. Go to Summaries → Register.
  2. Download the report for the required period.
  1. Review the Summary ID column.

Interpretation

Each transaction should be linked to a single summary. If a transaction has no summary ID associated with it, this indicates that it is missing from the summaries. If transactions appear under multiple summary IDs, the data contains duplicates.

  1. Two Summary IDs → This indicates a duplicate.
  2. One Summary ID → This is correct; each transaction should be linked to a single summary.
  3. No Summary ID → The transaction isn’t associated with any summary and isn’t recorded in the books.

Delete or generate summaries as needed to correct discrepancies.

Reconciliation by Aggregation Mode

Each aggregation mode follows a different reconciliation logic

Daily Aggregation: Matching Totals

The summary total in the Summaries list, or within a specific summary, shows how much you received during the day.

To reconcile:

  • Use the platform’s daily financial summary report (for example, Shopify Finances Summary or Stripe Balance Summary).
  • Compare:
    • Total sales (Shopify), or
    • Account activity before fees (Stripe)

The totals will match the Synder summary total.

Per-Payout Aggregation: Matching Totals

Per-payout summaries match payout reports.

  • The summary total matches the platform’s payout or settlement report total.
  • Synced journal entries or invoice lines match payout (settlement) report details.

Important Notes

  • If a payout spans multiple months, Synder creates multiple journal entries or invoices to recognize revenue in the correct periods.
    Example:
    If a Shopify payout covers September 28 to October 2, Synder creates:
  • One entry for September 28–30
  • One entry for October 1–2
  • If you enable multicurrency and account for transactions in different currencies, Synder may also create multiple journal entries or invoices.

FAQ

  • Can I manually create or force a Per-Payout summary?
    No. You cannot generate per-payout summaries manually. Contact support for assistance when switching modes.
  • Are Shopify daily reports useful in Per-Payout mode?
    No. Do not compare per-payout summaries to daily sales reports. Use payout or settlement reports.
  • Do summary totals always match bank deposits?
    Only in Per-Payout mode.

Daily, Monthly, and Custom summary totals do not represent bank movements. Use platform financial summaries for comparison.

Reach out to Synder Team via online support chat or email with any questions you have – we are always happy to help you!

Author

Leave a Reply

Your email address will not be published. Required fields are marked *