Change Your VAT Tax Period on EmaraTax

The VAT tax period — monthly or quarterly — is assigned by the FTA with the registration; it is an attribute of the registration, not a preference in the settings. Changing it therefore goes through the administrative exception request route on EmaraTax: a reasoned request the FTA reviews and decides, not a toggle the business flips.

The request needs a business reason the FTA can assess — cash-flow and reporting alignment, consistency across a group, a business scale that has outgrown the assigned cycle. Preference alone is weak; a reason tied to how the business operates is a reason. State it fully, evidence it where possible.

And the standing rule while the request pends: nothing changes. The existing tax period, its returns, and the 28-day filing deadlines continue exactly as before until the FTA approves. The request pauses nothing — calendar every current deadline and meet it.

The request below is the standard flow as of September 2026.

While the request is pending, the compliance machine runs unchanged: returns for every period under the current structure, filed and paid by the 28th, with the box-by-box discipline the return guide covers. The request is not a reason to let a deadline slip — and a slipped deadline during the request weakens the business's standing in it.

Calendar defensively: every current-period deadline diarised, every return prepared on the existing cycle, as if the request did not exist. The approval, when it comes, changes the future; it never excuses the present.

If the request takes long, resist the urge to act as if it were granted. Filing on the proposed period before approval creates a mismatch between the returns and the registered period — a new problem stacked on the old request. Patience is the compliance position.

Approval sets the new period from its effective date — and the decision's cutover detail governs the periods around the change. Read the approval carefully: which period is the first under the new structure, how the straddling period is treated, what the new deadline dates are.

Re-calendar everything from the effective date: the return cycle, the 28-day deadlines, the internal preparation timetable, the payment runs. The new period's discipline starts immediately — the first return under the new structure is due on its new deadline, with no grace for the transition.

File the decision with the VAT records alongside the request and the exchanges. The file proves the change was properly sought and properly implemented — the complete story from assigned period to new period, documented.

If the exception is rejected, assess on advice whether the reason has strengthened or the facts changed — repeated identical requests rarely succeed. Sometimes the honest conclusion is that the assigned period stands, and the better move is adapting the internal reporting rhythm to it rather than re-applying.

The rejection does not change the current period — it confirms it. Continue on the assigned cycle, keep the deadlines, and revisit the question only if the business reason materially changes. A rejection is information: the FTA's view of the current facts, which the business can either change or accept.

The remaining failures, matched to their fixes.

The FTA grants tax-period exceptions rarely, and only for genuine reasons. Understanding what counts — and what does not — saves the wasted application.

Genuine grounds: the assigned period creates a structural compliance hardship — the classic case is alignment with the financial year or the management reporting cycle, where the VAT period-end falls in the middle of the business's natural accounting close and forces a duplicate cut-off exercise every period. Seasonal businesses whose peak straddles the period boundary, and groups seeking alignment across members, can also make the case.

The evidence the case needs: the financial year-end, the reporting cycle, the demonstration of the hardship — "our year-end is 31 December; the assigned February-April cycle forces X additional cut-off procedures per year, as shown". Quantify the burden; the exception is granted on demonstrated need, not preference.

What does not count: preferring a different month, wanting the deadline on a more convenient date, the new finance manager's habit from a previous company. "We would rather file in March" is not a ground — and the application that argues preference reads as not understanding the regime.

The alternative to consider first: in many cases the real problem is not the period but the close process — a faster, cleaner month-end close removes the hardship without the exception. Fix the close before requesting the exception; the FTA is more receptive to the business that has its house in order.

Frame the request as the exception it is: the rule (the assigned period), the genuine hardship (evidenced), the proposed alternative (and why it resolves the hardship), the commitment (the compliance record that shows the business handles its obligations). Exceptions are granted to credible applicants with real reasons — be both.

The exception request is a formal application with a formal file. Build it completely — the FTA does not grant exceptions on thin papers.

The current position stated: the TRN, the currently assigned tax periods, the basis of the assignment (turnover band). The reviewer should see the starting point without looking it up.

The proposed periods: the specific alternative requested — not "a different period" but "calendar quarters ending March, June, September, December" (or the monthly equivalent). Precision matters; the vague request cannot be granted because there is nothing specific to approve.

The grounds argued: the hardship, evidenced — the financial year-end documentation, the reporting cycle description, the quantified burden of the current alignment. One ground argued well beats three gestured at.

The compliance record: the filing and payment history — on time, complete. The exception is a privilege for the compliant; the business with late filings requesting special treatment faces an uphill climb. If the record has blemishes, address them (and fix the pattern) before requesting the favor.

The transition plan: how the business will handle the stub period if the change is approved — the cutover date, the first return under the new cycle, the system updates. Showing the transition is planned signals the seriousness the exception requires.

Submit through the proper channel, keep the submission confirmation, and then — critically — continue on the current cycle until approval. The request does not suspend the assigned periods. The file that is complete, precise, evidenced, and backed by a clean record is the file that has a chance; everything else is correspondence.

Most exception requests are rejected — and most businesses then discover the assigned period was workable all along. The optimization guide for living with it.

Align the close process: the real friction is usually the period-end cut-off, not the period itself. A disciplined 3-day month-end close — sales cut-off confirmed, purchase invoices accrued, the VAT control reconciled — makes any period-end manageable. Invest in the close, not the exception request.

Build the period into the calendar: every period-end and every 28th-day deadline, calendared a year out, with owners and reminders. The business that treats the VAT cycle as fixed infrastructure stops fighting it.

Use the period's rhythm commercially: the quarterly filer gets a natural quarterly VAT review point — the return preparation becomes the quarterly health check (classification sample, threshold position, contact details). The period is not just a deadline; it is a cadence for control.

For groups: where members hold different assigned periods, the consolidation calendar maps them all — each member's period-ends, each deadline, one view. The complexity is managed, not wished away.

And revisit the exception question annually, honestly: has the hardship persisted, is the evidence stronger, is the compliance record now spotless? The rejected request can be re-made with a better file — but the business that optimized its close in the meantime may find it no longer needs to. The assigned period is the rule; exceptions are the rare, evidenced, well-argued departure. Most businesses thrive under the rule once they stop treating it as the problem.

If the exception is approved, the change creates a stub period — the awkward interval between the old cycle's end and the new cycle's start. Plan it before it arrives.

Map the cutover precisely: the last period under the old cycle (its end date, its return deadline), the stub period (its start and end dates, its return deadline), and the first full period under the new cycle. Three periods, three deadlines, one timeline — drawn up the day the approval arrives, calendared immediately.

The stub period's return follows the normal rules pro-rated to its dates: the supplies in the stub interval, the input VAT attributable to it, the 28-day payment deadline from the stub period-end. Short periods do not mean relaxed procedures — the cut-off discipline matters more, not less, when the interval is unusual.

Update every system on the cutover date: the accounting system's tax period configuration, the return preparation checklist, the compliance calendar, the finance team's briefing. The system that still thinks in the old cycle will prepare the wrong return; the briefing that does not happen leaves the preparer guessing.

Watch the cash flow: the stub period can bunch two payment deadlines closer together than usual (the old cycle's final payment and the stub's). Forecast the cash impact and ensure the funds are available — the transition's administrative neatness should not create a liquidity surprise.

File the transition working paper with the approval: the cutover map, the stub computation, the system updates confirmed. The exception was granted on the strength of the file; the transition is executed with the same discipline. The period change is complete when the first full period under the new cycle closes cleanly — not when the approval email arrives.

Tax period changes are exception work we handle — the reason built properly, the request filed completely, the deadlines kept throughout, the new cycle implemented cleanly. As an FTA-registered tax agency, TaxAdvisors can be appointed as your agent on EmaraTax through the portal's own authorization flow, and we manage the whole arc: the case for the change, the pending-period compliance, and the cutover.

That means no slipped deadlines during the wait, no early adoption, no cutover confusion — just the period the business needs, properly granted and properly run.

Tell us about the current period and the reason and we will quote the fee for your specific case in writing before any work begins; nothing is billed without your prior approval. Requesting yourself? The walkthrough above is the complete discipline — we are here when you would rather delegate it.