GCC VAT Return & Filing Pack

The problem

A Gulf group running Dynamics 365 Finance & Operations usually has the tax data but not the filing artefact. Sales tax codes, tax groups and item tax groups are configured, journals post correctly, and the standard sales tax payment and tax transaction inquiries reconcile — but the tax authority does not accept an F&O inquiry screen. It expects a return laid out box by box in its own order, with its own definitions of standard-rated supplies, zero-rated exports, exempt supplies, imports subject to reverse charge, and recoverable versus blocked input tax. When there are several legal entities across the UAE, Saudi Arabia, Oman, Bahrain, Qatar and Kuwait, each with a different registration number, filing frequency and box structure, the gap between "the ledger is right" and "the return is filed" is filled by spreadsheets that nobody can audit twelve months later.

Reverse charge makes it worse. Imported services, intra-GCC goods movements and domestic reverse-charge categories all need a self-assessed output entry and a matching input claim on the same transaction, mapped to different boxes of the same return. When that is handled by manual journal entries after the fact, the general ledger and the return drift apart, and the drift is only discovered during an audit — when the authority asks for a transaction-level file that ties every line of the return back to a posted voucher.

What ECOSIRE builds

We build an X++ extension package for Dynamics 365 Finance and Supply Chain Management. No overlayering: everything is delivered as extension models with event handlers, chain-of-command classes, table and form extensions, and new elements in our own model. Your base tax engine keeps working exactly as Microsoft ships it — we sit on top of the posted tax transactions rather than replacing them.

Jurisdiction report layouts

We build a configurable return-definition framework: a report layout per jurisdiction, made up of boxes, and a rule set that maps each box to a selection of tax codes, tax groups, item tax groups, tax directions and transaction origins. Because the mapping is data rather than code, you can add a tax code next year and assign it to a box without another development cycle. Each legal entity is bound to a layout, its own tax registration number, its filing frequency and its settlement period, so a group return run produces one correctly shaped output per entity.

Reverse charge and self-assessment

We extend the tax determination and settlement flow so reverse-charge categories generate the paired output and input amounts on the same source document — vendor invoices, purchase orders, and free-text and project invoices where relevant. The pairing is stored against the source transaction so the return, the general ledger and the audit file all draw on the same numbers. Blocked or partially recoverable input tax is handled through a recovery-rate rule set rather than a manual reduction, and the non-recoverable portion posts to the account and ledger dimensions you nominate.

Audit file and transaction detail

We build the transaction-level audit extract the authorities ask for, generated through the data management framework as a custom data entity so it can be exported on demand or on a recurring batch schedule. Every line carries the voucher, date, document number, counterparty registration number, tax code, base amount, tax amount, box assignment and the dimension values you choose, so any figure in the return can be drilled back to its posting. The same entity is exposed over OData for a BI tool or an external filing agent.

Return workflow and period control

The return run is a batch job with a period lock: once a period is submitted, the extension records the submitted figures as a frozen snapshot. Late postings into a closed period are detected and collected into an adjustment list for the next return rather than silently changing a filed number. Approval before submission runs through the standard F&O workflow framework, so review and sign-off use the roles, hierarchies and delegation you already maintain.

Validation before filing

We build a pre-submission validation set: missing or malformed counterparty registration numbers, transactions with no box assignment, tax codes not mapped in the active layout, reverse-charge documents missing their paired entry, and period totals that do not reconcile to the sales tax payment. Validation runs as its own batch job so you can clear exceptions during the month instead of on the filing deadline.

Who it is for

Groups running F&O across two or more GCC jurisdictions; single-country entities whose return preparation currently lives in a spreadsheet; shared service centres filing on behalf of several legal entities; and businesses with significant imported services or intra-GCC movements where reverse charge is a recurring reconciliation problem.

How delivery works

Everything here is built to order — nothing is pre-packaged or downloadable.

1. Scoping call. We go through your legal entities, jurisdictions, current tax configuration, filing frequencies, reverse-charge categories, recovery rules and the exact return layouts you must produce. We review your existing tax code and tax group setup so the mapping rules are grounded in your real configuration. 2. Fixed quote. You receive a written scope, a fixed price and a delivery date. Nothing starts until you approve it. 3. Build. We develop the extension against a matching F&O version in our own environment, with unit tests on the mapping engine and reverse-charge pairing logic. 4. Install in test. We deliver the deployable package into your sandbox through your LCS pipeline, configure the layouts and mappings with your tax team, and run parallel returns against periods you have already filed so you can compare box by box. 5. Production. Once your team signs off on the parallel run, the same package moves through your release pipeline to production. We are on the call for the first live filing cycle. 6. Support. A defined support window covers defects and configuration questions after go-live, with rule and layout changes handled as configuration wherever the framework allows.

Filing itself stays under your control. This extension produces the return figures, the return output and the audit file from your F&O data; where a jurisdiction offers an electronic submission channel we integrate to it if the scope you approve includes it, and otherwise you submit the generated output through the authority's portal.