Conditions Precedent and Closing in Moroccan Share Sales

A share sale does not always begin and end in the same instant. In many transactions the parties sign the agreement on one date and complete it — close it — on a later one, and the space in between exists so that certain things can be done or obtained before the buyer pays and the shares change hands. This guide is about that space: how a signed Moroccan share deal gets from signing to completion, and what has to be true before it can.

The organising idea is simple to state and easy to get wrong. Signing makes the agreement binding and fixes what the parties have promised to do; closing, or completion, is the process by which those agreed steps are actually carried out. Between the two sit conditions — matters that must be satisfied, or in some cases waived, before completion. Some of those conditions are purely contractual, negotiated by the parties; others reflect requirements that Moroccan law or a regulator imposes regardless of what the parties would prefer. Keeping those two categories apart is the single most useful thing this guide does.

It also keeps a firm boundary. This is the process layer of a transaction; it is not the transaction document itself and not the moment ownership legally vests. The structure and drafting of the agreement belong to the share transfer agreement guide, and the wider deal roadmap belongs to the acquisition guide. This page explains conditions, satisfaction, waiver, long-stop dates, failure, and the mechanics of closing — and it describes no service and provides no template.

Not necessarily. Signing is the moment the parties enter into a binding agreement; closing (completion) is the moment — which may be the same or later — when the agreed completion steps are performed and the transaction is carried out. Where nothing needs to be done or obtained first, signing and closing can happen together on a single day. Where something does, the parties separate the two and complete once the conditions are dealt with.

It helps to hold the difference concretely. At signing, the parties are bound to the deal on its terms, including the promises about what will happen at completion; but the buyer has not necessarily paid and the shares have not necessarily changed hands. At closing, the parties do the things the agreement says are to be done at completion — payment, delivery of transfer documents, corporate steps, and so on. Signing creates the obligations; closing performs them.

None of this is imposed by Moroccan law as a fixed sequence. Whether a particular deal has a single-step signing-and-closing or a two-step structure with a gap in between is a function of the transaction — what has to be obtained, how the price is to be paid, what the parties have agreed — not a statutory rule. The vocabulary of signing and closing is deal vocabulary; its Moroccan effect depends on the law and on how the agreement is drafted.

The usual reason is that something has to happen between the two. If a regulatory clearance must be obtained, a corporate approval or agrément secured, a third-party consent collected, a security interest released, or a pre-agreed step completed, the parties commit at signing and then complete once those conditions are satisfied. Separating the two lets them lock in the deal while the remaining items are worked through, instead of waiting until everything is ready before there is any binding commitment at all.

A split structure also gives each side a defined position during the gap. The buyer knows the seller is committed and can insist that the conditions in its favour are pursued; the seller knows the buyer is committed and can expect the conditions in its favour to be met. The interim period, the conditions, the long-stop date and the consequences of failure are the machinery that manages that in-between time — and each has its own section below.

Where none of this is needed, a simultaneous signing and closing is perfectly ordinary. It is wrong to assume that every Moroccan acquisition separates signing and closing; many do not. The separation is a response to real conditions that need time or third-party action, not a default feature of every deal.

A condition precedent is something that must be satisfied — or, where the agreement and the law allow, waived — before the parties are obliged to complete. In French practice these are conditions suspensives: the obligation to complete is suspended until the condition is met. Until then, the parties are bound to the agreement, but completion is held back pending the condition. The purpose is to make sure that, by the time value changes hands, the things the parties treated as essential to proceeding are actually in place.

Conditions come in more than one flavour. Some protect the buyer (for example, that a required clearance is obtained, or that no serious problem has emerged), some protect the seller, and some protect both. Who a condition is for matters later, because it bears on who is responsible for pursuing it and on whether it can be waived. A condition is not the same as an ordinary promise about how the company will be run in the interim, nor the same as a warranty about the company's state — those are separate mechanisms treated elsewhere.

The essential caution at the outset is that conditions precedent are not a universal feature of Moroccan share sales. They exist because the parties put them in, or because a legal or regulatory requirement operates as a gate to completion. A transaction with nothing to obtain and nothing to wait for may have no conditions at all and simply sign and complete together. There is no rule of Moroccan law that a share sale must contain conditions precedent.

This is the distinction to carry through the entire subject. A contractual condition precedent is one the parties negotiate into the agreement: its scope, the party it protects, the standard for treating it as satisfied, whether it can be waived, and what happens if it is not met are all primarily matters of the contract, read subject to mandatory law. A mandatory legal or regulatory requirement is different: it arises from Moroccan law or from a regulator, and it applies because the law says so — not because the parties chose to include it.

The consequences of the difference are large. A contractual condition can often be shaped, allocated and — by the party it protects — sometimes waived, because it belongs to the parties. A mandatory requirement cannot simply be defined away or waived by agreement; the parties cannot make a legal prohibition disappear by writing that the condition is waived, and they cannot lawfully complete in the face of a requirement that forbids completing. Calling something a condition in the contract does not change whether, underneath, it is a matter the parties control or a matter the law controls.

So two questions have to be kept separate for every item on a deal's list. First, is this a condition the parties created, or a requirement the law imposes? Second, if it is a legal or regulatory requirement, does the law merely require a step (which can be taken) or does it prohibit completing until something happens (which the parties must respect)? Much of what follows — waiver, failure, the competition-clearance gate — turns on getting these two questions right, and blurring the two categories is the most common and most serious error in this area.

Only where the transaction is a notifiable concentration under Moroccan merger-control rules — but where it is, clearance is a genuine gate to completion, not an optional formality. Under Article 12 of Law 104-12 (the law on freedom of pricing and competition), notification of a notifiable concentration to the Conseil de la Concurrence has suspensive effect: the parties may not implement the concentration until it is authorised. Completing before the required clearance is obtained is not a shortcut the parties can agree to take — it exposes them to sanctions.

That is why merger clearance is the clearest example of the earlier distinction. It is a mandatory legal requirement, not a contractual condition the parties invented, and it is therefore not something they can waive between themselves to close faster. Even if both sides wished to proceed, the suspensive effect means the transaction cannot lawfully be implemented before authorisation. Where clearance is refused, that is a legal prohibition on completing — a different situation from a contractual condition simply lapsing.

This guide deliberately stops at the gate. Whether a given deal is notifiable at all — the thresholds, how turnover is measured, the filing procedure and timetable, the substantive competition test, and any remedies — is a distinct and technical subject that belongs to a dedicated merger-control treatment, not here. The point for the signing-to-closing process is narrower and is the one to remember: where the regime applies, clearance is suspensive and mandatory, so it shapes the timetable and cannot be contracted away. The broader transaction context sits in the acquisition guide.

Many deals make a corporate approval a condition to completion. Whether one is needed, and in what form, depends on the company's legal form, its statutes and any shareholders' arrangement — the requirements are not identical across company types, and a SARL and an SA are not governed by the same transfer rules. For a SARL in particular, a transfer to a third party can require agrément (approval of the incoming transferee) under the applicable company-law framework; for an SA, the position depends on the statutes and the type of shares.

Where such an approval is required, the parties commonly make obtaining it a condition, and its satisfaction is evidenced by the relevant corporate decision. The detail of how transfers are approved and how they take effect as between the parties, the company and third parties is company-law doctrine owned by the share transfer agreement guide — this page treats corporate approval only as a condition in the closing process and does not re-derive the transfer-formality rules.

The caution is to avoid over-generalising. It is not the case that every transfer requires the same approval, nor that approval is a mere formality; what is required is a function of the specific company and its documents. Treat the corporate-approval condition as something to identify for the particular target, not as a fixed universal step.

Some of the target's contracts — financing, key commercial agreements, leases, licences — may contain change-of-control provisions that require a counterparty's consent, or give it rights, when the company's ownership changes. Where a material consent is needed, the parties often make obtaining it a condition to completion. Which contracts contain such provisions, and whether they are triggered by the particular transaction, is something legal due diligence is well placed to surface.

The important limit is that consent requirements are contract-specific. It is not true that every third-party contract requires consent on a share transfer; many do not, and whether any given one does depends on its own terms. A change of ownership at the shareholder level does not, by itself, mean every counterparty must approve — the question is always what the particular contract says and how it is affected.

Because consents depend on the individual contracts and on the mechanics of the relevant change-of-control regimes, this guide treats them only as an example of a contractual condition. The deeper subject of how change-of-control clauses operate across different types of contract is not developed here; the process point is simply that a material consent, where genuinely required, is a common and often time-sensitive condition to completion.

A condition is satisfied when the thing it requires has actually happened — the clearance has been granted, the approval passed, the consent obtained, the step completed — and satisfaction is normally shown by evidence appropriate to the condition: a decision, a certificate, a signed consent, a corporate resolution, a release document. The agreement typically says what will count as satisfaction and what evidence is to be produced, so that both sides can tell, on the day, whether the condition is met.

Responsibility for pursuing a condition is itself a matter the parties allocate. A condition in the buyer's favour may be the buyer's to pursue, one in the seller's favour the seller's, and some require both to cooperate — filings often need information from each side. Agreements commonly frame this as an obligation to use defined efforts to procure satisfaction and to cooperate, so that neither party can simply sit back and let a condition fail. What standard of effort applies, and to whom, is set by the contract.

Two cautions keep this accurate. First, whether a condition is satisfied is judged against what the agreement actually requires, not against a general impression that things are broadly in order. Second, a party cannot always rely on a condition it was itself responsible for and failed to pursue; agreements and general principles may limit that. The mechanics — who does what, by when, and to what standard — are contractual, and this guide describes the shape of them rather than prescribing any particular formulation.

Sometimes — but not always, and never as a blanket rule. Whether a condition can be waived depends on its nature and on whom it protects. A contractual condition included for one party's benefit may, depending on the agreement and applicable law, be capable of being waived by that party, allowing the parties to proceed even though the condition has not been met. That is a decision for the beneficiary of the condition, exercised on the terms the agreement provides.

A mandatory legal or regulatory requirement is different, and this is where the distinction bites hardest. The parties cannot make a mandatory requirement optional simply by describing it as waived. The competition-clearance standstill is the clearest example: because it is suspensive and mandatory under Article 12 of Law 104-12, the parties cannot agree between themselves to waive it and complete before authorisation. A waiver letter does not cure a missing regulatory clearance, and it does not make a prohibited step lawful.

So the safe formulation is deliberately qualified: whether a condition can be waived depends on the type of condition and on whom it protects; a mandatory legal or regulatory requirement is not something the parties can waive away. It is simply wrong to say, without qualification, that conditions precedent can be waived. Some can, by the party they protect and on the agreed terms; others — the ones the law controls — cannot.

The interim period is the gap between signing and completion, and it is the space the conditions live in. During it, the parties are already bound to the deal, the conditions are pursued, and the agreement usually regulates how the company is to be run in the meantime — typically requiring it to be operated in the ordinary course and restricting certain out-of-the-ordinary actions without the buyer's agreement, so the business the buyer contracted for is broadly the business it receives. Information-sharing, access and cooperation to obtain approvals commonly feature as well.

These interim undertakings are important, but they are a distinct subject with its own home. How pre-closing covenants and gap-period controls are structured — what the company may and may not do, what needs consent, how the ordinary-course obligation is framed — belongs to the share transfer agreement guide, which owns the agreement's undertakings. This guide treats the interim period only as the bridge across which conditions are satisfied, not as a full account of interim covenants.

The process point is that the interim period is active, not passive. It is when filings are made, consents chased, corporate approvals passed and problems cured, all against the long-stop date discussed below. If the conditions are worked through, the parties reach a point where they can complete; if they are not, the failure mechanics come into play.

A long-stop date is a contractual backstop: a date by which the outstanding conditions must be satisfied or waived, failing which the agreement provides for defined consequences. It is a creature of transaction practice, not a statutory Moroccan M&A deadline — there is no rule of Moroccan law that sets it. Its function is to stop the interim period running indefinitely, by giving the parties a point at which the position has to be resolved one way or the other.

What the long-stop date actually does when it arrives depends entirely on the agreement. Some agreements allow the date to be extended, often where a particular condition (a regulatory clearance, say) is close but not yet obtained; some give one or both parties a right to walk away if conditions remain unsatisfied by then; some combine the two. The date is tied to the state of the conditions: it matters precisely because conditions are still open as it approaches.

The cautions are to avoid importing consequences the contract has not created. A long-stop date does not automatically terminate the agreement, and it is not a legal deadline that operates of its own force; whether termination, extension or something else follows is a contractual question. This guide explains the function of the long-stop date and does not offer any model wording for it.

There is no single automatic answer: what happens depends on the nature of the condition, on what the agreement provides, and on mandatory law. It is wrong to assume that the failure of a condition automatically terminates the agreement. The consequences are whatever the parties built in — and, where a legal or regulatory requirement is in play, whatever the law dictates — read together.

It helps to separate two lines. On the contractual side, an unsatisfied condition may trigger whatever the agreement provides: a right to extend the long-stop date, a right for the protected party to waive the condition and proceed (where waiver is available), a right for one or both parties to terminate, or an obligation to keep pursuing satisfaction. Which of these applies, and to whom, is set by the contract. A condition may also be capable of being waived by the party it protects, so that its non-satisfaction is not fatal at all.

On the mandatory-law side, the situation can be categorically different. If completion would breach a legal requirement — a refused competition clearance, for example — the barrier is not a contractual condition that has simply lapsed; it is a prohibition on completing, which the parties cannot override by agreement. A legal impossibility or prohibition is not the same as a negotiated condition falling away, and the two should not be run together. In both lines, the honest position is that the outcome is determined by the specific agreement and the applicable law, not by a general rule.

Preparation for closing is largely a matter of confirming that the deal is ready to be completed: that the conditions are satisfied or duly waived, that the required approvals and consents are in hand, and that the documents and steps to be dealt with on the day are identified and organised. In practice this is often managed through a closing memorandum or agenda — a working document that lists what has to be done, in what order, and by whom — used to run the completion smoothly.

A closing agenda of this kind is a transaction-management tool, not a legal instrument and not a fixed Moroccan requirement. Its content is entirely deal-specific: it reflects the particular company, the conditions in the particular agreement, the deliverables the particular parties have agreed, and the structure of the particular transaction. It is a way of organising the day, and different deals organise it differently.

The important caution is that readiness is judged against the actual agreement, not against a generic idea of what a closing should contain. A checklist or agenda helps the parties keep track, but it does not itself create obligations or guarantee that everything required by law and by the contract has been done. Its usefulness is organisational; the substance comes from the agreement and the applicable law.

At a conceptual level, a closing is usually organised as a sequence: the parties confirm that the conditions are satisfied or waived; confirm that the required approvals and consents are in place; confirm that the agreed deliverables are ready; execute and exchange the closing documents; deal with the payment and funds-flow steps; implement the corporate and transfer steps; confirm that completion has occurred; and note the actions that remain to be done afterwards. Presented this way, the sequence shows how the pieces fit together on the day.

This is transaction organisation, not a statutory choreography — Moroccan law does not prescribe a fixed closing sequence, and the order and content vary from deal to deal. Two things are deliberately kept high-level here. The funds-flow is described only as a process step; the detailed price mechanics (how the price is fixed, adjusted or paid over time) are a separate subject. And where the transaction uses security such as an escrow, its role is mentioned only as a possible closing/funds-flow item — the way escrow protects the buyer against later liabilities is owned by the seller liability protection (GAP) guide.

The caution is not to treat the sequence as a template. It is a way of thinking about how a completion can be run, useful precisely because it is adaptable; it is not a legal-document form and not a fixed set of steps that every Moroccan closing must follow. This guide describes the shape of a closing and provides no drafting.

This is the point most worth getting right, and it is where cross-border assumptions most often go wrong. The contractual moment the parties call closing is not automatically the moment at which ownership of the shares transfers with full legal effect against everyone. Closing is when the parties implement the agreed completion steps; the legal effectiveness of the transfer, and its opposability to the company and to third parties, follow the formalities Moroccan law attaches to the relevant company form.

Those formalities are not the same for every company, and they are the province of the share transfer agreement guide, which sets out how validity, opposability and registration differ and how a SARL and an SA are treated differently. The essential process consequence is only this: completing the closing steps is necessary, but the transfer takes its full legal effect through those statutory formalities — so the closing date and the moment of complete legal effectiveness are not always one and the same, and it is a mistake to assume that signing, or even closing, transfers ownership automatically regardless of the required steps.

The practical takeaway is to distinguish the contractual event from the legal effect. At closing, the parties do what the agreement says; whether and when the transfer is fully effective and opposable is a separate question answered by company law and the applicable formalities, not by the parties' label of "closing." This guide flags the boundary and points to where the effectiveness doctrine is developed; it does not re-derive it.

Where signing and closing are separated, the agreement may require the seller's statements about the company to be reaffirmed at completion — that they remain accurate, or accurate in a defined way, as at the closing date — sometimes as a condition to the buyer's obligation to complete. In deal vocabulary this reaffirmation is called a bring-down, and it is the closing-side interface with the seller representations and warranties that the deal contains.

For the closing process, the point is limited and specific: a bring-down, where used, is a way of testing at completion that the position stated earlier still holds, and it may be tied to a closing certificate or made a condition. Whether an agreement uses one at all, and what it is tied to, is negotiated — not every deal has a bring-down.

What this guide does not do is reproduce the substance of the seller's statements — what they cover, how disclosure qualifies them, how knowledge and materiality work, or what follows if one is inaccurate. That analysis is owned by the representations-and-warranties guide and is only cross-referenced here. The closing guide's interest stops at the interface: the statements can be brought down to completion, sometimes as a condition, and the detail lives elsewhere.

Completion is usually not the very last step. A number of matters commonly fall to be dealt with after closing, and they are noted here only as a bridge. Corporate records and commercial-registry entries may need updating, and register entries completed, so that the transfer is properly reflected and opposable — the effectiveness dimension of which is, again, owned by the share transfer agreement guide. Registration (enregistrement) of the transfer deed within the applicable delay is a further formality; this guide does not state rates or periods.

For cross-border deals there is a foreign-exchange dimension that is frequently misunderstood. Reporting the financing of the investment to the Office des Changes chiefly serves to preserve the later repatriation of proceeds and revenues; it is generally a post-closing reporting and repatriation-enablement formality rather than a universal condition that must be cleared before closing. It should not be described as an approval every acquisition needs before completion, and this guide gives no filing instructions or figures.

The theme is that closing and complete legal and administrative finality are not always the same instant. Some steps are inherently after-the-fact, and the deal will provide for them. This guide keeps the post-closing treatment to a bridge; it is not a post-closing compliance manual, and the substantive homes for the effectiveness, tax and reporting points are noted rather than reproduced.

The role is not fixed; it depends on the transaction, the company and what the deal requires. Broadly, the work of a lawyer admitted in Morocco around conditions and closing may involve identifying which conditions are contractual and which reflect legal or regulatory requirements, checking that the way conditions are framed matches what actually has to be obtained, and confirming that satisfaction is properly evidenced against what the agreement requires.

Where relevant, that involvement may extend to considering whether a regulatory clearance or corporate approval applies to the particular deal, helping organise the closing so the steps are taken in a workable order, and confirming that the actions bearing on the transfer's effectiveness and opposability are addressed. 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 common search is for a ready-made Moroccan closing checklist, and it is worth being direct about why this guide provides none. There is no universal Moroccan closing checklist, because what a closing requires is exactly what a generic form cannot know: the company's legal form, its statutes, the sector it operates in, whether a regulatory clearance applies, which consents its contracts require, how the particular agreement defines its conditions and deliverables, and how the transaction is structured. Change any of those and the required steps change with them.

A generic form can show the general shape of a closing, but it cannot set the right conditions, the right deliverables or the right sequence for a specific Moroccan transaction — and a checklist that looks complete can quietly omit the very step that matters, or include steps that do not apply, in a way that is worse than having no list at all. A reused list can also give false comfort that a mandatory requirement has been handled when it has not. That is why this guide explains how the process works and deliberately provides no template, no model closing agenda and no drafting.

To be explicit about the limits: this guide explains the signing-to-closing process, not the whole transaction. It does not reproduce the share purchase agreement or its transfer-effectiveness doctrine, walk through the acquisition process, set out the due-diligence method, develop the seller's representations and warranties, or explain the economic-consequence mechanics owned by the garantie d'actif et de passif.

It is not a merger-control guide and states no competition thresholds, turnover tests or filing procedure; it does not develop price mechanics such as locked-box or completion accounts; and it does not set out change-of-control regimes contract by contract. It provides no tax, accounting or regulatory advice and no template, model clause or closing checklist. 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.