CasEngine by CodEngines
Billing & invoicing

Legal billing and invoicing software for law firms.

Money falls due the way your fee agreement says it does — by date, by litigation stage, or from recorded time — and the invoice is built from what is actually outstanding.

The problem

The work is done. Getting paid for it is a separate job, and nobody's job.

The time sits in one place and the disbursements in another, and the fee agreement said the second instalment falls due when judgment is issued at first instance — which happened three weeks ago, and nobody raised it. The money is not in dispute. It is simply not invoiced.

How it works

From fee agreement to money received.

  1. 01

    The fee agreement decides when money falls due

    Set it once on the matter: on a date, on reaching a stage of the litigation, on a payment stage, from recorded time, or as a fixed sum. The agreement stops being a document someone has to remember and becomes the thing that drives the billing.

  2. 02

    Dues appear when they are earned

    Reaching “First Instance — Judgement Issued” raises the instalment that the agreement attaches to it. Nobody has to notice the case moved, because the case moving is what raises the due.

  3. 03

    Invoice from what is genuinely outstanding

    Pick from the dues that have not been invoiced yet, filtered by client, matter, type or date range. Each arrives carrying its matter number, case number, responsible lawyer, office, description and amount — and a due already sitting on a live invoice cannot be picked a second time.

  4. 04

    Approve first, where the firm wants that

    An optional approval step means a due cannot reach an invoice until someone has signed it off — for firms where billing is reviewed before it goes out rather than after a client queries it.

  5. 05

    Receipts, credit and refunds

    Record payment by transfer, cheque or otherwise against the invoice it settles. Money a client paid ahead of that is held as credit on their account and counted before anything is chased.

Outcomes

What changes for the firm.

In detail

Everything included, in one place.

Billing that follows the litigation

Dues can be attached to a stage of the case rather than to a calendar — the instalment agreed on judgment at first instance is raised when that judgment is recorded. This is how fee agreements in the region are actually written, and it is the part generic billing software cannot express.

Five ways money falls due

By date, by litigation stage, by payment stage, from recorded time priced at its rate, or as a fixed sum — set per matter agreement rather than per firm, because one client's terms are rarely another's.

No double billing, by construction

A due that already sits on a live invoice is not offered again. Duplicate billing is prevented by the model rather than caught in review.

Optional approval before invoicing

Firms that review billing before it goes out can require a due to be approved before it can reach an invoice; firms that do not can leave the gate open.

Receipts and refunds

Payments are recorded by transfer, cheque or other mode against the invoice they settle, and refunded where that is what happened. The credit ledger behind money held on account is covered on the accounting page.

Read ›

Bilingual at the record, not the template

Client names, descriptions, offices, payment types and stage labels are all held in both languages, so an Arabic invoice is the same record rendered in Arabic rather than a separately maintained document.

FAQ

Common questions about this feature.

Yes, and this is the normal way to set it up. A fee agreement can attach instalments to litigation stages, so recording judgment at first instance raises the due that the agreement tied to it. Dues can equally be set by date, by payment stage, from recorded time, or as a fixed sum — per matter agreement, not per firm.

Related

Works with the rest of the platform.

See it on your own matters

A short walkthrough with our team, using the kind of work your team handles day to day.