Commercial customers rarely pay invoice by invoice. A managing agent or a main contractor runs the month's payments in one go and sends a remittance advice listing what it covers — usually because every job needed its own invoice with its own purchase order number on it.
Batch payment splits that one figure across those invoices in one action.
Ask Mucka
Open Mucka, or send a WhatsApp, and say:
"McKean have paid £4,300 covering the last five."
"That's the whole of October settled from Hartley, four thousand two hundred."
Mucka works out the split from what they actually owe — not in its head — and shows you a card naming every invoice and every figure before anything is recorded. Tap to confirm and the lot goes on together.
If the money doesn't quite cover everything, the card says so rather than making the arithmetic close.
Or use the form
From the Invoices page, tap Batch payment.
- Who paid. Pick the customer. Mucka lists everything they still owe, with the PO number on each one, oldest debt first.
- Amount received. The single figure that hit the bank. Mucka splits it down the list straight away — filling each invoice, then part-paying the one the money runs out on.
- Adjust it. Every line is editable and every one has a tick. Untick anything the remittance doesn't cover and the money re-splits across the rest.
- Date received, method and reference. Put the BACS reference in — it's kept against every payment in the batch, so the bank statement and Mucka agree later.
- Record.
The footer always shows three figures: what arrived, what you've allocated, and what's left over.
It goes in as one lot
Either the whole batch records or none of it does. If one invoice in it can't take a payment — it's still a draft, say — nothing is recorded and Mucka names the one that stopped it. You'll never end up with four of the five recorded and no way of telling which.
What it won't do
- It won't overpay an invoice. Each line is capped at what that invoice actually owes. If a customer has genuinely paid you more than they owe, record that on the invoice itself with Record a payment.
- It won't keep money on account. Anything left over isn't recorded anywhere — Mucka shows you the figure rather than putting it somewhere you'd have to go and find it. Tick another invoice, or record the rest separately.
- Subbie invoices aren't in the list. CIS comes off each invoice's own labour split, and a single lump sum has no way of expressing that. Record those one at a time from the invoice, where Mucka works the deduction out for you. If the customer has any, the sheet says how many so you're not left wondering where they went. See CIS suffered.
After it lands
Each invoice gets its own payment record, exactly as if you'd typed them in one by one — so the payment history, the client's payment-method breakdown and the revenue figures all read the same. Anything fully settled stops being chased, and the whole lot goes across to Xero, QuickBooks, FreeAgent or Sage if you're connected.
You get one notification for the batch rather than one per invoice.