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.

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 “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.