Moldova Public Procurement E-Invoicing: Supplier Guide

Moldova is building a public procurement e-invoicing workflow that links the e-Achizitii procurement system with e-Factura, rather than treating public-sector billing as a standalone PDF exercise. At the March 18, 2026 NPPP meeting, Moldovan officials presented the e-Achizitii concept and the draft procurement e-invoicing law, according to the EU4Moldova report on the meeting. The separate Moldova Ministry of Finance consultation notice says the reform is intended to close the digital chain from contract to invoice to payment to accounting records, make e-Factura interoperable with RSAP/e-Achizitii, and align procurement invoices with the European standard.

For suppliers invoicing ministries, agencies, municipalities, and other public bodies, the practical takeaway is straightforward: Moldova public sector e-invoicing is moving toward a structured workflow tied to contract, payment, and accounting records. The current Ministry consultation notice says the law is designed to enter into force on Moldova's EU accession date; until then, suppliers should track the final law, implementation acts, data schema, and buyer onboarding sequence.

What is active now

• Moldova already uses e-Factura in public-procurement invoicing for certain taxable supplies.

What is still emerging

• The 2026 reform is about deeper interoperability between procurement records, e-Factura invoices, payment execution, and accounting records, supported by the draft law and the e-Achizitii system concept.

How MTender, e-Achizitii, and e-Factura Fit Together

If you are trying to understand the Moldova MTender invoice workflow, start by separating procurement activity from invoice issuance. MTender is the procurement environment suppliers already encounter, where tender notices, competition documents, participation, award decisions, and contract records sit. The Ministry of Finance is using the name e-Achizitii for the proposed next-stage RSAP procurement information system intended to connect procurement records more tightly with downstream finance processes.

That system map matters because e-Achizitii is framed as the procurement-side environment, not the invoicing tool. The record of who won the contract, what public body is buying, and which contract references apply should stay anchored on the procurement side even as the workflow moves further into finance and accounting.

e-Factura sits later in the chain. The Public Procurement Agency explains that, from January 1, 2021, taxable supplies made within public procurement must be documented through e-Factura. Moldova is not starting from zero on B2G invoice digitization. What is new in the 2026 reform discussion is the effort to connect procurement records and invoice records more directly, rather than treat the invoice as a separate document that finance teams reconcile manually.

The consultation notice makes the intended architecture fairly clear: RSAP and e-Achizitii handle contract award and contract management, while e-Factura handles the financial execution side of those contracts. In practical terms, contract data originates in procurement, invoice data is issued through e-Factura, and the linked records can then support payment execution and accounting evidence. For a useful comparison in another public-sector setting, see Lithuania's SABIS public procurement e-invoicing system.

What is not yet fully confirmed in public is the supplier-facing detail. The high-level system relationship is visible, but final onboarding flows, document schemas, field mapping between procurement and invoicing, and some buyer-side operating rules may still depend on the final law and later implementation acts.

What the Draft Law Suggests About Supplier Requirements

The supplier takeaway from the March 18, 2026 NPPP meeting and the related consultation process is threefold: public-procurement invoicing is likely to cover both VAT and non-VAT issuers, invoice data is expected to align with EN 16931, and invoice content will need to match procurement-side records more closely than it does today. That is the operational shift behind the draft law.

The EU4Moldova meeting report, quoting a Ministry of Finance official, says the draft law would cover invoices issued by both VAT payers and non-payers. If you supply a ministry, agency, municipality, school, or hospital, do not assume the new model is irrelevant just because your entity is not VAT registered. Moldova B2G e-invoicing is moving toward a procurement-specific workflow rather than a narrow VAT-only rule set.

The standards point matters just as much. The draft-law package points toward alignment with the European standard for electronic invoicing, which means EN 16931 is the reference point suppliers should watch most closely. In the EU public-sector context, that standard is associated with Directive 2014/55/EU, so suppliers that already work with European public buyers should expect a familiar push toward structured invoice data and validation logic. In practice, that means clearer buyer and supplier identification, more reliable contract or procurement references, and stronger validation of mandatory fields before an invoice can move cleanly through a public-sector process. If you have seen Bulgaria's public-sector e-invoicing requirements for suppliers, the pattern is similar: the goal is not simply to email a PDF, but to submit invoice data in a form that public bodies can validate and reconcile consistently.

What suppliers still do not have is the full technical package. Final data schemas, validation logic, submission mechanics, buyer-side rejection rules, and rollout timing may still depend on the final law and later implementation acts. For now, suppliers should expect more structured invoice data, tighter contract-invoice matching, and clearer validation checks.

The Expected Contract-to-Invoice-to-Payment Workflow

For suppliers, the practical point of Moldova public procurement e-invoicing is not just sending an invoice electronically. It is keeping one connected record from procurement award through e-Factura, payment, and accounting evidence. Treat the expected Moldova MTender invoice workflow as a control checklist:

1. Capture procurement references at award. Keep the buyer identity, procurement procedure, contract number, lot or award reference, delivery terms, and framework or call-off details exactly as they appear in MTender or the buyer record.
2. Check delivery evidence before invoicing. Confirm that quantities, prices, VAT treatment, acceptance records, contract balances, and bank details support the amount being claimed.
3. Issue the e-Factura against matching public-buyer data. Use consistent buyer details, contract identifiers, dates, line descriptions, values, VAT fields, payment terms, and procurement references.
4. Resolve validation mismatches quickly. Contract number, buyer data, tax-field, and line-item differences are the likely correction points once procurement, e-Factura, and e-Achizitii data are connected.
5. Retain one audit file. Keep the e-Factura invoice, contract link, submission evidence, acceptance records, correction history, payment evidence, and reconciliation support together.

What Suppliers Should Prepare for Now

If you supply Moldovan public bodies, split the work into process cleanup now and rule monitoring next.

Do now

• Identify which public-sector contracts could fall into scope first. Build a list of contracts with ministries, agencies, municipalities, state institutions, and other contracting authorities, then note which entities already require tighter procurement documentation.
• Map the data your team already captures. Check whether every invoice can be tied back to a contract number, purchase order or award reference, supplier tax data, buyer details, line items, VAT treatment, payment terms, and acceptance evidence.
• Test whether your invoicing process can produce structured data, not just a PDF. Moldova public procurement invoice requirements are moving toward machine-readable exchange, so you should know whether your ERP, accounting system, or outsourcing partner can generate invoice data aligned with EN 16931, the European standard for electronic invoicing.
• Review approval and recordkeeping steps. Make sure your team can preserve the contract reference, invoice payload, submission evidence, correction history, and payment reconciliation in one audit trail.

Monitor next

• Assign one owner for rule monitoring. Someone in finance, tax, legal, procurement support, or shared services should track updates from the Moldova Ministry of Finance and translate them into internal process changes.
• Watch for the missing implementation detail. Suppliers should keep tracking the final legal text, the confirmed start date, which buyers will be onboarded first, how invoice transmission will work in practice, and whether any procurement-specific exceptions, phased rollouts, or transition periods will apply.
• Separate confirmed Moldovan public information from imported assumptions. Many businesses hear "e-invoicing" and immediately assume the same clearance model, portal logic, or PEPPOL-style routing used elsewhere in Europe. That may be directionally useful, but it is not the same as confirmed Moldova public procurement e-invoicing rules. The same caution applies to broader discussion of Moldova's e-Factura requirements: procurement invoicing may end up with additional references, controls, or handoff requirements that do not matter in ordinary B2B invoicing.