Georges Abou Mrad
Lawyer
I stopped keeping a parallel notebook. When a client questions a figure now, I open the matter and the answer is already there with a date on it.
Matters, conflicts, billing and payments on one record the firm can prove. Built natively for English, Arabic and French practices.
The language switcher above is live for this section. The entire platform operates in all three languages, genuinely mirrored.
A client exists in one system. The matter in another. The correspondence in personal mailboxes. The hearing on a wall calendar. The billing in accounting software. The payment in a bank statement. And the proof in someone's memory.
One matter. Seven places. One dispute. The scatter is exactly why there is no record when it matters.
Because the modern law firm produces enormous amounts of information, but very little of it remains connected. We did not build Mersal to give lawyers more buttons to click. We built it because when a dispute arises, when an audit lands, or when a partner must account for a file, memory is not evidence.
The conflict, on the record.
The invoice, on the record.
The receipt, sealed, on the record.
Mersal connects the record.
The matter is not a folder. It is the sovereign unit of your practice.
Not a screenshot. The actual document structure Mersal produces in the language your client reads. Arabic is the hardest test of layout engineering, and the one most systems fail.
| DESCRIPTION | QTY | AMOUNT |
|---|---|---|
| Articles of association drafting | 1 | $3,500.00 |
| Court filing fees, disbursed at cost EXEMPT | 1 | $1,200.00 |
| البيان | الكمية | المبلغ |
|---|---|---|
| صياغة النظام الأساسي للشركة | 1 | $3,500.00 |
| رسوم قضائية مدفوعة بالنيابة معفاة | 1 | $1,200.00 |
| DÉSIGNATION | QTÉ | MONTANT |
|---|---|---|
| Rédaction des statuts de société | 1 | $3,500.00 |
| Frais de justice, débours EXONÉRÉ | 1 | $1,200.00 |
The events Mersal records become part of an append-only operational record†BEFORE UPDATE and BEFORE DELETE triggers reject changes to recorded events, for every role, including administrators., enforced by database triggers that reject modification or deletion.
| 09:42:11 | CLIENT_CREATED | Cedar Star Shipping Ltd. added to firm register |
| 09:42:19 | CONFLICT_SCREEN_CLEARED | 6 related entities verified across register · 0 flags |
| 09:44:03 | MATTER_APPROVED | Authorized by Managing Partner R.H. · MAT-2026-089 activated |
| 11:16:42 | INVOICE_COMMITTED | INV-2026-0041 serial assigned · per-line VAT rules frozen |
| 14:32:08 | DOCUMENT_VIEWED | Client opened secure link · IP and user agent recorded |
| 14:32:14 | RECEIPT_ACKNOWLEDGED | Digital acknowledgment stamped server-side on invoice record |
| 16:08:31 | SETTLEMENT_RECORDED | Bank transfer confirmed · ledger updated · idempotency key checked |
| 16:08:32 | RECEIPT_SEALED | RCP-2026-0412 minted · permanent serial · immutable |
From intake to the moment settlement is certified. Re-created step by step from the product's actual flow.
He swears the invoice never arrived. You have a sent folder from a personal inbox, and his word against yours.
Two years into the file, the counterparty surfaces as a director of your oldest client. Nobody checked, and nothing says anybody did.
She asks why an exempt service sits in the VAT register, and who modified the rate after issue. On paper, the answer is your memory.
The danger is not that the work was not done. The danger is proving that it was.
Most legal software is sold as a list of modules. What a practice actually buys is a way to stop losing the thread between a client, a colleague and a file. This is the whole path, in order.
None of these are software problems on their own. Together they are the reason a firm cannot answer a simple question quickly.
You answer from memory, or you go looking. Three places later you are still not certain, and the client is still waiting.
THE ANSWER ARRIVES LATEHours were worked. Nothing was recorded against the matter. It surfaces at billing time, or it never surfaces at all.
WORK BILLED AT A DISCOUNT TO REALITYThe document exists. Locating it is a separate task, and only one person knows the folder logic.
RETRIEVAL BECOMES A FAVOURA deadline was agreed by email, in a personal mailbox nobody else can open. The firm cannot see what it promised.
THE FIRM CANNOT READ ITS OWN WORDOne person was told. The calendar was never updated. Everyone else learns on the day, or after it.
A DATE MISSED BY COORDINATIONIt was sent, allegedly. There is a sent folder and a silence, and no way to tell them apart.
NO PROOF, ONLY A SENT FOLDERWhich matters are exposed, what is unbilled, who is waiting on us. No report exists, so someone spends the evening building one.
GOVERNANCE BY RECONSTRUCTIONThe check happened, informally, and left no trace. When it is questioned, there is nothing to produce.
A CLEARANCE YOU CANNOT EVIDENCEConfiguration happens at the start and holds. Nothing here is repeated per matter.
Name, working currency and tax profile. The books are opened with their numbering rules already fixed.
Partners, associates, paralegals and billing staff. The role decides the reach, and the database enforces it.
Designate one folder in Gmail or Outlook. Everything outside it is never read and never stored.
VAT per service, invoice numbering, letterhead, signature, and how early each reminder should fire.
Import the client list in one pass, or enter clients individually. Conflicts index as they arrive.
The conflict screen runs before the matter exists. The clearance is recorded whichever way it resolves.
One ordinary day, and where each moment is written down.
Hearings, filing deadlines and tasks due, in your own local time†Times are stored as instants and rendered per member timezone. Reminder lead times are computed server-side, before the event., on one screen before the day starts.
Conflict pre-flight runs across directors, beneficial owners, counterparties and the historical register.
A partner approves it from the queue. The activation, and who authorised it, become part of the record.
The client reply is attached to the matter with one deliberate click. Private mail stays where it was.
A task with an owner and a due date, on the matter timeline where the partner can see it.
Recorded work drafts the invoice. VAT is ruled per line, the exchange rate freezes at issue.
First view is recorded server side. The acknowledgment is pressed, and that press is kept.
The receipt writes itself with its own serial and seals. No one can edit or delete it, including you.
Exposure, unbilled work, who is waiting. The answer is a screen that was already true.
The complete instrument list. Every item below is a working part of Mersal, not a roadmap entry.
| Specification | Conventional Practice Tools | Mersal Operating Record |
|---|---|---|
| Operational records | Distributed across disconnected tools | Connected to the sovereign matter record. |
| Issued invoices | Editable after dispatch | Frozen at issue. Corrections happen by auditable reissue.†Issued rows are locked by a database trigger. A correction is a new document with its own serial, and the original stays on the record. |
| Tax handling | One global rate applied to the whole bill | Per-line VAT. Standard and exempt lines file into distinct serial books. |
| Proforma estimates | Counted alongside real revenue | Isolated from revenue entirely until converted by authorized role. |
| Receipt certificates | Deletable bookkeeping rows | Sealed on payment with independent serial numbers. |
| Proof of delivery | An unverified sent folder | First view and client acknowledgment stamped server-side. |
| Language architecture | Superficial translation layer | Native trilingual engine (EN · AR · FR) with true right-to-left layout. |
Send from inside the matter, on your firm letterhead, with messages logged to the matter record. Receiving is equally disciplined: Mersal syncs only one designated folder from Gmail or Outlook. Your private correspondence, newsletters and unrelated emails never enter the firm database.
Corporate boards and institutional clients do not want complicated dashboards. Mersal provides a clean, authenticated space to review case submissions, verify court dates, inspect invoices, and access bank settlement details.
Court hearings, statutory deadlines and task commitments live on a unified schedule. Advance warnings escalate as a hearing approaches, keeping assigned fee earners aligned before a deadline passes.
| Specification | Implementation | Operational Benefit |
|---|---|---|
| Data isolation | PostgreSQL Row-Level Security | Firm and matter rows isolated at the database engine level.†Row-Level Security policies filter every query by firm and role. There is no application-side bypass. |
| Audit trail | Append-only event triggers (BEFORE UPDATE/DELETE) | Trigger rejects alteration or deletion of recorded audit rows. |
| Fiscal documents | Frozen snapshots at issue | Currency, tax rates and exchange rates frozen onto the row. |
| Reception evidence | Server-recorded view and acknowledgment stamps | Delivery timestamps logged server-side via service role. |
| Document security | SSRF-hardened PDF compilation | Restricts image embeds to verified storage hosts, blocking internal network queries. |
| Statutory alignment | Data protection & electronic transaction design | Engineered to GDPR-grade data-protection and electronic-transaction principles. |
Supervise firm-wide matter health, billable realization, upcoming hearings, and risk exposure without waiting for manual reports.
Work directly from the sovereign matter context instead of piecing together fragmented email threads and shared drives.
Receive dignified, clear documentation in their language, with transparent billing breakdowns and verified settlement certificates.
Lawyers, auditors, researchers and founders who run their work on Mersal.
What is written remains.
What remains can be proven.
In 30 minutes, we will run it through Mersal together. Conflict screening, matter creation, procedural docketing, document generation, and settlement verification. Experience your own workflow on an immutable record.
No sales presentation. We configure the session around your firm's typical matter structure.
Any firm can ask for it. We migrate your historical dossiers by hand, configure jurisdiction-specific tax books, and train every fee earner in their working language. No generic setup. A partner from our team is involved throughout.
Your client registry, matters and documents imported with their relationships intact.
Jurisdiction-specific serial books for VAT-subject, exempt and proforma documents.
Every fee earner trained in English, Arabic or French depending on their working language.
Run one real matter alongside your current tools before moving further files across.
No. PostgreSQL triggers reject UPDATE and DELETE operations on the audit tables for all database users. A corrected invoice is reissued, leaving the prior record visible in the ledger.
No. Mailbox synchronization is scoped to one designated label in Gmail or one folder in Outlook. Correspondence outside that folder never syncs to Mersal and never leaves your email provider.
Multi-sheet Excel workbooks separated into Subject to VAT, Exempt from VAT, Proforma, and Payables, plus print-ready master ledgers. Proformas and unissued drafts are separated from revenue by design.
The client receives an invoice in the agreed billing currency. The applicable exchange rate freezes onto the document at issue, calculating the converted tax reporting amount permanently.
Arabic is native to the architecture: true right-to-left orientation across every screen, authentic regional legal terminology, and bilingual document rendering.
Clients review invoices in the portal alongside your firm's bank settlement details. When payment is received, firm billing staff record the settlement, which seals an immutable receipt certificate with its own independent serial number.