Mucka doesn't connect to your bank account, so payments need recording when they land. It's quick: a tap or two from the invoice list opens a payment window with everything pre-filled.
Ask Mucka
Open Mucka and say:
"Walker just paid the £180 invoice by bank transfer."
"Mrs Doyle paid her invoice yesterday, £168."
Mucka pulls up the invoice, drafts the payment record and shows it for you to approve. One tap, the invoice flips to paid.
If the money landed on a different day, just say so. Mucka dates the payment to the day it arrived, not the day you got round to telling it.
Or use the form
From the Invoices page, find any invoice with status sent, partially paid or overdue and tap Mark as paid. On a phone, tap the invoice card to open it and Record a payment is in the panel at the bottom. The payment window opens with:
- Amount: defaults to the remaining balance (override for partials)
- Method: Bank Transfer, Card, Cash, Cheque, Direct Debit or Other
- Date received: defaults to today — change it if the money landed earlier
- Notes: reference number, who paid, anything useful
Save and Mucka updates the invoice.
If you're catching up a few days late
Most people record payments in a batch rather than the moment the money lands. Set Date received to the day it actually arrived and everything downstream stays honest — how long the invoice really took to get paid, and what was genuinely outstanding at the end of the month.
You can't date a payment in the future.
Partial payments
Big jobs often get paid in stages. Just type the amount that's landed and pick the method. Mucka:
- Flips the status to partially paid
- Updates the remaining balance shown on the invoice
- Keeps a separate row for each payment so you can see the full history
Record more payments against the same invoice over time. When the balance hits zero, status flips to paid and Mucka stops chasing it.
What gets tracked
Each payment record has:
- Amount (full or partial)
- Method (which of the six types above)
- Date the money landed
- Notes (your reference, their reference, anything useful)
This builds up over time into a payment-method breakdown on the client's profile, useful for understanding how a client likes to pay.
Common gotchas
- Recorded one by mistake? Just tell Mucka — "take that payment off", "no, they only paid the two grand". It puts the invoice back to what it owed, so it starts being chased again. If there's more than one payment on the invoice, Mucka lists them and asks which. Like any money change it stages a card for you to confirm first, so nothing moves until you tap.
- Refunding a card payment is a different thing and Mucka won't do it by deleting the record. If the money genuinely went through on a card, the record has to stay — otherwise the customer gets chased for something they've already paid. Refund it from the invoice instead.
- If the payment already went across to your accounts package, undoing it in Mucka does not undo it in Xero, QuickBooks, FreeAgent or Sage. Mucka tells you when that's the case; delete it there too or your books won't agree.
- Bank reconciliation. Mucka doesn't auto-match payments to bank statements. Match them yourself when reviewing the bank feed.
- Wrong invoice. Ask Mucka to take the payment off, then record it against the right one. Worth checking the invoice it names back to you when it confirms — that is there so a payment aimed at the wrong invoice is obvious before it settles.
- Payments taken through Mucka record themselves. If a client pays by card from the invoice link, the payment appears against the invoice on its own and the status updates. You only record payments you collected some other way, such as a bank transfer or cash. See Take card payments.