Mandato vs Clio: an honest comparison (2026)

A Spanish litigation practice receives its court notifications through LexNET. This isn't a preference; it is the channel. Every notification carries a deadline, and every miscounted deadline is a professional liability problem.

Clio does not connect to LexNET. A firm using Clio will still open LexNET separately, download the ZIP, file the document into the matter by hand and copy the date into the calendar by hand. The practice-management system does not know the notification exists.

In Mandato the notification reaches the matter by proceeding number, the deadline is calculated and appears in the calendar, and the matter's team is notified. And it doesn't stop at receiving: written submissions are filed through LexNET from the matter itself, too.

From 1 January 2027 for companies, and from 1 July 2027 for the self-employed and all remaining taxpayers, a Spanish firm's invoicing must comply with RD 1007/2023: chained records, signature, submission to the AEAT and a verifiable-invoice QR code on every invoice raised. 2026 is the voluntary period — arriving at the deadline without a system is not an option, and it does not tolerate a spreadsheet in the middle.

Clio invoices, and invoices well, but it has nothing to say about VeriFactu. A Spanish firm on Clio has to resolve compliance somewhere else, with its practice-management system unaware the obligation exists.

Mandato raises the invoice from the matter that generated it — retainer requests, proformas, fixed fees — with chained records and a QR as standard, ready for VeriFactu. If the firm's books live in Holded, the invoice exports there.

Clio logs client communications and has a portal — it's a good product at that, and we won't pretend otherwise. What it doesn't have is WhatsApp Business tied to the matter, and for a Spanish firm with international clients that is the channel much of the conversation comes in on.

In Mandato, the firm's WhatsApp, email and calls converge into a single inbox per matter, from a firm-owned number onboarded via 360dialog. In Clio, that WhatsApp conversation still lives on a lawyer's phone, outside the system.

Add that Clio's templates aren't written in legal Spanish — as the row above already says — and the upshot is that, to talk to a Spanish or German client the way the firm wants to, you have to step outside Clio. In Mandato, you don't.

Translating an interface is easy. Writing a deposit contract, an engagement letter or a written submission that a Spanish lawyer will sign without rewriting is another matter entirely. Mandato's templates are written in Spanish and in English by lawyers, not translated.

It's worth being precise here, because this is where a dishonest comparison would overreach. Clio isn't worse at bilingualism: its product simply isn't built for Spanish law, nor does it need to be. And in the other direction, Mandato has neither Clio's integration ecosystem nor its analytics, and probably never will at that level.

For a firm practising in Spain with international clients, the choice comes down to which costs you more: giving up two hundred integrations, or giving up LexNET and VeriFactu.