A large law firm needs practice management software that separates groups and offices, enforces confidentiality at the data layer, keeps an audit trail, and runs invoicing and collections across hundreds of matters. It also needs written terms on hosting region, support and identity before anyone signs.
LawAOS covers the operating layer: departments as child workspaces, ethical walls enforced in the database on matters, documents, invoices, calendar, docket, tasks and conflict search, per-module roles and attribute policies, an audit log, and firm-wide reports. Large firms buy the Enterprise plan, which is quoted, with implementation, migration and training scoped by agreement.
Buyers should know the platform's limits before a pilot. The primary database is hosted in one region, Asia-Pacific (Sydney). Residency, identity requirements and support terms are reviewed per Enterprise agreement, and the security page lists what the platform does and does not hold.
At volume, invoicing is a control problem. LawAOS numbers invoices PREFIX-YEAR-NNN across the firm and its departments, moves each through Draft, Finalized, Sent, Viewed, Partial, Overdue, Paid or Void, and allows only drafts to be deleted. Issued invoices are corrected by void or a numbered credit note that posts to the ledger.
Pre-bill review records write-downs that feed the realization figure, and an AI narrative review flags entries before billing; dismissing a flag needs a typed reason. Split billing allocates one invoice across several payers by percentage, and a daily job marks unpaid sent invoices past due as Overdue and notifies the creator.
- Walls under load
- Sign in as a walled user and search for the walled client, open its documents by URL and query its invoices. The database should refuse each.
- Department reporting
- Compare a department's billed and collected figures with the Firm-wide tab for the same period.
- Role boundaries
- Check that finance, payroll and HR permissions hold for a low-privilege member, since roles are checked on the server.
- Hosting and terms
- Confirm the hosting region, data processing terms and exit arrangements in writing against the DPA before live data goes in.
Scope the agreement
The Enterprise agreement sets implementation, migration and training, support terms and any residency or identity requirements before onboarding.
See the moduleModel groups and offices
Practice groups and offices become departments, and attribute policies express office or group rules on top of roles.
See the moduleApply confidentiality
An authorized administrator applies ethical walls, which the database enforces across matters, documents, file bytes, invoices, calendar, docket, tasks and conflict search.
See the moduleBill across the firm
Pre-bill review, AI narrative review, split billing and credit notes run the invoice cycle, with payments posting to the general ledger.
See the moduleReport to management
Firm-wide reports cover WIP by age, realization, collection rate, utilisation and aged receivables, and can be emailed on a schedule.
See the module
Stated plainly, so you can decide before you sign up rather than after.
- The primary application database is hosted in one region, Asia-Pacific (Sydney); other residency needs a separately scoped deployment agreed in writing.
- There is no screen for firm staff to raise or lift an ethical wall; an authorized administrator applies it.
- Two-factor authentication cannot yet be required firm-wide, and there is no IP allowlisting.
- Invoices carry one tax percentage per invoice, and there is no QuickBooks or Xero integration and no period close or lock dates in the ledger.
- LawAOS holds no third-party security certification, as the security page states.
Anything the list leaves open, our team answers directly.