Monaco Invoice Requirements: VAT Checklist and Rules

If you are asking what must be on an invoice in Monaco, the core Monaco invoice requirements are the parties, a continuous chronological invoice number, the issue date, the date of supply when it differs, a clear description of the goods or services, VAT information, and the tax totals. According to Monaco government's invoice obligatory notices guidance, Monaco invoices must include a continuous chronological number, an issue date, the date of supply when different, VAT details, and the wording "VAT not applicable, Article 87 of the Tax Code" for VAT-exempt businesses. Monaco also allows foreign-currency invoices if VAT due is calculated in euros, may require French translation during inspection, and accepts electronic invoices only when the recipient agrees and authenticity and integrity are guaranteed.

Use this Monaco tax invoice checklist as an operational validation tool:

• Confirm the seller and buyer are clearly identified.
• Check that the invoice number is unique and sequential.
• Verify the issue date and the date of supply when it is not the same date.
• Make sure the goods or services are described clearly enough for coding and review.
• Check discounts or price reductions when they affect the taxable amount.
• Check the VAT treatment, the tax amounts, and the totals.
• If the business is VAT-exempt, look for the wording "VAT not applicable, Article 87 of the Tax Code."
• Where the transaction requires it, verify that the relevant intra-Community VAT number is shown.
• If the invoice is in a foreign currency, confirm the VAT due is still calculated in euros.
• If the invoice is in a foreign language, be prepared to support it with a French translation if requested.
• If the invoice is electronic, confirm recipient acceptance and integrity controls.

---

Mandatory Fields and When the Date of Supply Matters

In Monaco, the mandatory invoice fields are a compliance control, not a formatting preference. The Turnover Tax Code framework means an invoice needs to support audit review, VAT treatment, reconciliation, and later document checks by someone who was not involved in the original transaction.

Start with the baseline fields. In practice, that means clear seller and buyer identification, a unique chronological invoice number, the issue date, enough detail about the goods or services to understand what was supplied, the VAT treatment, and the tax totals. Where discounts or price reductions affect the taxable amount, they should also be reflected clearly enough that the reviewer can understand how the final amount was reached.

The date of supply deserves separate attention because it is one of the easiest Monaco requirements to miss. If the delivery date, service completion date, or other tax-relevant supply date is known and differs from the invoice issue date, that separate date should appear on the invoice. For finance teams, this matters because the supply date helps confirm VAT timing, the correct accounting period, and whether the invoice lines up with the underlying commercial event.

This matters most when billing lags behind performance. A supplier may deliver goods on one day and invoice later, finish a service at month end but bill it in the next period, or raise an invoice after an advance payment or staged completion event. In each of those cases, the issue date alone may not tell you enough about the actual tax point.

The practical distinction is simple: some details belong on almost every Monaco invoice, while others become mandatory because of the transaction structure. The baseline fields tell you whether the document is complete. The transaction-specific details, especially the date of supply and any VAT identifier requirements, tell you whether the document is complete for this particular deal.

Why Monaco Uses France-Linked VAT Rules and When Article 87 Applies

Monaco invoice validation can feel unusual because Monaco applies VAT on the same basis and at the same rates as France under the Franco-Monegasque customs union, yet invoices still need Monaco-specific checking. In practice, that means many familiar French VAT mechanics carry over, but reviewers should not assume a French-format invoice is automatically correct for a Monaco transaction.

For AP and bookkeeping teams, the operational question is straightforward: is this a standard VAT-bearing invoice, or is it relying on a different treatment that has to be explained on the document? Reviewers may see Monaco references such as Article 153 of the Turnover Tax Code in the background of invoice formalities, but Article 87 is the rule that matters most when no VAT is being charged.

This is why Monaco Article 87 invoice wording matters so much in practice. If the supplier is relying on a VAT-exempt or non-applicable treatment, the invoice should include the wording "VAT not applicable, Article 87 of the Tax Code" when that is the correct basis. Missing wording, vague wording, or using the Article 87 reference where the transaction does not actually justify it can create avoidable problems during approval, VAT reconciliation, or a later tax review.

It helps to review Monaco VAT invoice requirements in three buckets:

• Standard VAT-bearing invoices: check that the tax base, VAT rate, and VAT amount are presented consistently.
• Article 87 or other non-VAT invoices: check that the non-taxation reason is stated precisely enough to support the treatment.
• VAT-identifier-sensitive invoices: check whether the relevant parties' intra-Community VAT number needs to appear in addition to the normal invoice fields.

That last point matters because some invoices need more than names, addresses, and totals. When the transaction type depends on VAT identification, the reviewer should confirm that the correct intra-Community VAT number is shown and that it aligns with the treatment claimed on the invoice. This is an edge-case check tied to transaction type, not a field to force onto every invoice, so it should be verified against the official Monaco rule whenever it becomes relevant. Teams that already use French controls can adapt them, and how French mandatory invoice mentions overlap with Monaco VAT practice is a useful comparison point. The final check still has to fit the Monaco transaction in front of you.

Foreign Currency, Language, and Electronic Invoice Validity in Monaco

These are not minor formatting details. For AP and bookkeeping teams, foreign currency, invoice language, and electronic format controls are practical validity checks that often decide whether a Monaco invoice can be approved as-is or should be escalated for manual review.

A Monaco invoice may be issued in a foreign currency, but the VAT due still needs to be calculated in euros. That distinction matters because the commercial amount and the tax basis are not the same compliance check. If an invoice is denominated in U.S. dollars, pounds, or another currency, the reviewer still needs a clear euro VAT calculation to confirm the taxable base, the VAT rate applied, and the amount of tax due. In practice, a complete-looking invoice can still be problematic if the tax is shown only in the foreign currency with no reliable euro equivalent for validation.

Language creates a different kind of risk. Cross-border invoices may appear in English or another language, but teams should assume a French translation may be requested during a tax review or inspection. That means Monaco invoice language requirements are not just about whether internal staff can read the document. They also affect whether the business can defend the invoice if authorities ask for evidence in French. A useful control is to flag foreign-language invoices that contain unusual tax wording or exemptions so a translation can be obtained quickly if needed. The same issue appears in how invoice language rules can affect validity in another European market.

Electronic invoices are also valid in Monaco, but not simply because they were sent as a PDF by email. Monaco electronic invoice rules depend on recipient acceptance and on controls that preserve authenticity and integrity. In practical terms, the receiving party must accept electronic invoicing, and the business must be able to show that the invoice came from the stated issuer and was not altered after issue. An electronic signature is one recognizable way to support those authenticity and integrity checks.

For review teams, the checklist is direct: confirm euro VAT calculation when the invoice currency is foreign, be ready to support foreign-language invoices with a French translation, and treat electronic invoices as valid only when acceptance and document integrity can be demonstrated.

A Monaco Invoice Review Workflow and the Mistakes Teams Should Catch

Once the rules are clear, the next step is turning them into a repeatable review order. A workable Monaco invoice check is easiest to run the same way every time: document basics first, VAT treatment second, timing third, then currency, language, and electronic-format controls.

1. Confirm the invoice is complete at a document level.

Check that the supplier and customer are clearly identified, the invoice has a unique number, the issue date is present, and the goods or services are described precisely enough for AP or bookkeeping review. If any of those basics are missing, hold the invoice before posting.

2. Validate the VAT path.

Decide whether the invoice is charging VAT under the normal Monaco and France-linked rules or relying on a special treatment such as Article 87. If VAT is not charged where Article 87 is being used, the required wording should appear on the invoice.

3. Check whether the date of supply needs to be shown separately.

If the tax point differs from the issue date, or the transaction structure makes the supply date relevant, confirm that the invoice states it.

4. Review currency handling.

If the invoice is issued in a foreign currency, verify that the VAT amount is also shown in euros where required for VAT reporting. An invoice that gives all taxable values and VAT only in dollars, pounds, or another non-euro currency should be held until the euro VAT treatment is clear.

5. Assess language and supportability.

A foreign-language invoice is not automatically invalid, but the team still has to be able to validate it. If the language prevents the reviewer from confirming the supplier, goods or services, VAT basis, or Article 87 wording, request a translation or supporting explanation before final approval.

6. Verify electronic invoice acceptance and controls.

Do not treat every emailed PDF as automatically compliant just because it was sent electronically. The real check is whether the recipient accepts electronic invoicing and whether the business can demonstrate authenticity of origin and integrity of content. If those controls are not documented, ask for the supporting process or audit trail rather than assuming the format alone is enough.

A simple decision rule helps reduce rework:

Block posting

• Missing core invoice fields such as invoice number, issue date, supplier identity, customer identity, or usable line-item detail
• VAT treatment cannot be determined from the document
• Article 87 appears relevant but the required wording is missing
• VAT is shown only in foreign currency and the euro VAT amount needed for reporting is absent
• The invoice is unreadable or incomplete as a record

Escalate for clarification or evidence

• The date of supply may matter, but the invoice does not clearly show it
• The invoice is in a language the review team cannot confidently validate
• The tax treatment may be correct, but supporting wording or references are too vague
• The invoice was delivered as a PDF by email, but the team has not confirmed recipient acceptance or integrity controls for electronic invoicing

For teams building a repeatable European process, another practical VAT invoice checklist for a European jurisdiction can help benchmark how neighboring VAT documentation rules are turned into AP review steps.

Practical next steps for maintaining Monaco invoice controls:

• Add a Monaco-specific exception box to your intake checklist for Article 87 wording, date of supply, euro VAT display, language support, and electronic invoice evidence.
• Separate your workflow into hard stops and escalation items so reviewers know what blocks posting versus what needs tax or controller review.
• Sample rejected and approved Monaco invoices each month to see which error types recur.
• Update reviewer guidance whenever tax advisors, auditors, or local finance teams identify new wording or documentation issues.