eliDocs
Country Guides

Sweden

Swedish B2G e-invoicing with Beliq, Peppol BIS 3.0 UBL, EAS 0007 Organisationsnummer (orgnr-not-VAT), and the DIGG / SFTI / PEPPOL.SE transmission boundary.

Sweden’s e-invoicing landscape uses standard Peppol BIS Billing 3.0 UBL (EN 16931) on the cross-border path. There is no country-wide national CIUS. Swedish endpoint addressing uses the Organisationsnummer (org-number register, authority: Bolagsverket) via Peppol EAS 0007not a VAT scheme. Authority for B2G operations: DIGG (Myndigheten för digital förvaltning). PEPPOL.SE is the Swedish Peppol Authority.

So a Swedish invoice in Beliq is a Peppol BIS invoice with Swedish parties (EAS 0007). See the Peppol BIS format reference for the full element layout.

Mandate timing

Mandate timing

Swedish public bodies have accepted Peppol e-invoices for years. There is no domestic B2B mandate today; the next hard date is the EU-wide ViDA obligation for cross-border trade.

DateWhat changes
1 November 2019Public-sector bodies must be able to receive EN 16931 e-invoices over Peppol.
1 July 2030EU ViDA introduces mandatory structured e-invoicing and digital reporting for cross-border B2B.

There is no domestic B2B e-invoicing mandate today; a government inquiry into one was launched in February 2026 and reports in November 2027. The next hard date is the EU ViDA cross-border obligation.

Last verified against the European Commission eInvoicing Sweden country page and the Swedish government's 5 February 2026 inquiry directive, reporting by 30 November 2027 on 24 August 2026. Official source.

If you sell to Swedish public-sector buyers today, you are already in scope on the receive-mandate side. B2B remains voluntary until ViDA harmonisation lands. For the dates Beliq tracks across every covered country, see the mandate calendar.

What Beliq does today

What Beliq does today

  • Generate Swedish Peppol invoices via standard: "peppol-bis" (profile peppol), addressed with the Swedish Organisationsnummer endpoint scheme (SE:ORG, Peppol EAS 0007).
  • Validate and parse Peppol BIS UBL against the full EN 16931 + Peppol BIS 3.0 Schematron (peppolVersion in the response).
  • Validation depth on the Peppol path is Authority-checked: Beliq asserts verdict parity against OpenPeppol’s own unit-test corpus (62 testSets, 335 cases) plus its 10 published example invoices. Sweden’s own Peppol rules ride that same pinned Schematron as the SE-R-* family, and OpenPeppol’s Swedish unit-test suite (24 testSets, 48 cases) is vendored and asserted beside the shared one. See how verification works for the tier definitions and the verificationTier field that reports them.
What Beliq does not do (Peppol transmission boundary)

What Beliq does not do (Peppol transmission boundary)

Sweden’s network is the Peppol Network. Beliq is not a Peppol Access Point. It does not:

  • Transmit invoices over Peppol or register you as a Swedish Peppol participant.
  • Operate the 4-corner exchange on your behalf.

Today you send Beliq’s UBL output through your chosen Access Point (BYOC). Managed delivery over Peppol is in build, targeting Q4 2026 and subject to certification.

Integration architecture (Beliq vs Peppol Access Point)

Integration architecture (Beliq vs Peppol Access Point)

Concern In Beliq today Outside Beliq (your stack / partner)
Peppol BIS 3.0 UBL invoice XML Generate, Validate, Parse
Peppol Network transmission (4-corner) Not offered, see boundary above Your Access Point provider
Organisationsnummer / Bolagsverket lookups Not offered Your registry / lookup service
Generating a Swedish Peppol invoice

Generating a Swedish Peppol invoice

Address both parties with the Swedish Organisationsnummer endpoint scheme (SE:ORG, EAS 0007) via the peppol block. Omit vatId — Swedish parties are identified by their 10-digit Organisationsnummer, not VAT. Use SEK for the invoice currency. Provide either a buyerReference or an orderReference (Peppol requires one).

generate-sweden-peppol.sh
curl -X POST https://api.beliq.eu/v1/generate \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "standard": "peppol-bis",
    "profile": "peppol",
    "output": "xml",
    "invoice": {
      "number": "2026-0001",
      "issueDate": "2026-06-04",
      "currencyCode": "SEK",
      "buyerReference": "SE-PO-3311",
      "seller": {
        "name": "Test Sälare AB",
        "vatId": "SE556777999501",
        "peppol": { "schemeId": "0007", "id": "5567779995" },
        "address": { "street": "Drottninggatan 1", "city": "Stockholm", "postalCode": "111 51", "countryCode": "SE" }
      },
      "buyer": {
        "name": "Test Köpare AB",
        "peppol": { "schemeId": "0007", "id": "5560000001" },
        "address": { "street": "Avenyn 2", "city": "Göteborg", "postalCode": "411 36", "countryCode": "SE" }
      },
      "lines": [
        {
          "description": "Professional services",
          "quantity": 1,
          "unitCode": "C62",
          "unitPrice": 1000.00,
          "lineTotal": 1000.00,
          "vatRate": 25,
          "vatCategoryCode": "S"
        }
      ],
      "taxSummary": [
        { "vatCategoryCode": "S", "vatRate": 25, "taxableAmount": 1000.00, "taxAmount": 250.00 }
      ],
      "totalNetAmount": 1000.00,
      "totalTaxAmount": 250.00,
      "totalGrossAmount": 1250.00
    }
  }'
Validation behaviour

Validation behaviour

On /v1/validate and /v1/generate, Swedish invoices run the full EN 16931 + Peppol BIS 3.0 Schematron; failures carry the relevant BR-* / PEPPOL-* rule id. The response reports profileDetected: "peppol" and a peppolVersion. CreditNote payloads are supported (documentType: "creditnote"). SEK currency round-trips cleanly through cbc:DocumentCurrencyCode.

Further reading

Further reading