Norwegian Contract Law: A Guide for UK Tech Companies

Last updated 5 July 2026 · by attorney-at-law Kjell Steffner

A UK SaaS or IT consultancy signing its first Norwegian enterprise customer usually asks one question first. Can we use our existing English-law templates, or does Norwegian contract law require something different? The honest answer is that the templates will rarely be invalid, but several of their core mechanisms — incorporation of standard terms, limitation of liability, IP transfer — work differently under Norwegian law, and a clause that reads as watertight in London may be read more narrowly, or set aside, in Oslo. This guide sets out the differences that matter commercially, with the statutory basis for each.

How does Norwegian contract law differ from English law?

English contract law is built on exhaustive drafting. Entire-agreement clauses, long definition sections, express warranties and detailed boilerplate carry the load, and the doctrine of consideration governs formation. Norwegian contract law takes a different route. It is principle-based, supplemented by statutory background rules, and it recognises a general duty of loyalty and good faith between contracting parties that influences how agreements are interpreted and performed. Norwegian courts will read a contract in light of its purpose and the parties’ reasonable expectations, not only its literal wording.

Norway has no requirement of consideration. A promise can be binding without anything given in return, and formation is analysed through offer, acceptance and the parties’ intention under the Contracts Act of 1918 (avtaleloven). English lawyers sometimes assume this is a uniquely Nordic feature, but Scots law also manages without consideration, so the concept’s absence should feel less foreign to a UK firm with Scottish experience.

The practical consequence is a shift in drafting emphasis. In Norway, less turns on whether a clause is technically airtight and more turns on whether the overall allocation of risk is one the courts and the counterparty will accept as reasonable between professional parties.

Can a Norwegian court set aside an unreasonable B2B contract term?

Yes, and this is the single most important background rule for a UK supplier to understand. Under section 36 of the Contracts Act, a contract may be set aside or amended, in whole or in part, if it would be unreasonable or contrary to good business practice to enforce it. The assessment considers the content of the agreement, the parties’ relative positions, the circumstances at formation and later developments.

The threshold in commercial contracts is high. Norwegian courts treat section 36 as a narrow safety valve between professional parties, and it is applied far more readily in consumer relationships than in negotiated B2B deals. A UK supplier should therefore not fear that a Norwegian court will casually rewrite its subscription agreement. The provision matters for a different reason. It discourages extreme one-sided terms — sweeping unilateral change rights, disclaimers of essentially all liability, termination mechanics that leave the customer without recourse — because those are precisely the clauses a court may trim. English law polices the same territory through the reasonableness test in the Unfair Contract Terms Act 1977 for exclusions on standard written terms, so the discipline is familiar. The mechanics differ, and Norwegian drafting should be calibrated to Norwegian expectations rather than ported from UCTA practice.

Will online standard terms bind a Norwegian business customer?

They can, but incorporation is the battleground. Norwegian law asks whether the terms were made part of the agreement before it was concluded and whether the customer had reasonable notice of them. Unusual or particularly burdensome clauses — a low liability cap, an exclusive-remedy service-credit regime, broad audit or suspension rights — should be made specifically visible rather than left in the depths of a linked document. A quote that says “standard terms apply” while the terms sit in a website footer is a weak foundation if the relationship sours.

Norwegian enterprise customers also negotiate more than many UK SaaS suppliers expect. Signed order forms, appendices and a separate data processing agreement are the norm in enterprise deals, and a battle of forms — each party referring to its own standard terms — creates the same uncertainty it does in England. The safe pattern is a signed framework or order document that expressly incorporates the supplier’s terms, with the unusual clauses surfaced.

Do liability caps and exclusions of indirect loss work in Norway?

Yes. Liability caps, exclusions of indirect and consequential loss, and agreed exclusive remedies are all generally enforceable in Norwegian B2B contracts. Three qualifications matter in practice. First, clarity is decisive, because ambiguity is construed against the drafter and vague category words such as “indirect loss” do not necessarily cover what an English precedent assumes they cover — data loss, business interruption and third-party claims should be addressed expressly. Second, a cap or exclusion can in principle be tested against section 36, and gross negligence or intent will as a rule defeat an exclusion regardless of its wording. Third, Norwegian enterprise and public-sector customers routinely require carve-outs from the cap for breaches of confidentiality, data protection obligations and IP infringement, so a UK supplier should decide its position on those carve-outs before negotiations start rather than during them.

Service credits deserve a specific mention. If service credits are intended as the sole remedy for SLA failures, say so expressly. If they are not, say that too, because silence invites the interpretation the supplier did not want.

Who owns the intellectual property in software and deliverables?

This is the area where UK assumptions most often fail, in both directions. The Norwegian starting point is that the person who creates a work owns the copyright in it.

Employee-created software and other works

For software the statute intervenes. Under section 71 of the Copyright Act (åndsverkloven), copyright in a computer program created by an employee in the course of the employment, or on the employer’s instructions, passes to the employer unless otherwise agreed. For software, Norway and England therefore land in the same place — compare section 11 of the Copyright, Designs and Patents Act 1988, which makes the employer first owner of copyright in employee works.

For everything an employee creates that is not software — documentation, designs, reports, training material — there is no equivalent statutory rule in Norway. Transfer to the employer follows an unwritten principle under which rights pass only to the extent necessary and reasonable for the employment relationship to achieve its purpose, and no further. That is materially narrower than the English rule, and it is why Norwegian employment contracts for technical staff should contain an express IP clause rather than rely on the default.

Consultants and subcontractors

Neither country transfers a contractor’s IP automatically. In England a commissioner does not own a contractor’s copyright without a written assignment, and in Norway it is unsettled whether the unwritten employment-transfer principle reaches independent contractors at all. The commercial rule is therefore the same on both sides of the North Sea. “If the customer pays, the customer owns it” is false for contractor work, and a supplier selling development or consultancy services into Norway must secure a clean chain of title through express written assignments from every consultant and subcontractor, distinguish pre-existing tools and reusable libraries from bespoke deliverables, and disclose open-source components and their licence obligations. In public-sector bids the open-source point is not optional, because contracting authorities ask.

Patentable employee inventions

Patentable inventions follow a separate statutory track. The Employee Inventions Act (arbeidstakeroppfinnelsesloven) gives the employer broad rights to inventions made within the company’s field of activity, against payment of reasonable remuneration to the inventor, with disputes referred to a dedicated mediation board. The UK counterpart is sections 39 to 43 of the Patents Act 1977, where the employer owns inventions made in the course of normal or specifically assigned duties and the employee can claim compensation only where the invention proves of outstanding benefit. The Norwegian remuneration mechanism is more accessible to employees, and contracts for R&D staff in Norway should address inventions and remuneration expressly.

England and Wales vs Norway — the differences at a glance

Which mistakes do UK suppliers make most often?

Five patterns recur in the contracts we review for UK technology companies entering Norway.

• Assuming standard terms linked from a website are incorporated because the quote says they apply.
• Treating an English-law limitation clause as if a Norwegian court will read it identically, particularly the phrase “indirect loss”.
• Relying on payment to transfer IP in consultant and subcontractor deliverables.
• Leaving open-source components undocumented in SaaS offerings and public bids.
• Negotiating with Norwegian enterprise and public customers as if they will accept the same risk allocation as a mid-market UK buyer.

A related point sits just outside contract law. Marketing to Norwegian recipients — including B2B e-mail campaigns and lead generation — is regulated by the Marketing Control Act, which requires consent or an existing customer relationship for electronic marketing and requires marketing to be identifiable as such. A UK outbound playbook should be checked against those rules before launch.

When should a UK tech company involve Norwegian counsel?

The economics are straightforward. A localisation review of a SaaS or consultancy template costs a fraction of one disputed enterprise deal, and it is a one-off exercise that then carries every Norwegian customer on the same paper. The moments where Norwegian input pays for itself are signing the first Norwegian enterprise customer, localising SaaS, licence, consultancy or reseller terms, negotiating liability caps and carve-outs with a Norwegian buyer, assigning or licensing software and IP deliverables, and appointing a Norwegian reseller or implementation partner.

Data protection and AI obligations run alongside the commercial contract and are covered separately in this series. If your route to the Norwegian market runs through public procurement, the tender rules and the state’s standard IT contracts change the contractual picture considerably.

Nordia Law helps UK technology companies enter and operate in the Norwegian market. As part of a Nordic firm with a presence in Norway, Sweden, Denmark and Finland — and through close cooperation with DAC Beachcroft and Laworld — we also coordinate cross-border legal questions across the Nordics and beyond.

Planning your first Norwegian customer contract? Book a short Teams call with Kjell Steffner to pressure-test whether your UK terms work under Norwegian law. Book a meeting.

Sources: Contracts Act (avtaleloven), Lovdata · Copyright Act (åndsverkloven), Lovdata · Employee Inventions Act, Patentstyret · Marketing Control Act (English translation), Lovdata · Copyright, Designs and Patents Act 1988 s. 11 · Unfair Contract Terms Act 1977 s. 11 · Patents Act 1977 s. 39, gov.uk