San Marino E-Invoicing Requirements Explained

If you need the short operational answer, San Marino e-invoicing requirements are not a blanket domestic mandate. San Marino does not currently require all local invoices between San Marino businesses to move through an electronic invoicing channel. In practice, the topic mainly concerns Italy-linked electronic invoicing flows, plus a set of exceptions where customs, paper handling, or supporting documents still matter.

That is why generic country summaries often send finance teams in the wrong direction. The first question is usually not "Do I issue XML?" It is "What kind of transaction is this, and which route applies?" For a San Marino operator, the answer can change depending on whether you are dealing with goods or services, whether the counterparty is in Italy, and whether the transaction falls into an import, export, or internal relationship scenario. A useful guide to San Marino electronic invoicing requirements has to start with classification, not with file format.

This distinction is explicit in San Marino's official e-invoicing FAQ, which says e-invoicing is not currently provided for internal relationships among San Marino operators. That single point changes how you should read every high-level summary or translated San Marino electronic invoice FAQ summary you find online. If your transaction is purely internal inside San Marino, you should not assume it belongs in the same electronic route used for Italy-linked invoicing.

Use this quick scope check before you change any process:

• Domestic San Marino transactions: there is no blanket domestic e-invoicing mandate.
• San Marino-Italy goods flows: this is the core SDI-linked use case.
• Services: treat them separately from goods instead of assuming the same route applies.
• EU and extra-EU imports or exports: the prior customs procedure still governs these scenarios.

The rest of this guide focuses on the decision points that actually matter in daily operations: when Italy-linked goods flows go through the SDI structure, how service scenarios differ, where imports and exports stay tied to customs procedures, which routing and code details affect delivery, what supporting documents still matter after the XML stage, and how to handle corrections such as rejections and credit notes.

---

How the Italy-Linked SDI Route Works

San Marino's official e-invoicing material is narrower than a typical domestic mandate guide. It is mainly framed around cross-border trade with Italy, especially the indirect-tax handling of goods. For transactions that fall inside that channel, the route is best understood as a shared XML electronic invoice path: the invoice is created in XML, moves through Italy's Sistema di Interscambio (SDI), and is then handled on the San Marino side through the tax-administration workflow rather than passing straight from one private company mailbox to another. If you already know Italy's FatturaPA and SDI workflow, the key difference is that San Marino SDI invoicing adds a San Marino tax-office layer to transport and presentation.

That is where the Ufficio Tributario becomes operationally important. It is part of the receiving and presentation chain, not just the body that published the rules. For purchases from Italian suppliers, the supplier does not use a company-specific SDI mailbox for each San Marino customer. The file is routed into the San Marino-side channel tied to the Ufficio Tributario, which is why the model feels more centralized than a standard domestic Italian setup. One useful technical detail is that the XML signature can be optional, so the working mental model is simply this: XML electronic invoice, SDI as the transport layer, and the Ufficio Tributario as the San Marino control point around receipt and presentation.

Where Goods, Services, Imports, and Exports Diverge

The easiest mistake is to assume that every invoice connected to San Marino follows one electronic workflow. It does not. The core e-invoicing use case is the exchange of goods between San Marino and Italy, using the Italy-linked SDI route and the controls that sit around it. Once you move outside that goods corridor, the rules split quickly.

A practical way to read the San Marino goods vs services invoice rules is to sort the transaction by what is moving, where it is moving, and whether customs procedures still apply. Domestic San Marino transactions are not automatically pulled into the same SDI logic. Goods moving between San Marino and Italy are the main area where finance teams need to think about XML transmission, SDI, and linked transport evidence. Services are different again. Official guidance does not treat them as a blanket extension of the goods framework, so you should not classify a service invoice by copying the rule you use for merchandise.

Here is the working classification most teams need:

• Goods sold from San Marino to Italy: This is a core electronic invoicing scenario. Classify it as a San Marino-Italy goods flow, route it through the SDI process where required, and make sure the invoice aligns with the underlying goods movement documentation.
• Goods imported into San Marino from Italy: Treat this as an Italy-San Marino goods flow, again centered on the electronic framework for goods, while also checking the import-side documentary path and tax handling. If your team needs the non-XML side of that process, this is where San Marino monofase and import-document handling becomes relevant.
• Services between operators: Do not assume the same rule set applies. Internal service relationships among San Marino operators are not currently under e-invoicing. Services supplied by an Italian operator to a San Marino operator may be issued electronically on an optional basis under Italian rules, but that is not the same as San Marino imposing a general domestic e-invoicing mandate for services.
• Purely domestic San Marino transactions: These should not be forced into the San Marino-Italy goods workflow just because both parties are businesses. Start by confirming whether the transaction is domestic and whether any other local documentation rules apply, rather than defaulting to SDI.

Imports and exports beyond the Italy goods channel also need separate treatment. Official FAQ guidance indicates that EU and extra-EU imports and exports of goods otherwise remain under the previous customs procedure. That matters because many teams overgeneralize from the Italy corridor and assume every cross-border invoice becomes an SDI file. For broader EU or extra-EU trade, that assumption can send the invoice into the wrong control path.

One detail often missed in San Marino import invoice procedures from Italy is that goods movement evidence still matters after the XML is created. If goods are moving to Italy, the DDT remains part of the control chain. The electronic invoice is not a substitute for transport documentation. In practice, missing or inconsistent DDT references can cause the invoice to fail required controls, not just weaken the audit trail, which is why it helps to understand the wider logic behind Italian DDT and deferred invoicing rules.

If your AP or compliance team needs a fast classification test, use this:

1. Is this goods or services? If services, stop and verify the service-specific rule before assuming SDI.
2. Is the counterparty in Italy? If yes, goods flows are much more likely to fall into the e-invoicing framework.
3. Is this broader EU or extra-EU import/export trade? If yes, check whether the prior customs procedure still governs the transaction.
4. Is there a DDT or import document that must tie back to the invoice? If yes, make that reference check part of invoice validation, not an afterthought.

That scenario-by-scenario split is what keeps mixed San Marino and Italy invoice traffic from being misclassified.

---

The Handling Details That Still Matter After XML

The operational burden in San Marino fatturazione elettronica does not end once the XML exists. In practice, finance teams still have to manage routing, presentation deadlines, official communications, and document preservation, because those handling steps determine whether the invoice process actually works.

When a San Marino operator buys goods from an Italian supplier, the supplier needs the correct San Marino SDI code destinatario so the invoice is routed through the right receiving path. The important point is that this code destinatario is not a private code assigned to each individual operator. It is shared because it identifies the Ufficio Tributario channel used for receipt, not a unique mailbox for one company. Operationally, your team needs a repeatable step for giving that code to Italian suppliers and confirming they use it correctly on outbound invoices.

You also need to calendar the ordinary presentation deadline for passive electronic invoices linked to imports from Italy. The standard timing is 60 days from the document date. Treat that as a live AP deadline, not a footnote in a tax memo. If the invoice date starts the clock, your process should capture that date immediately, assign ownership, and flag the file well before day 60 so presentation does not depend on someone noticing it late.

Another detail that gets missed is where follow-up messages go. Communications from the Ufficio Tributario about electronic invoices are sent to the legally required digital domicile email address. That means the compliance risk is not just technical transmission failure. It is also mailbox governance. Your team should know exactly which address is registered, who monitors it every business day, and how messages are escalated when an action is needed.

Finally, electronic transmission does not remove the preservation burden. During the transitional phase described in the official FAQ, Sammarinese operators still have to retain the received and uploaded documents themselves, or have a delegate do it on their behalf. In practical terms, that means your archive should cover more than the invoice XML alone. Keep the received file, the uploaded file where relevant, and the supporting records that prove what was sent, received, and matched, so the trail remains usable later for tax checks, reconciliation, and internal review.

Credit Notes, Rejections, and Linked-Document Fixes

If an electronic invoice is rejected, the correction rule matters because the same invoice number and date can still be reused. San Marino's FAQ says a corrected invoice can be retransmitted with the same number and date. When the rejection comes from SDI, the retransmission window is 5 days from the rejection notice. When the rejection comes from the Ufficio Tributario, the same number and date can still be reused, but the local issuance deadline still applies.

Credit notes also need a clear link back to the original invoice. In San Marino, the reference invoice is mandatory on a credit note, and if an incoming Italian note of credit does not already contain the linked-invoice field, the Sammarinese operator has to complete it in the integrative file before presentation. That is what keeps the tax position, the adjustment, and the audit trail tied to the same base document.

For goods already imported into San Marino, the official guidance distinguishes three broad situations:

• The credit note is presented together with the original invoice. In practice, that gives the tax office the cleanest view of the transaction and its adjustment as one linked file set.
• The credit note arrives before import tax on the original invoice has been paid. The adjustment reaches the file before the tax position has fully settled, so timing and linkage become the critical controls.
• The credit note arrives after that tax has already been paid. The adjustment becomes a post-settlement correction, which means the follow-up trail matters just as much as the note itself.

The practical point is that a note of credit is never just a free-standing reversal. You need to preserve the original invoice link, present the note in the right timing window, and understand whether the adjustment changes the tax position before or after settlement.

The same linked-document mindset applies beyond pure credit notes. If goods are worked on, returned, or tied to multiple related invoices, the documents have to be connected clearly rather than processed in isolation. For a finance team, that means correction handling is really a document-chain problem, not just a bookkeeping problem.

---

A Working Checklist for Finance Teams

If you want a weekly operating checklist rather than another summary, keep it to the controls that are specific to this regime:

1. Classify the invoice first. Decide whether you are looking at a San Marino-Italy goods flow, a service scenario, a domestic San Marino transaction, or an import/export case that stays on the prior customs route.
2. Confirm the receiving channel. For incoming Italian goods invoices, make sure the supplier is using the shared code destinatario tied to the Ufficio Tributario rather than treating the invoice like an ordinary company-to-company SDI delivery.
3. Track the timing rule that actually matters. If the invoice is an electronic import invoice from Italy, the ordinary presentation term is 60 days from the document date. If it is a correction, track the rejection or credit-note timing as part of the same file.
4. Keep one auditable record set. Store the XML, any DDT references, customs or monofase evidence, and any linked credit note or integrative file together so the route, tax handling, and adjustment trail stay visible.
5. Monitor the follow-up mailbox. Because Ufficio Tributario communications go to the legally required digital domicile, that mailbox needs an owner, a review cadence, and an escalation path.

If you later formalize this into an invoice data extraction workflow, make sure those controls sit in the same process map as the bookkeeping handoff. That is what turns San Marino e-invoicing from a legal reference topic into something an AP team can actually run every week.