1. Introduction

Digital Obligation Tracking Systems in Morocco refer to the use of electronic platforms, databases, automated reminders, digital signatures, document-management tools, and compliance-monitoring software to record, monitor, verify, and enforce civil-law obligations.

These systems can help individuals, businesses, financial institutions, landlords, contractors, and public-facing service providers manage obligations arising from contracts, payments, property transactions, commercial relationships, and civil liability.

The central legal question is whether a digital system can reliably establish what obligation exists, who must perform it, when performance is due, whether performance occurred, and what legal consequences follow from non-performance.

Morocco's legal framework provides several relevant foundations, particularly:

The Moroccan Code of Obligations and Contracts (Dahir formant Code des obligations et des contrats), which governs contractual obligations, performance, liability, and damages.

Law No. 53-05 on electronic data exchange in legal transactions, which introduced important rules concerning electronic transactions and electronic documents.

Law No. 43-20 on trust services for electronic transactions, which modernizes the framework for electronic signatures and related trust services.

Law No. 09-08 on the protection of individuals with regard to the processing of personal data.

The Moroccan Code of Civil Procedure and applicable evidentiary rules governing litigation, proof, and enforcement.

A digital tracking platform does not automatically create a legally binding obligation. Its legal effect depends on the underlying contract, applicable legislation, the reliability of the records, and the rules governing evidence and enforcement.

2. Meaning and principal functions

A Digital Obligation Tracking System (DOTS) is a technical and administrative system designed to follow civil obligations throughout their lifecycle.

How the system works

1. Obligation creation

Contract, court order, lease, loan, or service agreement

2. Digital registration

Parties, terms, deadlines, supporting documents, and responsible persons

3. Monitoring and verification

Reminders, payment records, delivery confirmations, and performance evidence

4. Breach detection and remedies

Overdue notices, requests for performance, dispute review, and potential legal proceedings

The system should distinguish between a recorded event and a legally established fact. For example, an automated notification may show that an email was generated, but it does not necessarily prove that the recipient legally received a demand for performance.

3. Legal framework in Morocco

A. Code of Obligations and Contracts

The Moroccan Code of Obligations and Contracts (DOC) is the principal legal foundation for ordinary contractual obligations.

It addresses matters including:

Formation and validity of contracts.

The binding effect of contractual commitments.

Performance in accordance with agreed terms.

Delay, non-performance, and contractual liability.

Compensation for legally established damage.

The consequences of a party's failure to perform.

A tracking platform can translate contractual provisions into operational fields, such as a payment deadline, a delivery milestone, a maintenance duty, or a reporting obligation. However, software-generated status labels cannot replace the legal analysis required to determine whether a breach actually occurred.

For example, a system may classify a payment as overdue on the day after a scheduled deadline. The legal consequences may nevertheless depend on the contract, applicable rules on notice or formal demand, any agreed grace period, and the circumstances preventing performance.

B. Electronic transactions and signatures

Law No. 53-05 established an important framework for electronic data exchange in legal transactions. Law No. 43-20 subsequently developed Morocco's framework for electronic trust services.

These laws are relevant to electronic contracts, signed records, authentication, and the reliability of electronic evidence.

For obligation tracking, the practical issues include:

Whether the electronic document is attributable to the relevant person.

Whether the signature satisfies the applicable legal requirements.

Whether the record has remained complete and unaltered.

Whether the system can establish the date and sequence of relevant events.

Whether the document meets any special formalities required for the transaction.

A scanned signature, a typed name, an authenticated electronic signature, and a qualified electronic signature should not be assumed to have identical legal effects.

C. Personal data protection

Law No. 09-08 is relevant where obligation-tracking systems process names, contact details, payment histories, identification information, employee records, or records of alleged non-compliance.

Organizations should assess the lawful basis and purpose of processing, data minimization, security, access controls, retention periods, and applicable obligations involving Morocco's National Commission for the Control of Personal Data Protection (CNDP).

Automated risk scores or breach alerts should also be reviewed for accuracy. A mistaken flag can cause financial or reputational harm, particularly if it is circulated to lenders, business partners, employers, or collection agencies.

D. Civil procedure and enforcement

Digital records may help prove that an obligation was created, that a payment was made, or that a communication was sent. However, the ability to obtain a judgment or execute against a debtor remains governed by applicable substantive and procedural law.

A private tracking system cannot independently exercise judicial authority, create an enforceable court order, or bypass legally required enforcement procedures.

4. Six important legal issues in digital obligation tracking

A. Tracking contractual deadlines

A system should record the precise date by which a party must perform an obligation. This is especially important for payment, delivery, repairs, installation, and recurring contractual services.

Under Articles 230 and 255 of the Moroccan Code of Obligations and Contracts, the binding effect of contracts and the consequences of an agreed deadline are important considerations. Article 255 addresses when a debtor is placed in default.

Practical example: A supplier agrees to deliver equipment by 15 November. The system records the deadline, stores delivery evidence, and flags a delay. The legal team then determines whether the delay triggers a penalty, damages, or another contractual remedy.

B. Recording performance and partial performance

The system should allow a party to upload invoices, receipts, signed delivery records, inspection reports, and acknowledgments.

The distinction between full and partial performance is essential. A debtor who has paid only part of an amount should not be recorded as having fully discharged the debt.

C. Sending notices and demands

A tracking platform can generate notices, but the validity of a notice depends on the relevant legal rules and contractual terms.

Where formal demand is required, the system should preserve the notice's contents, recipient, dispatch details, proof of receipt, and any applicable response period. Automated delivery indicators should not be treated as conclusive proof of legally effective service.

D. Preserving electronic evidence

Digital evidence must be capable of verification. Useful safeguards include:

Secure timestamps and audit logs.

Records identifying the person who created or changed an entry.

Preservation of original emails and attachments.

Document integrity checks and controlled access.

Backups and documented retention procedures.

E. Identifying breach and calculating remedies

A system can flag a possible breach, calculate a contractual penalty according to an agreed formula, and estimate unpaid balances. However, it should not automatically conclude that a party is legally liable.

The assessment may require consideration of excuses for non-performance, reciprocal obligations, the wording of the contract, causation, and the actual loss suffered.

F. Protecting privacy and procedural fairness

Obligation records may contain confidential commercial information and personal data. Access should be restricted according to role, and disputed entries should be open to correction and review.

A party should have a meaningful opportunity to challenge an inaccurate record before it is used to justify termination, debt collection, or litigation.

5. Moroccan case law: at least six relevant decisions

Important scope clarification: The decisions below concern electronic evidence, contractual performance, default, notices, and remedies. They provide legal principles relevant to digital obligation tracking by analogy. They should not be understood as six judgments directly approving digital obligation-tracking software. The reported case references are included to help distinguish the actual judicial decisions from the proposed technological applications.

Case 1. Court of Cassation, Commercial Chamber — Decision No. 250/1, 6 June 2013

Case file: 2012/1/3/894

Subject: Evidentiary value of electronic correspondence.

Legal principle: The Court of Cassation accepted the evidentiary significance of emails identifying their author and acknowledging a commercial obligation, despite the absence of a conventional handwritten signature or formal electronic signature.

Relevance to obligation tracking: A platform may rely on email correspondence to record an acknowledgment of commission, a payment commitment, or acceptance of a contractual duty. The record should preserve the original communication and evidence identifying its author.

Limitation: This decision does not mean that every email automatically proves a contract or debt. Authenticity, content, context, and applicable evidentiary rules remain relevant. The decision is reported under the case number and date stated above.

Case 2. Court of Cassation, Commercial Chamber — Decision No. 196/1, 1 April 2021

Case file: 2021/1/3/165

Subject: Contractual deadline, delay in delivery, and default.

Legal principle: The reported decision applies Articles 230 and 255 of the Code of Obligations and Contracts. Where the agreed performance deadline has expired, the debtor may be in default by virtue of the deadline itself. The decision also addressed the application of a contractual penalty for delayed delivery.

Relevance to obligation tracking: The platform should distinguish between a deadline that has passed and a case requiring a separate formal demand. It should also preserve the agreed delivery date and the actual delivery date.

Practical application: If delivery was due on 15 November but occurred on 25 November, the system can calculate the ten-day delay. The legal team must then verify the penalty clause and any relevant defences before applying it.

Case 3. Court of Cassation, Commercial Chamber — Decision No. 427/1, 1 October 2020

Case file: 2020/1/3/256

Subject: Formal notice and the effectiveness of service.

Legal principle: The reported judgment considered a formal demand served through a judicial officer. It held that service could be valid where it achieved its purpose of informing the debtor of the alleged non-performance, notwithstanding a contractual provision specifying another notification method.

Relevance to obligation tracking: A platform should record the actual method of service, the contents of the notice, and evidence that the recipient was informed. A system should not assume that sending a digital message is equivalent to legally effective service.

Practical application: A platform can generate a draft notice and record the service details, while a lawyer or authorized officer determines whether the chosen method satisfies the applicable legal requirements.

Case 4. Court of Cassation, Civil Chamber — Decision No. 4115, 16 November 2009

Case file: 2744/1/5/2008

Subject: Contractual non-performance and judicial termination.

Legal principle: The reported decision concerned a promise of sale and the remedies available for non-performance. It rejected an interpretation that would permit contractual termination only when performance had become impossible.

Relevance to obligation tracking: A system must not restrict its breach-management process to situations in which performance is impossible. Depending on the applicable law and contractual circumstances, non-performance may support a claim for performance, termination, or damages.

Practical application: Where a seller fails to meet a contractual obligation, the system should flag the default and preserve the relevant documents. It should present possible remedies for legal assessment rather than automatically terminating the agreement.

Case 5. Court of Cassation, Commercial Chamber — Decision No. 2/324, 30 June 2016

Case file: 2014/2/3/1475

Subject: Contractual non-performance, burden of proof, and judicial reasoning.

Legal principle: The reported decision concerned a dispute over the performance of a service contract and the reasoning required when deciding allegations of contractual breach.

Relevance to obligation tracking: A status such as “not completed” is not sufficient, on its own, to establish legal liability. A robust system should store evidence supporting each party's position, including proof of performance, objections, requests for correction, and communications about disputed work.

Practical application: If a software supplier claims that it completed installation but the customer alleges that staff training was omitted, the platform should maintain separate records for installation and training rather than treating the entire contract as completed.

Case 6. Court of Cassation, Civil Chamber — Decision No. 5731, 27 December 2011

Case file: 1615/1/7/2010

Subject: Reciprocal obligations and expiry of a contractual period.

Legal principle: The reported decision concerned a conditional promise of sale and mutual obligations. It addressed the consequences of non-performance when the period specified by the agreement expired.

Relevance to obligation tracking: A system must record dependencies between obligations. For example, a buyer's payment obligation may depend on the seller first satisfying a contractual condition. Recording only the payment deadline without the related condition can produce a misleading default alert.

Practical application: The system should distinguish between an unconditional obligation, a conditional obligation, and a reciprocal obligation that depends on the other party's performance.

The case references and summaries above correspond to reported Moroccan judicial decisions on electronic proof and contractual obligations. Their application to modern digital tracking systems is analytical rather than a claim that the courts considered those systems directly.

Case 7. Court of Cassation, Civil Chamber — Decision No. 75-7-2013, 26 February 2013

Case file: 883-1-7-2012

Subject: Contractual termination clause and failure to perform.

Legal principle: The reported decision applies Article 260 of the Code of Obligations and Contracts, which addresses agreements providing for termination upon non-performance.

Relevance to obligation tracking: Where a contract contains a legally effective termination clause, a tracking system can identify the relevant trigger and notify the parties. It should nevertheless verify the clause's wording, the nature of the breach, and any applicable legal requirements before recording the contract as terminated.

Practical application: A property-sale tracking system could flag that a seller has failed to complete agreed subdivision or registration steps by the specified deadline. It should preserve the evidence and refer the termination question for legal review.

Case 8. Court of Cassation, Commercial Chamber — Decision No. 510, 8 April 2009

Case file: 1282/3/2/2007

Subject: Extinction of obligations and novation.

Legal principle: The reported judgment explains that novation—the replacement of an existing obligation with a new one—is not presumed merely from the parties' conduct. Their intention and the required written evidence must be examined under the applicable rules.

Relevance to obligation tracking: A new payment schedule, revised contract, or restructuring agreement should not automatically overwrite the original obligation in the system. The platform should preserve the earlier record, the amendment, its authorization, and the effective date.

Practical application: If a creditor agrees to restructure a debt, the platform should identify whether the parties amended payment dates or intended to replace the original obligation. The legal effect must be determined from the actual agreement and applicable law.

These additional decisions reinforce a central principle: digital systems must preserve the legal history of an obligation rather than simply replace an old status with a new one.

6. Proposed architecture for a Moroccan digital obligation tracking platform

A well-designed platform should contain the following modules.

Obligation registry

Stores the contract, parties, amount, deadlines, conditions, applicable law, and required formalities.

Deadline and reminder engine

Tracks milestones, payment schedules, recurring duties, cure periods, and notice deadlines.

Evidence and authentication module

Preserves electronic signatures, document versions, acknowledgments, timestamps, and audit trails.

Breach and dispute module

Flags missed deadlines, records objections, calculates provisional amounts, and refers contested matters for review.

Privacy and access control

Applies role-based permissions, retention policies, security measures, and procedures for correcting inaccurate records.

7. Practical example: tracking a construction contract

Suppose a Moroccan construction company agrees to complete a building project for MAD 1,000,000. The contract specifies three milestones and a contractual penalty for unjustified delay.

The platform would operate as follows:

Registration: Store the signed contract, the milestone schedule, the penalty clause, and the identities of the parties.

Monitoring: Send reminders before each milestone and request supporting evidence.

Verification: Record the engineer's report and any objections by the customer.

Breach alert: Flag a missed deadline or incomplete work without automatically declaring liability.

Legal review: Determine whether the delay is attributable to the contractor and whether a contractual penalty or other remedy is available.

Resolution: Record any agreed extension, settlement, amended deadline, or judicial decision while preserving the original audit trail.

This approach reduces administrative errors and creates a more complete record if litigation later becomes necessary.

8. Principal legal challenges in Morocco

A further challenge arises when tracking software uses artificial intelligence to predict default. A prediction that a debtor is likely to miss a payment is not proof of a breach. The platform should distinguish predictive risk, verified non-performance, and a legally established liability.

9. Recommendations for implementation

For businesses and legal professionals adopting such systems in Morocco, the following measures are particularly important:

Map each obligation to its legal source. Record whether it arises from a contract, statute, court judgment, or another legally recognized source.

Define the trigger precisely. Distinguish a deadline, a condition precedent, a formal demand, and an event that requires acceptance by another party.

Use reliable electronic trust services. Apply appropriate electronic-signature, timestamping, and delivery services under the relevant Moroccan framework.

Maintain immutable audit history where appropriate. Corrections should be recorded transparently instead of silently overwriting earlier entries.

Separate administrative alerts from legal determinations. A software alert should initiate review, not automatically impose liability.

Design for privacy and security. Review the processing of personal data under Law No. 09-08 and relevant requirements administered by the CNDP.

Preserve litigation-ready evidence. Maintain original documents, transaction histories, relevant metadata, and records of communications in a form that can be retrieved and authenticated.

10. Conclusion

Civil Law and Digital Obligation Tracking Systems in Morocco bring together contractual law, electronic transactions, evidence, data protection, and civil procedure. Their principal benefit is the ability to make obligations visible, measurable, and easier to administer throughout their lifecycle.

Moroccan law already provides relevant foundations through the Code of Obligations and Contracts, Law No. 53-05, and Law No. 43-20. The cited judicial decisions illustrate how courts approach electronic proof, deadlines, default, formal notices, contractual remedies, and the preservation of existing obligations.

The decisive principle is that digital tracking supports legal compliance but does not replace legal judgment. A system is most useful when it produces accurate records, preserves evidence, identifies potential breaches, protects personal data, and allows contested matters to be reviewed under Moroccan law.

Research note: The judicial decisions discussed above are identified by their reported decision numbers and dates. Their relevance to digital obligation tracking is principally analogical; they should not be presented as direct rulings on tracking software. For formal legal submissions, verify the full judgments and current statutory texts.