NetSuite localization: official or partner?

Many Spanish NetSuite accounts still run a partner-built localization installed years ago, when Oracle's own did not cover enough. There is an annual fee, everything works and nobody touches it, until someone asks whether the fee still makes sense, or whether Verifactu is covered.

Here is what Oracle's documentation says the official localization covers, what it requires, where Verifactu lives and which dates to use. It also covers what most comparisons skip: invoices and credit notes that no person creates, because a Shopify, marketplace, Celigo or scripted integration does.

Short answer. Oracle's Spain Localization SuiteApp generates Modelos 303, 349, 390 and 347 and the SII files, with manual or scheduled submission to the AEAT, but only on OneWorld accounts with SuiteTax. Verifactu is not in it: Oracle documents it in a different SuiteApp, European Union Electronic Invoicing, and it is mutually exclusive with SII. A partner localization still makes sense if your account does not meet the requirements yet, provided the partner commits in writing to the updates. Either way, check the invoices your integrations create.

Verifactu notice, as of 15 October 2026. The postponement of Verifactu to October 2028 has been announced, but has not yet been published in the BOE (Spain's official gazette). Until the change is published, the legal dates remain 1 January 2027 and 1 July 2027. Plan as if the postponement is coming, but do not stop.

What the official localization includes

The official localization is the Spain Localization SuiteApp. According to Oracle's help:

• VAT returns through the Tax Reporting Framework's Country Tax Reports: Modelo 303, 349 (intra-EU transactions), 390 (annual summary) and 347 (transactions with third parties). The 303 is previewed in NetSuite and exported as a TXT file.
• SII files in XML for issued and received invoices (registration and correction), submitted to the AEAT manually or on a schedule.
• Spain financial reports, with sourcing already configured and not editable by hand.
• Predefined SuiteTax tax codes for Spain.

Much of this used to be bought from a partner. For SII invoice types, Oracle says the SuiteApp supports F1 and F2 for invoices and R1 to R5 for rectifying invoices: F1 and R1 by default, F2 (or R5) when the customer's tax number is empty, and F2 for B2C. Check Oracle's current list; it changes between releases.

What it requires

• A OneWorld account with SuiteTax. Oracle is explicit: the SuiteApp's features work only on OneWorld accounts with SuiteTax.
• A Spanish subsidiary, with country and nexus set to Spain and currency EUR.

Enabling SuiteTax cannot be undone, and Oracle recommends enabling it in Sandbox first. If you are still on Legacy Tax, moving is a project in itself. Several entities? See the multi-subsidiary chart of accounts.

And Verifactu? A different SuiteApp

Oracle documents Verifactu in the European Union Electronic Invoicing SuiteApp, for outbound invoices and credit memos. The transaction is certified through a service provider and carries a Verifactu URL, printable as a QR code, that links to the tax authority's site.

The sentence that matters for the decision: according to Oracle, the Spain e-invoicing features are mutually exclusive with the SII features of the Spain Localization SuiteApp. You cannot use both.

SII or Verifactu: which one, and which dates

This is information, not tax advice; your tax adviser (asesor fiscal) decides which regime applies.

Status as of 15 October 2026. On 5 October 2026 Spain's Ministry of Finance published an information note announcing it plans to postpone the pending obligations of Royal Decree 1007/2023 until October 2028, to coincide with mandatory e-invoicing for businesses with annual turnover up to 8 million euros. It is an announcement: we found no publication of the change in the BOE (we checked the daily BOE summaries for 5 to 15 October 2026), and the AEAT page, updated on 13 October, still gives the dates of Royal Decree-law 15/2025: before 1 January 2027 for Corporate Income Tax taxpayers and before 1 July 2027 for everyone else. Until the change is published, those are the legal dates.

In practice:

• Plan for the postponement, but keep working. According to the note, the integrity, retention and traceability requirements stay substantially equivalent, so adaptation work is not lost.
• If you are already on SII, the two NetSuite feature sets are exclusive. SII is mandatory for, among others, taxpayers with operations above 6,010,121.04 euros, REDEME registrants and VAT groups; others can opt in. Confirm with your tax adviser which applies.
• The Basque Country and Navarre have their own regimes, not covered here.

Official vs partner: the differences that matter

Standard is cheaper to maintain and custom has to earn its place: see standard vs customised.

When a partner localization still makes sense

It is reasonable if the account is not OneWorld or is on Legacy Tax and migration cannot be done safely before the first 2027 close; if you have fiscal casuistry the official sourcing cannot handle (test in Sandbox first); or if the partner commits by contract to updates, with dates. Plan the move anyway, and do not run both localizations on the same reports beyond a controlled test.

What almost nobody checks: invoices created by integrations

In many companies most invoices and credit notes are created by a flow, and every flow has to leave in NetSuite the fields the localization needs.

• Which fields. SII invoice type, predefined Spain tax codes, customer tax ID and, for B2C, the simplified type. If a flow writes to the previous localization's fields, remap them. If the ecommerce platform issues its own invoices, decide one issuer per channel.
• Simplified invoices and credit notes. A B2C shop mostly produces F2 and, with returns, R1 to R5. See returns, refunds and credit notes.
• The cut-over date. Oracle warns that all relevant transactions, and their whole chain, must be created after installing the SuiteApp to be reported correctly: a sales order created before and invoiced after can cause SII discrepancies. With open orders arriving through ecommerce order integration, pick the date with those orders in view.
• Which flows create transactions. The NetSuite–Shopify integration and marketplace settlements are examples. With Celigo, the mapping lives in the platform.
• Test the whole chain in Sandbox: order, fulfilment, invoice, SII or Verifactu record, AEAT response, channel by channel. It does not replace your tax adviser.

Atypical is not an Oracle NetSuite partner and does not implement localizations: we review how your integration flows behave against the one you choose.

An autumn decision checklist

1. Which localization bundles or SuiteApps are installed, and who publishes them?
2. Is the account OneWorld, and on SuiteTax or Legacy Tax?
3. What does the partner localization cost, and when does it renew?
4. Which reports and submissions run automatically, and which by hand?
5. Does SII or Verifactu apply? Confirm with your tax adviser.
6. Which channels create invoices, and which custom fields do they write?
7. Is there a Sandbox to test the full chain?
8. Is the partner's commitment in writing: what, who certifies, by when?

Changing partner? Our freelancer vs partner comparison has a handover list that works here too, and life after go-live covers who should answer when something breaks.

FAQ

Does NetSuite's official localization include Verifactu?

No. Oracle documents Verifactu in the European Union Electronic Invoicing SuiteApp, which is mutually exclusive with the localization's SII features.

What does the Spain Localization SuiteApp require?

A OneWorld account with SuiteTax and a Spanish subsidiary with country and nexus Spain and currency EUR, according to Oracle.

Can I use SII and Verifactu at the same time in NetSuite?

No. According to Oracle the two feature sets are mutually exclusive. Your tax adviser confirms which regime applies.

When is Verifactu mandatory?

As of 15 October 2026 the legal dates are still before 1 January 2027 for Corporate Income Tax taxpayers and before 1 July 2027 for everyone else, under Royal Decree-law 15/2025. On 5 October 2026 the Ministry of Finance announced a postponement to October 2028, but it has not yet been published in the BOE, so it is not a legal date until it is. Plan for it, without stopping.

Does the official localization cost extra?

Oracle SuiteApps are not billed as a third-party licence, but activation is a project, and Verifactu involves a certification service provider. Confirm terms with Oracle.

What about invoices created by my ecommerce integrations?

They must fill the fields the localization uses (invoice type, tax codes, tax ID). When you switch, test every flow and set the cut-over date with open orders in mind.

My account is on Legacy Tax. What now?

Moving to SuiteTax is a project in itself and cannot be undone, so test it in Sandbox first. Plan early, or get the partner's 2027 commitment in writing.

Sources

All accessed on 15 October 2026.

• Oracle NetSuite Help Center, Spain Localization Overview.
• Oracle NetSuite Help Center, SII Transaction Record Information.
• Oracle NetSuite Help Center, Spain Veri*Factu Outbound Transactions.
• Ministerio de Hacienda, information note of 5 October 2026 on the invoicing-systems deadlines (in Spanish).
• AEAT, Extension of the deadline to adapt invoicing systems (in Spanish), page updated 13 October 2026.
• BOE, daily summaries for 5 to 15 October 2026 (open data): no publication of the postponement.

Let us review your flows before December

If your invoices start in Shopify, Amazon, PrestaShop or a Celigo flow, let us check that they reach SII or Verifactu correctly. Book a call.