To automate rent collection, move the schedule out of your head and into the system of record: rent charges generate themselves from each lease on its own cycle, every payment is recorded once against the charge it pays, overdue reminders send themselves, and a balanced accounting entry posts behind every move. What stays yours is the judgment: the payment terms, the exceptions, and the decision of what to do when the rent does not arrive.
Here is the morning that process replaces. It is the 3rd, 8:40 AM, and you are finding out what happened on the 1st: the bank tab on one screen, the spreadsheet on the other, matching deposits to units. $1,450 is unit 12. $2,900 is either one payment or two. Unit 31 is short again, which you know because you remember, not because anything says so. Two hundred units in, who has paid is a research project, and it is the same project every month.
What automated rent collection actually automates
Automated rent collection is software that creates each period's rent charges from the lease itself, tracks every payment against the charge it belongs to, sends the overdue reminders, and posts the accounting behind each move, with nobody keying the cycle by hand.
Most write-ups treat automated rent collection as a synonym for autopay: the resident authorizes a recurring debit and the money moves on the 1st. Autopay is one leg of the cycle, and it is the leg that belongs to the resident. The operator's side of the cycle is four legs, and all four can run automatically whether or not any resident automates their own payment: creating the charges, knowing where each one stands, chasing the ones that go quiet, and keeping the books true behind all of it. An operator who automates those four has automated rent collection even if every resident still pays by check, because the work that consumed staff time was never the payment itself. It was everything around it.
The rent collection process, step by step
The process is the same at four units or four hundred, in any system, and each step exists to keep a later one honest.
- Fix the terms in the lease. Amount, frequency, due day, grace period, late fee. The lease is the source of record, and every step below reads from it.
- Create the period's charges from the lease. Never from memory and never by copying last month's row. A charge that was never created is rent that is never chased.
- Tell residents how to pay, once, in writing. The accepted methods, where each one goes, and what counts as the payment date.
- Record every payment against its charge the day it arrives. Against the specific charge, not into a running balance, so a partial payment or a dispute stays traceable to the month it belongs to.
- Work the exceptions from statuses, not memory. Overdue, partially paid, disputed: each should be a list you open, not a set of facts you recall.
- Close the loop in the books. Every charge, payment, fee, and reversal becomes a balanced entry. Collection you cannot reconcile is collection you cannot prove.
- Read the cycle before it ends. Collected against due, and what is still open, while there is month left to act on it.
Where the money stands: the rent roll and the rent ledger
Two records carry the state of the cycle, and they answer different questions. A rent roll is the live list of every tenancy's rent: who owes what, on which cycle, and where each charge stands right now. It answers the portfolio question, this month. A rent ledger (the per-tenancy history of charges and payments) answers the other one: how a tenancy got to its balance, month by month, payment by payment.
Both records are only as good as the states they carry. A charge is scheduled, then due, then paid, partially paid, or overdue, and eventually closed one way or another: collected, waived, written off, or refunded. When those states live on the record, the roll is a report you open. When they live in a person, the roll is a reconstruction, and it is rebuilt from the bank statement every month by whoever holds the most history in their head.
Partial payments, late fees, and the other exceptions
The exceptions are where a clean cycle gets tested. A partial payment should land against its charge and leave the shortfall visible: the charge stays open, the balance shows, and the month it belongs to is never in doubt. A late fee should be recorded as its own line beside the rent rather than blended into it, so fee income and rent income stay honest in the books. A payment that bounces should reverse cleanly and put the balance back where it was.
Then there are the endings that are decisions rather than payments: waiving a charge you chose not to pursue, writing off rent that will not arrive, refunding money that has to go back. Each of those is a judgment call, each changes the books, and each should demand a recorded reason at the moment it happens. The decision framework for that last mile, when to keep chasing and when to close a charge out, is its own topic; the process rule here is narrower: no charge disappears silently, and every ending posts its matching entry.
What automates and what stays yours
The division of labor, leg by leg:
| The leg | Who carries it | What that means |
|---|---|---|
| Creating the period's charges | The system | Generated from each lease on its own cycle; nobody keys the month in |
| Knowing who has paid | The system | A status on every charge; the roll is a report, not a reconstruction |
| Overdue reminders | The system | Sent on schedule, throttled, with replies routed to a person |
| Paying | The resident | By card on a secure per-invoice link, or by any offline method you accept |
| Recording offline payments | Your staff | One entry against the charge, dated, attributed, and receipted |
| Waive, write off, refund | Your staff | A decision with a recorded reason; the entry posts itself |
| The bookkeeping | The system | A balanced entry behind every charge, payment, fee, and reversal |
How rent collection runs in Scaalr
Rent collection software is judged on exactly those legs, and this is how Scaalr carries them. Every night, a background service creates the next rent charge for every active lease due that day. Five billing frequencies are supported (monthly, weekly, biweekly, annual, and one-time), each reading the lease's own schedule: monthly charges fire on the chosen due day with month-end handling, so a lease due on the 31st bills correctly in February, and weekly and biweekly charges fire on the chosen weekday. Each new charge inherits the lease's amount, currency, and residents, and generation is duplicate-proof, with a database-level safeguard against double-billing even across multiple servers.
The rent roll is the working surface. Tabs filter to Active, Overdue, Paid, In Dispute, Closed, and All, with narrower cuts beneath them, and every charge carries one of eleven color-coded statuses, from Scheduled and Pending through Partially Paid, Overdue, Waived, Written Off, Refunded, and In Dispute. Each charge links to its lease, its unit, and its residents, and opens to a detail page with a Payments tab showing running totals and the outstanding balance. A charge's status stays in sync with its lease, and a one-click action flips any fully-paid charge that is still showing open to Paid.
Recording a payment is one click: amount, an optional method and note, and an optional fee. A shortcut records the full balance, partial payments move the charge to Partially Paid with an overpayment guard, and a late fee entered with a payment is booked as its own line. The payment history shows the date, amount, method, note, and which staff member recorded it, reversed and refunded payments are badged automatically, and a toggle reveals the underlying journal entry behind any payment, down to the debit and credit.
The endings demand their reasons. Cancel, Waive, Write Off, and Refund each require a stated reason and post the matching accounting entries: a write-off lands in Bad Debt Expense, and a refund returns money from the bank. Back-dated edits into closed accounting periods are blocked, one-off manual charges are supported, and editing a charge's financial fields automatically reverses and re-creates its entries rather than leaving the books stale.
When rent goes quiet, the reminders leg wakes up. A nightly sweep flags charges more than three days past due and emails every resident on the charge a branded Overdue Rent Payment Notice. Nobody is re-emailed about the same charge more than once every three days, reminders respect a per-lease opt-out, and the notices carry your mailbox as the reply-to address, so a resident who answers reaches a person.
The card leg runs through invoicing. An emailed invoice carries a Pay Now link to a secure, branded page the resident opens without an account, with Apple Pay where available and no added platform fees; a successful payment posts its entry, marks the invoice paid, and is linked to the matching open rent charge where possible, so the roll updates without anyone touching it. The full flow, from line items to the no-login payment page, is covered in Invoicing for Property Management: Residents, Owners, and Contractors, and the rent-specific answer, from the card and Apple Pay question to collecting online without a tenant portal, is covered in Can Tenants Pay Rent by Credit Card? Yes, and They Don't Need a Portal. Invoice emailing and online card payments are Growth and up.
Behind all of it sit the books. Every rent move posts a balanced double-entry journal tagged back to the charge: charges, payments, late fees, reversals, refunds, waivers, and write-offs alike, with each charge carrying its own currency and tax booked separately to Sales Tax Payable. That is the same automatic-postings spine described in Property Management Accounting: The Complete Operational Guide, and it is what makes month-end a review instead of a rebuild: the deposits you match in Bank Reconciliation for Property Managers: A Step-by-Step Guide arrive with their ledger entries already posted. The dashboard keeps the cycle honest in between, with a collection-rate card showing cash collected against rent due so far this cycle, per currency and stamped as-of today, and an attention tile for overdue rent with the amount owed. And when the rent itself changes, the increase rides its own scheduled, validated process, covered in How and When to Raise Rent: Scheduling, Notice Periods, and Documentation. Rent collection is part of every plan, including Starter.
The same morning, current
Back to the 3rd. The charges for the month existed before anyone woke up on the 1st, because the leases say what they are. The roll shows collected against due as of this morning, unit 31's charge sits at Partially Paid with the shortfall visible, and the two payments that arrived by bank transfer yesterday were each recorded in a click against their own charge. Nothing about the month needs reconstructing, because none of it ever existed only in your head. Your first act of the month is a decision, not a census.
Key questions
Does automated rent collection mean putting residents on autopay?
No. Autopay is one leg of the cycle, the payment itself, and it is the leg that belongs to the resident. The operator's side automates whether or not the resident automates theirs: charges that generate themselves, statuses that track every payment, reminders that send, and entries that post. Scaalr does not offer resident autopay or ACH; residents pay by card on a secure per-invoice link, and staff record payments that arrive any other way.
What day of the month should rent be due?
Whatever day the lease says, and the first of the month is the convention for a reason: one due day across the portfolio makes the cycle readable, and month-start aligns with how most residents budget. A grace period, if the lease grants one, delays the late fee, not the due date; rent paid inside it is still late. Whichever day you pick, the schedule has to enforce it, because a due day that lives in memory drifts.
Should I accept partial rent payments?
Only with a policy you set in advance and apply identically to every resident. Record whatever you accept against the specific charge, so the shortfall stays visible instead of blending into a running balance. A partial payment is better than nothing and worse than a plan, so pair it with a dated agreement on the remainder. One caution: in some jurisdictions accepting a partial payment affects an eviction already in progress, so know your market's rule before you set the policy.
How do I keep track of rent payments?
Record every payment against the charge it pays, on the day it arrives, with the method and who took it, and let statuses carry the state: paid, partially paid, overdue. A spreadsheet can hold this discipline at a handful of units. What breaks at scale is not the arithmetic but the reconstruction: a ledger that only says what came in cannot say what is missing, and rent collection is mostly the second question.
Which Scaalr plan includes rent collection?
All of them, including Starter. Charge generation, the rent roll, payment recording, overdue reminders, and the accounting behind every move are part of every plan; Starter is free for the first 5 units, then $0.99 a unit a month. Growth, at $99 a month for the first 50 units and then $1.49 per additional unit, adds invoice emailing and online card payment, which is how residents pay rent by card on a no-login link.