Choosing the correct DIR3 offices for a Spanish public invoice

A Spanish public invoice needs a destination inside the buying organisation. Naming the ministry or municipality on the commercial document does not tell its systems which office should process the charge. The supplier needs the correct combination of DIR3 offices for the particular contract, together with the buyer's contract and order references. This decision belongs in the handover from the sales team to accounts receivable, while the people who agreed the work are still involved.

There is also a practical change for anyone following an older invoicing guide. The previous FACe invoice-listing page now describes itself as a historical consultation service for invoices submitted through 27 February 2026. It directs suppliers to the new supplier portal for both old and new invoices. That notice makes an old browser bookmark a poor starting point for establishing today's submission and tracking workflow. Use the official FACe historical-service notice and its current destination, then retain the contract-specific routing information separately.

Three roles within one buying relationship

The government's DIR3 and FACe guidance describes three roles. The accounting office handles accounting and the invoice accounting register. The managing body has responsibility for approving the expenditure file. The processing unit handles its administration. Organisations first register their units in DIR3, then activate and relate them inside FACe. A directory entry by itself therefore does not establish a usable invoice destination.

For a supplier, the valuable distinction is between knowing an organisation and knowing how that organisation will handle a particular bill. A contract manager may work at the delivery location, while the relevant administrative functions sit elsewhere. Copying the delivery address into a customer record does not resolve that difference. Nor does a company need to infer the whole public body's organisational chart: it needs the combination that its customer confirms applies to the order being invoiced.

A useful customer record keeps the three role names visible beside their codes. Recording only a sequence of identifiers makes later review unnecessarily difficult. If a colleague asks why a unit was selected, accounts staff should be able to identify its function, the contract it relates to and the buyer instruction from which it came. This preserves the reasoning when staff change or the next invoice falls in a different financial year.

One municipality can contain several invoice routes

Alicante's published instructions provide a concrete illustration. Its page for commerce, consumer affairs, markets and health lists the same code for the accounting and managing roles, with different processing units for commerce-related work and health. The page also identifies a separate third-party registration step before invoicing. Its displayed update date is February 2020, so the value of this example is the organisational distinction; a supplier should obtain current instructions for its own contract before reusing any listed code. See the municipality's service-specific invoice page.

Consider a hypothetical refrigeration-maintenance company serving a municipal market and a public health facility. The legal customer name may look similar across both assignments, but the operational contacts, acceptance records and administrative destinations can differ. A single undifferentiated customer template would make it easy to bill the correct amount to the wrong processing unit. Separate contract records let the company reuse stable legal details while preserving the distinct destination and references for each job.

That distinction also affects invoice preparation. If the supplier wants to combine charges from several assignments, it should establish whether the buyer has authorised that arrangement and which routing instructions apply. Splitting or combining documents simply to fit an accounting-system default can create a reconciliation problem. The commercial contract, the completed work and the destination of the invoice should remain traceable to one another.

Establish the route during contract mobilisation

Ask the buying organisation for an invoice example or written instruction tied to the actual award. The response should explain the destination, the reference expected on the document and the person or function responsible for confirming delivery. Record any separate onboarding requirement alongside those instructions. This gives the implementation team a defined administrative task instead of leaving the first invoice as an experiment after the work is complete.

The invoice route is a later decision than admission to a procurement procedure. A business that used ROLECE evidence for a simplified Spanish tender should not assume its tender registration completed the customer's supplier-payment setup. The tender record helps establish the offer and award history; the invoice handover connects that history to recurring administration.

For the maintenance company, the handover could identify the service contract, each covered site, the agreed monthly charge and the approved destination for that charge. Emergency work would carry its own instruction and approval reference when required by the contract. Accounts staff could then identify an extra callout without guessing whether it belongs in the monthly service amount. The route and the amount become independently reviewable parts of the same document.

Separate a routing problem from a disputed charge

Suppose the company's monthly service charge is €2,400 and an authorised repair adds €650. If the customer accepts the monthly service but questions whether the repair was approved, correcting a DIR3 identifier will not resolve the commercial disagreement. Conversely, sending another copy of the repair approval will not fix an invoice routed to an unrelated unit. The first useful investigation identifies which question the customer is actually trying to answer.

Build the enquiry around the invoice identifier, contract reference, destination used and the latest response received. Then identify the narrow point requiring action: administrative destination, missing supporting record, incorrect amount or unresolved acceptance. This helps a buyer route the supplier's enquiry internally. A message containing only a balance outstanding forces the recipient to reconstruct the transaction before addressing it.

For the supplier's own records, preserve the original submission evidence and subsequent correspondence as a sequence. If a correction is requested, establish the buyer's required correction process before creating another live demand for the same payment. The aim is to leave both sides with one understandable transaction history, including why any document changed and how the replacement relates to the earlier version.

Keep portal migration separate from customer data

Moving to a new supplier portal is a reason to review access arrangements and stored links. It is not, by itself, evidence that a contract's administrative destination has changed. Treat those as two independent checks: where the company submits and monitors invoices, and which organisation receives each contract's invoice. The distinction reduces the temptation to overwrite every customer record during a systems migration.

The same discipline applies when reviewing the electronic offer submitted through PLACSP. Preserve the award and tender references as historical evidence while updating operational instructions only when a current buyer instruction justifies it. The result is a short, usable invoice-routing record that accounts staff can apply repeatedly, with enough context to recognise when a new site, revised order or organisational change requires fresh confirmation.

Review this record before the next billing cycle following a contract amendment. That is when changed scope can otherwise pass unnoticed from the delivery team into an unchanged invoice template. A few targeted checks at that point are more useful than repeatedly searching a national directory after an invoice has already gone astray.

Give the person preparing the invoice access to the agreed routing instructions, so resolving a routine billing question does not depend on locating the salesperson who originally won the contract.