Current VAT Return Status (MTD), Sage

Card class: Hero • Category: Ecommerce Platform

The live status of your HMRC Making Tax Digital VAT return cycle. Overdue means surcharge risk plus repeat-offender escalation, so this is the card a UK finance team keeps in view all quarter.

​

At a glance

The status of where your current VAT return sits in the Making Tax Digital cycle, shown as a status with a days-to-deadline number. It moves through a predictable lifecycle: open period, period closed, return prepared, return submitted to HMRC, HMRC accepted. The card’s job is to tell you, at a glance, whether you are on track or drifting toward a surcharge. Where Period Close / VAT Return Past Deadline is the alert table that fires once you have slipped, this card is the forward-looking executive read that keeps you from slipping in the first place. Overdue is not just late; for a repeat offender it escalates the surcharge rate, so the status here carries real money.

​

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 multi-channel business on Sage Intacct, VAT registered on the standard quarterly stagger, selling DTC through Shopify Plus and B2B through BigCommerce B2B. The VAT quarter ended 31 May 26, so the HMRC MTD deadline is 7 Jul 26. Snapshot 23 Jun 26. Reporting currency GBP. Warning window set to 5 days. Five things to notice:

1. Fourteen days to deadline with one blocker is a healthy green state, and reading the card this way is the entire discipline. The May period closed on time, so the structural prerequisite is met; the only thing standing between this business and a clean, early submission is twelve revenue lines still missing a VAT code. The card shows green-but-watch because there is plenty of runway and a single, identified blocker. The mistake a less disciplined team makes is treating “14 days away” as “not urgent yet” and discovering the twelve uncoded lines on 6 Jul 26 with hours to spare. The card exists to make the blocker visible while the runway is long.
2. The status is gated by the missing-code count, which is why the two cards are read together. This return cannot move to Prepared (final figures locked) while Revenue Lines Missing VAT Code (MTD) is non-zero, because a return built over uncoded lines is incomplete. The twelve remaining lines are the literal to-do list for advancing this card’s status. Clear them, and the status advances to Prepared; finalise, and it advances to Submitted; HMRC accepts, and it goes fully green and clears for the quarter.
3. The deadline is 7 Jul 26 because HMRC sets it, and the card reads it from the obligation feed, not from an assumption. One calendar month and seven days after the 31 May 26 period end gives 7 Jul 26 for this standard-stagger entity. Because the card pulls the deadline directly from the live MTD obligation feed, a change in stagger group or filing frequency is picked up automatically; a manual tracker keyed to an assumed stagger would silently desync. This is the difference between a date someone typed into a spreadsheet and the date HMRC is actually holding you to.
4. The five-day warning window is when the card turns from green to amber, and it is configurable for a reason. A team that reliably files a week early can leave the warning at five days; a team that has been burned before, or one with a complex multi-entity filing, widens it to ten so the amber warning lands with more runway. The window is a tuning knob on how early you want the card to start pressing. Whatever the setting, the red overdue state is unambiguous: the deadline has passed and surcharge risk is now live.
5. For a repeat offender the cost of going red is not flat, it escalates, which is why owner is a role on this card. HMRC’s default surcharge regime increases the penalty rate on successive defaults within a surcharge period, so an entity that has slipped before pays more for slipping again. The single executive number here is the early-warning system that keeps a business off that ladder entirely. Pair with Period Close / VAT Return Past Deadline for the moment-of-breach alert and Sage Health Score for how VAT status feeds the composite ledger-health read the board sees.

​

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) shows the current return, its period, its state, and the deadline against HMRC. Applications → Tax → MTD Obligations is the live HMRC obligation feed; the deadline and obligation status here are authoritative. Applications → Tax → VAT Detail Report shows the transactions that make up the return, the working data behind the status. Reports → General Ledger → Period Close Checklist confirms whether the period the return covers has closed. Interactive Custom Report (ICR) on the tax data source filtered to the current obligation, showing state and days to deadline.

For Multi-Entity Console accounts, view the VAT Returns list at the consolidation level with the entity column on, so each VAT-registered entity’s status is visible in one place rather than requiring a per-entity login. Common reconciliation pitfalls:

• Submitted vs accepted. A return marked Submitted in Sage has been sent; HMRC then returns an acceptance receipt. A submission that errored at HMRC may show Submitted locally but is not accepted. The card distinguishes these where the feed exposes acceptance; confirm which state your workspace treats as fully filed.
• Deadline source. The authoritative deadline is the HMRC MTD obligation, not a date typed into Sage. The card reads the obligation feed; a manual tracker can show a different date if it assumed the wrong stagger.
• Period vs return. The accounting period closing and the VAT return submitting are two different events. A closed period with an unsubmitted return is a normal mid-cycle state; do not read “period closed” as “return filed”.

Why our number may legitimately differ from a Sage Intacct VAT view: Cross-connector reconciliation: The cross-connector point is that a VAT return is only as correct as the revenue underneath it, and that revenue comes from systems Sage does not control. If commerce orders have not posted, or revenue lines are uncoded, then a return finalised on schedule is finalised wrong, and a wrong return filed on time is its own compliance problem. The status on this card is therefore not just “have we filed” but “is the underlying data ready to file”, which is why it is read alongside the revenue-gap and missing-code cards. Sage Intacct is the only place that holds the HMRC obligation, the period state, and the revenue base together, so it is the only place this status can be true. The card turns the quarterly VAT cycle from a recurring scramble into a watched, predictable lifecycle.

​

Known limitations / merchant FAQs

What exactly does each status mean? The lifecycle runs Open (period still trading), Period Closed (the accounting period the return covers has closed), Prepared (figures finalised and missing codes cleared), Submitted (sent to HMRC), and Accepted (HMRC confirmed receipt). Overdue is the red state: the deadline has passed without an accepted submission. The card shows the current status plus the days until or past the HMRC deadline so you always know both where you are and how long you have. Where does the deadline come from? The live HMRC Making Tax Digital obligation feed, not a date typed into Sage or a spreadsheet. For most UK quarterly stagger groups it is one calendar month and seven days after the VAT period end. Reading it from the obligation feed means a change in stagger group or filing frequency is reflected automatically, which a manual tracker would miss. What is the difference between this card and the past-deadline alert card? This card is forward-looking: it shows where the return is in its cycle and how many days remain, so you act before the deadline. Period Close / VAT Return Past Deadline is the breach alert: it lists entities and periods that have already slipped. Together they cover the full timeline, before and after the line. A well-run finance team lives mostly in this card and rarely sees a row in the other one. Why can’t the status go green while missing VAT codes exist? Because a return built over revenue lines with no VAT code is incomplete; the box-by-box figures would be wrong. The card gates the Prepared and later statuses on the missing-code count being cleared, so Revenue Lines Missing VAT Code (MTD) reaching zero is a literal precondition for finalising. This is intentional: it stops a team from filing a return that looks done but is missing tax records HMRC requires. What is the surcharge risk if I go overdue? HMRC’s default surcharge regime applies a penalty to late VAT, escalating for repeat offenders through successive defaults within a surcharge period (rising percentages of the unpaid VAT), with lighter first-stage treatment for smaller businesses. The exact mechanics shift with HMRC policy and the newer points-based penalty system; always confirm current rules with your tax adviser. The key point for reading the card is that the cost of going red is higher the more often you have gone red before, so staying off the ladder entirely is the goal. Does the card file the return for me? No. Vortex IQ is the detection and status layer; the actual MTD submission happens in Sage Intacct or your bridging software. The card makes the cycle visible and warns you in time; a human still reviews the figures and submits. Submitted vs accepted, which is fully filed? A return shown as Submitted has been sent to HMRC; HMRC then returns an acceptance receipt. A submission that errored at HMRC can show Submitted locally while not actually being accepted. Where the obligation feed exposes the acceptance, the card treats accepted as the fully-filed state, because that is what protects you from a surcharge. Confirm in your workspace which state maps to filed; the safer setting requires confirmed acceptance. How does this work for a multi-entity group? Each VAT-registered entity has its own MTD obligation and therefore its own status on this card. Watch each entity separately, because they file independently and a quiet subsidiary can drift while the main trading entity is on track. The consolidation-level VAT list with the entity column on is the equivalent native view. We changed our VAT stagger group, will the card keep up? Yes. Because the card reads the deadline and obligation state from the live HMRC MTD feed, a stagger or frequency change is reflected automatically on the next refresh. A manual tracker keyed to the old stagger would show the wrong deadline; the card will not. Can I make the card warn me earlier? Yes. The default amber warning window is five days to deadline; you can widen it (for example to ten days) per workspace if you prefer a longer runway, which is common for complex multi-entity filings. Widening the window changes when the card turns amber, not the underlying deadline or status. How fresh is the status? It reads the obligation feed and the Sage VAT return record live, so the status changes as the underlying events happen: the moment HMRC accepts, the card goes green. The days-to-deadline number ticks down each day. This immediacy is the point of a real-time time window: the card is meant to be glanced at any day of the quarter and be correct.

---

​

Tracked live in Vortex IQ Nerve Centre

Current VAT Return Status (MTD) 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.