How LexiManage is checked — and where it falls short

You answer for what this software produces. So here is what is checked before a release reaches you, where the figures and forms come from, and the gaps we know about and have not yet closed.

Current as of October 1, 2026

Before every release

The release script runs all of these and stops if any one fails.

• About 240 files of automated tests covering the calculators, trust and billing arithmetic, the court forms, permissions and confidentiality screens.
• The money paths, run against a real database — invoices, payments and trust movements posted and read back, because tests that imitate a database can pass while the real one refuses.
• Every page's data, read as two different people — a managing partner and a law clerk — so that a screen one role should not see is caught.
• Every action that saves something, tried against a scratch database.
• Every screen opened in a real browser before it ships.
• The database layout compared with what the software expects, so a missing change is found before it fails in use.

Court forms

LexiManage fills 426 forms: 144 under the Family Law Rules, 236 under the Rules of Civil Procedure and 46 for the Small Claims Court. Where the Government of Ontario publishes a form in Word, LexiManage fills the government's own file rather than a copy of it.

• Every form is built in testing and checked to open as a sound Word document.
• The visible text and tick boxes of each family law form are compared with a stored copy, so an unintended change shows up.
• A civil form fails its test if any value meant for it finds no place to go.
• The government's exact headings in the financial statements (Forms 13 and 13.1) are checked word for word.
• Three family law forms (6, 6A and 32C) are published by the government only as PDFs. LexiManage rebuilds them from the published text.

Support and tax figures

• Income tax for every province and territory outside Quebec, 2023 to 2026, is read from the CRA's own forms (Form 428, the T1 return and the T4127 payroll formulas). Each figure records where it came from, and a test fails if one loses its source. Earlier years come from the CRA's published tables.
• Child support tables are loaded from the Federal Child Support Guidelines tables published by Justice Canada.
• Spousal support follows the Spousal Support Advisory Guidelines and the Revised User's Guide, and its results have been compared with worked examples published for a Law Society of Ontario continuing-education program.
• Quebec child support is cross-checked in each case against the regulation's own method of calculation.
• Every calculation shows its working, so you can check any figure yourself.

Keeping up with the rules

Each week LexiManage checks the official Ontario sources for changes:

• whether a regulation it relies on has a newer consolidation on e-Laws;
• for each deadline it calculates, whether the exact rule it cites has changed;
• whether the government's table of court forms has added, changed or withdrawn a form;
• whether a regional practice direction has changed.

A change is reported to a person to read. Nothing in LexiManage rewrites a deadline or a rule on its own.

Trust accounting

• A matter cannot overdraw its trust. The database refuses the entry itself, so no screen, import or later feature can get around it.
• Every journal entry must balance, also enforced by the database.
• Cash over the By-Law 9 limit ($7,500 on one client file) is refused unless you record which exception applies. This check is made by the application before anything is posted, on both invoice payments and trust receipts.
• A trust reconciliation will not close until the bank balance, the general ledger and the client trust listing agree to the cent. This is checked by the application when you complete the reconciliation.

Your data on the hosted service

• Hosted in Beauharnois, Quebec, by a Quebec company with no United States parent.
• The database and documents sit on encrypted storage. The key is not kept on the server, so a copied disk, snapshot or backup is unreadable. This protects stored data; it does not protect against someone who controls the running application, and no hosted software can.
• Backups run nightly, are encrypted before they leave the server, and are kept in a second location. Each night's backup is opened and checked before any older one is deleted.
• Nothing from your database is sent to an AI service. The help assistant receives, from you, only the question you type — so do not type a client's name into it.

What we have not done yet

If you find something that is wrong, tell us at hello@leximanage.ca. A wrong figure is fixed before anything else.