Skip to content
digitapulia.com

Intercompany invoicing between two countries without a week of reconciliation

Why the invoices between head office and a foreign subsidiary do not match at month end, what Italian and Spanish rules fix, and how one record can serve both sides.

· 22 min read

A hand balance hanging from its hook, two brass pans on green cords, one pan lower than the other.
Photo: Auckland Museum · CC BY 2.0

Picture the third working day of the month. Head office in Italy has closed its books and sends the subsidiary in Spain a statement of what the subsidiary owes it. The subsidiary’s figure is different. Someone opens a spreadsheet with both lists of invoices, sorts them by date and starts ticking them off. By the end of the week the difference is explained: two invoices the subsidiary booked in the following month, a credit note nobody forwarded, a recharge of shared costs calculated on last month’s key, a few invoices keyed with a tax the other side never charged. Next month it starts again.

Nothing in that week is a mistake in the usual sense. Each company followed its own rules, its own calendar and its own system. The two sets of books describe the same transactions from two sides, and wherever those two descriptions can drift apart, they did.

This piece is about removing the week, not about getting through it faster. It looks at why one invoice between two companies of a group so often becomes two different figures. It sets out what the rules of Italy and Spain already fix about those invoices, the dates by which they are issued and recorded, the exchange rate and the tax treatment, and what they leave to you. Then it describes the one change that removes most of the work: an invoice issued by one company arrives in the other company’s system as the same record, with the rules applied once, and a report at month end shows only what does not match.

The examples are an Italian head office and a Spanish subsidiary, because that is the pair whose rules this piece quotes. The method is the same for any two countries, and a section near the end says what changes when the subsidiary is outside the European Union. It is not tax advice: where a question is your adviser’s, the piece says so.

Why one invoice becomes two figures

When two companies of the same group invoice each other, the sale in one company’s books is a purchase in the other’s, and what one is owed is what the other owes. When the group prepares consolidated accounts, those balances are eliminated: a group cannot owe itself money. They can only be eliminated cleanly if they are equal, which is why the reconciliation happens at all, and why it happens every month.

The differences that make the reconciliation slow come from a handful of causes, and the same causes return each month until something changes them. Each one leaves a trace that someone has to find by hand.

TIMEOne invoice, two monthsIssued and booked in the month of the sale;booked by the other company when it arrives.RATEOne invoice, two exchange ratesWhen the books are kept in two currencies, eachside converts on its own day, from its own source.TAXOne invoice, two tax treatmentsAn intra-EU sale without VAT, keyed on the otherside as a domestic purchase, or taxed twice.CREDITA credit note only one side hasIssued at the end of one month, received in thenext, or still waiting in a mailbox.SPLITA recharge on two keysShared costs split by this month's key on oneside and accrued by last month's on the other.CODETwo codes for one relationshipThe subsidiary as a customer, head office as asupplier, and nothing linking the two records.Each one leaves a difference that someone finds by hand at month end.
Six ways one intercompany invoice ends up as two different figures. The reconciliation week is the time it takes to find which one each difference comes from.

One invoice, two months

Head office issues an invoice on the last day of the month and records it the same day. The subsidiary receives it a few days later and records it in the following month, which is when, for the subsidiary, the invoice exists. Each followed its own procedure. At month end the two balances differ by that invoice. Goods still on a truck at month end do the same: the sale is in one company’s month and the receipt in the other’s.

One invoice, two exchange rates

Between Italy and Spain this cause arises only for invoices in a currency other than the euro, because both companies keep their books in euros. Between Italy and Mexico, Switzerland or the United Kingdom it can be the largest. The invoice is issued in one currency and recorded in the other, and if each company converts it at the rate of a different day, or takes the rate from a different source, the two figures differ even when everything else is right.

One invoice, two tax treatments

A sale of goods from an Italian company to a Spanish one, with the goods leaving Italy for Spain and both companies identified for VAT, is invoiced without Italian VAT when the conditions quoted in the next section are met, and the Spanish company accounts for the Spanish VAT itself. If the subsidiary keys that invoice as an ordinary domestic purchase, or if head office charges Italian VAT on a service where the customer should account for it, the two sides record different totals and different tax, and someone has to work out which side is right.

A credit note only one side has

Returns, discounts and corrections travel as credit notes. One issued on the last day of a month reaches the other company in the next, or waits in a mailbox until somebody asks for it. Until it arrives, one side has reduced its balance and the other has not.

A recharge on two keys

When head office runs services for the whole group, such as accounting, systems or purchasing, it charges each subsidiary its share. When the share depends on a key, such as headcount, revenue or hours, and the key changes, one side may book the new figure while the other has already accrued the old one.

Two codes for one relationship

In head office’s system the subsidiary is a customer, with a customer code. In the subsidiary’s system head office is a supplier, with a supplier code. The invoice number is head office’s, while the subsidiary registers the invoice under its own number. Nothing in either system says that these two records are the same invoice, so matching them is a person’s job, and that person needs both systems open.

What the rules of the two countries already fix

Several of the six causes are not left entirely to the two finance teams. The VAT rules of Italy and Spain fix by when an invoice is issued, in which month the tax on it falls, which exchange rate the tax base uses and which tax treatment applies. They do not remove the differences, but they set the limits inside which your own rules have to fit. What follows is what the texts say; how they apply to your transactions is your adviser’s to confirm.

By when the invoice is issued

In Italy, an invoice is issued within twelve days of the transaction (Article 21, paragraph 4, of Presidential Decree 633/1972). The same paragraph allows one deferred invoice, by the fifteenth of the following month, for goods delivered in the same month to the same customer with a transport document, and for services documented the same way; services to a business established in another EU country are invoiced by the fifteenth of the following month too. For goods shipped to a business in another EU country, the invoice is issued by the fifteenth of the month after the transaction, stating that it is not taxable and showing the customer’s VAT number (Article 46, paragraph 2, of Decree-Law 331/1993).

In Spain, Royal Decree 1619/2012 asks for the invoice at the time of the transaction, but, when the customer is a business, allows it to be issued before the sixteenth of the month after the one in which the VAT accrued (Article 11.1). For goods shipped to another EU country, it is issued before the sixteenth of the month after the transport began (Article 11.2). One invoice may group a month’s transactions with the same customer, and for a business customer it is due before the sixteenth of the following month (Article 13).

Read together, the rules of both countries allow an invoice for October’s sales to be issued in the first half of November. That is legitimate, and it is exactly the first cause of difference: the issuing company may record October, the receiving company November.

In which month the receiving company records it

When the Spanish subsidiary buys goods shipped from Italy, the Spanish VAT on that intra-EU acquisition accrues on the fifteenth of the month after the transport began, or on the date of the invoice if it was issued earlier (Articles 75.Uno.8º and 76 of the Spanish VAT Act, Law 37/1992). The subsidiary is the one liable for that tax (Article 85). So the month in which the subsidiary accounts for the tax is set by when the transport began and when the invoice was issued, not by when the invoice arrived.

A subsidiary in the SII, Spain’s immediate supply of VAT information, also sends the details of every invoice to the AEAT within four days, Saturdays, Sundays and national holidays excluded: four days from issue for the invoices it issues, in any case before the sixteenth of the month after the VAT accrued, and four days from booking for those it receives, in any case before the sixteenth of the month after the VAT period that includes them (Article 69 bis of Royal Decree 1624/1992). The AEAT lists who is in the SII by obligation: among others, large companies with turnover over 6 million euros, VAT groups and companies in the monthly refund register.

When head office in Italy receives an invoice from the Spanish subsidiary for goods, it completes that invoice with the euro value and the Italian VAT and numbers it (Article 46, paragraph 1, of Decree-Law 331/1993), and records it, with reference to the month of receipt, by the fifteenth of the following month (Article 47, paragraph 1). If no invoice has arrived by the end of the second month after the transaction, head office issues one itself, by the fifteenth of the third month (Article 46, paragraph 5). The data of purchases from parties not established in Italy also goes to the Italian tax authority through the SdI, by the fifteenth of the month after the document is received or the transaction made (Legislative Decree 127/2015, Article 1, paragraph 3-bis); the Agenzia delle Entrate’s technical specifications take the date of receipt for intra-EU purchases.

Which exchange rate the tax base uses

When an invoice is in a currency other than the euro, each country fixes the rate for its VAT. Italy uses the rate of the day of the transaction or, if the invoice does not state the date of the transaction, of the day the invoice is issued; failing that, the nearest previous day’s quotation; and a company may instead use the European Central Bank’s rate, for all its transactions in the calendar year (Article 13, paragraph 4, of Presidential Decree 633/1972). Spain uses the selling rate set by the Banco de España in force when the VAT accrues (Article 79.Once of Law 37/1992); the invoice may be in any currency, as long as the Spanish VAT on it is stated in euros (Article 12.1 of Royal Decree 1619/2012).

The two rules do not name the same source, or always the same day. Between two companies that both keep their books in euros this matters only for invoices in another currency; between Italy and a country outside the euro, the accounting rate is a choice your finance team makes, alongside these tax rules, and should make once for both sides.

Which tax treatment applies

For goods shipped from Italy to the Spanish subsidiary, Italy treats the sale as a non-taxable intra-EU supply when the goods are transported to another EU country for a business customer (Article 41, paragraph 1, letter a, of Decree-Law 331/1993). The non-taxable treatment depends on the customer having given its VAT number from another EU country and on the seller having filed the recapitulative listing (paragraph 2-ter). Spain mirrors it for goods going the other way: an exempt supply, on condition that the customer has given a VAT number from another EU country and that the seller includes the sale in its recapitulative statement (Article 25.Uno of Law 37/1992). A Spanish invoice for an exempt sale refers to the exemption, and one where the customer is liable for the tax carries the words «inversión del sujeto pasivo» (Article 6.1, letters j and m, of Royal Decree 1619/2012).

For services between businesses, the general rule in both countries is that they are taxed where the customer is established: Article 7-ter of the Italian decree and Article 69.Uno.1º of the Spanish law. An Italian invoice for most services to the Spanish subsidiary therefore carries no Italian VAT and the words «inversione contabile» (Article 21, paragraph 6-bis, letter a, which leaves out some exempt services, financing among them), and the subsidiary, as the business customer of a supplier not established in Spain, accounts for the Spanish VAT itself (Article 84.Uno.2º, letter a, of Law 37/1992).

This is where a received invoice keyed by hand can go wrong: a non-taxable or reverse-charge invoice keyed as a domestic one, or a domestic invoice keyed as reverse charge.

What price the two companies may charge each other

The price between two companies of a group is not free. Spain’s corporate income tax law values transactions between related parties at their market value (Article 18.1 of Law 27/2014). Italy’s income tax code asks, for transactions with non-resident companies that control, are controlled by or share a controller with the Italian company, the conditions and prices that independent parties would have agreed, when that increases the Italian income; when it decreases it, the same rule applies through the procedure of Article 31-quater of Presidential Decree 600/1973 (Article 110, paragraph 7, of the TUIR). The OECD publishes Transfer Pricing Guidelines on these questions, and your advisers will work with them. In Spain, the AEAT’s instructions for form 232 ask companies to declare their transactions with each related party when they exceed 250,000 euros in the tax year, among other cases.

VAT has its own, narrower rule. Italy replaces the agreed price with the normal value only between companies linked by control, and only where one side’s right to deduct VAT is limited and the price moves the tax in its favour (Article 13, paragraph 3, of Presidential Decree 633/1972). Spain’s rule is limited in a similar way to cases where a deduction is restricted, though its definition of related parties is wider than control (Article 79.Cinco of Law 37/1992). Between two companies that deduct their VAT in full, the price they agree is the VAT base.

Setting the price is a job for your advisers, and documenting it is part of that job. The connection’s job is to apply the price they set, the same way, on every invoice, on both sides.

What the rules leave to you

The rules set the outer limits: the latest day an invoice can be issued, the month in which the tax falls, the rate for the tax base, the treatment of each kind of transaction. Inside those limits they leave a great deal open. Which date the receiving company uses in its accounts, within the VAT months the rules fix, which rate the accounts use, which code each company has in the other’s system, how a recharge is calculated and when its key changes, who issues a credit note and when, on which day each company closes its month. No law decides any of these, and all of them are where the reconciliation week goes.

One invoice, one record on each side

Each of the six causes above has the same root: one transaction is entered twice, by two people, in two systems, at two moments, each applying the rules as they understand them. The reconciliation week is the cost of comparing the two entries afterwards. The change that removes most of it is to stop entering the transaction twice.

The invoice exists once, in the system of the company that issues it. The other company’s system does not receive a PDF for someone to retype. It receives the invoice as data, and creates from it the received invoice: the issuing company’s number and date kept as references, the same lines and amounts, the exchange rate the written rule sets and the tax treatment the written rule assigns to that kind of invoice. Where its own rules ask it to number or date the invoice in its records, the receiving company still does; both records point at the same issued invoice. Nobody keys it, so nobody keys it differently.

Head office's ERPissues the invoice, as it does todayThe rules your finance team wrote downwhich exchange rate, from which source and daywhich tax treatment for each kind of invoicewhich code each company has in the other's systemSubsidiary's ERPthe same invoice arrives as a received one:issuer's number and date, same amountsMonthly reconciliation reportMatches on both sidesOnly on one sideDifferent amount or rateDifferent tax treatmentYour finance team reads only the lines outside the first group.
One invoice, one record on each side. The same path runs the other way when the subsidiary invoices head office.

This does not move any decision from your finance team to a program. Which rate, which tax treatment and which price are still decided by the people who decide them today, with their advisers. What changes is that the decision is written down once and applied to every invoice in the same way, instead of being taken again by whoever keys the invoice that day.

It also does not need the two companies to use the same ERP. The connection reads the issued invoice from one system and writes the received invoice into the other, through whatever each system offers for that: an interface, a file it imports, a table it reads. It works the same way when the two companies run different systems, as they do when a subsidiary was bought with its own.

The same path runs in the other direction when the subsidiary invoices head office, and between any other pair of companies in the group that invoice each other. Each pair has its own rule table, because the tax treatment of an invoice from Spain to Italy is not the mirror image of one from Italy to Spain in every case.

The rules to write down before connecting anything

The connection is the easy part. The work that makes it useful is writing down, in plain language and before any code, the rules that today live in the heads of the people who key the invoices. These are the ones that matter most.

Which exchange rate, of which day, from which source

For companies whose books are in different currencies, write which rate converts an intercompany invoice: the rate of the invoice date or of the transaction date, and from which source, such as the European Central Bank or the national bank of one of the two countries. The VAT rules quoted above say which rate the tax base uses; the accounting rate is a choice your finance team makes and should make once. When both sides read the same rate, from the same source, for the same day, the rate stops being a cause of difference.

Which tax treatment, for each kind of invoice

List the kinds of invoice the two companies exchange: goods shipped from one country to the other, goods sold without leaving a country, services, recharges of shared costs, interest on a group loan. For each, write the tax treatment and the wording the invoice carries, as your advisers set it. The connection then assigns the treatment by the kind of invoice, and the received invoice arrives with it already applied.

Which date each company uses in its accounts

Agree which date the receiving company uses in its accounts, within the VAT months the rules fix, and what happens to an invoice issued on the last day of a month. One option is for the receiving company to accrue in its accounts, in the issuing company’s month, an invoice that arrives before its own close, while its VAT records keep the month the rules set; another is to record in the month of arrival and report the invoices in transit separately. The rules quoted above set the outer limits; inside them, the choice is yours, and it has to be the same every month.

Which codes, on each side

Write which customer code each company has in the other’s system, which supplier code, and which item or service codes correspond. Keep the issuing company’s invoice number on the received invoice, in a field the report can read. This table is short, and without it no program can match anything.

What happens to a credit note

A credit note follows the same path as an invoice, with a reference to the invoice it corrects. Write who issues it, when, and what the receiving company does with a credit note for an invoice it has not received yet.

Who closes when

Write the close calendar of the two companies side by side: the day each one stops recording the month’s intercompany invoices, and the day the report runs. A report that runs before the other side has closed shows differences that are only timing.

The reconciliation report at month end

The report puts the two companies’ intercompany invoices side by side, matched by the issuing company’s invoice number, and sorts every line into one of four groups.

Matches on both sides

Same issuer number and date, same amounts, and tax treatments that correspond on the two sides. Nobody needs to read them.

Only on one side

An invoice or a credit note issued and not yet received, or received and not issued: usually timing, sometimes an invoice created by hand outside the connection. The report shows its date, so a line from the last days of the month is read differently from one that is three months old.

Different amount or rate

The same invoice with different totals. When the connection creates the received invoices, a line here points at an invoice someone changed by hand on one side, or one created outside the connection.

Different tax treatment

The same invoice with tax treatments that do not correspond: the sign that a kind of invoice is missing from the rule table, or that someone overrode it.

Your finance team reads only the lines outside the first group, each with its cause already named. Each of those lines points at a rule to add or a manual habit to stop, so the list is also the work for the following month.

When the subsidiary is outside the European Union

Two things change, and the method does not.

The tax treatment changes. Goods leaving Italy for Mexico are not an intra-EU supply: they leave the European Union through customs, and other articles apply to them; services to a business follow the same place-of-supply rule, with different wording on the invoice. The rows of the rule table are different, and your advisers in both countries write them.

The subsidiary’s own invoices follow local rules of their own, and in some countries those rules are strict: our piece on tax invoicing in Latin America sets out what Mexico, Chile, Colombia and Brazil require before an invoice counts. The connection still creates the received invoice from the issued one, and any local document is linked to it rather than replacing it.

And the exchange rate can become the largest cause of difference rather than a rare one. The written rule on which rate, which day and which source matters more here than anywhere else.

Where to start this month

You do not need a project to see where the week goes. These steps use a month you have already closed.

Take a month already closed

Ask both finance teams for the intercompany invoices of the same closed month, from both systems, with number, date, amounts, tax and currency. Put them side by side.

Sort the differences by cause

For each difference, write which of the six causes it comes from. Count them. The cause that comes back most often is where the first rule goes.

Write the exchange-rate rule

If the two companies keep their books in different currencies, write the rate, the day and the source, and ask both finance teams to use it from next month.

Ask your advisers the two questions only they can answer

Which tax treatment applies to each kind of invoice the two companies exchange, and how the price between them is set and documented. The answers are the core of the rule table.

Choose the pair of companies that costs most

If the group has more than two companies, start with the pair whose reconciliation takes longest today. The same method then serves the others, one pair at a time.

How we do it

This is the work of our intercompany invoicing solution. First we look with you at what the group’s companies invoice one another for and how each invoice is recorded today in both. Then we write how an invoice passes from one system to the other: which exchange rate is used and how the taxes of each country are applied, as your finance team already applies them. We connect the systems, test with the invoices of a month already closed and set up the reconciliation report.

You receive an automatic flow and a monthly reconciliation report. The subsidiary no longer re-enters head office’s invoices by hand, nor head office the subsidiary’s. Which rate, which taxes and which prices apply is still decided by your finance team and your advisers, as it is today. The code, the accounts and the documentation are in your name from day one.

If you want to see how it would work in your case, start with a free one-hour video call: tell us how your companies invoice one another today and we will tell you what we would look at first.

The official texts we cite

What we do about it: Intercompany invoicing

All resources