Use “Record a payment” in Recued. Take a payment off an invoice's balance. Part payments are supported; overpayment is refused rather than absorbed, and the invoice settles when the balance reaches zero.
Record a payment
Use “Record a payment” in Recued. Take a payment off an invoice's balance. Part payments are supported; overpayment is refused rather than absorbed, and the invoice settles when the balance reaches zero.
Complete workflow
Use Invoice Book in Recued for invoicing, receivables, getting paid, and freelance. It includes 17 built-in actions and 9 ready-to-run workflows. Actions that change data use Recued's approval controls.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Issue an invoice” in Recued. Turn the entries you picked into an invoice: lines frozen at issue time, total computed once from minutes, and a balance that payments come off.
Use “Who owes you” in Recued. Every open invoice with what is outstanding, which are overdue, and the oldest one still unpaid.
Use “What each client owes” in Recued. One line per client: what is outstanding, across how many invoices, and how long the oldest has been due.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Use “Add something billable” in Recued. Anything you can charge for that is not logged time — a fixed fee, materials, a call-out. A negative amount is a credit.
Show all 10 recipes
Use “Delete a pending item” in Recued. Remove something from the pending list. If it came from logged hours, you choose whether those hours go back on the unbilled list or get deleted with it.
Use “Pull hours into pending items” in Recued. Turn unbilled time entries into pending billable items, priced at a rate you give.
Use “What could go on an invoice” in Recued. Everything billable and not yet invoiced — hours you pulled across and fees you typed in — each with its id, so you can choose.
Use “Carry a balance forward” in Recued. Close a part-paid invoice and issue a new one for exactly what is left, with the VAT carried in proportion. The new invoice takes no items.
Recording money in
A payment comes off the invoice's balance. Part payments are normal — the invoice stays open until the balance reaches zero, then settles.
⛔⛔ THE BALANCE IS ARITHMETIC ON FIXED-POINT DECIMALS, NEVER FLOATS. total = amount_paid + outstanding holds after every payment. That is the one property worth losing sleep over here: an invoice that reads settled while a few pence are outstanding, or open when it is paid, sends you chasing a client who already paid you.
⛔ An overpayment is REFUSED, not absorbed. Paying more than is outstanding almost always means the wrong invoice, a duplicate entry, or a typo — and silently flooring the balance at zero hides all three. Fix the amount, or record it against the invoice it belongs to.
⚠ A settled invoice takes no further payment. Re-running this recipe with the same figures cannot double-credit, because the second run has nothing left to pay off.
⚠ settled_on is only written when the invoice actually settles. A part payment leaves it alone, because a date on an open invoice reads as the day it was paid off — right by accident on the final payment and wrong every time before it.
⚠ It reconciles nothing. No bank feed, no payment provider. You tell it money arrived.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
note
setting
=
amount
setting
=
0
method
setting
=
reference
setting
=
invoice id
setting
=
[object Object]
received on
setting
=