Legal Billing Software vs Accounting Software: Why Law Firms Need More

A general accounting package assumes an invoice is homogeneous: a set of lines that are all the same kind of thing, taxed the same way, owed by the party named at the top. Most commercial invoices fit that assumption.

A legal statement usually does not. Close an ordinary matter and you may be billing professional time, which most tax regimes treat as a taxable service; recovering a court fee you advanced on the client's behalf, which many regimes treat as outside the scope of tax; and rebilling a translator's invoice, which follows its own treatment again. Three lines, three tax positions, one document the client expects to receive whole.

Software that applies a single rate to a whole invoice cannot describe that statement. It offers two escapes, and both are wrong: tax the disbursement you should not have taxed, or split one piece of work across several documents and hope the client reconciles them.

Firms quote before they bill. In a general ledger the natural way to do that is to raise a draft invoice, which is where the trouble begins, because a draft is one status change away from being counted.

A proforma needs to be structurally incapable of being revenue: its own numbering sequence, excluded from every revenue and outstanding figure, unpayable. Otherwise the partner's dashboard flatters, aged receivables include work nobody has agreed to, and the number the firm plans around is not a number at all.

The conversion from estimate to fiscal invoice also has to be a single, guarded operation. Two people converting the same proforma on the same afternoon must produce one invoice, not two.

Fiscal numbering looks administrative until an auditor asks why number 47 is missing. Most jurisdictions expect an unbroken sequence per book, and most general packages give you one sequence with gaps wherever someone deleted a draft.

A law firm typically needs several books running in parallel — taxable, exempt, proforma, and receipts — each unbroken on its own terms. That is not a reporting preference. It is the difference between an afternoon with an auditor and a week.

Retainers and funds held on account are the sharpest divide. Money a firm holds is not money the firm has earned, and in many jurisdictions the rules governing it are stricter than anything in general commercial accounting.

Billing against funds you already hold has to be visible as a sequence — what was held, what was drawn, on what authority, and what remains — rather than as a net figure that happens to reconcile. When a regulator or a client asks how a balance moved, a net figure is not an answer.

Commercial invoices are rarely litigated. Legal fees are, and often long afterwards, which changes what the accounting system has to be able to prove: which version of the invoice was sent, when the client saw it, what was agreed, and that none of it was edited after the fact.

A ledger an administrator can amend answers none of those. Neither does an email thread, since threads fork and mailboxes are pruned. What survives is a record written as the work happened, that the application itself cannot rewrite.

None of this means a firm abandons its accountant's tools. Statutory accounts, payroll and the annual return live where the accountant works, and should. The distinction is about where the fiscal source documents are produced.

The practice system issues the invoice, rules its tax per line, seals it, records the payment and issues the receipt. The accounting package receives the resulting figures. Reversing that — producing legal invoices in a general ledger and re-keying matter context afterwards — is where the reconciliation work, and the errors, come from.

Mersal issues from three separate serial books — VAT, exempt and proforma — each with its own unbroken sequence. Tax is ruled per line, so one statement can carry taxable time and an exempt disbursement honestly, on one document.

A proforma is never a receivable: it carries its own serial, is excluded from every revenue and outstanding figure, and cannot be paid. Converting one recomputes tax from the stored per-line rates and stamps the charged amount, under a compare-and-swap so a double conversion cannot happen.

Issued invoices freeze. Their stored values always outrank current firm settings, so changing a rate or a currency later never rewrites what a client was charged. Settlement records partial or full payment under an idempotency key — a retry or a second browser tab cannot double-record a payment — and receipts issue on their own sealed serial. Every step lands in an append-only ledger the application cannot amend.