Connect the Danish electronic invoice recipient with current purchase-order and staff references, using FMI’s August 2026 instructions as a concrete buyer example.
An electronic invoice addressed to the right Danish organisation can still arrive without the information needed to connect it to an order. For a foreign supplier, the practical task is to establish both the recipient and the transaction references before the first invoice is generated. A working electronic connection is one part of that task.
Danish Defence provides a useful current example because its instructions connect electronic delivery, purchase-order information and the employee responsible for the purchase. Those details should travel from the order desk to the finance team with the contract. Leaving them in the salesperson's email creates a predictable delay when the delivery team asks for payment.
The Danish Business Authority's Nemhandel overview describes a shared infrastructure combining document standards, a recipient register and a transport layer. It identifies OIOUBL and Peppol BIS among the document standards. This explains why “we support electronic invoices” is an incomplete answer to a particular Danish customer's requirements.
The Nemhandelsregistret's public information distinguishes a lookup of profiles for a participant endpoint from a CVR search showing the endpoints associated with an organisation. The recipient identifier and its registered capabilities therefore need to be considered together. Use the current recipient information supplied by the customer and check the relevant route with the invoicing provider.
Do not treat the first identifier found under an organisation's name as the destination for every invoice. A public body may have different operational arrangements for different purchases. The question for the supplier is which endpoint the customer has specified for this order, rather than which endpoint looks most familiar from a previous transaction.
An EAN or GLN recipient reference also does a different job from a purchase-order number. One directs the electronic document; the other connects the requested payment to the customer's purchasing record. Accounts staff need both concepts even if their accounting software presents them on a single customer screen.
FMI's invoice and payment guidance, updated 14 August 2026, requests electronic invoices in OIOUBL format to the stated EAN number, with a ten-digit purchase-order number, a staff reference and the project or purchase title. It says order references are updated at the turn of each year. The page also lists supported profiles, including Peppol BIS 3, and distinguishes Invoice, CreditNote and Reminder documents.
These instructions create a concrete clarification point for a supplier whose provider normally sends Peppol BIS invoices. Confirm the intended supported route and the required reference fields with the buyer and provider before changing the company's accounting setup. The presence of several profiles is useful evidence, but the supplier should not resolve a mismatch between its configuration and the purchase instruction by silently selecting a different route.
The staff reference is particularly easy to lose when responsibility moves between sales and finance. Preserve it as a distinct item. A person's ordinary name or an informal description of the project may help a human reader, but it does not necessarily perform the function assigned to a structured buyer reference.
Consider a hypothetical supplier delivering commercial workshop inspection services to a Danish Defence customer. The supplier's finance system already has a Danish customer record from a previous organisation. Its account manager receives a new order with the current recipient and references, but the finance clerk duplicates the earlier invoice template.
The avoidable mistake is not poor arithmetic. It is allowing an old customer template to override the current order. The invoice can display the correct service description and amount while preserving the wrong electronic destination or an obsolete order reference. The team may then spend several days discussing payment without examining the field that caused the problem.
A better handover gives finance a concise first-invoice record: the legal customer, the instructed electronic recipient, the actual purchase order, the specified staff reference and the agreed billing milestone. Attach the underlying order so that unusual entries can be checked at their source. This is a commercial record, not an invitation to copy identifiers from an online example.
Before sending the first real invoice, ask the provider how those references are represented in the transmitted document. A preview is useful, but a familiar label on the invoice image does not establish how the information is carried electronically. The person checking the mapping should be able to explain which buyer instruction each field satisfies.
FMI's annual order-reference instruction makes a December-to-January service period worth discussing before invoicing. A supplier should establish which reference applies to each authorised billing period and how the buyer wants work spanning the boundary represented. Retaining the old number because the commercial relationship continues is not a reliable method.
In the inspection-services example, the business could complete one assignment in December and another in January under a continuing relationship. The service manager should identify the work actually performed, while finance uses the order information applicable to the corresponding invoice. If the buyer has issued a replacement or additional order, save that record with the billing decision.
This also improves forecasting. An expected January payment based on an unresolved order-reference question is less certain than a payment supported by a complete billing package. The finance forecast can identify the missing operational input directly, rather than classifying every delay as a slow-paying customer.
For suppliers approaching Denmark through smaller advertised public contracts, this administrative effort belongs in the initial economics. A small assignment can remain attractive, but its margin calculation should include setting up a dependable first payment route. Subsequent invoices become simpler when the first transaction creates an accurate reusable record.
When an invoice appears delayed, establish what happened to the original. Was it transmitted, received by the intended endpoint, rejected for a document problem or held pending transaction information? Each answer points to a different person and remedy. Sending another invoice without that diagnosis can complicate reconciliation.
A technical rejection requires the finance system or provider to address the relevant message problem. A missing purchase reference requires the commercial and buyer records to be reconciled. A disagreement about the delivered service requires the contract and delivery evidence. These distinctions allow a small supplier to escalate a precise issue rather than circulate a general demand for payment.
FMI's page states that its payment period runs from receipt of a correct and complete invoice, with a minimum of thirty days net. Apply the actual contract and buyer instructions when assessing the individual payment date. Keep the accepted correction and its relationship to the earlier document visible in the account file, including any credit-note or replacement instruction.
The people met through DALO industry engagement and follow-up may introduce a requirement without administering its invoices. Once a purchase is agreed, the account manager should establish the operational and finance contacts appropriate to that transaction. This turns an initial relationship into a manageable delivery account.
The supplier's useful end state is a confirmed recipient, a supported electronic route, correctly mapped purchase references and a clear record of what was billed. Those details let finance identify the next action when something fails, and let the commercial team price future Danish work using experience rather than assumptions about payment administration.
Danish Business Authority, live Nemhandelsregistret information and FMI guidance updated 14 August 2026 reviewed 6 September 2026. FMI lists OIOUBL instructions and Peppol BIS 3 support; supplier advised to confirm its actual route rather than infer exclusive format eligibility.
Suggest a correction