Matching a Finnish government e-invoice to the purchase order

A Finnish government invoice can contain several references that look like variations of a contract number but perform different jobs. The supplier needs to preserve the buyer's intended meaning when those references move from an order or agreement into its accounting system. Otherwise a correct amount can arrive without a dependable connection to the purchase it concerns.

The commercial task is to establish the recipient, the applicable invoicing channel and the required order or agreement references before the billing cycle begins. Finland's current central instructions and a March 2026 supply-security supplier letter show why both the national model and the particular customer's information matter.

Identify the customer before copying its invoice address

The National Emergency Supply Agency's supplier letter of 17 March 2026 explains a concrete organisational change: from 1 April 2026, the agency and the National Emergency Supply Fund have separate invoice addresses. The letter gives the fund's electronic address and sets out its required purchase references. A familiar organisational relationship therefore does not establish one permanent billing destination.

For a supplier serving a preparedness programme, the useful enquiry is which entity issued and administers the particular purchase. The programme name may remain familiar even when the financial recipient changes. Preserve the buyer's instruction with the order rather than selecting an address from an older customer template.

A hypothetical consultancy delivering continuity-planning workshops could have several assignments associated with the same wider public mission. Its finance team should identify the recipient and purchasing record for each assignment, even if the same operational contact helped organise them. That avoids merging distinct commitments simply because the workshop subject and contact person are similar.

The March letter is evidence of a specific 2026 change, not a general rule that every Finnish agency has multiple invoice addresses. It illustrates the reason to confirm the current recipient whenever an order, organisational change or buyer instruction makes the existing customer record uncertain.

Keep the purchase references distinct

The State Treasury's current instructions for invoicing the state distinguish the actual procurement-agreement identifier from a V1 order number, a VSK1 reference used for contract matching and a TK1 accounting reference. In the stated Finvoice mapping, the agreement identifier belongs in AgreementIdentifier, the order in OrderIdentifier and the VSK1 reference in BuyerReferenceIdentifier. These identifiers need to appear in the electronic data, not only the invoice image.

That distinction matters because a supplier's accounting software may use ordinary labels such as “contract” or “your reference” for fields with different electronic mappings. Finance should confirm the actual mapping with its provider rather than assuming that a familiar screen label matches the State Treasury's terminology.

The team should also preserve the buyer-supplied reference exactly. Adding the project name or a contact person's name to the same structured field can make a previously usable identifier ambiguous. Keep the explanatory description in the appropriate separate location and retain the reference as the buyer instructed.

For the workshop consultancy, the contract may establish the commercial relationship while an individual order authorises a particular set of sessions. Recording both does not duplicate work: it connects the payment request to two different levels of the purchasing record. The service lead should be able to explain which delivered sessions the invoice covers without relying on finance to reconstruct the relationship.

Match the invoice grouping to the authorised purchase

The supply-security letter explains that several deliveries may be invoiced together where they share the same invoice-level purchase-order or contract reference. It distinguishes that situation from combining separate orders or agreements. The supplier should therefore decide invoice grouping from the actual purchasing structure, not simply from its preference to send one monthly document.

Suppose the consultancy delivers three workshops under one order and a separate exercise under another. A single month-end invoice might seem convenient, but it can conceal the separate authorisations. The practical approach is to reconcile the delivered work with the buyer's order structure before deciding which items belong together.

This reconciliation should occur in the service record, where the team knows what happened. Finance then receives a billing package that identifies the applicable order, completed work and amount. Asking finance to infer the grouping from calendar entries or travel claims introduces avoidable uncertainty into a straightforward purchase.

If the buyer requests a different arrangement, obtain a clear instruction and determine how it fits the applicable invoice requirements. Keep that instruction with the account record. An informal request for a “combined invoice” is not enough detail when it leaves the reference treatment unresolved.

Choose the channel appropriate to the customer

The State Treasury says suppliers without their own suitable invoicing system should generally use the Handi supplier portal, with the buyer initiating the onboarding route. It separately identifies Basware Portal for Defence Forces suppliers. This buyer-specific distinction matters to a foreign company entering Finland; familiarity with one government portal should not override the actual customer's route.

A company with an established electronic invoicing provider should first determine whether that provider can transmit the required document and references. A company using a buyer portal should establish the named operator and the registration process in time for billing. The commercial decision is how to produce a correct invoice reliably at the expected transaction volume.

Palkeet's current supplier-service information describes Handi functions including viewing orders, invoicing and following invoice stages. These capabilities can help a small supplier maintain the relationship between the order and the payment request. They should be considered alongside the company's own records, so staff can still retrieve the relevant commitment when responsibility changes.

For an occasional workshop provider, a portal may fit the limited transaction volume. A supplier handling repeated orders across several agencies may need a more systematic finance configuration. Compare the work involved in accurate recurring processing, including correcting exceptions, instead of evaluating only whether the first document can be sent.

Resolve the right problem when an invoice stalls

A stalled invoice needs a precise diagnosis. Establish whether the problem concerns the electronic document, the recipient, the buyer reference or the substance of the billed work. A missing reference should send the team back to the order; an incorrect billing amount should send it to the agreed scope and delivery evidence.

The invoice record should preserve the original transmission and any subsequent buyer instruction. If a correction is required, finance needs to understand its relationship to the earlier document. This reduces the risk of treating the correction as a second independent claim for the same work and makes later reconciliation easier.

For suppliers pursuing a Hansel dynamic purchasing system and its customer competitions, the invoicing customer is the organisation behind the resulting purchase. Admission to the system does not replace the need to identify that customer's order and billing process. Carry the relationship from the competition into the delivery file.

The same applies when a company follows Finland's defence and digital-resilience funding opportunities. A grant-supported activity, a programme relationship and an invoiced purchase are different commercial records. Accurate recipient and reference information helps the business keep those records connected where appropriate without treating them as interchangeable sources of payment.

A useful Finnish billing setup therefore makes the legal customer, purchase authorisation, delivered work and electronic references visible together. Once those relationships are established, the finance team can process repeat work with less interpretation and identify the exact missing input when a new assignment differs from the previous one.