Monaco EC Sales List Guide: DES Rules and Deadline

Monaco DES guide covering in-scope services, France exclusion, invoice-date deadlines, VAT number setup, and e-DES filing steps.

Published
Updated
Reading Time
11 min
Topics:
Tax & ComplianceEUFranceMonacoDES filingEC Sales Listreverse-charge services

The Monaco EC Sales List, or DES, applies when a Monaco business supplies reverse-charge services to an EU customer established outside France. You must file it within 10 working days of the month after invoicing, and the clock starts from the invoice date, not the payment date. Even VAT-exempt businesses may still need an intra-community VAT number before they can register for e-DES and file online. Incoming services purchased by Monaco businesses are not reported through DES.

In plain English, the Monaco EC Sales List is not a report of every foreign invoice. It is a filing for qualifying outbound service invoices. According to the Monaco government's EC Sales List procedure, as of 1 January 2010, Monaco businesses that provide reverse-charge services to EU customers other than France must submit a DES within ten working days after the month following invoicing, and the obligation is triggered by invoice creation rather than payment.

This guide is for you if you issue service invoices to EU customers, build monthly compliance controls, or advise clients on whether a workflow creates a filing obligation. The rest of the article follows the same sequence finance teams use in practice: classify the invoice, apply the France carve-out, use the invoice date to control the deadline, and confirm the VAT number and e-DES setup before filing.

Which Service Invoices Actually Create a Monaco DES Obligation

A Monaco DES obligation starts only when an outbound service invoice falls within the reverse-charge rules for a customer in an eligible EU Member State. A Monaco EC Sales List for services is not a list of all foreign invoices. It is a narrower filing for Monaco reverse-charge services to EU customers.

Use this working test before you add any invoice to your DES workflow:

  1. You issued a service invoice. The transaction must be a sale of services by your Monaco business, not goods and not an incoming supplier invoice.
  2. Your customer is established in an EU Member State other than France. The customer has to be in the EU for this reporting logic to matter, and France sits outside this Monaco DES perimeter.
  3. The service is covered by the reverse charge mechanism. Under Article 11 of the Turnover Tax Code, the practical question is whether the customer accounts for the tax in its Member State under reverse charge rather than you charging it in Monaco.
  4. The invoice has been drawn up. Once the invoice exists, it becomes a live compliance item for DES review.

If one of those conditions is missing, the invoice should not go onto the Monaco EC Sales List for services.

One in-scope example is a Monaco management consultancy invoicing a VAT-registered company in Germany for advisory services. It is a service invoice, the customer is in an EU Member State, the transaction falls under reverse-charge treatment, and the invoice has been issued. That invoice belongs in the Monaco DES review process.

A similar-looking invoice can still be out of scope. Suppose a Monaco business invoices a private customer in Spain for design work. It is still cross-border and still a service, but a key condition is missing: this is not the usual B2B reverse-charge setup. Because the reverse-charge condition is not met, that invoice does not belong on the DES.

That distinction matters if your team handles a mixed batch of domestic work, non-EU work, exempt items, and B2B EU services. A loose "foreign invoice = DES" rule will create errors. You need an invoice-by-invoice classification step that isolates only Monaco service invoices to EU customers that actually fall under the reverse charge mechanism. If you also review cross-border service invoicing in other jurisdictions, Malta's reverse-charge rules for foreign service invoices show how quickly that logic changes from one country to another.

Why France Is Excluded From Monaco DES Reporting

The rule that confuses most readers in any Monaco DES guide is this: Monaco DES applies to customers established in EU Member States other than France. France is not just another EU destination that happens to be nearby. For Monaco filing purposes, it is an explicit carve-out, and your invoice review controls should treat it that way.

That is why generic EC Sales List guidance can mislead Monaco businesses. A broad EU VAT article may tell you that cross-border B2B services to EU customers belong on an EC Sales List. A Monaco business cannot use that rule without adjustment. Under Monaco's own DES framework, a service invoice to Germany, Italy, Spain, or another qualifying EU country may be reportable, but a comparable invoice to a customer in France is not reported through Monaco DES.

The first compliance question should therefore not be only, "Is the customer in the EU?" Ask instead, "Is the customer in an EU country other than France?" If the customer is in France, stop the Monaco DES workflow there. If the customer is in another EU Member State, continue the DES review. That single country check prevents a large share of filing mistakes.

Build the France exclusion for Monaco DES reporting directly into your month-end or invoice-by-invoice checklist:

  • Customer established in France: no Monaco DES filing for that invoice
  • Customer established in another EU Member State: continue the DES eligibility review
  • Customer outside the EU: outside Monaco DES scope on that basis alone

Do not copy a wider EU VAT workflow that ignores Monaco's special rule. That is how teams end up over-reporting French invoices or creating a false late-filing panic for items that never belonged on a DES in the first place. For Monaco purposes, France is the stop sign in the DES workflow. If you need the French invoice-treatment side of the issue, review France's reverse-charge invoice rules for autoliquidation separately.

Why Invoice Date, Not Payment Date, Controls the Deadline

Once you know the invoice is in scope and France is not part of the filing, the next control is timing. For the Monaco DES deadline, the clock starts when you issue the invoice, not when the customer pays it. If a service invoice is in scope for DES, you report it within 10 working days of the month following invoicing. In practice, that means an invoice dated 31 March belongs to your March DES workflow and must be filed within the first 10 working days of April, even if the customer does not pay until May.

That invoice-date trigger matters at month-end. A common mistake is to wait for the bank receipt and treat payment as the filing event. It is not. In the invoice date vs payment date Monaco DES question, payment timing affects collections, not the DES reporting month. If your team waits for cash before reviewing invoices, you increase the risk of filing late even when the invoice itself was raised correctly.

A workable control is to review issued invoices, not cash movements, as part of your close. For each potentially in-scope service invoice, capture and check:

  • Invoice date so the transaction falls into the correct filing month
  • Customer country to confirm the customer is in an EU Member State other than France
  • Service nature to confirm the supply is the type that belongs in the DES workflow
  • VAT status to confirm the reverse-charge logic and customer identification have been assessed
  • DES inclusion flag so the invoice is clearly marked for filing, follow-up, or exclusion

This is why finance teams often separate DES review from cash application. Your receivables report tells you who has paid. Your DES control should tell you which invoices were issued in the month and whether each one created a filing obligation. You can see the same invoice-driven discipline, with a different reporting rhythm, in how Cyprus handles monthly VIES reporting for intra-EU services.

The Filing Setup: Intra-Community VAT Number Before e-DES

After scope and timing are clear, the remaining question is whether your business is set up to file. The Monaco sequence is fixed: confirm the invoice is in scope, obtain an intra-community VAT number if you do not already have one, activate e-DES separately, then submit the DES online using the customer and invoice details you already checked during review.

A point that trips up first-time filers is VAT-exempt status. Being exempt from VAT in your day-to-day Monaco activity does not automatically remove cross-border identification requirements. If your business supplies reportable intra-community services, Monaco may still require an intra-community VAT number so the transaction can be identified properly for DES purposes. VAT exemption and cross-border identification are not the same thing.

That is why your Monaco intra-community VAT number has to be in place before filing. If the business does not yet have that number, fix that gap before you start e-DES activation. Otherwise the process stalls before the first declaration is prepared.

After that, complete Monaco e-DES registration. e-DES is the filing channel used by the Department of Tax Services for DES submissions. Registration for e-DES is a separate step from obtaining the VAT number, so do not assume one application covers both. The practical sequence is:

  1. Confirm the invoice is an in-scope outbound service invoice to an EU customer outside France.
  2. Check whether the business already has a valid intra-community VAT number.
  3. If not, apply for that number with the Department of Tax Services.
  4. Register for e-DES.
  5. Once access is active, file the DES online through the Department of Tax Services workflow using the invoice date, invoice reference, customer country, and VAT details already gathered during review.

Before your first filing, have this ready:

  • Your business identification details and the valid intra-community VAT number
  • Active e-DES access, including the credentials or activation items the Department of Tax Services has issued
  • The customer's VAT number and country details
  • The relevant service invoice details, especially the invoice date and invoice reference
  • Internal confirmation that the invoice is an outbound service transaction, not an incoming purchase, and that France is not the customer's country

What Does Not Belong on a Monaco DES, and the Errors That Cause Late Filing

Once classification, timing, and setup are in place, most Monaco DES problems come from preventable review errors. The final check is mostly a filter: keep reportable outbound services in the filing, and keep everything else out.

Start by excluding incoming services. If your Monaco business buys services from a supplier, that purchase is not reported through DES. It belongs in the turnover tax return or purchase-side reverse-charge workflow. This article is also limited to services, so do not use it as a guide for goods reporting.

The most common Monaco DES errors are predictable:

  • Including invoices issued to customers in France
  • Waiting for payment instead of using the invoice date
  • Assuming a VAT-exempt business never needs an intra-community VAT number
  • Adding incoming services purchased by your business into the DES
  • Treating this Monaco DES guide as if it also covers goods

Use this monthly decision checklist before submission:

  1. Is this an outbound service invoice? If it is a purchase invoice, leave it out of DES and send it through the purchase-side turnover tax or reverse-charge review.
  2. Is the customer established in an EU country other than France? If the customer is in France, stop. Do not include it in Monaco DES filing.
  3. Was there an invoice issued this month? Use the invoice date as the trigger for your compliance calendar. Do not hold the item back just because payment has not arrived yet.
  4. Do you have the setup in place? Confirm the customer VAT number details are available and that your business has completed the intra-community VAT number and e-DES setup needed to file.
  5. Is the transaction a service, not goods? If it is goods, move it out of this workflow and into the correct reporting process.
  6. Are you wrongly relying on VAT-exempt status? VAT exemption does not automatically remove setup obligations for reportable cross-border service activity.

If those checks line up, your process is usually on solid ground. For every period, the same four Monaco DES issues must match the invoice record: scope, France exclusion, invoice-date timing, and setup prerequisites.

About the author

DH

David Harding

Founder, Invoice Data Extraction

David Harding is the founder of Invoice Data Extraction and a software developer with experience building finance-related systems. He oversees the product and the site's editorial process, with a focus on practical invoice workflows, document automation, and software-specific processing guidance.

Editorial process

This page is reviewed as part of Invoice Data Extraction's editorial process.

If this page discusses tax, legal, or regulatory requirements, treat it as general information only and confirm current requirements with official guidance before acting. The updated date shown above is the latest editorial review date for this page.

Continue Reading

Invoice Data Extraction

Extract data from invoices and financial documents to structured spreadsheets. 50 free pages every month — no credit card required.

Try It Free