Skip to content

Icelandic customers

How to create an Icelandic customer with the Legal Entities API: the kennitala (scheme 0196) first, what is verified, and what an Icelandic sub-tenant can send.

The kennitala comes first

Register an Icelandic customer under scheme 0196 with its kennitala: 10 digits, without the hyphen, with a check digit we verify. Icelandic invoices carry the seller's kennitala as its legal identifier (rule IS-R-002), and the first identifier registered is the one written there, so the kennitala always comes first.

POST /v1/legal-entities (body)
{
  "externalId": "customer_1042",
  "companyName": "Dæmi ehf.",
  "country": "IS",
  "address": { "line1": "Laugavegur 1", "city": "Reykjavík", "zip": "101" },
  "identifier": { "scheme": "0196", "value": "7112998079" }
}

In production a customer carries one identifier: the kennitala. In the sandbox, an ordered list in identifiers may add a GLN (0088) after it, never before. A customer whose first identifier is not 0196 is refused at creation with 400 legal_entities.iceland_identifier_order.

Verification

  • The kennitala is checked against Iceland's company register (Skatturinn, Iceland Revenue and Customs), with the company name you send.
  • A kennitala that identifies a person (a sole trader's) is never sent to the register: the customer is approved by our team instead.
  • There is no test register. In the sandbox too, the kennitala is checked against the real register, so test with a real company and its exact name. The test scheme 9915 cannot be used for an Icelandic customer: it is refused at creation by the rule above.

What an Icelandic customer can send

This endpoint does not accept the Icelandic VAT number (IS:VAT): it is not a Peppol address. An Icelandic customer created here therefore has no VAT number registered, and can only send invoices outside the scope of VAT (VAT category O). An invoice that charges VAT is refused with 422 and the code sender_tax_identifier_missing (see Sender tax identity mismatch). If your Icelandic customers need to invoice with VAT, contact us.

Rules on Icelandic invoices

Icelandic invoices follow the national rules of the Peppol network (IS-R). getpeppr refuses before sending, with 422 invoices.country_rule_violation, what the network would reject after:

  • Icelandic buyer: an invoice between two Icelandic companies must carry the buyer's kennitala (IS-R-004) — address the buyer by it (to.peppolId 0196:…), or give it as to.companyId with to.companyIdScheme 0196.
  • Final due date (EINDAGI): one attachment at most may be described EINDAGI; its id is the date written YYYY-MM-DD, with no time; the invoice must then carry a dueDate, and the EINDAGI date must be the same as or later than it (IS-R-008 to IS-R-010).
  • Payment: Icelandic payment claims (krafa, code 9) and Icelandic bank transfers (code 42) are not supported and are refused with 422 invoices.unsupported_payment_means. Use a credit transfer to an IBAN.

Receiving

If the company already receives on Peppol through another provider, it must remove its registration there first: see switching provider.