Verify Norwegian Organisasjonsnummer and MVA Before Paying

A Norwegian supplier invoice with an organisasjonsnummer or an "NO...MVA" VAT number needs four checks before AP approves payment or relies on the input VAT: the nine-digit number must pass Norway's MOD-11 structure test, Brønnøysundregistrene must confirm the entity exists and is current, the VAT Register must confirm MVA registration when VAT is charged, and the registered name must match the supplier on the invoice.

That is the practical workflow behind the search intent to verify Norwegian organisasjonsnummer and MVA before paying. A valid-looking number is not enough. The checksum only proves the number is structurally possible. It does not prove that the supplier exists, has not been deleted, is allowed to charge MVA, or is the same legal entity named in your purchase order and supplier master.

Treat the checks as payment controls, not as a single lookup:

• Structure: normalize the value from the invoice and test the MOD-11 check digit. If it fails, request a corrected invoice before approval.
• Register existence: look up the organisation number in Brønnøysundregistrene. If no entity is returned, hold payment and escalate supplier onboarding.
• MVA status: if the invoice charges Norwegian VAT, confirm that the supplier is registered in the VAT Register. If registration is not confirmed, do not rely on the VAT amount until the supplier resolves it.
• Name match: compare the registered legal name and address with the invoice, contract, purchase order, and supplier master. If the mismatch is more than formatting or a known trading name, hold the change and ask for evidence.

This article is deliberately buyer-side. Official register pages explain the facts behind Norwegian organisation numbers and VAT registration; thin validators tell you whether a number format passes. AP still needs a decision sequence that turns invoice fields into actions: approve, hold, correct, escalate, or treat the MVA as unresolved.

The same discipline matters whether the check is manual for one invoice or automated across a supplier list. The invoice supplies the data points: supplier name, organisation number, MVA suffix, invoice date, VAT amount, total, payment reference, and source document. The control only works when those fields are extracted consistently and compared against the right register data before payment is released.

Normalize the number and run the MOD-11 structure check

Start by reducing the invoice value to the nine-digit organisation number. A Norwegian supplier may print it as plain digits, with spaces, or as a VAT number wrapped with "NO" and "MVA". For the structure check, remove spaces, dots, "NO", and "MVA". What remains should be nine digits.

The Brønnøysund Register Centre guidance on Norwegian organisation numbers states that a Norwegian organisation number consists of 9 digits, with the last digit being a modulus 11 check digit; if a business is registered in the VAT Register, its VAT number is the same as its organisation number.

The MOD-11 check uses the first eight digits and the weights 3, 2, 7, 6, 5, 4, 3, and 2. Multiply each digit by its weight, add the products, divide by 11, and subtract the remainder from 11. The result is the check digit. If the division leaves no remainder, the check digit is 0. If the result is 10, the organisation number is invalid.

For the official example 123456785:

• Digits: 1, 2, 3, 4, 5, 6, 7, and 8.
• Weights: 3, 2, 7, 6, 5, 4, 3, and 2.
• Products: 3, 4, 21, 24, 25, 24, 21, and 16.

The products add to 138. Dividing 138 by 11 leaves a remainder of 6. Subtracting 6 from 11 gives 5, so the full organisation number is 123456785.

For a failure example, take the fictitious first eight digits 10000013. The weighted products add to 12, which leaves a remainder of 1 when divided by 11. Subtracting 1 from 11 gives 10, and 10 cannot be used as a check digit, so no valid ninth digit exists for that sequence.

This is the right first filter for validating a Norwegian VAT number on an invoice, but it is only a format test. A checksum-valid organisation number may still be the wrong supplier, a deleted entity, or a real entity that is not registered for MVA. Passing MOD-11 should move the invoice to the register checks, not straight to payment approval.

Confirm the entity exists and is current in Brønnøysundregistrene

Once the number passes MOD-11, check whether it identifies a real entity in Brønnøysundregistrene. For AP, this is not a broad business-information search. It is the control that answers whether the legal supplier named on the invoice exists in Enhetsregisteret and whether the supplier master should trust that identity.

For a one-off check, AP can use Brønnøysund's public search. For a system or spreadsheet-assisted process, the Open Data API supports a single-entity lookup at the "api/enheter" endpoint by organisation number. The relevant finance point is not the code; it is which returned fields should be compared with the invoice and supplier master:

• organisasjonsnummer, to confirm the number returned is the number on the invoice.
• navn, the registered legal name.
• forretningsadresse, the business address.
• organisasjonsform, such as AS, ENK, or NUF.
• næringskode, the industry classification, useful as a reasonableness check.
• slettedato, where a populated deletion date is a strong stop signal.
• Other status signals in the response where the API provides them.

Brønnøysund's API documentation treats a valid request for a non-existent resource as a 404 response. In AP language, that is not a minor exception. If the organisation number was copied correctly from the invoice and no entity is returned, hold payment and send the case back through supplier onboarding. Do not "fix" the number by guessing.

Also keep main entities and sub-entities separate. The legal supplier on the invoice should map to the entity you pay and book against, not merely to a workplace, branch, or operational unit that happens to carry related data. If a supplier gives a workplace-level identifier or a number that does not match the legal entity in the contract, clarify before changing the supplier master.

A Brønnøysund supplier lookup for an invoice should leave AP with evidence, not just a pass or fail. Save the lookup result or exception note with the invoice approval record, especially when the supplier is new, high value, or has changed legal details since the last invoice.

Check MVA registration when the invoice charges VAT

The "MVA" suffix changes the AP question. A Norwegian organisation number can be real without the supplier being registered in the VAT Register, so the register-existence check and the MVA-registration check are separate controls.

On Norwegian supplier invoices, the same nine-digit organisation number is used as the VAT number when the business is registered for MVA. That is why invoices often show the value as "NO" plus the organisation number plus "MVA". The suffix is a supplier statement, not independent evidence. If the invoice includes Norwegian VAT, AP should confirm that status before relying on the VAT amount.

In Brønnøysund's Open Data API, the relevant field is registrertIMvaregisteret. Read it as "registered in the VAT Register." If the entity exists but this field does not confirm registration, the invoice should not move through normal VAT treatment without clarification. Skatteetaten VAT Register guidance says that when an enterprise is no longer registered, it must not issue invoices with VAT, which is the practical reason AP should hold the MVA element until the status is resolved.

This is also where invoice-date context matters. A status checked today may not answer every historical case by itself. If the invoice relates to a supply period around a registration or deregistration date, AP should ask whether the supplier was registered for the period covered by the invoice, not only whether the current lookup is positive.

The remediation is straightforward:

• If the supplier is MVA-registered and the invoice details line up, continue with the normal approval route.
• If MVA is charged but registration is not confirmed, hold the VAT treatment and ask for a corrected invoice or evidence from the supplier.
• If the supplier has deregistered, avoid claiming input VAT until the finance owner confirms the correct treatment.

For the separate question of what a Norwegian VAT invoice must contain, including when the MVA suffix belongs on the invoice, use the Norwegian MVA invoice mandatory fields guide rather than turning this verification check into a full invoice-format review.

Treat name, address, and trading-name mismatches as hold-and-clarify events

The name check is where many false positives and real risks look similar. Brønnøysund returns the registered legal name. The invoice may show a brand, department, shortened trading name, old name, or personal-name sole proprietorship. AP should not reject every difference automatically, but it should not update the supplier master on trust either.

Use the mismatch severity to decide the next action:

• Low-risk formatting difference: punctuation, spacing, legal suffix placement, or capitalization differs, but the legal name, address, organisation form, and purchase order all point to the same supplier.
• Plausible trading-name difference: the invoice uses a known foretaksnavn, brand, or department name. Ask for support if the supplier is new or the amount is material.
• Recent legal-name or address change: hold supplier-master changes until procurement, the contract owner, or the supplier provides evidence.
• High-risk mismatch: the registered entity, bank details, invoice narrative, and supplier history do not line up. Hold payment and route the case through the fraud or supplier-onboarding process.

This check is not the same as bank-detail verification. A correct organisation number does not validate a new bank account, and a familiar bank account does not validate a changed legal supplier. Keep those controls separate so one apparent pass does not mask another exception.

Foreign-supplier invoices need their own judgment. A foreign supplier with no Norwegian footprint may not have a Norwegian organisation number at all; the Norwegian buyer may instead need to self-assess VAT under Norway reverse-charge VAT rules for foreign supplier invoices. A NUF, by contrast, is a Norway-registered foreign enterprise and should have an organisation number. VOEC is a separate scheme for certain foreign sellers in consumer e-commerce and should not be treated as a normal B2B supplier organisation number.

The invoice fields that support this decision are the supplier legal name, address, organisation number, MVA suffix, invoice date, total, payment reference, and the source page. If those fields are scattered across a PDF, email attachment, and supplier master note, mismatches are easier to miss.

Build the checks into supplier onboarding and periodic refreshes

The four checks should not wait for an audit sample. Run them when a supplier is created, when the first invoice arrives, when bank details change, when an invoice is unusually high value, and on a monthly or quarterly supplier-master refresh.

For a periodic refresh, export the supplier list with organisation number, registered name, address, VAT status held in the master data, last invoice date, and owner. Compare the list against Brønnøysund data and flag exceptions: populated deletion dates, changed legal names, changed addresses, and MVA status changes. The finance team does not need to review every supplier manually. It needs a clean exception list with the invoice or supplier record that caused each concern.

Norwegian-native accounting systems often support Brønnøysund lookup at supplier creation. That helps at onboarding, but it does not remove the need for periodic checks if suppliers change status later. Multinationals using SAP, NetSuite, Dynamics, Xero, or spreadsheets may need a manual export, an API-assisted check, or a small data-quality workflow outside the accounting system.

The quality of the check depends on the invoice data going into it. AP needs the supplier legal name, organisation number, MVA suffix, invoice date, VAT amount, total, and source reference in a consistent structure before exceptions can be reviewed efficiently. For Norwegian payment workflows, extracting KID payment references from Norwegian invoices is a separate control, but it belongs in the same extracted dataset when AP is preparing invoices for payment.

Invoice Data Extraction fits this workflow at the field-capture stage, not as a substitute for Brønnøysund or Skatteetaten. Users upload invoices, describe the fields they need in a prompt, and download structured Excel, CSV, or JSON output. The product can process large mixed batches of PDF, JPG, and PNG files, and every output row includes a source file and page reference for review. That makes invoice data extraction for supplier-verification workflows useful when AP wants a supplier list ready for register checks instead of manually copying names, organisation numbers, MVA suffixes, totals, and invoice dates out of PDFs.

What AP should do when a check fails

Use the failed check to decide the hold reason. A supplier-verification exception should produce a specific action, not a vague note that the invoice "needs review."

• The nine-digit value fails MOD-11: request a corrected invoice or written clarification before approval. Do not guess the missing or wrong digit.
• Brønnøysund returns no entity for the organisation number: hold payment and escalate to supplier onboarding. Confirm whether the supplier gave the wrong number or whether the invoice is not from the expected legal entity.
• The entity has a deletion date or other stop signal: hold payment, check whether the supplier has a successor entity, and require approval before changing the supplier master.
• The invoice charges MVA but VAT-register status is not confirmed: treat the VAT amount as unresolved. Ask for a corrected invoice or evidence of registration before claiming input VAT.
• The registered name or address does not match the invoice: hold supplier-master changes, compare contract and purchase-order records, and ask the supplier for evidence when the difference is more than formatting or a known trading name.
• A foreign supplier has no Norwegian organisation number: check whether the supplier should have a NUF, whether the invoice falls under reverse-charge review, or whether another country identifier is the relevant supplier evidence.
• The organisation number matches but the bank details changed: do not approve the change from the organisation-number check alone. Use the separate bank-detail change control.

The same pattern appears in other jurisdictions: AP teams need country-specific authenticity checks before they rely on invoice data, such as AP-side verification of Indian GST e-invoice IRNs for Indian GST invoices. For Norway, the core decision record is the four-part supplier check: MOD-11 structure, Brønnøysund entity status, MVA registration where tax is charged, and legal-name match.