Intra-Community Acquisition VAT from Supplier Invoices

When a VAT-registered business receives a supplier invoice for goods from a vendor in another EU member state with no VAT charged, the buyer normally self-accounts for VAT under the intra-community acquisition reverse charge. The posting is not "no VAT"; it is output VAT at the buyer's domestic rate, plus input VAT in the same period where the buyer has full recovery. In a fully taxable business, those two VAT lines net to zero, but both still need to appear in the VAT records and on the return.

That is the core treatment for intra-community acquisition VAT from supplier invoices where the invoice is for goods. EU service invoices use a related buyer-side reverse-charge workflow under B2B place-of-supply rules, but they are not goods acquisitions and they do not create Intrastat arrivals. Before posting either type, AP needs evidence that the invoice really belongs in the reverse-charge workflow: the supplier's EU VAT number, the buyer's VAT number, reverse-charge wording on the invoice, the taxable amount, the invoice date, and a valid VIES check. The return mapping is national. In Ireland, for example, the self-accounted VAT appears in VAT3 Box T1, the matching input credit appears in Box T2 where deductible, and the value of goods received from other EU countries appears in Box E2.

The practical AP sequence is:

1. Read the face of the invoice for a zero VAT line and reverse-charge wording.
2. Confirm both VAT numbers are present and belong to VAT-registered businesses in different EU member states.
3. Validate the supplier's VAT number in VIES and keep the evidence.
4. Set the tax point from the supplier's invoice date or the statutory fallback date, not just the date AP received the PDF.
5. Post the purchase, supplier liability, output VAT, and recoverable input VAT.
6. Map the acquisition to the correct VAT-return boxes for the buyer's member state.
7. Decide whether the invoice is for goods, services, or a mix, because goods can also feed Intrastat arrivals reporting.

That sequence matters because an EU supplier invoice booked in AP with no VAT line can be valid, wrong, incomplete, or simply waiting for evidence. The same-looking invoice can be a clean intra-community acquisition, a supplier master-data problem, a missing buyer-VAT-number exception, or an import-VAT case outside the EU acquisition rules. Treating every zero-VAT EU invoice as automatically correct is how small AP shortcuts become filing-period errors.

Read the reverse-charge wording and VAT numbers on the incoming invoice

Start with the invoice face before touching the ledger. A valid intra-community acquisition invoice normally gives AP four things to read directly from the document: no VAT charged by the supplier, reverse-charge wording, the supplier's VAT number with its member-state prefix, and the buyer's own VAT number. If one of those is missing, the invoice is not automatically wrong, but it should leave the straight-through posting path.

Article 226 of the EU VAT Directive requires the reverse-charge reference where the customer is liable for VAT. In practice, AP teams do not receive one neat English phrase. They receive supplier invoices in the supplier's language, so the marker often looks like this:

Supplier language	Common reverse-charge marker	AP reading
English	Reverse charge	Customer self-accounts for VAT
German	Steuerschuldnerschaft des Leistungsempfängers	VAT liability shifts to the recipient
Italian	Inversione contabile	Buyer accounts for VAT
French	Autoliquidation	Customer self-assessment
Spanish	Inversión del sujeto pasivo	Reverse charge to the taxable recipient
Dutch	Btw verlegd	VAT shifted to the customer
Danish	Omvendt betalingspligt	Reverse payment liability
Portuguese	Autoliquidação	Self-assessment by the buyer
Polish	Odwrotne obciążenie	Reverse charge
Swedish	Omvänd betalningsskyldighet	Reverse payment liability

The wording is a diagnostic marker, not proof that the treatment is valid. The supplier may have printed the right phrase while using an expired VAT number, missing the buyer's VAT number, or applying B2B logic to a customer record that was never validated. AP still needs the VIES check and the tax-point decision before posting.

The buyer's VAT number is a common exception. If the invoice has a reverse-charge phrase and a zero VAT line but does not print the buyer's VAT number, hold the invoice for correction or tax review rather than quietly posting it. The supplier may need to reissue the document so the buyer has a defensible audit trail.

Supplier-side invoice guides are useful only as a checklist for what should have appeared on the incoming document. For example, what a French supplier's autoliquidation invoice should contain helps AP recognize the expected French wording, while Cyprus reverse-charge VAT and Article 11 treatment is relevant when the supplier's country rule explains why the invoice arrived without VAT. The buyer's job is still separate: validate, post, and report the acquisition in the buyer's own member state.

Validate the supplier in VIES before accepting the zero-rated invoice

VIES is the buyer's gate between "this invoice appears to be reverse charge" and "AP can support the reverse-charge posting." Use the supplier's VAT number and member-state prefix from the invoice, check it in the EU VIES portal at vies.europa.eu, and keep evidence of the result with the invoice support. A valid result does not complete the accounting treatment by itself, but it supports the supplier's B2B zero-rating and lets AP continue to the tax-point and posting steps.

For a valid response, retain enough evidence for audit: supplier name if returned, VAT number, member state, validation date, validation time, and the user or system that ran the check. If the buyer's own VAT number is part of the validation input, retain that too. The evidence should sit with the invoice image, approval history, or tax coding support, not in a separate inbox that disappears before audit.

For an invalid response, do not simply post the invoice because the PDF says "Reverse charge." Put the invoice on hold, contact the supplier, and ask for corrected VAT details or a corrected invoice. If the supplier cannot produce a valid VAT number, AP should escalate to the tax owner before accepting the zero-VAT treatment. Depending on the facts, the supplier may need to issue a standard-rated invoice in its own country instead of treating the sale as an exempt intra-community supply.

The awkward case is timing. A supplier number can be valid on the invoice date and invalid by the payment date, or invalid in VIES because of a data lag or member-state update. The defensible control is to validate when the invoice is processed, keep the timestamped result, and follow local tax guidance for historical status changes rather than silently recoding the invoice because a later lookup says something different.

VIES also appears on the supplier side of the transaction, but the buyer's use is narrower. The supplier uses customer VAT data to support its own reporting, including recapitulative statements in many member states; how VIES recapitulative reporting works from the supplier side is a useful contrast. In AP, the point is simpler: prove that the incoming invoice's zero VAT treatment belongs in the reverse-charge workflow before the journal entry is posted.

Set the tax point from the invoice date, not only the AP receipt date

For intra-community acquisitions of goods, the VAT period is driven by the chargeability rule, not by the date the PDF happens to enter the AP queue. Under the EU timing mechanic, VAT becomes chargeable when the supplier issues the invoice, or by the 15th day of the month following the acquisition if no invoice has been issued by then. Services use the B2B reverse-charge place-of-supply framework rather than the goods-acquisition rule, so AP should not treat every foreign EU supplier invoice as the same timing problem.

Take the common month-end case. A German supplier ships goods to an Irish buyer and issues an invoice dated 28 June. AP receives the PDF on 12 July because it sat in a shared mailbox or the approver was away. For VAT, the invoice date can put the acquisition in the June period, or the return period that includes June, even though AP first touched the document in July. If the team posts every reverse-charge invoice in the receipt month, it may put the output VAT and input VAT in the wrong return.

The practical control is to preserve the dates that explain the decision:

• supplier invoice date
• AP receipt date
• posting date
• goods receipt or service completion date, where available
• exchange-rate date used for the VAT amount
• reason for any period override

That evidence matters most when the accounting and tax periods diverge. The P&L accrual might be acceptable in July for internal reporting, while the VAT return needs the acquisition in June. In that case the posting support should show why tax coding followed the invoice-date rule rather than the AP receipt date.

Late-arriving invoices are also where automation and accounting controls need to agree. If the extraction output captures only invoice total and supplier name, the tax reviewer still has to reopen the PDF for the invoice date, supplier country, VAT marker, and delivery context. For intra-community acquisition tax point invoice date decisions, those fields are the difference between a clean period decision and a manual exception.

Post the reverse-charge journal entry from the foreign EU invoice

The reverse charge journal entry from a foreign EU invoice has two layers: the commercial invoice posting and the VAT self-accounting posting. Keep them separate in the working paper even if the accounting system generates the VAT lines automatically.

Assume a supplier invoice for EUR 1,000 of goods, no VAT charged, and a buyer domestic VAT rate of 20 percent. In a fully taxable business, the entry is:

Line	Debit	Credit
Purchases or inventory	EUR 1,000
Supplier liability		EUR 1,000
Input VAT recoverable	EUR 200
Output VAT payable		EUR 200

The first two lines record the supplier invoice. The second two lines are the reverse charge VAT entry from the EU supplier invoice: the buyer charges itself VAT and, because it has full input recovery, claims the same amount in the same period. The VAT account nets to zero economically, but the return still needs both sides.

Partial exemption changes the recovery side, not the output VAT liability. If the same buyer can recover only 60 percent of input VAT, the output VAT remains EUR 200. The recoverable input VAT is EUR 120, and the blocked EUR 80 becomes irrecoverable VAT, either posted to a separate tax cost account or added to the purchase cost according to the buyer's accounting policy.

Line	Debit	Credit
Purchases or inventory	EUR 1,000
Supplier liability		EUR 1,000
Input VAT recoverable	EUR 120
Irrecoverable VAT cost	EUR 80
Output VAT payable		EUR 200

For invoices in a currency different from the buyer's VAT-reporting currency, convert the taxable amount using the exchange-rate method required in the buyer's member state. The support should show the original invoice currency, the converted taxable amount, the rate source, and the date used. If the accounting system uses one rate for the supplier liability and another for VAT reporting, the reconciliation needs to show both rather than bury the difference in a clearing account.

Map the acquisition to the correct VAT-return boxes

The ledger entry is only half the compliance work. The acquisition also needs to land in the buyer's VAT return where that member state expects intra-community acquisitions, with output VAT and deductible input VAT shown according to the local return design.

Ireland is a clean example of the self-accounting pattern. Revenue's self-accounting for VAT guidance on intra-community acquisitions states that the purchaser accounts for VAT on a reverse-charge basis in Box T1 of the Irish VAT3 return and, where entitled to an input credit, reclaims the same amount in Box T2 within the same return. The same Revenue example also includes the value of goods received from other EU countries in Box E2.

For a pan-EU AP team, keep a return-mapping table in the tax-coding procedure. The labels and form layouts change, so treat this as a coding reference to confirm against the current local return instructions:

Buyer member state	Where the acquisition usually appears	AP coding note
Ireland	VAT3 Boxes T1, T2, and E2	T1 records the self-accounted output VAT; T2 records deductible input VAT where recovery is allowed; E2 records the value of goods received from other EU countries
France	CA3 Box B2 for acquisitions intracommunautaires	Use the acquisition base and related VAT fields required by the French return
Germany	Umsatzsteuer-Voranmeldung lines for innergemeinschaftliche Erwerbe	Map by tax rate and acquisition category where the form requires it
Netherlands	OB-aangifte Box 4b and Box 5b	Box 4b captures EU purchases; Box 5b captures deductible input tax
Italy	Acquisti intracomunitari rows in the periodic VAT process and dichiarazione IVA	The domestic integration or self-invoice workflow can matter before return reporting
Malta	VAT return lines for intra-community acquisitions	Confirm the local line for the period and rate used
Luxembourg	VAT return lines for intra-community acquisitions	Confirm the local line and deductible input VAT treatment

The table is meant to stop AP from treating "reverse charge" as one universal tax code. The journal pattern is conceptually similar across fully taxable buyers, but the return box is not. A company filing in Ireland, France, and the Netherlands can receive the same kind of German supplier invoice and still need three different return mappings.

Italy deserves special care because the buyer-side foreign-supplier workflow can involve domestic e-invoicing and document-type requirements before the VAT return is completed. The Italian-language guide to Italian autofattura TD17/TD18/TD19 for foreign-supplier invoices covers that jurisdiction-specific workflow, while this guide stays with the multi-country AP coding view.

---

Separate goods, services, Intrastat, and AP exceptions

Goods and services can arrive in the same AP queue, but they do not create the same overlay. Goods bought from a supplier in another EU member state are the classic intra-community acquisition: destination-state VAT treatment, reverse-charge self-accounting by the buyer, and possible Intrastat arrivals reporting once the buyer crosses the national arrivals threshold. Services follow the B2B place-of-supply rule and the reverse charge can still apply, but services do not create Intrastat arrivals.

That distinction keeps two workstreams from being merged by accident. VAT answers who accounts for tax and in which return. Intrastat answers statistical trade questions about movements of goods. Country-of-origin checks answer a different customs and supply-chain question again. The same supplier invoice may feed all three datasets, which is why AP teams benefit from extracting Intrastat arrivals data from the same supplier invoices and reconciling country of origin from the same supplier invoices without confusing those outputs with the VAT entry.

Do not use this workflow for UK imports. Since Brexit, a UK import purchase is not an intra-community acquisition, and UK postponed VAT accounting for post-Brexit imports runs on import evidence and postponed import VAT statements rather than an EU supplier's reverse-charge invoice.

The recurring AP exceptions are narrow enough to standardize:

• Supplier charged VAT anyway: Hold for tax review. The supplier may have treated the buyer as non-business, used the wrong customer VAT record, or applied a domestic rule. Do not reclaim foreign VAT as if it were domestic input VAT.
• Buyer VAT number is missing: Ask for a corrected invoice or document the tax owner's approval before posting.
• Supplier VAT number changes status: Keep timestamped VIES evidence from the processing date and escalate if later checks conflict with the invoice-date evidence.
• Self-billed invoice: Confirm who issued the document and whether the self-billing agreement supports the VAT treatment.
• Triangulation: Do not force a three-party chain into the standard acquisition posting. Triangulation has its own evidence and reporting requirements.
• Mixed goods and services: Split the coding where the invoice contains both, because only the goods lines can create Intrastat arrivals.

This is also the point where volume becomes the operational problem. An AP team can make the tax decision invoice by invoice, but it still needs the same fields every time: supplier VAT number, buyer VAT number, reverse-charge wording, taxable amount, currency, invoice date, supplier country, and line-level goods or services indicators. With automated supplier-invoice data extraction, a finance team can upload supplier invoices, prompt for those fields, and download structured Excel, CSV, or JSON before the bookkeeper applies the VAT treatment. Invoice Data Extraction does not decide the law for the buyer; it removes the rekeying step that slows down the control.