Seller Representations and Warranties in Moroccan Share Sales

When a buyer acquires the shares of an existing Moroccan company, it needs a contractual account of what it is buying. That account is given mainly through the seller's representations and warranties — a set of negotiated statements about the company that the seller makes in the transaction agreement. Moroccan and French practice calls these déclarations et garanties. They cover matters such as ownership of the shares, the accounts, material contracts, tax, employment and litigation, and they are the layer of the deal where the information gap between seller and buyer is managed.

Two boundaries frame everything below, because most cross-border misunderstandings start here. First, the familiar English label does not carry its English-law consequences into a Morocco-governed contract: these statements are negotiated contract terms, and their effect comes from the agreement read under its governing law, not from an imported doctrine. Second, a statement later proving inaccurate is not the same thing as fraud — an inaccuracy engages the contract; dol (fraud) is a separate legal question with its own test.

This is an informational guide to that statements layer. It deliberately stays between two neighbours it does not re-cover: legal due diligence, which investigates and tests the facts, and the garantie d'actif et de passif, which allocates the economic consequences if a defined liability arises. It also sits inside the wider share transfer agreement, which it does not reproduce. It describes no service and provides no template.

In a share sale, seller representations and warranties are the contractual statements by which the seller tells the buyer, in binding form, what is true about the company as at agreed dates. They are the seller's assertions of fact and status — the shares are owned free of encumbrances, the accounts were prepared on a stated basis, there is no undisclosed litigation of a defined kind, and so on. In Moroccan and French practice the same idea is expressed as déclarations et garanties, and the two words are generally used together as a single transaction concept rather than as two separate legal categories.

Their function is to allocate information risk. The buyer knows less about the company than the seller does, and cannot verify everything; the statements move part of that risk back to the seller by giving the buyer a contractual position if reality turns out to differ from what was stated. That is why they matter even when due diligence has been thorough — diligence tests what it can reach, and the statements address what it cannot.

It also helps to say what they are not. They are not a due-diligence report, not a guarantee that the company is problem-free, and not, by themselves, a mechanism that fixes the financial consequences of a problem. They are statements; how far they bind, and what follows if one is wrong, depends on the rest of the agreement and on its governing law.

There is no codified Moroccan "representations-and-warranties regime" for share sales. Moroccan company law (Law 5-96 on the SARL and Law 17-95 on the SA) governs how shares transfer; it does not define, require or standardise a catalogue of seller statements. Where these statements appear, they do so because the parties negotiate them into the contract under freedom of contract, within the limits of mandatory law and public policy.

That does not mean Moroccan law is silent on the surrounding questions. The Dahir des obligations et des contrats (DOC) — the general contract-law framework — supplies the rules that make a validly agreed statement binding, the doctrine of defects in consent (erreur and dol, error and fraud) that can affect a contract, and the principles of contractual liability that come into play when an undertaking is not honoured. The point is narrower: the statements themselves are contractual constructs, not a statutory list that Moroccan law supplies by default.

So the safe formulation is this: seller representations and warranties are negotiated contractual statements resting on general contract-law principles — not a code-based right, and not something Moroccan law compels a transaction to contain.

"Representations and warranties" is deal vocabulary that foreign teams carry from one jurisdiction to the next, and it is perfectly usable in a Morocco-facing transaction. The caution is about legal effect, not language: the label travels, but the consequences do not travel automatically with it. In some common-law systems, "representation" and "warranty" are distinct legal categories with different remedies (misrepresentation versus breach of warranty, with their own measures of recovery). It would be a mistake to assume that this distinction, or those remedies, apply of their own force to a Morocco-governed contract.

The reliable way to read these terms in a Moroccan deal is functional. Treat them as the seller's contractual statements about the company, and look to the agreement and its governing law for what happens if a statement is wrong — the remedy, the limits, the time to claim — rather than importing an English-law outcome by reflex. This guide uses "representations and warranties" and "seller statements" interchangeably for readability, without suggesting that either word produces a particular automatic consequence.

The same caution applies in reverse to the French and Arabic terms. Déclarations et garanties is the natural Moroccan-practice expression, but it too takes its effect from the contract and the applicable law, not from any single fixed doctrine. Where terminology has no clean equivalent across systems, the honest course is to explain the function rather than to pretend the concepts map perfectly.

This is the distinction most worth getting right. Legal due diligence is the buyer's investigation: it examines the company's documents and facts and identifies risk. Seller representations and warranties are the seller's contractual statements about those same facts. One investigates; the other asserts. They are complementary, and neither replaces the other.

The relationship runs in both directions. Diligence shapes the statements — what the buyer discovers influences which assurances it asks for, how they are qualified, and which specific risks need separate treatment. And the statements backstop diligence — because an investigation can never be certain it has found everything, the seller's statements give the buyer a contractual position on matters diligence could not fully verify.

Two things must stay honest. Seller statements do not replace due diligence: a contractual assurance is not an investigation and cannot surface an unknown problem before the deal. And a clean diligence result does not make the statements unnecessary, because diligence does not guarantee that everything was found. The workable summary is the one used across these guides: diligence finds, and the agreement allocates.

Seller statements and a garantie d'actif et de passif (GAP) are different layers, and keeping them apart is essential. A representation or warranty asserts that something is true about the company. A GAP does something else: it allocates to the seller the defined economic consequences of pre-sale liabilities or asset shortfalls that surface after the sale. The statement describes; the guarantee allocates the financial outcome.

It follows that one does not automatically produce the other. An inaccurate statement may trigger contractual consequences if — and only to the extent that — the agreement so provides; a GAP is not the automatic result of every inaccuracy, and a GAP can respond to a defined liability whether or not any particular statement was wrong. The two often work together in the same deal, but they answer different questions and are drafted separately.

This guide stops at the boundary. The economic-consequence machinery — how a claim is triggered and made, caps, thresholds and baskets, the contractual claim period, security such as escrow, and the mechanics of specific indemnities — belongs to the guarantee and is developed in its own guide. Here, the focus stays on the statements and how disclosure qualifies them.

Seller statements are usually organised by subject matter, and it helps to see the typical fields — while remembering that no two agreements carry the same list and that not every deal covers every area. Common subjects include: the company's corporate existence and standing; the seller's authority and capacity to sell; title to and ownership of the shares, free of encumbrances; the accounts and financial information; the company's assets; material contracts; employees and social-security matters; tax; litigation and disputes; regulatory and compliance matters; intellectual property; data protection; debt; and related-party arrangements.

Two of these are worth singling out because they behave differently. Title to the shares is often treated as a fundamental statement — it goes to whether the buyer gets what it is paying for — and it connects to the transfer formalities covered in the share-transfer-agreement guide rather than being re-explained here. Statements about the accounts are contractual statements, not an accounting audit opinion: the seller is stating something on an agreed basis, and that is not the same as a professional assurance that the figures are correct.

These are given only as examples of subject matter, at the level of the legal framework. This guide draws no tax, employment, litigation, IP or accounting conclusions — each of those has its own domain — and it does not suggest that a seller "guarantees" any of them beyond what a specific agreement actually says.

Seller statements rarely stand unqualified, and disclosure is how they are qualified. Rather than state something without exception and risk being wrong, the seller discloses specific facts against the statements — "this is true, except for the following" — so that the disclosed matter is carved out of, or contextualised within, the assurance. Disclosure is therefore part of this page's core subject: it is the mechanism that turns a broad statement into an accurate, bounded one.

In transaction practice, disclosure is often organised through a disclosure document or disclosure schedules attached to the agreement, and practitioners sometimes distinguish general disclosure (for example, matters treated as disclosed by virtue of public registers or the diligence materials as a whole) from specific disclosure (a particular fact set against a particular statement). Whether a deal uses a formal disclosure letter at all, and how general and specific disclosure are defined, varies from transaction to transaction; none of this is a fixed requirement of Moroccan law.

The point that must not be overstated is the effect. Disclosure does not automatically remove the seller's liability. Whether a disclosed matter is excluded from a claim, and to what degree, depends on the wording of the specific agreement — how "disclosed" is defined, how fairly and specifically the matter was disclosed, and what the governing law makes of it. A disclosed risk and an undisclosed inaccuracy are analytically different animals, but the difference between them is set by the contract, not by a universal rule.

Not necessarily — and this is a point where cross-border assumptions cause trouble. Making a document available in a virtual data room is not the same, in every deal, as achieving effective contractual disclosure against the seller's statements. Whether data-room material qualifies a statement depends on how the agreement defines disclosure: some agreements treat everything fairly made available in the data room as disclosed; others require specific, itemised disclosure and give no automatic effect to the mere presence of a document.

The safe way to hold this is as a drafting question, not a settled outcome. It is not correct to assume that "anything in the data room is automatically disclosed," nor to assume the opposite. What counts as disclosed, and with what effect on a later claim, is exactly the kind of term that has to be read in the specific agreement and under its governing law.

A knowledge qualifier narrows a statement to what the seller knows. Instead of stating flatly that something is the case, the seller states it "to its knowledge" — so that the seller is answerable only if the matter was within a defined field of awareness. In transaction drafting these qualifiers take different shapes, such as actual knowledge or knowledge after some defined degree of inquiry, and they materially change how much the statement is worth to the buyer.

The essential caution is that a knowledge qualifier has no universal meaning. What "knowledge" covers — whose knowledge, actual or constructive, with or without a duty to inquire — is whatever the agreement defines it to be, and it should be read as a defined term rather than assumed. It is not true that a knowledge qualifier always protects the seller, and it is not true that it never bites; the effect depends entirely on how it is drafted and on the applicable law. This guide explains the concept and does not propose any standard formulation.

Materiality qualifiers limit statements to matters of real significance — for example a statement given "in all material respects," or one confined to "material" contracts or "material" breaches. Their function is to stop trivial or immaterial discrepancies from counting as inaccuracies, and so to focus the statements (and any later claim) on things that actually matter to the deal.

Like knowledge qualifiers, materiality is a negotiated drafting device, not a legal standard supplied by Moroccan law, and "material" means what the agreement makes it mean. This guide keeps materiality at that level and does not import broader transaction constructs, such as "material adverse change" conditions, which are a different subject and are not developed here.

Sometimes, depending on the deal. Where a transaction signs and completes at the same moment, the statements are simply given as at that point. Where there is a gap between signing and a later closing, the parties may agree that some or all of the statements are also given, or repeated, as at closing — so that they speak to the company's position at completion, not only at signing — or they may agree that they are not repeated. There is no universal requirement that statements be repeated at closing.

This connects to the wider signing-versus-closing structure of a transaction, which belongs to the share transfer agreement and the acquisition guides and is not reproduced here. The only point specific to the statements is that when, and as at what date, they are given is itself a negotiated choice.

"Bring-down" is transaction shorthand for confirming or repeating the seller's statements at closing — bringing them down to the completion date so that they are given again as at that later moment, sometimes as a condition to the buyer's obligation to complete. Where the agreement ties a bring-down to completion, that requirement operates within the broader conditions precedent and closing process. It is English-language deal vocabulary, and where a deal uses one, a bring-down is a way of testing that the position stated at signing still holds at closing.

Two cautions. Not every agreement contains a bring-down; whether one is used, and what it is tied to, is negotiated. And the term is drafting practice, not a Moroccan legal category — in French and Arabic the same idea is expressed descriptively (the statements are reaffirmed at completion) rather than by a transliterated label. This guide names the concept so the reader recognises it, without suggesting it is standard or required.

If a seller statement turns out to be inaccurate, what follows is decided by the agreement, not by a fixed rule. The relevant questions are contractual: was the matter disclosed and therefore carved out; was the statement qualified by knowledge or materiality; is the inaccuracy significant enough to count; and what does the agreement say should happen as a consequence. An inaccuracy is a breach of a contractual statement, and its treatment runs through the contract's own terms and the general principles of contractual liability under the applicable law.

What should not be assumed is an automatic remedy or an automatic amount. There is no default rule that an inaccurate statement produces a particular payment, and — importantly — no imported measure of "warranty damages" applies of its own force in a Morocco-governed contract. Whether the buyer can recover, how much, and by what route depends on the agreed remedies, any liability limits, the disclosure position and the governing law. The economic-consequence side of this, where the deal channels an inaccuracy into a defined payment, is typically handled through the guarantee mechanics rather than left to general principle.

No. This is one of the most important safety points on the page: an inaccurate declaration is not automatically dol (fraud). A statement can be wrong for many reasons — an honest mistake, an ambiguity, a matter the seller did not know, a disclosure that did not go far enough — none of which, by itself, establishes fraudulent conduct. Inaccuracy engages the contract; dol is a separate legal question.

Dol, under Moroccan contract law, concerns intentional wrongdoing affecting consent — broadly, deceit or concealment that induced the other party to contract — and it has to be established on its own terms, distinct from the mere fact that a statement proved untrue. The analysis turns on things the contractual inaccuracy alone does not settle: knowledge, intention, concealment and the effect on consent. It would be wrong to treat every breach of a statement as fraud, and equally wrong to assume that contractual caps or exclusions necessarily shield deliberately fraudulent conduct; how mandatory law treats fraud is a separate question from how the contract allocates ordinary inaccuracies.

The practical takeaway is to keep the two lanes apart. Most inaccuracies are contractual matters resolved through the agreement's own machinery. Fraud is a distinct and serious allegation with its own legal test and its own consequences, and it is not made out simply because a representation turned out to be inaccurate.

Because seller statements are contractual, the consequences of getting one wrong are largely whatever the parties agree, within the limits of mandatory law. Depending on the deal, an inaccuracy might be channelled into contractual damages, a specific indemnification, a price adjustment, a consequence attached to a condition before closing, or a claim under the transaction's guarantee — or a combination. No single one of these applies automatically; they are alternatives the agreement selects among.

The same is true of the limits. Claims arising from the statements are commonly subject to negotiated boundaries — a cap on the seller's exposure, thresholds or a basket below which claims do not proceed, a contractual period within which claims must be brought, and defined exclusions. This guide flags that these exist, but their detailed mechanics belong to the garantie d'actif et de passif, which owns the economic-consequence architecture; the guide states no standard cap, no standard survival period and no figures.

One duration point is worth isolating because it is often confused. The contractual claim period — how long the buyer has to bring a claim under the agreement — is not the same as the statutory limitation (prescription) rules that govern the underlying liability. The two are set separately, and a negotiated contractual period should not be assumed to override the mandatory limitation rules that apply to the underlying matter.

The clearest way to hold all of this is as a single workflow, because each mechanism has a distinct place in it. Due diligence comes first: the buyer investigates and surfaces an issue. The seller's statements then address the relevant facts, stating the position on the matters the parties care about. Where a statement cannot be given cleanly, disclosure qualifies it — the seller carves out the specific fact so the statement is accurate as bounded.

From there, the parties assess the consequence of a known issue, and they have a menu. A disclosed, accepted risk may simply be excluded from later claims. A quantifiable concern may be priced into the purchase price. A specific identified risk — often a concrete diligence finding — may be handled by a specific indemnity tailored to it. And the broad field of undefined pre-sale exposure may be allocated through a garantie d'actif et de passif. Each of these is a different tool for a different situation.

Seen this way, the boundaries between the guides are also the boundaries between the mechanisms: due diligence investigates, the seller's statements and disclosure (this guide) assert and qualify, and the guarantee allocates the economic consequences — all inside the share transfer agreement as the container. This section describes how they relate; it is not negotiation advice.

A Moroccan lawyer's role here is not fixed: it depends on the transaction, the company and what due diligence brings to light. Broadly, the work of a lawyer admitted in Morocco may involve connecting diligence findings to the seller's statements — making sure that what was discovered is properly reflected in what is stated, qualified or disclosed — and checking that any references to Moroccan law in the statements are accurate.

Where relevant, that involvement may include distinguishing known from unknown risks; identifying what should be disclosed and how; reviewing knowledge and materiality wording so it means what the parties intend; aligning how and as at what date the statements are given between signing and closing; considering whether a particular exposure needs a specific indemnity or belongs in the guarantee; and assessing how the statements interact with the governing-law and dispute-resolution choices. Not every transaction needs all of this, and not every lawyer performs each task. Where a lawyer is involved, professional secrecy (secret professionnel) may cover the exchanges concerned, and it is not identical to the common-law notion of attorney-client privilege. This describes a possible role in general terms; it is not an offer of service.

A frequent search is for a model set of representations and warranties, or a standard disclosure letter, and it is worth being direct about why this guide provides none. The content that makes a set of statements correct is exactly what a template cannot know: which company is being sold and its risk profile, what diligence found, what the seller can and cannot state, what must be disclosed, how knowledge and materiality should be framed, which risks need a specific indemnity, what governing law controls, and how remedies and limits are set.

A generic form can show the shape of these documents, but it cannot set the right statements, the right qualifications or the right disclosure for a specific Moroccan transaction — and a form that looks comprehensive can quietly be inaccurate, over-broad, or wrong on exactly the point that later matters. A broad, unqualified "no liabilities" or "no litigation" statement copied from a template is a good example of how a reassuring form can create risk rather than manage it. That is why this guide explains how the statements work and deliberately provides no template, no model clause and no drafting.

To be explicit about the limits: this guide explains the seller's contractual statements and how disclosure qualifies them, not the whole transaction. It does not reproduce the share purchase agreement, walk through the acquisition process, set out the due-diligence method, or develop the economic-consequence mechanics owned by the garantie d'actif et de passif.

It provides no tax, accounting, employment, litigation, IP or insurance advice, and no template, model clause or disclosure-letter form. Where a defined legal question needs a formal conclusion, that is the province of a Moroccan-law legal opinion, and the governing-law question belongs to the choice-of-law guide. It describes no service and makes no offer.