San Marino Monofase Tax Guide: Invoices and Imports

This San Marino monofase tax guide starts with the key point: San Marino does not apply a standard VAT model to imported goods. Instead, it uses imposta monofase, a single-stage tax charged on importation, not a multi-stage VAT collected and offset across successive sales in the supply chain. In its May 16, 2025 San Marino Ministry of Finance's 2025 Budget at a Glance, the Ministry described monofase on imports as an ad valorem tax of 17%.

For finance teams, that difference changes the invoice process from the start. The San Marino Tax Office says its Indirect Taxation Section manages invoices submitted under the import-tax law, so the real control issue is not just whether a supplier invoice looks complete. It is whether the invoice, customs paperwork, and supporting evidence all match the import event and the way the tax is handled. In a normal VAT workflow, teams often focus on VAT fields, recovery logic, and supplier tax treatment across the transaction chain. In San Marino, that mindset can lead to errors because the tax trigger, evidence trail, and processing steps are different.

That is why a generic VAT invoice checklist is misleading here. AP and bookkeeping teams need to confirm when monofase applies, which import and invoice documents actually support the tax position, and how those records should be booked and retained for later review. This guide focuses on three practical questions: when monofase applies, which documents matter, and how to record and keep the evidence.

---

Where Monofase Applies and How the Tax Office Fits In

San Marino monofase tax sits in the Republic's indirect tax system as an import tax on goods, not as a standard VAT collected and reclaimed at each stage of a supply chain. In practical terms, the San Marino monofase vs VAT distinction matters because the tax trigger is tied to goods entering San Marino and the related import formalities, rather than to a broad input and output VAT mechanism that finance teams reconcile across routine purchase and sales invoices.

For AP and bookkeeping teams, that means ordinary EU VAT habits can be misleading. A supplier invoice for goods shipped into San Marino is not just a bill to post and later match against reclaimable input tax. Under the Law on Import Tax, it becomes part of an import tax file that may involve Tax Office submission and official review. This guide is limited to imported goods. If you are dealing with services or other non-goods transactions, review them separately rather than assuming the same workflow applies.

The institutional anchor for this process is the Ufficio Tributario, particularly its Indirect Taxation Section. Operationally, that means the invoice may need to follow a documented handling path with office-linked references that your team can retrieve later. A process built around standard VAT posting logic will usually miss that control point. A better approach is to treat the invoice as an import record, an accounting record, and an official tax document at the same time.

If you want a useful comparison point for how a VAT-alternative indirect tax changes invoice requirements, the same lesson applies here: once the tax system departs from standard VAT logic, invoice handling has to follow the governing institution and filing mechanics, not just the familiar accounting labels.

The Invoice and Supporting Documents You Need for San Marino Imports

For imported goods, the supplier invoice is essential, but it is not enough on its own. A workable San Marino monofase invoice process depends on a document packet that lets your team trace one transaction from the supplier sale to the goods entering San Marino. In practice, that packet should keep the invoice linked to the import and commercial records that explain what was shipped, when it moved, and what value was declared.

A solid San Marino import invoice documents file will usually include the supplier invoice, the relevant customs or import paperwork, transport or delivery evidence where that is part of the trail, and any commercial records that explain the transaction. Depending on the shipment, that can include purchase orders, order confirmations, packing lists, carrier documents, goods receipt records, contract terms, correspondence about price changes, and credit or debit adjustments. The goal is not to create paperwork for its own sake. It is to make sure the invoice can be reconciled to the actual import event.

When reviewing San Marino monofase invoice requirements, focus first on whether the file identifies the parties, goods, values, dates, and transaction references clearly enough to reconcile the purchase from supplier billing through import handling. Supplier details, goods descriptions, quantities, currency, and shipment references should line up across the invoice, customs papers, and internal receiving records.

Supporting documents matter because monofase is tied to imported goods entering San Marino, not just to the existence of a commercial invoice. The file needs to show what entered, when it entered, what value was declared, and how that import event connects back to the supplier billing. If those links are weak, the accounting team can struggle to support the treatment of the transaction during review, reconciliation, or a later records check.

A practical intake checklist for San Marino customs supporting documents should cover four questions:

• Who are the parties? Confirm the supplier, importer, consignee, and any customs-facing party are identifiable and consistent across the file.
• What goods are involved? Match item descriptions, quantities, units, and product references across the invoice, import paperwork, and receiving evidence.
• What value is being supported? Check line values, freight or incidental charges where relevant, currency, and any later changes that affect the commercial value.
• Which movement or import event does the invoice belong to? Confirm shipment dates, delivery dates, customs references, and internal receipt records point to the same transaction.

This is especially important when invoices are issued before arrival, when multiple deliveries sit under one commercial arrangement, or when values change after shipment. In those cases, the invoice alone may not explain the full story. Teams often need transport records, customs declarations, and internal receiving evidence to bridge the gap. That is similar to the discipline used in cross-border customs and invoice controls outside the EU VAT system and in delivery-note evidence for deferred invoice workflows in Italy, where finance teams rely on linked records rather than a single billing document.

For day to day operations, it helps to store these records as one transaction file rather than as separate accounting, logistics, and customs documents. If AP has the supplier invoice but logistics keeps the transport evidence elsewhere and customs paperwork sits in another folder, reconciliation slows down and control gaps appear. A cleaner process is to index each import purchase with one shared reference so the invoice, supporting documents, and any later changes remain tied together from intake through retention.

---

How AP and Bookkeeping Teams Should Run the Workflow

For finance teams, the goal is one auditable chain from the supplier invoice to the import evidence, the relevant tax-office reference, and the final bookkeeping entry. Do not drop monofase into a generic VAT input-tax workflow. It needs its own coding logic, review points, and exception handling because the tax treatment is tied to the import and supporting formalities.

A workable control sequence looks like this:

1. Identify whether the invoice belongs in the San Marino import workflow. Confirm that the goods are entering San Marino and that the transaction is not being treated under a different domestic or foreign tax process.
2. Collect the full document packet before posting where possible. At minimum, this should include the supplier invoice, transport or customs evidence, goods receipt or warehouse confirmation if relevant, and any internal reference showing the import's tax-office handling trail.
3. Match the commercial details across the file. Check supplier name, invoice number, date, currency, item description, quantities, shipment references, and declared values against the import documents and receiving records.
4. Confirm the tax-office step or record reference tied to the import. The team should be able to point to the document, filing, or internal log entry that proves the transaction has been routed through the correct monofase handling path.
5. Code the transaction using accounts designed for the monofase model. Do not force it into a standard VAT input account structure if that structure does not reflect how the import tax position is actually documented and controlled.
6. Route mismatches to exception review before final posting. Missing import evidence, value differences, unclear shipment references, or incomplete tax-office documentation should be escalated to the controller, tax reviewer, or designated compliance owner.
7. Post only when the file is complete enough to support audit follow-through. If the business allows provisional posting, it should be flagged clearly, tracked in an exceptions log, and cleared against outstanding documents within a defined deadline.
8. Retain the full linked record in one retrievable place. A reviewer should be able to open one file and follow the transaction from invoice intake through import support to ledger entry without searching separate systems for missing context.

This workflow works best when responsibilities are explicit. AP should verify invoice completeness and basic document presence. Bookkeeping should check coding, posting support, and ledger consistency. A controller or senior reviewer should handle exceptions, approve unusual adjustments, and confirm that the retained file would stand up to later audit or tax inspection.

For teams documenting their procedure, a short operating checklist can keep the process consistent:

• Confirm the invoice is for goods entering San Marino.
• Assemble invoice, import support, receipt evidence, and tax-office reference.
• Match values, dates, supplier details, and shipment identifiers.
• Review account coding under the monofase process, not a generic VAT workflow.
• Escalate missing or conflicting evidence before final posting.
• Save the complete file so every document and ledger reference is easy to retrieve later.

---

Handling Credit Notes, Adjustments, and Electronic Records

After goods have been imported, the commercial file can still change. A supplier may issue a credit note, replace an invoice, grant a rebate, accept a return, or send a later charge that changes the value or narrative behind the original transaction. For finance teams handling monofase-related records, the main risk is not only the adjustment itself, but the loss of a clear link between the original import event and the later correction.

The safest control is to preserve document lineage from the first invoice through every later change. Each file should keep the original supplier invoice, the adjustment document, a short explanation of the business reason for the change, any supporting paperwork such as return records or revised commercial correspondence, and any official references connected to the case. Those items should stay linked in one retrievable record so that someone reviewing the file later can understand what changed, why it changed, and which documents support the revised position.

In practice, that means AP and bookkeeping teams should avoid overwriting the original record or filing the adjustment in isolation. A corrected invoice should not sit in the system as if the first version never existed. A credit note should not be stored without the invoice it relates to. If goods are returned, damaged, discounted, or repriced after import, the finance file should show the before-and-after story clearly enough that a reviewer does not have to reconstruct events from inbox fragments.

Electronic invoicing platforms, ERP workflows, and document-management tools can help by creating links between records, preserving timestamps, and controlling version history. That traceability is useful, but it does not replace the core evidence. Teams still need the underlying supplier invoice, the import evidence, and any official supporting documents that explain the adjustment. Good systems improve retrieval and auditability, but the defensible record still depends on complete source documents.

Because post-import changes can raise technical questions, teams should treat unusual adjustments as escalation points rather than assuming every commercial change should be handled the same way. If the amount changes significantly, the goods are partially returned, or the documentation no longer matches the original import story, involve the responsible finance lead or external advisor early and record that review in the file. When the original import file changes, the safest response is to keep the adjustment trail explicit rather than relying on memory or detached emails.