Practice management for law firms worldwide

Built around the trust ledger.

Matters, time, billing and trust accounting — built so the ledger is defensible on the day somebody asks to see it.

Where it runs
Serving firms internationally. Hosted in Canadian regions.
Trust profiles
Ontario trust workflows, resolved per account. Other jurisdictions are reviewed during onboarding.
Languages
English and French throughout — money and date formats, not only labels.

Built in Canada. Working with law firms across the globe.

We now supply law firms around the world, with relationships in the U.S., Europe, the Middle East, East Africa and Japan.

  • United States
  • Europe
  • Middle East
  • East Africa
  • Japan

One place for the firm’s work, wherever its relationships take it. Jurisdiction-specific trust workflows and connected services are reviewed with each firm during onboarding.

A firm holds two kinds of money. Confusing them is professional misconduct, not a bug.

Operating money is the firm’s. Trust money is the client’s. Every list, every balance, every form and every receipt has to make which is which impossible to get wrong.

Two sheets of ruled ledger paper laid side by side, divided by a hard shadowed gap.

The treatment

Trust money never relies on colour.

A doubled edge, a hatched field and a TRUST · FIDUCIE label, everywhere it appears. Three signals, so the distinction survives a photocopy.

Beaulieu v. NadeauFees invoiced · bill 2026-0418
$4,120.00
Operating
Beaulieu v. NadeauRetainer held for the client Trust · Fiducie
$12,500.00
Trust

Greyscale is not an accessibility afterthought here. It is the test the treatment was designed against — it has to hold across a desk, on a printout, and for a colourblind reader.

A client’s balance cannot go negative.

Not per pooled account — per client, per matter. The rule lives in the ledger itself, so it is not a warning that can be dismissed, a setting that can be switched off, or a check that a future change could quietly skip.

The rule, as the ledger holds it

No matter’s trust balance may ever fall below zero. A withdrawal that would breach it is refused before it is written.

Held per matter rather than per client, which is stricter than the regulation asks: if every matter is whole, every client is. Two disbursements raised at the same moment are settled in order rather than against the same stale figure, so the second one sees the first.

Electronic trust transfers need two people.

Requisition, authorisation, execution. The person who authorises can never be the person who requisitioned — the ledger refuses it outright, rather than trusting a policy.

  1. Requisition

    Someone raises the transfer: the client, the matter, the amount, the reason and an expiry.

  2. Authorisation

    A second person authorises it. If the two are the same person, it does not proceed.

  3. Execution

    Only then does the money move, and the record keeps who did each of the three acts.

pendingauthorisedexecutedcancelledlapsed

Required by LSO By-Law 9, s. 12.

Days remaining in the current 25-day reconciliation window
—
days

Reconciliation is a legal deadline.

Trust reconciliation is due within 25 days of month end, and cannot be completed while any unexplained difference remains. RYVO counts the days.

on timedue soonoverdue

The dial runs on your own clock against the real rule — it is the deadline, not a firm’s data.

Then it has to be faster than resenting it.

Ten to thirty time entries a day, and every one of them resented. The whole design question is how few seconds each one is allowed to cost.

Manual entry is built for a lawyer typing six entries in a row at five o’clock without touching the mouse.

Nobody records time while the work is happening.

So there are two ways in, and they are built to agree with each other. A timer, for work you are inside. A grid, for the day you are rebuilding from memory at five o’clock.

Several at once, and still there tomorrow

Start a timer from anywhere without leaving the page. Run as many as the day demands, because interruptions do not queue. Pausing banks the time instead of restarting it, and closing the tab does not end the clock — they are still counting when you come back.

A timer belongs to the day it began

One left running past midnight is recorded against the morning it started, not the small hours it was stopped in. The date is stamped once, at the start, and never worked out again afterwards.

It hands the time back rather than losing it

Stopped under a minute, it records nothing instead of inventing a minute. Naming no matter, it says so instead of disappearing. Every reason a timer cannot become an entry is put on the screen: a stop button that quietly drops twenty minutes of an afternoon is the failure nobody notices until the bill goes out short.

And the same hour cannot be billed twice

If time is already on the clock for that matter on that day, the grid says so before it saves. When a date falls outside the two weeks the screen is holding, it says the check did not run — rather than letting silence imply that it passed.

Catch-up gridKeyboard first
The shape of the catch-up grid: its columns, a running timer shown inline, and the three ways a duration may be typed.
DateMatterDescriptionDurationBillableValue
Mon Running timer 0:41
Mon 1.2
Mon 1:12
Tue 72m
Tab moves Enter adds a row ⌥↑ copies the row above 1.2 · 1:12 · 72m

Running timers appear in the grid, marked, so the hour already on the clock is not keyed a second time underneath it. A duration is read however a lawyer types it. An hour budget on the file warns; it does not refuse.

A rate that appears without its reasoning is a dispute waiting to happen.

Six levels, highest first. The product walks them and stops at the first that has a value. Every level stays on the screen, including the empty ones — hiding them would make the list look like the answer rather than the reasoning.

Where this rate came fromPress a row to set or clear it

WinsMatter rate

The shape of the walk, not a firm’s figures. No amounts, because the dispute is never about the number that appeared — it is about which level produced it.

Nothing is still a fee

A flat fee of nothing is set. It does not fall through to the next level, because treating zero as absent would bill a file that was meant to be included.

A typed rate stays put

A rate written on the entry survives a change of matter or of activity. Replacing it quietly would lose the figure the lawyer meant, and the next bill would carry a number nobody chose.

No rate does not become zero

If every level is empty, the entry has no rate. It is refused, not defaulted. Inventing a number so the row can save is how a bill goes out at the wrong figure.

Work becomes a bill, and the bill closes behind it.

Tick the unbilled work and it becomes bills — one for each matter, with any discount taken off before tax, because the tax follows the charge. From there the bill moves through five states, and what you may still change shrinks at every one.

01 draft 02 pending approval 03 approved 04 paid void, from anywhere before payment
What is still editable, by state.
Field Draft Pending Approved Paid Void
Line items editable editable closed closed closed
Dates editable editable closed closed closed
Discount editable editable closed closed closed
Note on the bill editable editable editable closed closed
Invoice number editable until the bill is first issued closed closed closed closed
Editable Editable until the bill is first issued Closed

Where a field is closed, the screen names the one move that would open it again — remove the payment, remove the approval, return it to draft — and names nothing at all when no move would. An explanation that offers a remedy which does not work is worse than no explanation.

The number is set once

A bill takes its number the first time it leaves draft, and keeps it — even if it goes back to draft and comes forward again. That is audit practice rather than a rule of the profession, and it is here as prudence, not as law.

Trust cannot pay a bill the client has not seen

Money held for a client settles the firm’s fees only once the billing has been delivered to them. Generated is not delivered; approved is not delivered.

Undoing happens on the record

Voiding leaves the bill in place with a void stamp, returns its work to unbilled, and does not reuse the number. Removing a payment is for a keying error only — no money moves, and it stays on file marked reversed. A credit note reverses the billing without touching the bill it came from.

The reminder is the invoice, again

Offsets live on the firm, or on the contact. When a due date is that many days away, the same invoice goes out with a fresh one-day portal link. A skip is logged. It does not invent a second letter.

22 reports. A clearer view of the whole firm.

Live figures for the firm, over the range you choose. An empty range stays empty — nothing is smoothed, carried forward or estimated so that a page looks finished.

Receivables, by age

What is owed · as at a date

Current
1–30
31–60
61–90
Over 90

Approved bills that still carry a balance, by days past due. Currencies are kept apart rather than converted at a rate nobody agreed to.

Issued, and collected

Revenue · over a range

Issued
Collected

Two different questions, kept apart. What the firm billed in the period, and what actually arrived in it — a single revenue figure quietly merges them.

The shape of each sheet, not a firm’s figures.

Who is producing

Productivity by person: the billable minutes recorded, and how much of that was actually billed. Task productivity sits beside it. A lawyer opening the same report sees their own row and nobody else’s — the narrowing happens where the figures are read, not in the page that displays them.

The owner’s view

Work in progress, realization, billing history, payments and refunds, effective rates, matter balances and caseload: the reports cover the firm’s work and money. Trust ledgers, receipts and disbursements have their own views. Access follows each person’s role.

Firm ownerall 22 reports
Bookkeeperall 22 reports
Lawyerthree productivity reports
Clerknone

Every report leaves as Excel or PDF, for exactly the range on the screen.

A template, a document, a signature, and a record of it.

The vault holds the firm’s paper — filed against a matter, newest first, each filename kept exactly as the person who uploaded it wrote it.

Filing

Choose the matter, then drop the file anywhere on the page. PDF, Word, text or an image, up to 25 MB. A refusal says which of those it failed and files nothing at all — a half-uploaded document is not a document, and nothing is ever left looking filed when it is not.

Templates that keep their versions

A Word file with merge fields in it, filled from the matter at the moment you generate. Each template keeps its versions, so revising the retainer next month does not change what a client signed last month. Archiving one stops it appearing when generating and deletes nothing.

Refused before, not after

Generating checks every field first and lists what it cannot fill: one this matter has no value for, one that is not a field at all, and two custom fields sharing a name — because nothing can tell which of the two you meant, and guessing would put the wrong name in a retainer.

Sharing is a decision somebody makes

A document in the vault is not visible to the client until someone marks it visible. There is no default that shares.

The template

A Word file carrying {{client.display_name}} {{matter.display_number}} and your firm’s own fields. Add {{signature}} and the document it produces carries a signature box.

The document

Generated against one matter and filed straight into the vault, with every field resolved before a single page was written.

The signature

Sent to a contact on the matter who has an email address. They type their name or draw it — or decline, with a reason that comes back to the firm. The link is good for fourteen days.

Signature · Signature

awaiting signatureopenedsigneddeclinedexpired

The certificate

The document as it was sent
fingerprint
The document as it was signed
fingerprint
Which version of the template
recorded
Sent, opened, signed
timestamped
The signer’s address
not kept
The signer’s browser
not kept

Two content fingerprints are the whole basis of the claim, and neither the address nor the browser strengthens it. Both are personal information about someone who never offered it, so neither is kept. The certificate is the firm’s, and it needs a session to download — the signing link cannot hand it out.

The client sees two things. Nothing else is on that side.

No account to create, no password to reset, no invitation to look around. A link that works once and lasts a day.

What the client opens

The portal

Outstanding invoices
Documents shared with them

Approved bills that still carry a balance — issued, due, total, owing, and the invoice itself — and the documents someone at the firm marked visible.

What stays with the firm

Never on that page

  • The matter file
  • Time entries, and what they say
  • The trust ledger
  • Matters nobody shared
  • Every other client

Not hidden behind a setting that could be switched off. Those reads are tied to the one client the link belongs to, and there is no screen on that side that asks for anything else.

The link is single-use and lasts twenty-four hours; sending a new one cancels the last. A session left alone closes after twelve. Paying the bill from that page is still to come — today the portal shows what is owed and hands over the invoice.

Everything hangs off the matter.

Time, trust, documents, the calendar and the tasks are not five products. They are five views of one file, so a balance and a deadline are never sitting in two different tools.

Trust · Fiducie Held on this file, not in a pooled total

The matter file

Open date, limitation date, practice area, and a stage that belongs to that area. Move it to a stage from another area and the file refuses the move.

Time

Every entry, timer and rate on this file. Billed work stays on it, readable, and cannot be edited.

Calendar

Events linked to the file, with recurrence. An edit asks this occurrence or the whole series. The firm’s holidays sit beside them.

Tasks

Lists that belong to the file, not a personal board that forgets which matter they were for.

Contacts

On the file. A client, a counsel, a court — people the matter needs, not a separate address book.

Documents

The vault for this file: templates, the record, the signature, the certificate.

Leads

Before it is a matter, it is a lead. The same book, one step earlier.

Everything in it

The whole day, not a module.

A practice runs on one book, not seven tools that each hold a piece of it. This is the index of that book.

01

The matter file

  • Matters and stages
  • Contacts
  • Calendar, with recurrence and holidays
  • Tasks and task lists
  • Leads and public intake forms
  • A document vault
  • Templates with merge fields
  • Electronic signing
02

Money and trust

  • Timers and the catch-up grid
  • Six-level rate resolution
  • Unbilled work
  • Bills, payments and credit notes
  • Card payments, LEDES and late fees
  • Operating general ledger
  • Trust ledgers, per client
  • Disbursements
  • Electronic transfers
  • Monthly reconciliation
03

Firm and client

  • A client portal
  • Google and Microsoft 365, mailbox filing and SMS
  • Identity checks and API connections
  • 22 standard reports and saved custom views
  • An immutable audit log
  • Access by role
  • English and French, throughout
  • Ontario trust workflows
  • Sessions close after thirty idle minutes
  • Hosted in Canadian regions
Marked entries carry the trust treatment throughout.

More of the day, in one place.

From the first enquiry to the firm’s books, these capabilities are part of RYVO today. Connect external services in the firm’s settings where required.

Card payments, straight from the invoice.

Give clients a payment link tied to their bill, with the payment recorded against the same invoice.

The firm’s own merchant account

Open the firm’s merchant account inside RYVO. Once payment processing is configured, clients pay through a hosted checkout; card numbers never pass through RYVO.

A receipt, once

Payment confirmations are checked before they are recorded. A repeated confirmation does not create a second payment.

RYVO

Work, accounted for.

Professional servicesRecorded
Invoice balanceReady to pay
Paid. And on the record.

One invoice · one payment record

Illustrative workflow. No client data.
The week ahead
MonClient meeting
Tue
WedFile review
Thu
FriFollow-up
Google CalendarMicrosoft 365ICS
Illustrative workflow. No client data.

Your calendar, connected to the file.

Connect Google Calendar or Microsoft 365 from inside RYVO, and bring the matter calendar into the tools your firm already uses.

Both connections are here

Import events from the connected calendar and send new RYVO events outward. Linked events are recognised when synchronization runs again.

Calendar files, too

ICS import and export sit alongside recurring events, occurrence-level changes and the firm’s holiday calendar.

Correspondence belongs beside the matter.

Connect the firm’s Gmail or Outlook mailbox and file email against the matter it concerns.

Meeting arrangementsGmail or Outlook
Documents for the matterFiled once, linked to the matter
Next stepsClient correspondence

The complete conversation.

PeopleCorrespondenceDocuments
Filed email
Illustrative workflow. No client data.

Find it from the file

Filed messages remain accessible from the matter, alongside the work, people and documents they concern.

Visible failures, fewer duplicates

A message is filed once by its message identifier. Connection and retrieval failures stay visible on the matter.

A reminder of our meeting tomorrow. Please bring the documents we discussed.

Example reminder
Send recordedFailure visible on the matter
Illustrative workflow. No client data.

A reminder without leaving the matter.

Send a client an SMS from their matter, keeping the reminder and its outcome with the file.

Use the client’s number

Short reminders can go out by text through the configured messaging connection.

Know when it did not arrive

Delivery failures appear on the matter so the team can follow up. Silence is not treated as a successful send.

The first enquiry already has a place.

Publish an intake form and bring prospective clients into the firm’s lead pipeline before opening a matter.

A public form

The right questions, from the beginning.

NameContact detailsYour enquiry

A lead to review

A structured place for the firm to follow up.

Review the enquiryTrack its progressDecide to proceed

A matter begins

Convert when the firm is ready to act.

Client + matter
Illustrative workflow. No client data.

Forms for the work you take on

Create public forms with the fields the firm needs. Submissions enter a structured intake process instead of becoming another email to retype.

From lead to matter

Review the enquiry, track its progress and convert it into a client and matter when the firm is ready to take it on.

Electronic billing in the format clients ask for.

Export LEDES from the billing record, without building a second version of the invoice in a spreadsheet.

1998B
1998BI
XML 2.0
XML 2.1
One billing record. Four supported formats.

Four export formats

LEDES 1998B, 1998BI, XML 2.0 and XML 2.1 give the firm options for client billing requirements.

Missing details are named

Required firm identifiers, client identifiers and timekeeper classifications are checked before export. Missing information is reported rather than invented.

The issued invoice

Services, amounts and issue date

Original billing preserved

Late fee

Linked to the overdue invoice

Illustrative workflow. No client data.

An overdue charge keeps its own record.

Apply a late fee to an overdue invoice as a separate charge, with a clear link to the bill it concerns.

The original bill stays intact

The fee does not rewrite an issued invoice. The original billing and the later charge remain distinguishable.

A deliberate billing action

Record the charge against the overdue bill so the team can trace what was added and why.

The view your firm needs, saved for next time.

Build named report views from defined datasets, choose the columns and return to the same view whenever you need it.

22standard reports across the firm
BillingProductivityMattersTrust
Your saved viewNamed & saved
MatterClientBalance
Excel · PDFReturn to the same view

Illustration of a saved view, not a live report.

Alongside 22 standard reports

Billing, productivity, matters and trust each have their own reports. Custom views extend that library with a selection of fields chosen by the firm.

Exports and scheduled reporting

Take report results into Excel or PDF. Schedule supported standard reports weekly or monthly for delivery to a team member’s RYVO inbox.

Identity checks stay with the client.

Run checks for people and companies through the firm’s configured verification providers.

The person

Canadian legal identity checks, associated with the individual contact.

FCT

The company

Company checks, associated with the organisation the firm acts for.

Trulioo

The right check for the subject

FCT handles Canadian legal identity checks for individuals; Trulioo handles company checks. Results stay associated with the contact.

No result is a visible outcome

A provider failure or inconclusive response does not become a successful verification. The record retains the returned status.

The firm’s books have their own ledger.

A chart of accounts, balanced journal entries and a trial balance bring operating bookkeeping into RYVO.

Operating journal

Debit

Operating bank1,000.00

Credit

Accounts receivable1,000.00
Total debits = total credits
Example of a balanced operating entry. Trust money remains in its own ledger.

Debits and credits must agree

Post a journal entry only when it balances. Review account activity and the trial balance from the books workspace.

Trust stays separate

The operating general ledger does not replace the trust ledger. Client money retains its own records and controls.

A trust receipt must not be forgotten.

See Ontario trust cash receipts that remain undeposited after the next banking day.

A calendar that counts banking days

Deposit tracking uses banking days and the applicable Ontario holiday calendar to identify overdue receipts.

Keep the evidence together

Cash receipt records retain the payer, client, matter, amount and signatures alongside the trust reporting tools.

  1. Receipt recordedClient, matter and amount
  2. Next banking dayOntario banking calendar
  3. Still undeposited?Flagged for the firm to follow up
Illustrative workflow. No client data.

Connect with permissions that stay in place.

A versioned public API provides authenticated access within the permissions granted by the firm.

A defined starting point

The current endpoints expose API version and granted permissions, plus a trust-account count for authorised tokens.

Access follows its owner

Tokens are scoped and revocable. They cannot grant more access than the person who created them.

API

API version & granted permissions

Authorised trust-account count

Scoped. Revocable. Within the creator’s permissions.
The current API scope, shown explicitly.

Prepare connections to the firm’s other tools.

Configure outbound webhook destinations and review their delivery history. Event publishing and delivery are enabled as part of integration setup.

EventPublished by an integration
Signed deliveryVerify the sender
DestinationThe firm’s connected tool
Delivery historyRecorded attemptsRetriesFailures retained
Integration setup enables event publishing and delivery.

Check the sender

Signed events let a receiving integration verify the message before acting on it.

Follow failed deliveries

Delivery attempts are recorded and retried. Messages that exhaust their attempts remain available for investigation.

Who it is for

Four people, one book.

A firm of two or a firm of fifty. The lawyer and the bookkeeper want opposite things from the same screen, and averaging them makes something mediocre for both — so they are designed for separately.

01

The lawyer

Opens the matter, records the time, works the file. The product’s highest-traffic surface is the one that costs them the fewest seconds.

Time · matters · documents · calendar

02

The clerk

Keeps the file moving — contacts, tasks, deadlines, documents out and signatures back.

Tasks · contacts · templates · signing

03

The bookkeeper

Carries the regulatory risk. Bills, reconciles, and answers for the trust account when somebody asks.

Billing · trust · reconciliation · reports

04

The owner

Wants the number, not the spreadsheet. Realisation, receivables, and who is producing.

Reports · dashboard · receivables

See it against your books.

A walkthrough with your own trust structure, your jurisdictions and your reconciliation month. Thirty minutes, with someone who has read the rules.

No account required. Not a per-user licence — a walkthrough against your books is how it starts.