
Picture a group that has decided to open a subsidiary in Spain in six months. There are premises, perhaps a manager, a date. There is no system yet: no ERP, no way to invoice, nothing that connects the new company to head office. Every software vendor proposes its own product, and at head office no one knows which of them will be able to talk to the group’s system, or what Spain requires of the program that issues an invoice.
One way out is to open with whatever is at hand: orders in a spreadsheet, invoices from a stopgap tool, the data typed again at head office, and a promise to sort it out once the subsidiary is running. In Spain that promise has become harder to keep. The rules on the program that issues invoices already have dates, and the e-invoice between businesses has a calendar of its own. A tool chosen in a hurry can turn out, on the first day, to be a tool the subsidiary may not even keep installed.
This piece is for the six months before opening. It separates what must work on day one from what can wait. It sets out the Spanish rules that decide the choice of systems, read in the official texts: the tax number, the registration for trading inside the EU, the rules on the invoicing program and the coming e-invoice. It covers the head office’s side in Italy, and what changes if the new subsidiary is in Italy instead. Then it turns to choosing the ERP, connecting it to head office and ordering the work in stages.
As always: this is not tax or legal advice. The legal form, the taxes and the registrations are for your advisers. What follows is the systems side, and it is meant to be read with a local tax adviser, which is how we work.
Day one: what has to work, and what can wait
A subsidiary does not need everything on the day it opens. It does need a few things to work from the first order and the first invoice, because fixing them afterwards means redoing work already done, or correcting invoices already issued.
What has to work
The subsidiary can be identified for tax purposes, with its Spanish tax number and, if goods or services move between it and head office, its number for trading inside the EU. It can issue a compliant invoice from the first one, with a program that meets the rules that apply to it. Its customers and items are the group’s, not a second list that drifts away from the first. Its orders go into a system once, and head office sees them without anyone forwarding a spreadsheet. And the invoices between the two companies flow in both directions, with their data reaching the Italian exchange system on time.
What can wait
The Spanish e-invoice between businesses has dates in 2027 and 2028, so it does not have to work on day one; it does have to be possible with the system you choose. Automating the less frequent flows, the reports that go beyond what head office needs to see, the dashboards: all of these can come in later stages. The test is simple. If something missing on day one means an invoice issued wrongly or data typed twice, it belongs in the first column. If it means a manual step that can be done correctly for a few months, it can wait.
The subsidiary’s tax identity in Spain
Before the first invoice, the subsidiary needs to exist for the Spanish tax agency, the Agencia Tributaria (AEAT). Three things matter to its systems.
The tax number
According to the AEAT, legal persons and entities must, as a rule, have a tax identification number (NIF) when they are going to carry out transactions with tax relevance; so must non-resident entities and the permanent establishments of non-resident companies operating in Spain. An entity applies for it with form 036. If not all the required documents are provided, the NIF assigned is provisional, and the entity must provide what is missing to obtain the definitive one within one month of its entry in the relevant register, or of the deed of incorporation where no registration is needed. While the NIF is provisional, the AEAT adds the words «EN CONSTITUCIÓN» to the company’s name.
For the systems, the tax number is not a detail. Every invoicing record under Royal Decree 1007/2023 carries the issuer’s tax number (Articles 10 and 11), and so, later, will the unique code of every Spanish e-invoice. The company record in the ERP is set up with it, so the request for the NIF belongs at the very start of the timetable.
Trading with head office inside the EU
The AEAT says that a business established in Spain (on the mainland and the Balearic Islands) must obtain a VAT number for intra-EU trade, the NIF-IVA, by registering in the Registro de Operadores Intracomunitarios (ROI), if it is going to make intra-EU supplies of goods, taxable intra-EU acquisitions of goods, or certain transactions in services with businesses not established in Spain. The registration is requested with the same form 036, ticking the box for registration and stating the planned date of the first transaction. If the AEAT has not decided within three months, the request may be considered refused.
The AEAT adds that the exemption of an intra-EU supply applies only if the customer has given the supplier a valid VAT number of a member state other than Spain, and the supplier reports the transaction in its recapitulative statement (form 349). In a group where goods move between Italy and Spain, the subsidiary’s NIF-IVA is therefore one of the first requests, not the last. The ERP keeps it in the company record, and checks the counterpart’s number in the EU’s VIES service before relying on it.
Large companies and the SII
The AEAT keeps a register of large companies, for a volume of operations above 6,010,121.04 euros. The Immediate Supply of Information system (SII), under which the taxpayer sends the AEAT the details of its invoicing records within four days, not counting Saturdays, Sundays and national holidays, is compulsory for those who file VAT monthly: among others, large companies, which the AEAT describes as those with a turnover above six million euros, VAT groups, and businesses registered for monthly VAT refunds (REDEME). Any other business may opt into it, and then stays in it for at least the calendar year. Whether your subsidiary will be in the SII is a question for your adviser, and it matters here because it changes which rule its invoicing program has to meet.
The invoicing program: a rule that applies from the first invoice
Royal Decree 1007/2023 of 5 December approves the regulation on the requirements of invoicing systems, known as VERI*FACTU. It does not concern how an invoice reaches the customer. It concerns the program that issues it.
What it asks of the program
The system must guarantee the integrity, preservation, accessibility, legibility, traceability and unalterability of its invoicing records. With each invoice, at the moment of issue or immediately before, it generates a record carrying a hash; the records are chained, so that their trail can be followed from the first to the last, and a correction is made with a further record, never by altering the original. A system that does not send its records also signs them electronically and keeps an event log. A system that sends every record to the AEAT continuously, automatically and instantly is a VERI*FACTU system: it is presumed to meet the requirements of Article 8 and only has to calculate the hash of the records; it does not sign them and, according to the AEAT, needs no event log. The AEAT also offers a free invoicing application, which counts as a VERI*FACTU system. According to the AEAT’s frequently asked questions, invoices issued with any system bound by the regulation, VERI*FACTU or not, carry a QR code that the recipient can scan to send certain data to the AEAT; in a structured e-invoice, its content takes the place of the image.
When it applies
The regulation’s fourth final provision, as amended by Royal Decree-Law 15/2025 of 2 December, sets two deadlines: companies paying corporate income tax (the Impuesto sobre Sociedades) must have adapted systems before 1 January 2027; the other parties bound by it, before 1 July 2027. A subsidiary that opens in six months will issue its first invoice after the first of those dates. Under the text in force today, a Spanish company paying corporate income tax and bound by the regulation will therefore need an adapted system from its very first invoice.
The AEAT is explicit about what happens after the deadlines: merely holding a non-adapted program able to issue invoices is an offence. A stopgap tool chosen for the first few months is therefore no longer a neutral choice: it has to be an adapted program. The AEAT’s own application is one, although the AEAT expects it to be used by micro-businesses and professionals that issue a limited number of invoices, typed into its form.
Who it applies to
The AEAT sums the scope up in what it calls the «regla de los 4 NO», the rule of the four NOs: the regulation reaches businesses established in Spain that issue invoices with a computer system, are not in the SII, are not domiciled for tax purposes in the foral territories of the Basque Country or Navarre, and have no resolution exempting them. A subsidiary that is in the SII is outside it and has to meet the SII’s reporting instead. That is why the question of the previous section comes first.
A deadline that may move
On its page about these systems, the AEAT lists a «Comunicación del Ministerio de Hacienda de 05/10/2026» on a planned extension of the adaptation period. It is a plan, not a rule: as this piece is written, the regulation in the Boletín Oficial del Estado (BOE) still reads as above. Check its current wording before you plan around a date.
The e-invoice between businesses: not on day one, but already in the choice
The duty to e-invoice between businesses comes from Law 18/2022 of 28 September, known as «Crea y Crece», which rewrote Article 2 bis of Law 56/2007: all businesses and professionals must issue, send and receive electronic invoices in their dealings with each other, and report the status of each invoice. Royal Decree 238/2026 of 25 March is its regulation. According to the AEAT’s calendar, its periods run from 6 October 2026, when Order HAC/1028/2026 of 2 October came into force. The duty applies on 6 October 2027 to businesses whose volume of operations exceeded eight million euros in the previous calendar year, and on 6 October 2028 to the rest. For a company opened in 2027, your adviser will tell you which of the two applies.
The subsidiary will not need it on day one. It will need it with the system it chooses now, and the regulation describes what that system will have to do.
The format
Article 7 asks for a structured message following the EN 16931 semantic data model, in one of four syntaxes: CII, UBL, the EDIFACT invoice message or Facturae.
The routes
Invoices travel through private exchange platforms, through the AEAT’s public solution, or both (Article 5). A business that has not expressly agreed with its suppliers to receive through a private platform is taken to have chosen the public solution, and one that receives through a private platform publishes its entry point (Article 6). The recipient cannot oblige the issuer to use a particular platform or provider (Law 56/2007, Article 2 bis, paragraph 3 bis).
The statuses
Every recipient tells the public solution about the full payment of each invoice, with its date and due date, within four calendar days of the payment, not counting Saturdays, Sundays and national holidays, or else about its rejection (Article 12).
What this means for the choice
The system the subsidiary chooses now will be the one that has to hand its invoices to a platform or to the public solution, take in its suppliers’ e-invoices from the dates those suppliers are bound, and report payments. A vendor that cannot say how its product will do that is giving you an answer too.
The head office’s side, in Italy
If the subsidiary buys from head office, sells to it, or both, the Italian side of those flows has its own rules, and head office’s ERP has to be ready for them on the day of the first intercompany invoice.
Invoices from the subsidiary to head office
Royal Decree 238/2026 applies when the recipient has its seat, a permanent establishment or, failing those, its domicile in Spain, and the transaction is addressed there (Article 3). An Italian head office with no seat or establishment in Spain is outside that scope. Royal Decree 1007/2023 is another matter: according to the AEAT, it covers every invoice a business must issue, intra-EU supplies included, so if it applies to the subsidiary, its invoices to head office also carry an invoicing record and the QR code. In Italy, Article 1, paragraph 3-bis, of Legislative Decree 127/2015 asks Italian businesses to send the Italian tax authority, the Agenzia delle Entrate, the data of purchases from parties not established in Italy, save the exceptions it lists. Since 1 July 2022 that data goes through the Sistema di Interscambio (the SdI), in the format of the e-invoice, by the fifteenth day of the month after the document was received or the transaction took place. The specifications of the FatturaPA, the Italian e-invoice format, provide integration documents for these cases, such as TD17 for services bought from abroad and TD18 for goods bought from another EU country. Which type fits is a tax decision; generating the document from the invoice received is a systems decision.
Invoices from head office to the subsidiary
For sales to parties not established in Italy, the same paragraph asks for the data within the deadlines for issuing the invoice. The FatturaPA specifications set a fixed recipient code for it, XXXXXXX, and the Agenzia delle Entrate’s Circular 26/E of 13 July 2022 states that with that code the SdI does not deliver the file to the customer: the subsidiary has to receive its invoice another way. The same circular adds that if the Italian company issues the e-invoice through the SdI with a recipient code the customer has given it, and a country code other than IT, that invoice also fulfils the duty. Head office can therefore agree with the subsidiary how it will receive: through an SdI code, or through another channel alongside the seven-X file. Whether the Spanish e-invoice duty also reaches those invoices, from the date that applies, depends on whether head office has to issue them under the Spanish invoicing regulation (Article 3 of Royal Decree 238/2026): ask your adviser before anything is designed.
If the new subsidiary is in Italy
The same question can run the other way: a group whose head office is in Spain, or elsewhere, opens a company in Italy. The tax registrations in Italy are for your adviser there, and we do not cover them here. On the systems side, one rule decides almost everything from day one.
Article 1, paragraph 3, of Legislative Decree 127/2015 says that for supplies of goods and services between parties resident or established in Italy, and their later corrections, only electronic invoices are issued, through the SdI, in the format the law sets: the FatturaPA. For a new company this means that its first invoice to an Italian customer is an e-invoice that goes through the SdI, and so is the first invoice an Italian supplier sends it.
To receive invoices straight into its own system, the subsidiary needs a channel the SdI can deliver to. The FatturaPA specifications describe two: a seven-character code, which the SdI assigns, on request through the B2B recipient-code function on fatturapa.gov.it, to whoever has accredited a receiving channel, the company or its intermediary; or a certified email (PEC) address, with the code 0000000. Its invoices to the foreign head office follow the seven-X rule described above, and its purchases from head office the fifteenth-of-the-month rule, except in the cases the paragraph excludes, such as transactions covered by a customs bill. A local system, or the group’s, therefore has to produce the FatturaPA from the first day, as well as connect to head office.
Choosing the ERP: the group’s system, or a local one
There are two honest answers, and the right one depends on the group.
One system for both companies
The group’s ERP is extended to the subsidiary. Items and customers are shared, an order taken in Spain is already in the system head office reads, and intercompany invoices can be generated on both sides from the same transaction. Royal Decree 1007/2023 allows one computer system to serve several taxpayers, as long as each one’s invoicing records are kept separate and each meets the requirements on its own. The cost is that the group’s ERP has to meet the Spanish rules for the Spanish company, with an adapted version now and the local formats later, and offer screens the local staff can work in.
A local system connected to head office
A system sold and supported in Spain is chosen for the subsidiary and connected to the group’s. Local support comes with it; whether it meets the local rules is the first of the questions below. The cost is the connection: someone has to decide which system is the master of each piece of data, and every flow between the two has to be built, tested and kept running.
The questions that decide
Whichever way you lean, the same questions separate a system that will work from one that only looks as if it will:
- Is there a version adapted to Royal Decree 1007/2023, and from which release?
- Can it keep the invoicing records of each company separate?
- Which of CII, UBL, EDIFACT and Facturae can it produce, or which platforms does it connect to?
- Can it take in suppliers’ e-invoices and report payment statuses?
- How does it exchange orders, items, customers and invoices with head office’s system?
- Who supports it, in which language, and who holds the accounts and the data?
The AEAT itself recommends asking the maker of a non-adapted invoicing program whether an adapted version exists, because one often does; the same question works for every vendor on your list. The decision on the system is yours; the decision on what the rules require is your adviser’s. Our part is to put the two side by side.
Connecting the subsidiary to head office
A connection is a set of flows, and each flow has an owner, a moment and a failure mode. Writing them down before building anything is most of the work.
Items and customers
The group’s item codes are the ones the subsidiary sells. If the local system keeps its own list, decide which side creates a new item and which side receives it, and what happens when the two disagree. Customers work the same way, with the added question of who may change a customer’s tax details.
Orders
An order taken in Spain enters a system once. If the subsidiary sells what head office makes or stocks, the order reaches head office without being typed again, and its status comes back.
Invoices and payments
The intercompany invoices described above are generated from the transaction, on both sides, with the Italian data sent to the SdI on time. Payments between the two companies are matched to those invoices, not to a spreadsheet.
What head office sees
Head office sees the subsidiary’s orders, invoices and open payments in its own system or on a dashboard, without asking anyone to send them. That is the test that the connection works: no one at head office needs a forwarded file to know what happened in Spain yesterday.
Six months, in stages: an example
Here is one way to order the work, as an example. Your dates depend on the incorporation, on the answers of your adviser and on the system you choose. What matters is that each stage closes before the next begins, and that at each one you know what is done and what comes next.
Month one: the start-up plan
What day one needs and what can wait, the flows with head office, the dates that apply to the subsidiary, reviewed with the adviser. One person at head office decides. Alongside the plan, the request for the tax number goes in.
Month two: the choice
The local system or the group’s, chosen against the questions above. Alongside it, if goods or services will move between the two companies, the registration for intra-EU trade is requested, since the AEAT may take up to three months to decide.
Months three and four: the connection and the invoicing
The flows built one by one, items and customers first. The invoicing set up alongside the local adviser, so that the first invoice complies with the rules that apply.
Month five: the tests
Test invoices in both directions, intercompany included: a normal invoice, a credit note, an invoice with several tax rates and one with a missing detail. The Italian data checked against the deadlines of paragraph 3-bis.
Month six: the handover
The local staff take over working systems, with an explanation of how they are used and the documentation. No order or invoice goes through a spreadsheet.
Where to start this week
None of this needs a project to begin. Four things can be done by the people you already have, and they turn a vague worry into a short list of decisions.
- Write down the planned opening date, the legal form and the one person at head office who decides.
- Ask your adviser whether the subsidiary will pay corporate income tax, be in the SII, need the ROI, and which e-invoice date applies.
- Draw the flows between the two companies: orders, items, customers, invoices, payments.
- Send the questions above to every vendor on your list, and to the maker of the group’s ERP.
How we do it
This is the work of our systems start-up for a new subsidiary. First we write the start-up plan with you: what the subsidiary needs on day one and what can wait. Then we choose the subsidiary’s system together, connect it to head office, set up invoicing alongside the local tax adviser and check with the adviser that the first invoice meets the rules that apply. Finally we hand the working systems over to the local staff, show them how they are used and leave them the documentation.
You receive a start-up plan, the systems connected and the handover to the local staff. We tell you which systems can be connected to head office and, with the local adviser, which meet what the country requires; the decision is yours. The code, the accounts and the documentation are in your name from day one.
If you are opening in Spain or in Italy and have not chosen anything yet, start with a free one-hour video call: tell us the date, the people and the systems you already have, and we will tell you what we would settle first.
The official texts we cite
- The AEAT’s pages on the NIF of legal persons and entities and on applying for an entity’s NIF with form 036.
- The AEAT’s page on ROI, VIES and the NIF-IVA.
- The AEAT’s pages on who must be registered and on the Immediate Supply of Information.
- Spanish Royal Decree 1007/2023, with its fourth final provision as worded by Royal Decree-Law 15/2025.
- The AEAT’s page on invoicing systems and its frequently asked questions.
- Spanish Law 18/2022, Article 12 (the new Article 2 bis of Law 56/2007).
- Spanish Royal Decree 238/2026 of 25 March, and the AEAT’s implementation calendar.
- Italian Legislative Decree 127/2015, Article 1, paragraphs 3 and 3-bis (Agenzia delle Entrate).
- FatturaPA technical specifications, version 1.4 (fatturapa.gov.it).
- Circular 26/E of the Agenzia delle Entrate, 13 July 2022 (Agenzia delle Entrate).
What we do about it: Systems start-up for a new subsidiary