Preparing an EHF invoice for a Norwegian public customer

An EHF invoice can pass a document check and still fail to match the Norwegian public customer's purchase. A supplier should distinguish three questions: whether the invoice is structurally acceptable, whether it reaches the intended recipient and whether its references and billed work match the buyer's order. Each question needs different evidence.

That distinction is useful for a foreign business whose accounting provider handles electronic transmission. The provider may confirm that it sent a valid message, while the customer is still unable to identify the purchase. A productive investigation establishes the failed stage instead of repeatedly changing the invoice layout or sending the same document again.

Start with the customer's purchasing record

Forsvarsmateriell's invoice guidance, dated 24 October 2023 and still published on its supplier site, requests EHF invoices to organisation number 916075855. It says each invoice must refer to one purchase order and that invoices with a missing reference or incorrect address will be returned. Treat those as buyer-specific instructions to reconcile with the actual contract.

The instruction is more specific than a general statement that a document needs some form of buyer reference. The supplier should obtain the real purchase-order number from the customer and connect it to the delivered goods or services. An internal project number is useful to the supplier but cannot be assumed to identify the same record in the buyer's system.

Consider a hypothetical company providing commercial translation services to a Norwegian public customer. Its internal job number follows the language team and delivery date, while the buyer's order authorises a particular assignment. Both references should remain available. The invoice process needs to carry the buyer's reference without losing the supplier's ability to trace the underlying work.

Understand what a format rule actually checks

The current Peppol BIS Billing 3.0 rule R003, in the May 2026 release, requires either a buyer reference or a purchase-order reference. That is a message-level condition. It does not establish that the supplied value is the correct reference for the customer's transaction or that every buyer accepts the same alternative.

This creates a useful example of the difference between validation and commercial matching. A document can contain a populated reference field and satisfy that rule while carrying the supplier's own job number. The buyer may still be unable to connect it to an authorised order. The remedy is to establish and transmit the correct reference, not to argue that passing the rule proves the invoice is substantively correct.

Similarly, a document can be structurally acceptable while billing the wrong quantity, period or service. A successful technical check narrows the investigation; it does not replace comparison with the order and delivery record. The finance team should know what its provider's validation report does and does not cover.

For the translation supplier, the first-invoice review could compare one actual job with the buyer order and the transmitted invoice. Check the agreed language service, the relevant delivery, the billed quantity and the purchase reference together. This is more informative than reviewing an empty template containing plausible-looking example numbers.

Confirm the recipient through the appropriate evidence

OpenPeppol's directory explanation warns that directory updates are the responsibility of service providers and are not mandatory, so not every registered receiver appears in the directory. A missing search result therefore needs further checking. It does not, by itself, prove that the customer cannot receive a Peppol document.

Use the recipient information supplied by the buyer and ask the provider to confirm the relevant endpoint and supported capability. Keep the distinction between the organisation's legal identity and the electronic address used in the message. An address copied from a previous customer should not be allowed to survive merely because the organisations have similar names.

This is particularly helpful when a supplier serves several bodies within the same public sector. A defence-related assignment may involve a different purchasing entity from the one used for a previous research project. The account record should identify the actual invoicing customer and retain the source of the routing instruction.

If a provider reports that delivery failed, preserve the specific response rather than paraphrasing it as “Norway rejected the invoice”. The error may concern an endpoint, a document capability or the message itself. Each can be investigated without reopening the substantive service agreement.

Distinguish correction from a dispute about delivery

The Norwegian public-procurement invoice and credit-note process guide describes checking an invoice against the order, examining discrepancies and relating credit notes to the original invoice. It also calls for checking the customer's correction request against delivery documents. The guide's process history records a text revision in October 2023.

That last step matters commercially. A request for a credit is not merely a data-maintenance task. Finance should understand whether the buyer has identified a duplicate, an incorrect price or work that it disputes. The person responsible for delivery may need to confirm what was authorised and completed before the supplier agrees the financial correction.

In the translation example, a difference could arise because the customer ordered a shorter document and later authorised an additional section. If the invoice includes both, the parties need to reconcile the change and its purchasing record. Changing the reference alone will not settle whether the extra work was authorised at the billed price.

Once the parties establish the correction, keep the original invoice, the agreed reason and the replacement or credit relationship together. Retain the person who authorised the correction and the date, so a later account query can reconstruct the decision. This helps both sides avoid leaving the original claim open while also processing a new document for the same service. The exact handling should follow the buyer instruction and the supplier's accounting process.

Use the invoice evidence to improve the next order

A supplier can learn from exceptions without turning every invoice into a large administrative exercise. Record the cause in a useful category: incorrect recipient, missing buyer reference, wrong field mapping, disputed quantity or an unresolved order change. These distinctions reveal where the business needs to improve its handover.

If several invoices fail because finance never receives the buyer order, the problem begins before invoicing. If references are supplied correctly but transmitted in the wrong fields, the provider configuration needs attention. If the service team repeatedly performs additional work without a clear purchasing instruction, the account-management process needs to change.

Businesses developing their Norwegian procurement and supplier account should include that learning in delivery preparation. The commercial contact who understands the opportunity can help establish the correct ordering route before the first assignment begins. That is usually more efficient than finding the right person after an invoice has been returned.

An industrial relationship also creates different records from an invoice for a specific purchase. A company considering a Norwegian industrial-cooperation work package should keep the project agreement and its reporting separate from the order references governing individual bills. Their commercial purposes may be connected, but one identifier should not be substituted for another without a buyer instruction.

The useful outcome is an invoice whose format, destination and purchasing context can each be demonstrated. Technical validation then becomes one clear part of a dependable payment process, and the supplier can identify the right next action when the document reaches an exception instead of a routine match.