The person
Canadian legal identity checks, associated with the individual contact.
Practice management for law firms worldwide
Matters, time, billing and trust accounting — built so the ledger is defensible on the day somebody asks to see it.
We now supply law firms around the world, with relationships in the U.S., Europe, the Middle East, East Africa and 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.
The treatment
A doubled edge, a hatched field and a TRUST · FIDUCIE label, everywhere it appears. Three signals, so the distinction survives a photocopy.
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.
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.
Requisition, authorisation, execution. The person who authorises can never be the person who requisitioned — the ledger refuses it outright, rather than trusting a policy.
Someone raises the transfer: the client, the matter, the amount, the reason and an expiry.
A second person authorises it. If the two are the same person, it does not proceed.
Only then does the money move, and the record keeps who did each of the three acts.
Required by LSO By-Law 9, s. 12.
Trust reconciliation is due within 25 days of month end, and cannot be completed while any unexplained difference remains. RYVO counts the days.
The dial runs on your own clock against the real rule — it is the deadline, not a firm’s data.
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.
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.
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.
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.
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.
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.
| Date | Matter | Description | Duration | Billable | Value |
|---|---|---|---|---|---|
| Mon | Running timer | 0:41 | |||
| Mon | 1.2 | ||||
| Mon | 1:12 | ||||
| Tue | 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.
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.
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.
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 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.
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.
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.
| 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 |
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.
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.
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.
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.
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.
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.
What is owed · as at a date
Approved bills that still carry a balance, by days past due. Currencies are kept apart rather than converted at a rate nobody agreed to.
Revenue · over a range
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.
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.
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.
Every report leaves as Excel or PDF, for exactly the range on the screen.
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.
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.
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.
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.
A document in the vault is not visible to the client until someone marks it visible. There is no default that shares.
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.
Generated against one matter and filed straight into the vault, with every field resolved before a single page was written.
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
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.
No account to create, no password to reset, no invitation to look around. A link that works once and lasts a day.
The portal
Approved bills that still carry a balance — issued, due, total, owing, and the invoice itself — and the documents someone at the firm marked visible.
Never on that page
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.
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.
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.
Every entry, timer and rate on this file. Billed work stays on it, readable, and cannot be edited.
Events linked to the file, with recurrence. An edit asks this occurrence or the whole series. The firm’s holidays sit beside them.
Lists that belong to the file, not a personal board that forgets which matter they were for.
On the file. A client, a counsel, a court — people the matter needs, not a separate address book.
The vault for this file: templates, the record, the signature, the certificate.
Before it is a matter, it is a lead. The same book, one step earlier.
Everything in it
A practice runs on one book, not seven tools that each hold a piece of it. This is the index of that book.
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.
Give clients a payment link tied to their bill, with the payment recorded against the same invoice.
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.
Payment confirmations are checked before they are recorded. A repeated confirmation does not create a second payment.
Work, accounted for.
One invoice · one payment record
Connect Google Calendar or Microsoft 365 from inside RYVO, and bring the matter calendar into the tools your firm already uses.
Import events from the connected calendar and send new RYVO events outward. Linked events are recognised when synchronization runs again.
ICS import and export sit alongside recurring events, occurrence-level changes and the firm’s holiday calendar.
Connect the firm’s Gmail or Outlook mailbox and file email against the matter it concerns.
Filed messages remain accessible from the matter, alongside the work, people and documents they concern.
A message is filed once by its message identifier. Connection and retrieval failures stay visible on the matter.
Send a client an SMS from their matter, keeping the reminder and its outcome with the file.
Short reminders can go out by text through the configured messaging connection.
Delivery failures appear on the matter so the team can follow up. Silence is not treated as a successful send.
Publish an intake form and bring prospective clients into the firm’s lead pipeline before opening a matter.
The right questions, from the beginning.
A structured place for the firm to follow up.
Convert when the firm is ready to act.
Create public forms with the fields the firm needs. Submissions enter a structured intake process instead of becoming another email to retype.
Review the enquiry, track its progress and convert it into a client and matter when the firm is ready to take it on.
Export LEDES from the billing record, without building a second version of the invoice in a spreadsheet.
LEDES 1998B, 1998BI, XML 2.0 and XML 2.1 give the firm options for client billing requirements.
Required firm identifiers, client identifiers and timekeeper classifications are checked before export. Missing information is reported rather than invented.
Services, amounts and issue date
Original billing preservedLinked to the overdue invoice
Apply a late fee to an overdue invoice as a separate charge, with a clear link to the bill it concerns.
The fee does not rewrite an issued invoice. The original billing and the later charge remain distinguishable.
Record the charge against the overdue bill so the team can trace what was added and why.
Build named report views from defined datasets, choose the columns and return to the same view whenever you need it.
Illustration of a saved view, not a live report.
Billing, productivity, matters and trust each have their own reports. Custom views extend that library with a selection of fields chosen by the firm.
Take report results into Excel or PDF. Schedule supported standard reports weekly or monthly for delivery to a team member’s RYVO inbox.
Run checks for people and companies through the firm’s configured verification providers.
Canadian legal identity checks, associated with the individual contact.
Company checks, associated with the organisation the firm acts for.
FCT handles Canadian legal identity checks for individuals; Trulioo handles company checks. Results stay associated with the contact.
A provider failure or inconclusive response does not become a successful verification. The record retains the returned status.
A chart of accounts, balanced journal entries and a trial balance bring operating bookkeeping into RYVO.
Post a journal entry only when it balances. Review account activity and the trial balance from the books workspace.
The operating general ledger does not replace the trust ledger. Client money retains its own records and controls.
See Ontario trust cash receipts that remain undeposited after the next banking day.
Deposit tracking uses banking days and the applicable Ontario holiday calendar to identify overdue receipts.
Cash receipt records retain the payer, client, matter, amount and signatures alongside the trust reporting tools.
A versioned public API provides authenticated access within the permissions granted by the firm.
The current endpoints expose API version and granted permissions, plus a trust-account count for authorised tokens.
Tokens are scoped and revocable. They cannot grant more access than the person who created them.
Configure outbound webhook destinations and review their delivery history. Event publishing and delivery are enabled as part of integration setup.
Signed events let a receiving integration verify the message before acting on it.
Delivery attempts are recorded and retried. Messages that exhaust their attempts remain available for investigation.
Who it is for
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
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
Keeps the file moving — contacts, tasks, deadlines, documents out and signatures back.
Tasks · contacts · templates · signing
03
Carries the regulatory risk. Bills, reconciles, and answers for the trust account when somebody asks.
Billing · trust · reconciliation · reports
04
Wants the number, not the spreadsheet. Realisation, receivables, and who is producing.
Reports · dashboard · receivables
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.
Tell us where you practise and we will bring your own trust structure and reconciliation month to the call.
Someone from the Technology Division will be in touch within one business day.