Precedent S
The bill is a document, not a spreadsheet.
Precedent S is the electronic bill of costs in England and Wales: a workbook with a fixed order, a phase for every line of work, and totals that have to reconcile to the penny. Most reductions happen in the assembly rather than the argument.
Good to know
- Practice Direction 47 governs the electronic bill. This page describes the structure; the direction and your order decide what is required.
- Workbook
- Fixed sheet order
- Per entry
- Date · time · rate · phase
- Export
- Excel + voucher PDF
The workbook
What it has to carry.
Six parts, in an order the reader expects. Leave one thin and the rest of the bill is read with suspicion.
- Summary and totals
- The figures the court reads first: profit costs, disbursements, VAT and the total claimed — each one traceable to the sheets beneath it.
- Fees
- One line per fee earner entry: the date the work was done, the time recorded, the rate claimed, the phase it belongs to and the narrative the court will actually read.
- Disbursements
- Each voucher as its own line — payee, net, VAT, date — linked back to the document it came from rather than typed in from memory.
- Time records
- The underlying entries, so any total in the bill can be reconstructed line by line instead of being taken on trust.
- Non-recoverable schedule
- Overheads such as photocopying, binding and travel held separately: visible to the reader, outside the recoverable total.
- Voucher bundle
- The invoices and receipts behind the disbursement lines, in the order the bill references them.
Where it goes wrong
Six reasons a bill gets reduced.
None of these are arguments about whether the work was done. They are assembly failures, and they cost real money.
| Comparison | What goes wrong | What Costs Engine does about it |
|---|---|---|
| Block-billed days | Flagged before export so a day can be split into the attendances it was actually made of. | |
| The same narrative twice | Duplicate narratives detected across entries, with both line references shown side by side. | |
| Rates applied by bill date | Every entry capped against the table in force on the date the work was done, not the date the bill is drawn. | |
| Disbursement lines with no voucher | Lines matched against vouchers as they are ingested, so a missing receipt appears before the workbook closes. | |
| Overheads in the recoverable total | Non-recoverable items identified and moved onto their own schedule at export. | |
| Phases inherited from the ledger | Entries mapped to the phase the work belongs to, so phase totals reconcile with the narrative rather than with the file structure. |
Assembly
What the engine does, in order.
Five passes, all of them on your machine. The judgment calls stay where they belong.
01
Ledger read
Excel, CSV or tab-delimited, mapped into entries with a date, a time and a fee earner.
02
Vouchers matched
Scanned bundles parsed for payee, net and VAT, then matched to their disbursement lines.
03
Papers read
Pleadings, orders and the chronology in Word: the budget split at the CCMC date, and Tab 3's synopsis taken from them.
04
Rates capped
Each entry against the table in force on its own date, region and band.
05
Workbook exported
Written into the official MoJ template at the XML level, so the PivotCaches and validations still work, with the voucher bundle and a summary the fee earner can sign.
Questions
The questions draftsmen actually ask.
Including the ones where the honest answer is that the court decides.
Keep reading
Then there is the rate question.
Structure takes you to a bill the court can read. Date-matched capping is what stops it being cut.
Precedent S
Bring a real disbursement bundle.
The assembly is only convincing on a real matter: 500 scanned pages, four years of entries, one workbook at the end of it.
One reply, one call, one decision. We will not add you to a sequence.
