Connect the FatturaPA receiving office, CIG/CUP where applicable, order references and delivery evidence without confusing SdI messages with payment.
An Italian public invoice needs to connect the right supplier, receiving office, procurement reference and delivered work. Creating valid invoice data is only one part of that connection. A technically delivered invoice can still leave the customer's finance team unable to identify the order or establish what the payment concerns.
For a supplier using FatturaPA, the practical task is to agree the invoice record when the contract is set up, then carry those references through delivery and billing. Waiting until the first invoice is ready can expose missing information that the sales team could have obtained with the order.
The official FatturaPA format overview distinguishes required fiscal and transmission information from additional data supporting the customer's accounting, payment and information needs. The format can therefore hold references that matter commercially even when they are not the same as the minimum data needed to route a file.
Ask the contract owner for the receiving office, order or contract reference, relevant procurement identifiers and any line-level information the administration expects. Finance should store those instructions against the customer contract, rather than repeatedly asking an account manager to search old emails.
A public organisation can buy different services through different offices. The legal customer's name on the contract does not, by itself, tell the invoice team which receiving office should handle a particular bill. Resolve the specific office before configuring the first recurring invoice.
For suppliers entering the market through negotiated MePA work, the RdO response guide explains why the final offer and resulting commercial documents must describe the same service. Those documents are the starting point for billing references after award.
AgID's IPA portal guide explains the search for organisational units with an electronic-invoicing service. The search can include current or historical services, and results show the service's activation and any cessation dates. This is a more precise lookup than copying the first code found on an old invoice.
Use the customer's instruction and the directory together. If they disagree, ask the customer to resolve the discrepancy. A historic record may explain why last year's invoice used a different code, but it should not silently replace the current contract instruction.
Keep evidence of which office was confirmed for the contract. A company serving several departments may need separate invoice configurations even when the broader customer name is identical. This prevents an apparently helpful customer-master consolidation from sending all future invoices to the office used by the first contract.
The person maintaining that configuration should understand the difference between the purchasing contact, the service recipient and the invoice recipient. They can belong to the same institution while performing different roles in the transaction.
The Città Metropolitana di Venezia's published invoice instructions illustrate the separation. They list office codes, place the receiving-office code in CodiceDestinatario, and call for CIG and, in the applicable cases, CUP. They also specify an internal determination reference. The page records a September 2021 verification date, so its individual codes and buyer-specific fields should be reconfirmed for a new order.
The example shows why these identifiers should not be stored in one generic reference field. The destination routes the invoice. A procurement or project identifier connects it to a different part of the customer's record. The company should obtain the applicable identifiers from the actual order documentation and ask about any missing or apparently inapplicable reference.
Do not invent a CUP because another public customer required one. Nor should an invoice clerk infer the CIG from an unrelated competition involving the same administration. The correct connection is between this invoice and the contract or order under which the work was supplied.
Consider a hypothetical supplier servicing climate-control equipment in three public archive buildings. Its contract covers scheduled maintenance and separately authorised repairs. The service team records visits by building and equipment group, while finance initially plans to invoice one monthly total labelled maintenance services.
That total may be arithmetically correct but difficult for the customer to reconcile. A clearer invoice design connects the scheduled service to its agreed period and the additional repair to its authorisation. The precise fields and supporting documents must follow the contract and the buyer's instructions; the commercial objective is to make each charge traceable to the work being billed.
Suppose the illustrative monthly scheduled service is €4,000 and an authorised repair adds €850. If the supplier combines them without showing the distinct basis, a question about the repair can lead to a discussion of the entire €4,850 invoice. Clear separation gives both parties a better starting point for identifying the issue. It does not predetermine how the customer must process a disputed amount.
Operations should supply the completion information before finance finalises the invoice. A billing process that depends on reconstructing visits from engineers' calendars will become fragile as the contract grows.
The official SdI file and message guidance distinguishes rejection by system checks, delivery confirmation, temporary non-delivery and the customer's acceptance or rejection message. It also explains the notification issued when the customer-outcome message window expires. These events describe the exchange process; a delivery receipt is not evidence that money has arrived.
Give the invoice team a response based on the actual message. A system rejection calls for examination of the identified technical problem. A successfully delivered invoice with an unresolved service query needs coordination with the contract team. Repeatedly retransmitting the same material is not a substitute for understanding which stage is incomplete.
Store the invoice identifier and its messages together. When an intermediary sends invoices on the supplier's behalf, establish who retrieves those messages and how exceptions reach the person able to resolve them. Outsourcing transmission should not leave the supplier without visibility of the customer's billing record.
The official FatturaPA site announced new B2G technical specifications effective from 15 May 2026. That update is a reason to confirm the current implementation with the invoicing provider, rather than assuming that an old format guide covers every current transmission detail.
The provider should be able to explain which supported format and channel it uses for the company's actual situation. Foreign suppliers should establish that route for their circumstances instead of assuming that another firm's domestic setup is automatically appropriate.
A software update does not resolve a missing purchase-order reference. Keep technical configuration and customer-specific billing data as separate responsibilities, with an identified owner for each. This makes faults easier to diagnose when a previously working invoice process starts failing.
Review the first completed billing cycle with sales, operations and finance. Establish whether the correct office received the invoice, the references matched the order, supporting work records were available and the accounting team can trace the eventual payment. Record what required clarification so the next period does not repeat the same work.
The French Chorus Pro invoice-tracking guide provides a useful comparison for businesses operating in both markets: national platforms organise the process differently, while the underlying commercial need to connect the order, delivered service and invoice remains.
For the Italian account, the useful outcome is a repeatable billing record agreed with the actual customer. That record should make routine invoices easier to reconcile and leave the contract team free to address substantive delivery questions when they arise.
Official format, message and IPA guidance reviewed on 6 September 2026. Venice is a dated buyer-specific illustration; confirm actual office codes and contractual requirements.
Suggest a correction