Think Build Implement Repeat
London, UK +44 7367 067226
WhatsApp FOLLOW f in X
  1. Home
  2. Blog
  3. How Do We Keep Track of Court and Council Deduction Orders for Our Clients' Employees?
Problems We Solve

How Do We Keep Track of Court and Council Deduction Orders for Our Clients' Employees?

A payroll bureau receives attachment of earnings orders for client employees by post, then deducts and pays them over. We build an order register and routine.

Updated 3 min readBy SpiderHunts Technologies

Free estimateNo obligation

Get a free estimate

Tell us what you need. A senior engineer reads every enquiry.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →

Quick answer — TL;DR

Deduction orders go wrong because they arrive on paper at the client's address, reach the bureau late, and then live in a folder while deductions and payments to the issuing body are handled by memory each period. We build an order register across your clients, with scanned orders read into structured records, deductions prepared for each run, payments to each issuing body tracked, and variations and discharges applied on the right date.

A letter from the court, forwarded a fortnight later

An attachment of earnings order for one of your client's employees lands on the client's doormat. The office manager is not sure what it is, puts it in a tray, and eventually scans it to you. Meanwhile a council tax attachment for another employee has arrived at a different client, and a child maintenance deduction order is already running for a third.

Each order has its own reference, calculation basis, payment details and dates. Some need a protected earnings check each period. Each deduction must be paid to the right body with the right reference. When one is varied or discharged, another letter arrives, and the cycle begins again.

Why deduction orders are handled badly

They are rare enough per client that nobody at the client knows what to do, and common enough across a bureau that someone should have a routine. They arrive on paper at the employer's address, not the bureau's. The detail of each order sits in a scanned PDF that has to be read every time someone needs it. Payments to the issuing body are often made outside the payroll software, by a separate bank payment, and tracked on a list.

The rules on how each type of order is calculated and applied come from the order itself and the legislation behind it. Your team follows them. The problem the bureau has is knowing what orders exist, applying them each period and paying them over, without relying on memory.

What mishandled orders cost

Starting late or deducting the wrong amount can leave the employer answerable to the court or council, and the client will look to the bureau. Payments sent without the right reference go astray and get chased. Employees under orders are often in difficult circumstances, and an error in either direction hurts them. And when an order is discharged but deductions continue, the refund and apology fall to you.

StageWhat usually goes wrong
Order received by the clientReaches the bureau late
Order set up in payrollDetails retyped from a scan
Each period's deductionProtected earnings or rate misapplied
Payment to the issuing bodyMissed, late or wrong reference
Variation or dischargeApplied late or not at all

How we build an order register for a bureau

  1. Clients get a simple way to send any order they receive, by photo, scan or forwarded email, straight to a bureau address that recognises it as an order.
  2. Each order is read into a structured record: employee, client, order type, issuing body, reference, amounts or rates, payment details and dates. A model does the first pass and an administrator confirms every field against the original.
  3. The order is linked to the employee's pay element in your payroll software, and each run shows the administrator which orders apply and what the payroll calculated for them.
  4. After each run, a payment list per issuing body is produced with amounts and references, ready for payment through your usual route, and marked paid when it goes.
  5. Variations and discharges are matched to the existing order and applied from the right period, with the change recorded.
  6. When an employee under an order leaves, the register reminds the administrator of the notification the order requires, so it is not missed in the leaver process.

The register keeps records and prompts your team. How each order is calculated is set by the order and applied through your payroll software and your team's judgement.

Orders handled as a routine

Every live order across every client is on one list, with the original document one click away. Each run shows the deductions due, and each period ends with payments to issuing bodies made and recorded. Variations and discharges are applied on time. And the client, who was nervous about a letter from the court, sees that the bureau has it in hand.

Is this how orders reach you?

  • Deduction orders arrive at clients by post and reach you late.
  • Order details are kept in scanned PDFs in client folders.
  • Payments to courts or councils are tracked on a separate list.
  • A discharged order has kept deducting before.
  • Leavers under an order have slipped through without the right notice.

FAQ

Frequently asked questions

The questions readers ask us after this guide.

Still have a question?

Ask us directly — a senior engineer will get back to you.

Ask about your project

Can the system calculate the deductions?

Your payroll software does the calculation from the order details. The register makes sure the details are right, current and applied each period.

Can it pay the issuing bodies?

It prepares the payment list with amounts and references. Payment is made through your usual banking route by your team.

What if a client never forwards an order?

Nothing can catch an order nobody sends. We make sending one as easy as taking a photo, and remind clients periodically what to look out for.

Is scanned order data kept securely?

Orders are stored in your systems or hosting you approve, with access limited to the administrators who need it, and every access logged.

Keep reading

More on Problems We Solve

Start here

Tell us where your payroll bureau's week gets stuck

Describe your client base, the payroll software you run and the part of the pay cycle that causes the most trouble. We will tell you what we would build around it, what we would not touch, and if a smaller change would fix it, we will say so.

  1. You tell us what you needTwo minutes on the form, or a message on WhatsApp.
  2. A senior engineer reviews itAnd comes back with questions, a realistic range and an honest view on fit.
  3. Free 30-minute scoping callWe talk through scope, options and a realistic estimate — with no obligation.
Free estimateNo obligation

Talk to someone who builds this

Send a short brief and we will come back with an honest view and a realistic range.

Takes under a minute. We never share your details.

  • Free consultation
  • No commitment
  • NDA on request

Prefer to talk? Book a free 30-minute call →