Ledger, statements and accounting

The trust ledger

Available: website and law firms

What it does: Records receipts, disbursements and reserves, and computes balances and schedules from the rows themselves.
What it refuses: No model writes a word or a number into a court form, notice or accounting. Court forms, statutory notices, packets and fee disclosures are assembled from deterministic templates, and accounting totals are computed from ledger rows. (Generative boundary: level L2)
Limits: Totals come from ledger rows; nothing estimates a balance.
Who may use it: The trustee of the matter; the firm's staff on its matters.
Inputs and outputs: In: Ledger entries.Out: Balances, schedules and a CSV export.
Availability: Available to website trustees and law-firm tenants.
AI use: No model
Access: Signed-in account, limited to its own records
Evidence: 3 automated suites run on every change.

Available: website and law firms

What it does: Reads a bank or brokerage statement into proposed ledger lines that a person reviews one by one.
What it refuses: No AI chats with you or writes to you. Software may extract dates, names and amounts from a document you upload so you can confirm them. It never converses, answers questions or writes text for you. (Consumer-lane rule I2)
Limits: Nothing enters the ledger until a person accepts the line.
Who may use it: The trustee of the matter; the firm's staff on its matters.
Inputs and outputs: In: A statement file.Out: Proposed ledger lines.
Availability: Available to website trustees and law-firm tenants; the model provider configured for this deployment is present on this deployment.
AI use: Structured: fields a person confirms, never prose to a reader
Access: Signed-in account, limited to its own records
Evidence: 2 automated suites run on every change.

Not enabled on this deployment

What it does: Connects a bank account through the bank-connection provider and brings its transactions in as proposed ledger lines.
What it refuses: None recorded
Limits: A connection can be disconnected at any time.
Who may use it: The trustee of the matter; the firm's staff on its matters.
Inputs and outputs: In: A bank connection.Out: Proposed ledger lines.
Availability: Requires a bank-connection provider configured for this deployment, which this deployment does not carry.
AI use: No model
Access: Signed-in account, limited to its own records
Evidence: 1 automated suite runs on every change.

Available: law-firm tenants

What it does: Assembles the trust accounting under section 736.08135 from the ledger for the firm's attorney to review.
What it refuses: No model writes a word or a number into a court form, notice or accounting. Court forms, statutory notices, packets and fee disclosures are assembled from deterministic templates, and accounting totals are computed from ledger rows. (Generative boundary: level L2)
Nothing is filed or sent on anyone's behalf. Forms and notices fill their factual blanks from the record; a person edits, sends or files them and records the delivery. The software prepares nothing for anyone and files nothing. (Claims register: self-help forms and notices)
Limits: Every figure comes from the ledger.
Who may use it: The firm's staff.
Inputs and outputs: In: The ledger and the accounting period.Out: A printable accounting.
Availability: Available to law-firm tenants.
AI use: No model
Access: Firm staff on matters they are staffed on
Evidence: 1 automated suite runs on every change.

Source commit: 9b7ff8f1f1c49e6088a15c891886364873e9e665
Built: 2026-09-25 04:52 UTC
Release run: 36096103588 (attempt 1)
Required checks: CI (verify, end-to-end, Lighthouse gate): run 36095197104 (attempt 1)
Row-level security matrix: run 36095197149 (attempt 1)
Security scan (secrets, static analysis, dependencies): run 36095197106 (attempt 1)

Availability and counts on this page were computed when this build ran, from its own configuration and the records committed at its source commit.