Legal Documents for a Major B2B Contract in France

Definition

Before signing a first large contract with a business customer, a founder quickly asks the same question: which legal documents do I need, and from what contract value? It is often said that a 50,000 euro threshold is the tipping point. We could not verify any legal basis for that threshold: none of the official French sources opened for this article ties an obligation to a contract value of 50,000 euros. The rules described below, on general terms of sale, payment terms, invoices and personal data, apply whatever the amount. The amount matters for another reason: the higher it is, the closer your customer's procurement or legal team looks at your file.

This guide covers a French company selling a service or software to another business in France. It relies on official French and European sources: Entreprendre Service Public, the CNIL, the INPI and Légifrance. It does not treat the American Stripe guide as a rule. That guide, What legal documents do startups need in the US, lists the main legal documents founders may need to create and run a company in the United States. It is useful for spotting the broad families of documents (founder agreements, intellectual property assignment, confidentiality agreements), but it describes American law. In France, both the names and the rules differ.

In practice, the document stack for a B2B contract looks like this, with the French counterpart of the Anglo-Saxon terms an international customer may use:

• the contract itself: a services or licence agreement, sometimes preceded by a framework agreement (the "MSA") and completed by a schedule of services and deliverables (the "SOW");
• your general terms of sale (in French, conditions générales de vente or CGV), or the buyer's terms if they prevail;
• a confidentiality agreement (the "NDA") when sensitive information is exchanged before signature;
• a personal data processing contract (the "DPA"), when you process data on the customer's behalf;
• proof that your company exists and that you hold the rights to what you sell: a registration certificate and intellectual property assignments;
• compliant invoices carrying the mandatory mentions.

A note on transparency: this article is published by Ember, which also builds Fund Your Growth. That capability organises finance, traction, legal and investor materials in a Data Room connected to the file. It stores and retrieves your documents; it does not draft your contracts and does not replace a lawyer. This text is general information, not legal advice.

To place this topic in the company's financial context, the Knowledge guides for finance bring together deeper guidance on the same field.

Prerequisites

Before discussing clauses, three prerequisites shape everything else: a company that exists, a clear right over what you sell, and an identified contact on the customer side.

A registered company. A commercial company proves its legal existence with a Kbis extract. According to the page How to get a K or Kbis extract, verified on 3 April 2026, the Kbis extract "proves the legal existence of a commercial company" and is an up-to-date "identity card" of a company registered in the trade and companies register (the page is published in French; this is our translation). The same page says that for many administrative procedures the Siren number or a registration certificate from the national business register, downloadable free of charge, can be enough. A customer may ask for one less than three months old, so keep an up-to-date copy.

A clear right over your product. Software is protected by copyright without any formality: the INPI states that software, and source code in particular, is considered a work of the mind. The question is therefore who holds those rights in your company. We return to it in the next section, because the rule differs between an employee and a contractor.

A written commercial base. Your general terms of sale must state the payment term. The page Payment terms between professionals and late payment penalties says the payment term must appear on the invoice and in the general terms of sale, and refers to articles L441-1 and L441-9 of the Commercial Code.

A contact on the customer side. Large accounts often have their own contract template and purchasing conditions. Ask early who at the customer signs off the legal part, IT security and data protection. That avoids discovering these steps in the last week.

A public buyer is a separate case. If your customer is an administration or a public body, the contract is a public procurement contract, with its own execution and payment rules. The page Request payment and invoice a public contract states, for example, that invoices must be sent through the Chorus Pro portal. This guide does not cover that case.

Steps

Here is the sequence we suggest for preparing a significant B2B contract. The order is a working proposal, not a legal requirement.

1. Map what the contract will cover. Write, on one page and in plain language, the purpose of the service, the deliverables, the duration, the price, the invoicing rhythm and the data exchanged. This page is the basis for every other document and prevents the schedules from contradicting each other.

2. Sign the confidentiality agreement before sharing sensitive documents. The INPI explains that secrecy over valuable knowledge can be preserved by contractual means (a confidentiality clause) or physical means, and recommends confidentiality clauses in engagement letters (our translation of the French page). A mutual confidentiality agreement is the usual form before a negotiation where both sides reveal information. None of the pages opened for this article makes it mandatory: it is a prudent choice. Also specify how long the obligation lasts after discussions end, and what each side must return or destroy.

3. Check the chain of rights over the product. According to Entreprendre Service Public (page verified on 3 May 2024), a copyright assignment contract must be in writing and must list the assigned rights exhaustively. The same page says that for software created by an employee in the course of their duties or on their employer's instructions, the economic rights are assigned automatically to the employer. That rule concerns employees. For a cofounder who is not an employee, or a freelancer who built part of the product, the pages we opened provide no automatic transfer: plan a written assignment that lists the rights assigned. Stripe's American guide makes the same point about outside contributors.

4. Frame personal data. If your service processes personal data on the customer's behalf (its contacts, employees or users), you are in principle its processor under the GDPR. The text of article 28 of the GDPR, published by the CNIL, provides that processing by a processor is governed by a contract or other legal act that sets out the subject matter and duration of the processing, its nature and purpose, the type of personal data and the categories of data subjects. The contract must notably provide that the processor acts only on documented instructions from the controller. This is the French-law counterpart of the "DPA" that international customers ask for.

5. Draft or negotiate the main contract. The contract sets the scope, price, acceptance conditions, duration, exit terms, each party's liability and the governing law. On liability, keep in mind article L442-1 of the Commercial Code, which covers submitting or attempting to submit the other party to obligations creating a significant imbalance in the rights and obligations of the parties (our translation of the French text). Our reading, which a lawyer should confirm: a clause protecting only one party, with no counterpart, deserves discussion.

6. Set payment terms within the legal limits. Failing agreement, the term is 30 days. Parties may agree a longer term within limits: 45 days end of month from the invoice date, if it is in the contract and is not an abuse, or 60 days from the invoice date. These points come from the page Payment terms between professionals, verified on 7 August 2026.

7. Prepare the signing file. Gather the recent Kbis, the insurance certificate if the customer asks for it, the terms of sale, the schedules, the rights assignment and the processing contract. Keep them in one place with the signed version of each, and note who in your company has the authority to bind it: the customer may want to check that the signatory is duly empowered.

Worked example

This example is illustrative: the company, the people and the figures are invented to show the method, and describe no real case.

Imagine a young French company that publishes an order-analysis tool, which we will call Atelier Donnée. Its first major customer is a retail distributor handling tens of thousands of orders a month. The customer's procurement team sends a six-page contract template, a security schedule and a request for a data processing agreement.

Atelier Donnée proceeds in this order.

• Confidentiality. Before sharing test data extracts, both parties sign a mutual confidentiality agreement. It runs two pages and states how long the obligation lasts.
• Rights. The founder reviews who wrote what. The first prototype was coded by a freelancer, so she has them sign an assignment that lists the rights assigned, their scope and their duration. Without it, the company could not assure the customer that it holds the rights to the tool.
• Data. The tool processes names and addresses of the distributor's end customers. Atelier Donnée is therefore a processor. It answers the customer's request with a processing contract covering the headings of article 28 of the GDPR, starting from a CNIL sample of clauses adapted to its service.
• Payment. The customer proposes 60 days from the invoice date. Atelier Donnée accepts, provided the term appears in the contract and in its terms of sale, together with the late payment penalties and the 40 euro flat recovery fee that the law provides for.
• Liability. The customer's template caps the publisher's liability but not its own. The founder asks for a reciprocal cap and has a lawyer review the clause before signing.

The outcome: four weeks of preparation, and a complete signing file on the day the customer asks for it. This scenario shows the sequence, not a target duration: timing depends on your customer and your product.

Common mistakes

Believing in a magic threshold. Waiting for "the 50,000 euro contract" to deal with terms of sale, confidentiality or data is a bad bet. The obligations we verified do not depend on that amount. Conversely, a 5,000 euro contract that involves personal data already calls for a processing contract.

Copying an American guide. A guide written for the United States talks about corporations, LLCs, American tax elections and non-compete rules that vary from state to state: Stripe's guide lists them itself. None of these transposes as is to a French simplified joint-stock company (SAS). Use it as a list of questions, never as a list of rules.

Forgetting the rights assignment. A copyright assignment must be written and detail the rights assigned. The classic case: a freelance developer writes part of the product, nobody signs anything, and six months later the customer asks for a warranty of ownership. Regularise while the relationship is good.

Neglecting invoice and terms-of-sale mentions. The payment term, the late payment penalties and the 40 euro flat recovery fee must appear in the terms of sale and on the invoice. The official page says a company faces an administrative fine that can reach 2 million euros for a company when it breaches payment deadlines or omits these mentions. Invoices are also changing: the page Mandatory invoice mentions, verified on 11 August 2026, describes new mentions linked to electronic invoicing from 1 September 2026, such as the customer's Siren number or the nature of the operations, with a phased rollout by company size, reaching SMEs and micro-enterprises on 1 September 2027.

Signing without reading the schedules. Security, service-level and subprocessing schedules often create the heaviest commitments. Read them as carefully as the main contract, and have them validated by the person who will have to honour them. For example, a schedule promising continuous availability commits your technical team, not only the person who signs.

Treating confidentiality as a formality. A useful confidentiality agreement states what is confidential, for how long, and what happens when discussions end. A clause declaring everything confidential forever is rarely accepted by the other side.

To prepare the document side of your file as well, How do B2B founders build a winning fundraising data room? details how to organise a set of documents the other party will actually open.

Tools

No tool replaces a lawyer to draft or validate an important contract. Several free official resources will still save you time.

• INPI. The institute provides resources on secrecy, copyright and the national special register of software (RNSL). According to its page on software, registration in the RNSL is essential to make your rights enforceable against third parties (our translation). The INPI also publishes a model mutual confidentiality agreement that defines confidential information, its use and its protection: adapt it to your situation and have it reviewed.
• CNIL. The page Working with a processor explains that processing carried out by a processor must comply with the GDPR and be framed by a contract with the controller, and that this contract can be fully or partly based on standard contractual clauses (our translation). The CNIL also publishes sample subprocessing clauses, to adapt to your service.
• Entreprendre Service Public. The pages on payment terms, invoices and the Kbis extract give up-to-date rules and mentions, with the date of the last verification.
• Annuaire des entreprises. It lets you download a registration certificate free of charge, equivalent to a Kbis for many procedures.

On the organisation side, you also need one place to keep signed versions. Fund Your Growth, Ember's capability for structuring a project and its funding, offers a Data Room connected to the file: you can add your own documents without starting a generation, file them in folders and share a revocable link. The entrepreneur can approve, reject or edit proposals before they enter the file. It is a tool for storage and preparation: it does not validate the legal compliance of your contracts.

When to use this method

This preparation is worth doing as soon as you enter negotiation with a business customer that has a legal team, procurement or a security team, whatever the amount. These signals tell you it is time to start.

• The customer sends its own contract template or a security questionnaire.
• You are going to receive the customer's personal data, even during a trial: the GDPR then applies to the relationship.
• The product was partly written by people who are no longer employees, or by contractors.
• You are preparing a fundraising round in parallel: the contract documents will also help answer an investor's review.
• Payment is staged or conditional on acceptance: the payment term and penalties must then be precise.
• The customer asks for a clause you have never seen, for example on data reversibility or on further subprocessing: better to understand it before answering.

On the cash side, a large contract changes the company's life: collection depends on the agreed terms. A customer who pays at 60 days from invoice ties up your cash longer than one at 30 days. This connects to our guide on 13-week cash discipline, which explains how to link a signed contract to your runway.

In practice, How B2B Founders Build a Credible Investor Target List? completes this framework if the contract is part of a fundraising preparation.

When not to use it

This guide is not made for every case.

• You sell to consumers. The rules for consumer sales (pre-contractual information, withdrawal) are different and are not covered here.
• Your customer is a public body. A public contract follows its own award and payment rules, as Entreprendre Service Public reminds for invoicing through Chorus Pro. The framework of this article is not enough.
• Your customer or your company is established outside France. The governing law, the competent court and the tax rules may change. We did not open an official source on these cases: ask a lawyer.
• You are still in a trial phase with no contract. If no customer is in sight, light preparation is enough: an up-to-date Kbis, simple terms of sale, and a rights assignment signed by anyone who wrote code. Investing in bespoke contracts before the first paying customer slows the product down.
• The contract carries special stakes. Complex industrial property, a regulated sector, export, very high liability: legal advice is indispensable, and this guide does not replace it.

One last point: rules change. The pages cited carry their verification date; reread them before signing, because a rule may have changed since this article was last updated.

Action plan

Here is a four-step plan, from most urgent to least urgent.

Week 1: the inventory.

• Download a recent registration certificate.
• List every contributor to the product (employees, freelancers, cofounders) and check for each what is written about intellectual property rights.
• Reread your terms of sale: payment term, late payment penalties, 40 euro flat recovery fee.

Week 2: the documents to produce.

• Prepare a mutual confidentiality agreement template, starting from the INPI resources.
• Prepare a personal data processing contract, starting from the CNIL sample clauses, if you process data on behalf of your customers.
• Have the missing rights assignments signed.

Week 3: the negotiation.

• Compare the customer's template with your documents and list the gaps on liability, payment terms, ownership of deliverables and confidentiality.
• Have a lawyer review the clauses that heavily commit the company.
• Check that the agreed payment term appears in the contract, in the terms of sale and on the invoice.

Week 4: signature and archiving.

• Gather the signed contract, its schedules and the supporting documents in a single folder, for example in the Fund Your Growth Data Room if you use it.
• Enter the collection dates provided by the contract in your cash forecast.
• Put the review dates in your calendar: renewal, extension, expiry of the confidentiality agreement.

Before deciding, What Evidence to Check Before Choosing Fund Your Growth helps connect this method with adjacent priorities.

Sources and methodology

We opened each source below on 29 September 2026 and use only what it says.

• Payment terms between professionals and late payment penalties, Entreprendre Service Public, verified 7 August 2026: 30-day default term, options of 45 days end of month and 60 days, mandatory mention in the terms of sale and on the invoice, 40 euro flat fee, administrative fine.
• Mandatory invoice mentions, verified 11 August 2026: new mentions and the electronic invoicing calendar.
• Copyright assignment contract, verified 3 May 2024: written form, rights listed, employee software assigned to the employer.
• How to get a K or Kbis extract, verified 3 April 2026: role of the Kbis and registration certificate.
• Request payment and invoice a public contract, verified 25 June 2026: specifics of a public customer.
• CNIL, GDPR chapter IV and Working with a processor: processor contract and standard clauses.
• INPI, Confidentiality agreement (model): model mutual agreement.
• INPI, Secrecy and Software as a special case: confidentiality clauses, copyright over code, RNSL.
• Article L442-1 of the Commercial Code, Légifrance: significant imbalance.
• Stripe, What legal documents do startups need in the US: American reference, cited to illustrate document families and not as French law.

Limits. We did not open an official source on shareholders' agreements, the capitalisation table, professional liability insurance, international contracts or liability-limitation clauses in civil law: these topics are not presented as rules here. Large-account practices (security questionnaires, contract templates) reflect our general observation, not an official source. No text we opened sets a 50,000 euro threshold. This guide is not legal advice: for a contract that heavily commits your company, get a lawyer's help.