Automatic Quarterly Summary Updates After AgentOS Sync
Automatic Quarterly Summary Updates After AgentOS Sync
Introduced in v1.0.27
Every time the AgentOS incremental sync runs and pulls in new transactions, the platform automatically identifies which quarterly summaries are affected and recomputes them — keeping your draft summaries accurate without any manual intervention.
Overview
When new transactions arrive from AgentOS, they can fall into any number of quarterly tax periods. Previously, a summary would only reflect new transactions if you manually triggered a recompute. As of v1.0.27, this happens automatically as part of the sync completion event.
Trigger
The workflow is event-driven and activates on:
agentos/incremental-sync.completed
This event is emitted by the AgentOS incremental sync process each time it finishes importing transactions. No polling or scheduled jobs are involved.
What Happens Step by Step
-
Sync completes — AgentOS incremental sync emits
agentos/incremental-sync.completed. -
Affected orgs identified — The workflow collects all organisations for which at least one new transaction was imported in this sync cycle.
-
Quarterly periods resolved — For each new transaction, the system calls:
deriveTaxYear(transactionDate)— determines the UK tax year the transaction falls into.getQuarterForDate(transactionDate)— determines which of the four quarterly periods (Q1–Q4) the transaction belongs to.
-
Draft summaries recomputed — For each unique (org, period) combination identified above, if a
quarterlySummaryrecord exists with a status ofdraft, its aggregates are recalculated andlastComputedAtis set to the current timestamp. -
Notification emitted — A notification is created for the organisation:
"X new transactions imported — your Q{n} summary has been updated."
Status Guard
The recomputation logic only applies to summaries in draft status. This protects any summary that is already in motion toward or has completed an HMRC submission:
| Summary Status | Will Recompute? |
|---|---|
draft | ✅ Yes |
pending | ❌ No |
submitting | ❌ No |
submitted | ❌ No |
This ensures that once you have initiated or completed a quarterly submission to HMRC, the system will never silently alter the figures associated with it.
Notifications
After each successful recomputation, a notification is created and surfaced in-app. The message follows the format:
X new transactions imported — your Q{n} summary has been updated.
Where:
- X is the count of newly imported transactions for the organisation.
- Q{n} is the affected quarter (e.g. Q1, Q2, Q3, or Q4).
If multiple quarters are affected by a single sync, a notification is emitted for each updated summary.
Entities Involved
| Entity | Description |
|---|---|
agentosTransactions | Raw transaction records received from AgentOS |
transactions | Normalised internal transaction records |
quarterlySummaries | Quarterly income/expense aggregates used for HMRC MTD submissions |
notifications | In-app notifications delivered to the organisation |
Frequently Asked Questions
Will this affect a summary I have already submitted to HMRC?
No. Summaries with a status of submitted, submitting, or pending are never modified by this workflow.
What if no quarterly summary record exists yet for an affected period?
The workflow only recomputes existing quarterlySummary records. If no record has been created for a period yet, nothing is changed — the summary will be computed fresh when you open that period.
Can I turn this off?
This workflow runs automatically as part of the core sync pipeline. If you have concerns about specific summaries being recomputed, ensure they are moved out of draft status before the next sync.
How quickly does this happen after a sync?
Recomputation is event-driven and triggered immediately upon agentos/incremental-sync.completed, so summaries are typically updated within seconds of a sync completing.