The Quiet Loop
01 · Messy data · accounting jobFrom $150 a job

Transaction cleanup before bookkeeping

Transactions come in with cryptic descriptions, duplicate lines and the same payee spelled five ways.

We clean and normalise. The coding and the bookkeeping stay with you.

Send us the transactions

The files, or a sample. We reply in writing within one working day.

What you send, and what comes back

How we work
You send
The bank or card exports, or the statements, for the period.
We return
The transactions with payees normalised, duplicates flagged and a list of every change we made.
How you check it
Totals before and after match, and every change is listed with the original text beside it.
Free sample
50 rows of your own file, cleaned.
Price
From $150 a job. Large or repeat volumes: the monthly term, on the pricing page.

What it looks like

Invented names and figures.
Cleaned transactionsExample

Fennick Tile Co. · card account · August 2025

Cleaned transactions, an invented example
Original descriptionPayeeChange
CARD 4417 QUAYFUEL STN 22 REF 88213QuayfuelPayee normalised
QUAYFUEL 22 NORTHGATEQuayfuelPayee normalised
BACS BRAMBLEGATE EST RENT AUGBramblegate EstatesPayee normalised
DD LUMEN NINE TEL (22 AUG)Lumen Nine TelecomPossible duplicate, flagged

More on this job

Cleanup and catch-up work is hard to quote because nobody knows which transactions are wrong until someone has read every one. Reading them is mechanical; deciding what to do with them is not. We do the reading and the preparation, and hand back a short list of what needs a decision, which turns an open-ended job into one you can plan. Our note on why cleanup takes longer than quoted explains where the time usually hides.

What we look for

The same few problems account for most of what needs fixing in neglected transaction data, and each one can be checked for on purpose:

  • Payees spelled several ways, which splits one supplier across several names.
  • Bank descriptions that hide the payee behind card numbers, branch codes and references.
  • Duplicates that share no field exactly, such as the same expense arriving by photo and by email. See the folder that double-counts.
  • Transfers between the client’s own accounts mixed in with spending, where coding both ends as a cost counts the money twice.

Every change is listed, never applied silently

You get the transaction file with payees normalised and possible duplicates flagged, not deleted, so the totals before and after still match. Beside it is a list of every change, with the original text next to the new one. A correction made without a record looks exactly like the error it replaced, so we keep the record and you decide.

Catch-up periods

For catch-up and historical work the same applies across many months at once: statements converted, transactions cleaned, missing periods listed. If a keyword rule in the existing books has caught the wrong transactions, the pattern is easy to see once the payees are clean; see a rule that matched inside a word. What to recode, and how, stays with you.

Questions about this job

Do you make changes in our clients’ books?

No. You get the cleaned transaction file and a list of every change, with the original text beside it. Your team decides what to import or apply.

Can you take on one messy client rather than a monthly arrangement?

Yes. A single cleanup is a fixed-scope job with a fixed quote in writing, and it is a sensible way to start. Repeat work can move to the monthly term later.

What about transactions you cannot work out?

They are listed as unresolved, with what we could see. We do not guess a payee or remove a line we are unsure about.

Do you code transactions to our chart of accounts?

No. We clean and normalise the data so the coding goes faster. The coding and the bookkeeping stay with you.

What we do not do

  • Bookkeeping, tax or any judgement on the figures
  • An opinion on what the figures mean

The full list of limits

Send us the transactions

Send us the transactionsThe files, or a sample. We reply in writing within one working day.