BDI

Defense technology.
Buyers, markets, opportunities.

Preparing the FVOE evidence record for an Italian public tender

Map declarations, supporting documents and buyer access separately when preparing FVOE evidence, including the distinct routes available to foreign suppliers.

In this article
  1. Separate the evidence repository from the tender response
  2. Distinguish tender access from preliminary verification
  3. Establish the foreign supplier's actual route
  4. Build a document map that preserves meaning
  5. Distinguish an unavailable record from a system delay
  6. Carry the reviewed record into the next opportunity
  7. Sources & evidence

An Italian tender can require a supplier to coordinate three different things: the declaration it submits, the evidence supporting that declaration, and the buyer's ability to obtain or inspect that evidence. FVOE, the Fascicolo Virtuale dell'Operatore Economico, supports the third part. Treating it as a certificate that proves the whole company is qualified misses the work needed for a particular competition.

For a foreign supplier, the practical decision is which documents can be made available through the system and which need a separately agreed verification route. Resolve that distinction while the bid team still has time to obtain records from the relevant issuing authorities.

Separate the evidence repository from the tender response

ANAC's current FVOE service page describes buyer access to evidence of general, technical, organisational and financial requirements, alongside documents supplied by the economic operator. FVOE 2.0 applies to verification for procedures initiated from 1 January 2024 through the public-contract platform. The former PassOE mechanism has been discontinued for that version.

The commercial implication is that an old bid folder may contain the wrong administrative instructions even when its company facts remain accurate. A previous PassOE document, an expired certificate and a current declaration are not interchangeable evidence objects. Give the bid coordinator a record of what each document proves and for which legal entity, rather than a folder labelled completed registration.

The underlying requirement still comes from the actual procurement. A financial record relevant to one selection criterion may not establish the capacity requested in another competition. Before uploading additional material, map each requirement to the document or verification channel intended to address it.

The cross-border evidence guide to e-Certis is useful when identifying the home-country document corresponding to an unfamiliar requirement. That identification work complements FVOE administration; it does not replace the buyer's assessment.

Distinguish tender access from preliminary verification

ANAC's clarification published on 30 May 2025 explains access following the supplier's consent in its offer. The buyer must still request access; a further separate supplier authorisation is no longer required for that tender workflow. The current service page separately describes preliminary checks before a procurement begins, where explicit operator authorisation remains necessary.

This distinction should shape the internal response to a notification. Ask whether the request concerns a tender the company has entered or a preliminary verification. The two situations can reach the same administrative team but require different handling. An instruction to approve every request automatically would erase the distinction the official guidance makes.

Keep the relevant notice with the commercial record. The person responsible for access should be able to identify the contracting authority and the procurement or preliminary enquiry involved. That makes it easier to resolve a legitimate request promptly and to ask an informed question when the context is unclear.

Do not allow an old workflow diagram to outweigh the current clarification. ANAC's service page retains introductory material describing the earlier approval mechanism, followed by the newer simplification. Reading only the first description can therefore produce an incomplete operating instruction.

Establish the foreign supplier's actual route

The service page provides an ANAC credentials-and-OTP route for foreign users who lack an Italian tax code and cannot use eIDAS. Separately, ANAC's digitalisation FAQ, question E.2, says intra-EU operators without a stable establishment in Italy can be verified without FVOE.

These statements address access and verification in different circumstances. They should not be converted into a universal claim that every foreign bidder must create the same account or that every overseas supplier is exempt from evidence requirements. Put the company's establishment facts and the proposed verification route to the buyer through the tender's authorised clarification channel.

Consider a hypothetical Lithuanian provider of translation services bidding for an Italian public institution. Its corporate records are issued in Lithuania, its directors operate there and its proposed work is performed by a distributed team. The bid coordinator should identify the company actually submitting the offer before asking an adviser to obtain an Italian login on its behalf.

The useful question to the authority is precise: for this bidder and this required record, which document and submission or verification method should be used? That question gives the buyer enough information to respond. A general enquiry about whether foreign companies can use FVOE may leave the decisive issue unresolved.

Build a document map that preserves meaning

For the translation supplier, create a short evidence map covering the issuing body, named legal entity, relevant period, language and requirement addressed. A company-register extract and a client reference may both be official-looking documents, but they answer different questions. A translated title should not conceal that difference.

Where a translation or other formality is required by the procurement, schedule it against the underlying document's availability. Translating an outdated copy first and replacing it later creates avoidable expense. Equally, a translator should not be asked to infer a legal equivalence that the bid team has not established.

ANAC's operator manual, version 1.1 of February 2024, distinguishes documents from the fascicoli to which they are associated. It describes document validity, association and disassociation, with searches by procurement and document attributes. Use that document-management explanation alongside the newer access guidance.

A shared-service team supporting several subsidiaries should also identify whose account and whose records it is using. Similar trading names can conceal different legal entities, and an accurate certificate for one subsidiary does not automatically establish the facts of another.

The original document and its association should both be checked. A correct file stored in the repository may still be associated with the wrong procurement. Conversely, repeatedly uploading differently named copies can make it harder for the team to identify the current evidence.

Distinguish an unavailable record from a system delay

The May 2025 clarification distinguishes temporary retrieval problems from certificates that are not obtainable through interoperable databases. That matters operationally because waiting for the platform will not create a record that the issuing body does not make available through it.

For the supplier, the response should identify the missing evidence and its owner. If a home-country authority must issue a document, establish the request date and expected response. If the buyer is retrieving an existing record, preserve enough information to identify the relevant request. These are different dependencies and should have different entries in the bid team's schedule.

Avoid giving the sales director a single green status for evidence merely because files have been uploaded. A more useful view distinguishes obtained documents, outstanding issuing-authority requests and buyer questions awaiting clarification. This makes the remaining commercial risk visible without forcing management to read every administrative attachment.

Carry the reviewed record into the next opportunity

After the procurement, retain the requirement-to-evidence mapping and the buyer's clarifications. They explain why a particular document was used and prevent a future team from treating an exception or procedure-specific response as a general Italian rule.

For a company working through Consip, the guide to SDAPA admission and specific competitions addresses the separate timing of market admission. FVOE preparation concerns the evidence behind the supplier's position, while admission and the later offer determine which commercial opportunity it can pursue.

The durable asset is a maintained evidence record with clear ownership and provenance. It should shorten the next bid's preparation while leaving room to check the next buyer's actual requirements, current access process and foreign-document route.

Sources & evidence

  1. Fascicolo Virtuale dell’Operatore Economico — current service instructionsANAC
  2. Facilitazioni sull’utilizzo del fascicolo digitale, 30 May 2025ANAC
  3. Digitalizzazione dei contratti pubblici — FAQ E.2ANAC
  4. FVOE 2.0 operator manual v1.1, 5 February 2024ANAC

Current ANAC service page and FAQ reviewed on 6 September 2026 alongside the May 2025 clarification. The February 2024 manual is used for document management, not superseded access permissions.

Suggest a correction