- How linked transactions work in the Summary mode
- How webhooks work and why summary dates may differ from transaction dates
- How does Synder handle this?
- Why summaries can show a date mismatch
- Does this affect accounting or reconciliation?
- How to double-check what you’re seeing
When reviewing a summary in Synder, you may occasionally notice transactions dated later or earlier than the summary period itself. This can be confusing at first glance, but it’s completely expected behavior and doesn’t indicate any issue with your data, your summaries, or your reconciliation.
Below, we’ll walk you through why it happens and how the process works.
How linked transactions work in the Summary mode
Each summary in Synder displays all linked transactions associated with the activity that occurred during that summary period, not only the transactions whose own event dates fall strictly within that day. This happens because Synder receives data from your platforms (Stripe, Shopify, Amazon, etc.) as webhooks or event bundles.
A single webhook can include multiple related events tied to the same transaction (invoice, payment, fee), even if those events occurred on different dates. This is normal for many e-commerce/payment platforms and is part of their internal event structure.
How webhooks work and why summary dates may differ from transaction dates
Let’s walk through a real example:
January 1st — Your customer creates an invoice.
January 3rd — The customer pays the invoice.
These are two separate events on two different days.
However, many platforms don’t send these events to us separately. Instead, they keep updating an already existing webhook of the order that contains:
- the invoice data
- the payment data
- any updates to the customer or order
This means: Even though the invoice is dated January 1st and the payment is dated January 3rd, the platform only provides a single webhook for both events.
How does Synder handle this?
Synder receives a single webhook on January 3rd, which contains multiple events with different actual dates. To keep your books accurate, Synder assigns each event to the summary it should belong to.
That is why Synder:
- Extracts each individual event inside the webhook.
- Reads the true date inside the event (e.g., the invoice date of January 1st).
- Places each event in the correct summary period, even though the webhook itself is dated as January 3rd.
This approach makes sure that your books stay accurate.
Why summaries can show a date mismatch
This happens because:
- The summary date = the date Synder received the webhook.
- The linked transactions in the summary = the actual dates from the platform.
This is normal in any webhook-based system.
N.B. The reverse situation is also normal. A summary may arrive later, even when its linked transactions occurred earlier.
Does this affect accounting or reconciliation?
No, not at all. This behavior does not:
- Duplicate revenue
- Distort balances
- Affect your Summary totals
- Interfere with reconciliation in QuickBooks or Xero
Each linked transaction is included only when needed to ensure accurate reporting and consistency with how your platform provides data.
How to double-check what you’re seeing
If you’re interested in what summaries a particular transaction relates to, we can trace all these events in Synder:
- Go to the Transactions list and locate the transaction you want to review.
- Click the “Explain” button next to that transaction.
- This opens the Sync Log, where each financial event tied to this transaction (e.g., invoice, payment) is listed separately.
- Each event has its own unique internal ID.
- Copy the ID of the event you want to investigate.
- Open the Register page and paste the ID into the search field. In the Register, you will see:
- All the individual lines Synder created for that event,
- The posting dates associated with each line,
- Which Summary (or Summaries) does the transaction belong to
This makes it easy to confirm that everything is syncing as expected.
If you need any assistance with your Summaries or reconciliation, reach out to our Synder Support Team – we’re happy to help.
