Use “Record a rent payment” in Recued. Records what a tenant actually paid, against their account rather than against an invoice. A partial payment is one receipt for the part; an overpayment is one receipt for the whole, and the credit carries.
Record a rent payment
Use “Record a rent payment” in Recued. Records what a tenant actually paid, against their account rather than against an invoice. A partial payment is one receipt for the part; an overpayment is one receipt for the whole, and the credit carries.
Complete workflow
Use Rental Book in Recued for property, landlord, ledger, and records. It includes 24 built-in actions and 18 ready-to-run workflows.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Add a building” in Recued. Records one building or complex. Units hang off it.
Use “Add a unit” in Recued. Records one rentable unit against a building. It uses the connections and settings you choose when you run it.
Use “Add a tenant” in Recued. Records one tenant and how they pay: cash, autopay, or stripe.
Use “Open a rental contract” in Recued. Binds a tenant to a unit at a monthly rent. The contract is what a period charge is raised against.
Use “Raise the period's rent charges” in Recued. Raises one rent charge per live contract for a billing period. Safe to run unattended on a monthly schedule and safe to run twice — the charge id is the (contract, period, kind) tuple, so a repeat is a no-op rather than a second bill.
Show all 19 recipes
Use “Collection sheet” in Recued. The month's collection list as a table and as CSV, one row per active contract, each carrying the contract id the import matches on.
Use “Import payments” in Recued. Reads the collection sheet back and records one receipt per row that carries an amount and the date it arrived. Re-uploading the same sheet records nothing twice, and a row it cannot record is named rather than dropped.
Use “Tenant statement” in Recued. One tenant's account: everything charged, everything received, and the balance derived from the two. Not read off any invoice, because no invoice knows about the payment that arrived against a different month.
Use “Buildings” in Recued. Every building you hold, with a way into each one's units.
Use “Building” in Recued. One building: what it is, and every unit in it. It uses the connections and settings you choose when you run it.
Use “Unit” in Recued. One unit: who is in it now, and every tenancy it has had. It uses the connections and settings you choose when you run it.
Use “Contracts” in Recued. Live tenancies by default; expired ones only when you ask.
Use “Customers” in Recued. Everyone on the book, most recent first — and the way to start a tenancy for one.
Use “Retire or restore a customer” in Recued. Takes a customer off the working list without deleting anything they are attached to, or puts them back.
Use “End a tenancy” in Recued. Closes a contract on a date. The ledger it produced stays exactly as it is — ending a tenancy is not settling it.
Use “Change the rent” in Recued. Sets a contract's rent. Periods already raised keep the amount they were raised at.
Use “Collect the rent” in Recued. Type what each tenant paid, straight into a grid — one row per live tenancy, one save.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
It records what ARRIVED
Not what was billed. A tenant who owes 1200 and hands you 800 produces one receipt of 800 — there is nothing to mark half-paid, because the balance lives on the ACCOUNT and is derived.
An overpayment is the same act: 1300 against a 1200 charge leaves the account 100 in credit, and next period's statement consolidates it without anyone applying it anywhere.
The day it arrived is YOURS to say
⛔ This used to be the clock. The receipt was stamped with the moment you pressed the button, so a payment that arrived on Wednesday and was entered on Friday was recorded as Friday — and every statement, every ordering, every "last payment" read Friday. Nothing was wrong on screen; the date was simply not the date.
Leave the day blank and today is used, which is right when you are recording a payment as it lands. Fill it in whenever you are catching up: it is the tenant's date, not yours.
⚠ Write it as YYYY-MM-DD. 2026-08-03, not 3/8/26 — a date read two ways is how a year silently reorders itself, so a day that is not in that shape is refused rather than interpreted.
⚠ period is which month the money is FOR, and it is optional. Leave it empty when a tenant just pays money and you would rather the balance sort it out — the statement does not need payments matched to periods to be correct. It is a different question from the day the money arrived: rent for July can turn up in August.
⚠ The amount must be plain digits — 1200 or 1200.50. 1,200.00 is refused, and so is 1.200,00: the same three characters mean twelve hundred in one country and one point two in another, and a rent book that picked one would be wrong about money somewhere. Type the number without separators and nothing has to guess.
⛔ Not to be confused with Invoice Book's record-payment, which settles ONE invoice. This one moves an account balance — a different shape for a different business.
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
=
[object Object]
method
setting
=
cash
period
setting
=
reference
setting
=
contract id
setting
=
[object Object]
received on
setting
=