Skip to content
TrustList
Blog

Nine e-invoicing and tax-system deadlines in four days of news, and none of them in the EU or the US

Editorial

By TrustList Editorial

Our own count: nine e-invoicing and tax-system changes published 2 to 5 October from seven countries, none in the EU or US. Median warning 31 days; seven rest on one official page. How a buyer maps their own exposure.

About Nine e-invoicing and tax-system deadlines in four days of news, and none of them in the EU or the US

Nine e-invoicing and tax-system deadlines in four days of news, and none of them in the EU or the US

Between 2 and 5 October 2026 our news desk published nine items about changes to e-invoicing, e-reporting and other digital tax systems. They came from seven countries: Saudi Arabia, the United Arab Emirates, Pakistan, the Philippines, Ukraine, Brazil and Chile. Not one came from the European Union, the United Kingdom or the United States, the markets most software buyers think of first when they hear "e-invoicing mandate".

We went back over the nine items and counted what they have in common. Six of the nine carry a date that falls before 3 January 2027. Seven of the nine rest on the tax authority's or the vendor's own page and nothing else, because no independent report existed when we wrote them. Four had to be read in a language other than English: Ukrainian, Portuguese twice, and Spanish. All nine carry the red "not yet independently verified" note we add when the only evidence is the publisher's own. And the time between an announcement and the first thing a business had to do ranged from two days to just over six months, with a median of 31 days.

That last figure is the one that matters for anyone buying finance software. A month is roughly how long it takes to get a procurement request approved, never mind to select, contract and test an e-invoicing provider. If the median warning a tax authority gives is a month, the only buyers who are ready on time are the ones who chose software that was already prepared.

The nine items, as our records hold them

In order of the country, with the dates as each authority states them:

  • Saudi Arabia, ZATCA Wave 25 (published 2 October). The Zakat, Tax and Customs Authority set the criteria for the twenty-fifth wave of its e-invoicing Integration Phase: every taxpayer whose VAT-able revenue exceeded SAR 187,500 in any year from 2022 to 2025. Those taxpayers must connect their invoicing systems to the Fatoora platform by 1 February 2027. SAR 187,500 is the voluntary VAT registration threshold, so this wave reaches some of the smallest VAT-registered businesses in the kingdom. ZATCA's announcement is dated 24 July; we published it in October because the deadline was four months away and nobody else had.
  • United Arab Emirates, Federal Tax Authority (published 5 October). Businesses with revenue of AED 50 million or more must appoint an accredited e-invoicing service provider by 30 October 2026 and go live by 1 January 2027. Smaller businesses must appoint one by 31 March 2027 and go live by 1 July 2027. The authority's release is dated 29 September.
  • Pakistan, Federal Board of Revenue (published 2 October). Two orders dated 29 September extend e-invoicing from sales tax to federal excise duty and to the Islamabad services tax, and set rules for sealing the premises of businesses that fail to integrate their systems. Neither order states a start date, and some sector dates are to come by later notification. We read them from scanned PDFs whose text contained recognition errors.
  • Philippines, Bureau of Internal Revenue (published 5 October). Revenue Memorandum Circular 98-2026, dated 22 September, requires covered taxpayers other than micro taxpayers to be issuing structured electronic invoices by 31 December 2026. A business needs a permit first and a system certification within six months of it. The BIR has said that it has not yet accredited any e-invoicing service provider. We read the circular in a copy hosted by an accounting firm, not on the BIR's own site.
  • Ukraine, eExcise (published 2 October). The Ministry of Digital Transformation announced on 30 September that, from 5 October, all testing against the electronic excise system must move to a Sandbox, and that production registration opens on 12 October.
  • Brazil, Simples Nacional (published 5 October). Small businesses choosing the Simples regime for 2027, the first year of the new IBS and CBS consumption taxes, must apply by 15 October 2026. Companies already in Simples that want to pay IBS and CBS under the regular regime have until 30 October. The resolution was published on 28 September.
  • Brazil, split payment (published 5 October). Integration tests between payment service providers and the public split-payment platform start on 15 October 2026. Providers that wanted to join the first phase had to ask their trade association by 2 October; the rest can register from 16 November. The notice is dated 30 September and does not say when split payment becomes mandatory.
  • Brazil, foreign SaaS billed by AWS Brazil (published 3 October). AWS announced on 2 October that eligible software vendors outside Brazil can have AWS Brazil resell their SaaS licences, invoiced in reais with Brazilian taxes and with withholding calculated automatically. This is not a mandate, but it is a change in who invoices Brazilian buyers and how tax is handled, and it carries no start date beyond the post itself.
  • Chile, SII dispatch guides (published 5 October). New requirements for the electronic dispatch guides and invoices that accompany goods in transit apply from 1 November 2026, after a resolution published on 22 April postponed them.

Six of these items have a date before 3 January 2027: Ukraine, the UAE, both Brazilian tax items, Chile and the Philippines. Saudi Arabia's date is February. Pakistan's orders have none, and the AWS change has none.

What the count shows

The warning periods are short and uneven

Taking each item's announcement date and the first date on which a business had to do something, the lead times were 2 days (Brazil's first-phase nomination for split payment), 5 days (Ukraine's switch to the Sandbox), 17 days (Brazil's Simples option), 31 days (the UAE's provider appointment), 100 days (the Philippines' 31 December deadline), 192 days (Saudi Arabia's Wave 25) and 193 days (Chile's dispatch guides). Pakistan's orders and the AWS change have no date and are left out. The median is 31 days.

The two longest periods belong to authorities that have done this many times. ZATCA says it gives at least six months' notice before each wave, and Wave 25 was announced 192 days ahead. Chile's tax service postponed its own resolution, which is why 193 days were available. The shortest periods belong to the first steps of new systems, where the authority is still building the platform it is asking businesses to connect to.

Short warnings are not the same as short projects. In each of the nine cases the work falls on whoever runs the invoicing software: the business itself if it built its own, otherwise its ERP, accounting or billing vendor, and in several countries an accredited intermediary as well.

Most of the evidence is the authority's own page

Seven of the nine items rest on one page from the body that made the change and nothing else. That is not a weakness in the reporting; it is the nature of the subject. A tax authority's circular is the primary source, and in most of these markets the trade press arrives days or weeks later, if at all. When we published, the only independent material we found was an accounting firm's summary for the Philippines and a compliance vendor's summary for Chile, and we used both with that label.

It does mean that a buyer reading about these changes in a vendor's marketing email is usually reading the vendor's interpretation of a single government page, often translated. Three of the four non-English items were in Portuguese and Spanish, and one in Ukrainian. Where we read a scanned PDF, as with Pakistan's orders, the text itself was partly garbled. The safest habit is the one we follow: go back to the authority's own page, and note what it does not say.

The gaps are as useful as the dates

Three things the authorities did not say turned out to be as important as what they did. Pakistan's orders give no start date. Brazil's split-payment notice gives no date for when the mechanism becomes mandatory. And the Philippine bureau, with a deadline under three months away, had accredited no e-invoicing provider at all. In each case a business cannot finish the work until the authority publishes more, but it can start choosing software that will be able to absorb the missing piece when it arrives.

Why none came from the EU or the US

Our sample covers four days and nine items, so the absence of Europe and North America is partly chance. Some of it is not. The United States has no federal e-invoicing mandate. Europe's big changes, Poland's KSeF, Germany's B2B e-invoice, France's reform and the EU's VAT in the Digital Age package, have been announced for years, and their next dates were not moved in those four days. We did hold one European lead in the period, a reported plan to defer Poland's KSeF penalties, because the only source was a draft quoted by a specialist site; we will publish it when the finance ministry confirms it.

The point for buyers is that the most frequent changes are happening in the markets where many international software vendors have the least local presence. A company selling into Riyadh, Dubai, São Paulo, Karachi or Manila needs its invoicing stack to keep up with authorities that change the rules on a monthly rhythm, in their own language, and often with a month's notice.

How to map your own exposure

The method below is the one we use when we read a new tax-system notice. It does not need any paid tool, and a finance or procurement team can run it in an afternoon.

1. List every place you issue an invoice from, not every place you sell to

E-invoicing rules attach to the entity that issues the invoice and, often, to its VAT or sales-tax registration. Start with a list of every legal entity and every tax registration your company holds, and for each one note which system issues its invoices. A subsidiary in the UAE invoicing from a group ERP hosted in Europe is still subject to the UAE's deadlines.

2. For each registration, find the authority's own page and set a watch

The table of tax-authority pages in our source list gives one starting point. We listed 19 authorities' pages after probing them on 5 October, 18 of which could be read directly and one only in a browser; another 11 could not be read from our network at all, mostly because of bot checks or pages built entirely by scripts. Bookmark the authority's news page and, where it has one, the technical page for its e-invoicing system, and check both at least once a week. A deadline you discover from your vendor is a deadline you discovered late.

3. Write down three things for every notice: the date, the threshold and the gap

For each change, record the first date on which you must do something, the threshold that decides whether you are in scope (revenue band, tax type, sector, use of computerised systems), and what the notice does not yet say. The last column is the one people skip. In our nine items it included missing start dates, missing mandatory dates and an empty list of accredited providers.

4. Ask your software vendor four questions in writing

  • Which of our tax registrations does your product already support for this change, and since which release?
  • If the change needs an accredited intermediary or service provider, which one do you work with, and what does it cost us?
  • How will you handle the parts the authority has not published yet, and how quickly after publication will you ship them?
  • What happens to invoices that the authority rejects: who is told, and how are they corrected and re-sent?

A vendor that answers the first question with a release note and a date is in a different position from one that answers with a roadmap slide. Keep the answers: they become the baseline for the next notice.

5. Count the lead time you actually have

Take the authority's date and subtract the time your organisation needs to approve, contract and test a change. If the result is negative, escalate now rather than when the vendor's email arrives. Our median of 31 days suggests that, for most of these markets, the safe assumption is that you will not get more than a month's notice of the next step.

6. Treat intermediaries as suppliers, not as plumbing

Several of these systems route invoices through an accredited provider: the UAE requires one, Saudi Arabia's Fatoora integration is commonly done through one, and the Philippines plans to accredit them. That provider is a supplier with access to every invoice you issue. It deserves the same checks as any other: accreditation, data location, service levels, how you leave, and what happens if its accreditation is withdrawn.

What our count does not show

Our count covers nine news items published between 2 and 5 October 2026 and the 19 tax-authority pages we probed on 5 October. It is not a census of the world's e-invoicing changes, and four days is a short window: a different four days would give different countries. It counts what our desk published, which depends on which authorities we read and in which languages. Lead times were measured from the date on each authority's notice to the first date a business had to act, not to the final go-live, and two items with no stated date were left out of the median.

Every item still carries its red note, because at the time of writing no independent source had confirmed it. As independent reports appear, we add them to each item and remove the note, and if a date moves we correct the item and say so.

Disclosure. TrustList's parent company also makes software, sold as Rutba products. None of the nine items names a Rutba product, and no Rutba business is a party to any of the changes described.

Sources

Categories & features

Keep exploring

More on TrustList

Everything here links back to the same verified catalogue. Pick your next stop.