Period Close / VAT Return Past Deadline, Sage

Card class: Hero • Category: Ecommerce Platform

A real-time alert table listing every entity whose period close or MTD VAT submission has slipped past its deadline. Each row is an entity or period overdue and one HMRC surcharge waiting to happen.

​

At a glance

A live alert table, not a single number. Each row is an entity or accounting period whose close has not completed, or whose Making Tax Digital VAT return is past its HMRC submission deadline, by more than five days. This is the card a Finance Director keeps open during close week. An overdue VAT return is not an administrative nuisance, it is a surcharge liability and, for repeat offenders, an escalating penalty rate under HMRC’s default surcharge regime. The card watches every entity in a Multi-Entity Console at once, so a quiet subsidiary whose bookkeeper went on leave does not silently breach while head office watches the main trading entity.

​

Calculation

Calculated automatically from your Sage data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

​

Worked example

A UK group on Sage Intacct Multi-Entity Console with four entities: UK Trading Ltd (GBP, the main DTC and B2B trading company on a Shopify Plus and BigCommerce B2B stack), UK Wholesale Ltd (GBP, B2B only), IE Distribution Ltd (EUR, Irish subsidiary), and a dormant holding company (GBP). Group VAT is not used; each UK entity files its own MTD VAT return on the standard quarterly stagger. Snapshot 23 Jun 26, two days into the June period close. Reporting currency GBP. The card is left on all entities. Five things to notice:

1. UK Wholesale Ltd is the one that costs money, and it is the row a single headline number would have hidden. The Q ended 30 Apr 26 MTD VAT return is 16 days past the HMRC deadline (deadline was 7 Jun 26) with an GBP 84,200 net VAT liability unfiled and unpaid. Under HMRC’s default surcharge regime this puts the entity into a surcharge period; if the entity has already defaulted within the last twelve months the surcharge is a percentage of the unpaid VAT (escalating 2 percent, 5 percent, 10 percent, 15 percent on successive defaults). On GBP 84,200 even a 5 percent surcharge is GBP 4,210 of pure penalty, plus interest, plus the reputational cost of a repeat-offender flag with HMRC. The card’s job is to make sure this row never reaches day 16. In practice a finance team running this card open during close week catches it on day 6.
2. The two close-blocked rows (UK Trading Ltd and IE Distribution Ltd) are nine days into the May period and not yet closed, which is the upstream cause that eventually produces VAT slips. A period that will not close is usually waiting on something concrete: an unreconciled bank account, a batch of Pending transactions awaiting approval, an out-of-balance journal, or a revenue line missing a VAT code that the validation will not let through. Pair this card with Period Close Status, Open (Pending) Transactions, and Transactions Failing Validation (imbalance / missing VAT) to find what is actually holding the close. Closing on time is how you avoid filing late.
3. The Holding Co nil-return row matters more than its GBP 0 amount suggests. A dormant or nil-trading entity still has an MTD obligation if it is VAT registered. The classic miss is everyone assumes “nothing to file” means “nothing to do” and the return is simply forgotten. HMRC does not care that the return is nil; an unfiled nil return is still a default and still pushes the entity along the surcharge escalation ladder. The card surfaces it because the obligation exists, not because the amount is large. This single behaviour catches one of the most common avoidable penalties in multi-entity UK groups.
4. Days past deadline is the triage column, read it before the amount. A GBP 0 row at 16 days outranks a GBP 84,200 row at 1 day for HMRC-relationship risk, because the escalation ladder is driven by repeated lateness, not by size. The right operating rhythm is to clear the highest-days rows first regardless of amount, then sort by at-risk amount within the same day band. A finance team that triages purely by GBP value will keep paying small surcharges on small entities that quietly accumulate into a 15 percent escalation rate.
5. This card is the real-time partner to a backward-looking compliance metric, and the pairing is the point. Period Close VAT Return Past Deadline tells you what is on fire right now; Period Close On-Time Rate (12 months) tells you whether you have a structural problem. If this alert table is empty most months but the 12-month on-time rate is 70 percent, you have an occasional fire-drill culture. If this table has rows most weeks, you have a process gap, usually an approval-routing rule that is broken or an entity with no named close owner. The board cares about the trend; the controller cares about today’s rows.

​

Sibling cards merchants should reference together

​

Reconciling against Sage

Where to look in Sage Intacct: The native Sage Intacct views to run side by side with this card:

Applications → Tax → VAT Returns (MTD) lists each obligation, its period, deadline, and submission state (Open, Reviewed, Submitted) against HMRC. Reports → General Ledger → Period Close Checklist shows each entity’s close tasks and whether the period has reached a closed state. Company → Setup → Accounting Periods shows the configured close calendar dates the card compares against. Applications → Tax → MTD Obligations is the live HMRC obligation feed; the deadline shown here is the authoritative one the card aligns to. Interactive Custom Report (ICR) on the period and tax data sources filtered to periods past their close date or VAT obligations past deadline, grouped by entity.

For Multi-Entity Console accounts, run the VAT Returns view at the top consolidation level with the entity column enabled so every subsidiary’s obligation is visible in one list, otherwise a per-entity login is needed to see each subsidiary’s overdue state, which is exactly the blind spot this card removes. Common reconciliation pitfalls:

• HMRC obligation deadline vs internal close calendar. The MTD deadline is set by HMRC (typically one month and seven days after period end for the standard quarterly stagger); the internal close calendar is set by the finance team and is usually earlier. The card watches the HMRC deadline for the VAT trigger and the internal calendar for the close trigger. If your Sage close calendar differs from the HMRC deadline, the two triggers will fire on different days.
• Stagger group. UK businesses sit in one of three quarterly stagger groups, plus monthly and annual filers. The card reads the obligation deadline directly from the MTD feed rather than assuming a stagger, so a recently changed stagger group will not desync it. A manual reconciliation that assumes the wrong stagger will.
• Submitted vs accepted. A return marked Submitted in Sage has been sent to HMRC; HMRC then returns an acceptance receipt. A submission that errored at HMRC may show Submitted locally but is not accepted. The card treats a confirmed HMRC acceptance as the cleared state where the feed exposes it; confirm which state your workspace maps to “filed”.

Why our number may legitimately differ from a Sage Intacct VAT or period report: Cross-connector reconciliation: The cross-connector point is that an overdue VAT return is almost never a tax problem at root; it is an upstream data problem wearing a compliance costume. Commerce revenue that has not posted, a revenue line with no VAT code, an out-of-balance journal, a stale bank rec: any of these holds the period open, the open period delays the return, and the late return becomes the surcharge. Sage Intacct is the only system that sees the whole chain because it holds the GL, the tax obligation, and the period calendar in one place. The commerce platforms see orders; only the ledger sees whether those orders became a clean, filed, paid VAT return. This card plus its causal siblings is how a finance team moves from reacting to HMRC letters to never receiving one.

​

Known limitations / merchant FAQs

Is this card UK-only? The VAT-return trigger is UK MTD specific (it reads the HMRC Making Tax Digital obligation feed). The period-close trigger is universal and applies to any Sage Intacct entity in any jurisdiction. A US-only Intacct account will see close rows but no VAT rows; a UK group sees both. EU VAT regimes have their own deadlines and the card can be configured to watch those where the obligation data is available, but the out-of-the-box VAT logic targets UK MTD. What exactly is the HMRC deadline the card uses? For most UK quarterly stagger groups it is one calendar month and seven days after the end of the VAT period, which is also the payment deadline for non-direct-debit filers. The card reads the deadline directly from the MTD obligation feed rather than computing it, so changes to stagger group or filing frequency are picked up automatically. Direct-debit payers get a few extra days on the payment side but the same filing deadline. Why five days of grace and not zero? Filing on the deadline day is on time, so a card that lit up on the deadline would cry wolf every quarter. Five days separates “filed at the last minute” (fine) from “genuinely slipped” (needs a name against it). Conservative teams set it to one day; teams with reliable last-day filing habits sometimes leave it at five. It is configurable per workspace. Does a nil return really need filing? Yes, if the entity is VAT registered. HMRC requires the return regardless of whether there is any VAT to declare. An unfiled nil return is a default and still moves the entity along the surcharge escalation ladder. This is one of the most common avoidable penalties in multi-entity groups, which is why the card surfaces nil obligations even though their at-risk amount shows GBP 0. What is HMRC’s default surcharge regime in practice? After a first default within a twelve-month surcharge period, subsequent defaults attract a surcharge calculated as a percentage of the VAT unpaid by the deadline, escalating through 2 percent, 5 percent, 10 percent and 15 percent on successive defaults, with a minimum applied in some bands. Small businesses under a turnover threshold get a lighter first-stage treatment. The exact mechanics shift with HMRC policy and the newer points-based penalty system for some obligations; always confirm current rules with your tax adviser. The card’s job is to keep you out of the regime entirely. Does the card file the return for me? No. Vortex IQ is the detection and alerting layer; the actual MTD submission happens in Sage Intacct or your bridging software. The card makes sure the return never quietly slips past its deadline unnoticed; the human still reviews and submits. A period is showing overdue but we filed the VAT, why? The two triggers are independent. A filed VAT return clears the VAT row, but if the accounting period itself has not reached a closed state in Sage (for example because of unreconciled items or pending transactions) the period-close row stays lit. Filing the return and closing the period are two separate actions; the card tracks both. We reopened a closed period for an adjustment and the row came back, is that a bug? No. Reopening a period flips it back to open, so the close trigger re-fires until you re-close it. This is intended; an open period is an open period regardless of why it was reopened. Re-close promptly after the adjustment to clear the row. How does this work across a Multi-Entity Console? The card watches every entity in scope at once and shows one row per overdue entity-period. This is the core value: a quiet subsidiary whose bookkeeper is on leave will breach silently if head office only watches the main trading entity. Leave the card on all entities during close week. Each row carries its entity name and the responsible role so the alert routes to the right person. Submitted vs accepted by HMRC, which clears the row? Where the MTD feed exposes the HMRC acceptance receipt, the card treats acceptance as the cleared state, because a submission that errored at HMRC is not actually filed even though it shows Submitted locally. Confirm in your workspace field map which state maps to “filed”; the safer setting for surcharge-avoidance is to require confirmed acceptance. Does FX move the at-risk amount? The per-row at-risk VAT liability is shown in the entity’s base currency, which is the currency HMRC or the local authority is owed in, so FX does not change the liability itself. The summed group exposure across rows is presented in reporting currency at the configured FX cadence, so the group total can move slightly day to day on FX while no individual liability changes. What is the relationship between this card and the on-time rate card? This card is the real-time today view (what is overdue right now); Period Close On-Time Rate (12 months) is the structural trend (how often you slip). Read them together: an occasionally non-empty table with a high on-time rate is normal operational noise; a frequently non-empty table or a falling on-time rate is a process problem, usually a broken approval route or an unnamed close owner on one entity.

---

​

Tracked live in Vortex IQ Nerve Centre

Period Close / VAT Return Past Deadline is one of hundreds of KPI pulses Vortex IQ tracks across Sage and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. Start for free or book a demo to see this metric running on your own data.