Use FMV’s invoice instructions to distinguish purchase-order line references from the LandaID and work-order references used for direct orders.
A Swedish public-sector invoice needs to reach the correct electronic recipient and identify the purchase inside that recipient's organisation. Peppol can provide the delivery route, but the buyer's references determine how the invoice connects to the order and the people responsible for it. Suppliers should establish that relationship when the purchase is agreed.
FMV's published instructions make the distinction unusually concrete. They describe different references for a contract or purchase order and for a direct order. A supplier selling to several Swedish authorities should preserve those buyer-specific differences rather than adopt one national invoice template and assume every customer uses the fields identically.
FMV's invoice information gives its Peppol recipient identifier as 0007:2021000340 and explains that PDF or scanned invoices are not electronic invoices for the stated e-invoicing requirement. It identifies a Svefaktura alternative where Peppol is not possible and provides separate instructions on required purchase references. Suppliers should apply the route appropriate to their actual contract and current buyer instruction.
This is different from copying every delivery address displayed on a general contact page. Such a page may contain information for more than one legal or operational situation. The finance team needs to know which route applies to the invoice it is about to issue, not merely which address accepts some form of correspondence.
Digg's own invoicing instructions provide a useful comparison: the agency has a different Peppol identifier and offers an invoice-portal registration route for suppliers unable to send through their business system. A portal offered by one customer is not automatically the solution for another. Maintain the receiving authority as a distinct customer record.
FMV's invoice-labelling instruction dated 29 January 2024, still linked from its current page, places a contract or purchase-order reference in OrderReference and the corresponding order-line reference in OrderLineReference for Peppol BIS Billing 3.0. For a direct order, it instead specifies the buyer's LandaID in BuyerReference and the work-order reference, AO, in AccountingCost.
That is a commercial mapping decision with a technical consequence. The supplier first needs to establish what kind of purchasing record the buyer has issued. Only then can its accounting provider map the supplied references correctly. Trying to infer the purchasing arrangement from a familiar-looking number reverses the process.
Keep the original buyer instruction beside the mapping used in the finance system. The visible invoice and the transmitted data should tell the same story, but they are not the same record. A number appearing somewhere on the invoice image does not establish that it occupies the field the buyer uses for matching.
There is no need for every account manager to become an invoice-format specialist. The account manager should obtain the correct purchase information, finance should preserve its meaning and the service provider should explain how it is carried in the electronic message. Each handover needs enough context to prevent a number from being treated as interchangeable free text.
Consider a hypothetical supplier providing office-equipment maintenance under an FMV purchase order. The supplier's service system creates its own job numbers and invoice-line sequence. The buyer's order has a separate set of line references. Both sets are useful, but they identify different records.
If the first invoice line corresponds to the buyer's third order line, writing “1” as the buyer's order-line reference because it is the first line on the invoice creates an avoidable mismatch. The supplier should relate each billed item to the actual buyer order, while retaining its internal job reference separately for its own records.
A compact reconciliation can record the buyer's ordered item, the supplier's delivered service, the quantity or period billed and the relevant order line. This is especially useful when a single visit covers several tasks. The invoice can then reflect the authorised purchase rather than the order in which the technician happened to perform the work.
The same reconciliation helps resolve a dispute. If the buyer questions one item, the supplier can identify the corresponding authorisation and delivery record without re-opening the entire account history. Clear references reduce the time spent determining which service the conversation concerns, leaving the parties to address the substantive issue.
Now consider a separate, authorised direct order for a small workplace support service. The supplier should obtain the references applicable to that direct order instead of manufacturing a purchase-order number to fit its standard template. FMV's instruction makes this a distinct route with its own fields.
The commercial team can make that difference visible in the order handover. A field stating the purchasing route is more useful than a note saying “usual Swedish invoice”. It tells finance why the reference package differs from the previous transaction and identifies the buyer contact who can clarify it.
If the accounting software cannot represent the instructed fields, address that limitation before the invoice is issued. A manual workaround that only changes the printed appearance may not change the transmitted message. The relevant question to the provider is whether the actual electronic data can carry the buyer's required references in the appropriate places.
Suppliers developing a broader FMV tender and customer relationship should make this finance handover part of account preparation. The people assessing a product or service may not be the people who resolve invoice exceptions. Establishing the operational route early prevents a successful delivery from becoming a prolonged search for the right administrator.
An invoice problem can originate in delivery, data or the underlying purchase. Start by identifying which stage failed. A document that could not be transmitted needs a different response from one received successfully but lacking a usable order reference. A disagreement about the billed amount requires a commercial review, even if the electronic message is valid.
Maintain a short exception record linking the invoice, the reported problem and the agreed next step. If a reference needs correction, preserve the buyer's instruction and the relationship between the earlier and corrected documents. If the billed work is disputed, connect the enquiry to the contract, order and delivery evidence rather than asking the network provider to solve it.
Avoid presenting successful transmission as proof of payment approval. It is evidence about one stage in the process. The supplier's accounts receivable team should track the actual information it has, including any buyer response, so that its cash forecast reflects the unresolved issue accurately.
The invoice should contain the references and supporting information needed for the transaction. It need not reproduce every tender attachment or internal service record. Keep supporting material accessible and provide it through the appropriate route when required, while ensuring the invoice itself identifies the billed commitment clearly.
For sensitive commercial attachments, the supplier's Swedish public-procurement confidentiality planning provides a related discipline: identify the information and its purpose rather than attaching broad documents indiscriminately. Invoice preparation and tender preparation occur at different stages, but both benefit from controlled, relevant evidence.
A dependable Swedish billing process therefore preserves three relationships: the invoice recipient, the buyer's purchasing reference and the supplier's delivered work. Peppol supplies a structured route through which those relationships can be communicated. The commercial value comes from making them correct before the invoice leaves the supplier's system.
Current FMV and Digg HTML and FMV’s linked 29 January 2024 invoice-labelling PDF reviewed 6 September 2026. Peppol ID is a recipient identifier; the document format and buyer references are treated separately.
Suggest a correction