The Rent Arrears Build Standard
Rent accrues, and the escalation clock is written in legislation rather than in your credit policy. How to build arrears handling that respects both, and that knows when to stop.
Does the work of
- Property Manager
- Arrears Officer
- Head of Property Management
Your platform already sends the automatic reminders, and it should keep sending them. Those collect the tenancies that were going to pay anyway. What is left is a short list where something is genuinely wrong, and each one needs a conversation on a particular day. Automating arrears does not mean sending more messages. It means producing that short list correctly, and never messaging anyone who should not have been on it.
In short
- What this is
- An open build standard for arrears triage and escalation across a rent roll. Implement it in whatever you like.
- The core rule
- Arrears is a derived position, not a stored number, and the escalation clock belongs to legislation rather than to you.
- What it never does
- Serve a notice, apply a fee, or message a tenant whose ledger has not been verified. Drafting is the boundary.
- The hard part
- Knowing when to stop. A chase sent to someone who already paid, or who is in hardship, costs more than the arrears.
Want the whole thing by email?
This paper, plus the rest of the library. One click to stop them.
1. What this standard covers
Deciding, every day, which tenancies in a rent roll need a human to do something, and preparing that something. It covers triage, escalation timing, and the record. It does not cover serving notices or representing anyone at a tribunal.
Why arrears is not accounts receivable
An overdue invoice sits still: the amount is fixed and the counterparty is a business. Rent accrues. A tenant four days behind is five days behind tomorrow whether or not anyone opened the file, the counterparty lives inside the asset, and the escalation path is set by state legislation rather than by your credit policy. Anything built on receivables assumptions will get the timing wrong in both directions.
2. Derive the position, never store it
An arrears position is the output of a calculation over the ledger, not a number to be cached. It changes every day without anyone touching it, which is the property that breaks most implementations.
Three things have to be derived together, and reported together:
- Paid-to date — the date rent is paid up to, which is the figure legislation and tribunals reason about
- Days in arrears — derived from paid-to and today, not from when someone last looked
- Balance — the dollar figure, which is the least useful of the three on its own
Report the paid-to date first. A balance of $1,840 means nothing without knowing whether that is a fortnightly rent eight days late or a weekly rent a month behind, and the statutory clock runs on days, not dollars.
3. The four triage outcomes
Every tenancy showing arrears resolves to exactly one of these, and the ordering matters: check for the first before assuming any of the others.
Outcome 1
Not actually in arrears
Payment in transit, a part-payment misapplied, rent paid to the wrong reference, a ledger timing artefact
Suppress the chase and flag the ledger, never message the tenant
Outcome 2
Will self-resolve
A day or two behind, consistent payer, no history
The platform reminder is enough. Do not escalate a pay cycle
Outcome 3
Needs a conversation
Something has changed: a pattern break, a part-payment, a first-time miss on a long tenancy
Surface to a person with the history attached. This is the list that matters
Outcome 4
On the statutory path
The arrears period is at or past the threshold for formal action
Draft the notice, never serve it. Dates and service method are legal facts
Outcome 1 is checked first and is the reason to build this at all. Chasing someone who already paid is the single most damaging thing an arrears process does. It is also common, because payments arrive with the wrong reference, land on a weekend, or get applied to the wrong tenancy. A system that assumes the ledger is right will generate exactly this error at scale and much faster than a person would.
4. The stop conditions
A chase must not be sent when any of these is true. Evaluate them before every message, not once when the sequence starts — circumstances change mid-sequence and that is precisely when an automated chase does its damage.
Payment received or in transit
Including a part-payment that changes the position, and anything received since the list was built.
A payment arrangement is in place
If the tenant is meeting an agreed plan, they are not in arrears for chasing purposes even though the balance says otherwise.
Hardship, dispute or advocacy is on file
Once someone is engaged with a support service or has raised a dispute, the matter belongs to a person.
The tenancy is already on the formal path
Once a notice exists, messaging outside it can undermine it. One channel at a time.
A person has paused it
Explicitly, with a reason and a review date. The pause must survive the next run.
The ledger is unverified or the data is stale
If the feed has not updated, the correct action is to send nothing and raise it.
5. Six rules that keep it trustworthy
The clock belongs to legislation.
Thresholds for formal action are set per state and territory and they move. Hold them as dated, versioned rules the way a compliance calendar does, not as constants in the code.
Draft the notice, never serve it.
A breach or termination notice is a legal instrument whose date and service method are facts a tribunal will examine. Prepare it, present it, let a person serve it.
Verify the ledger before every message.
Not when the run starts. Between building a list and sending from it, someone will have paid.
Escalate the exception, not the balance.
The useful output is the short list where something has changed: a pattern break, a first miss on a long tenancy, a part-payment. A ranked list of everyone who owes money is what the platform already gives you.
Silence is a finding.
A tenant who has never missed and now has, and does not reply, is the highest-value row on the list. Non-response is a signal, not an absence of one.
Never apply a fee or a charge automatically.
Whether a fee is even lawful depends on the tenancy and the jurisdiction. This is not a decision to make at machine speed.
6. The parts that are harder than they look
Payment matching
Rent arrives by bank transfer with whatever reference the tenant typed, from an account in someone else's name, sometimes split across two payers on one tenancy. Unmatched receipts sitting in a suspense account are the most common cause of a wrongly chased tenant, and fixing arrears usually means fixing this first.
Part-payments and irregular cycles
A tenant paying $300 a week against a $420 rent is in arrears and paying. Fortnightly and monthly cycles, mid-cycle rent increases and pro-rata first periods all break naive day counts.
The paid-to date is not always what the platform says
Different systems compute it differently, particularly around part-payments and credits. Before automating anything, confirm the figure you are reading means what a tribunal would take it to mean.
Jurisdiction, and rent rolls that cross a border
Thresholds, notice periods and permitted contact all differ by state and territory. An agency with properties either side of a border needs the rule to know which applies.
Hardship is not a field
It arrives in a phone call, a text, or a support worker's email. If it lives only in someone's memory, the automation will keep chasing straight through it, which is the worst failure this system can have.
The owner is the second conversation
The landlord has views about how hard to push, and they are not always consistent with the legislation or with each other. Whose instruction governs, and where that is recorded, is a design decision you cannot avoid.
7. When the chase becomes a conversation
Everything above produces a short list of tenancies where somebody needs to talk to somebody. That is the point at which this standard stops being a data problem, and it is worth being honest about what changes.
Text and email are one-way. They deliver a message and wait. A conversation is different in kind: it has to hear an answer it did not expect, decide whether that answer is a stop condition, and get the next sentence right in front of a person who may be embarrassed, angry or in genuine hardship. A prototype that handles the expected reply is not most of the work — it is the beginning of it.
What hardening a conversation actually means
- Every branch a real tenant takes. “I paid yesterday.” “I lost my job.” “Talk to my advocate.” “That’s not my rent, I split it with my partner.” Each is a different outcome and one of them ends the call immediately.
- Recognising a stop condition mid-sentence. Hardship does not arrive as a form field. It arrives halfway through an explanation, and the conversation has to stop pressing the moment it does.
- Never negotiating. A payment arrangement is a decision with legal weight. A conversation may capture a proposal; it must not agree to one.
- Compliance while talking. Disclosure that it is an AI, permitted contact hours, recording consent, the Do Not Call position, and what happens if the person asks to stop.
- Reading the live ledger during the call. If a payment landed this morning, the conversation needs to know before its second sentence, not after.
- Writing back what was actually said, in a form the next person and a tribunal can both read.
This is the part of the standard we would not expect anyone to build from scratch, and the honest reason is not complexity — it is that a conversation fails in public, with a tenant, on a topic with legal consequences. The iteration required to make one safe is not a weekend, and the failure mode is not a wrong number in a queue.
Where this leads
This is the problem Office Voice exists for: a voice agent that reads live accounting data during the call, handles the branches, holds the compliance line, and writes back what was said. If you have built everything above and the remaining gap is the conversation, that is the piece to buy rather than build.
The rest of this standard stands on its own. A build that stops at the short list and hands it to a person is a good build, and most of the value is already in it.
8. What breaks after it works
- A threshold changes and nobody notices. The escalation dates are now wrong across the whole rent roll, in the direction of acting too late or too early.
- The suppression list decays. Hardship flags and payment arrangements are set once and never reviewed, so either they expire and the chasing resumes wrongly, or they never expire and real arrears goes unworked.
- It leaves when they do. Which tenants are genuinely struggling, which owners want a hard line, which references are habitually wrong — none of it is in the system.
- Nobody can show what was sent. At a tribunal the question is what was communicated and when. A sequence that fired without keeping the sent copy cannot answer it.
9. Conformance checklist
- The arrears position is derived from the ledger on every run, never cached.
- Paid-to date is reported alongside the balance, and drives escalation timing.
- Statutory thresholds are held as dated, per-jurisdiction rules, not constants.
- Every stop condition is evaluated immediately before each message, not once per sequence.
- A tenancy with an unmatched or stale ledger is escalated, never chased.
- Notices are drafted and never served without a person.
- No fee or charge is applied automatically.
- Every message sent is retained with its timestamp and recipient.
- If a conversation is automated, it discloses itself, respects contact hours, stops on hardship, and never agrees to a payment arrangement.
- Someone other than the builder can explain what it does, and it runs on an account the business owns.
Build it yourself, or have it built
This standard is free to implement and we would rather it was followed than owned. If you build it, the conformance checklist is the thing to hold your build to, and you are welcome to it whether we ever speak.
- Before you start— confirming what your platform’s paid-to date actually means, and how bad the unmatched receipts problem is.
- When it is stuck— usually payment matching, part-payments, or where hardship gets recorded.
- When the last gap is the conversation— section 7. Hardening a voice agent that holds a compliance line in front of a tenant is the piece worth buying.
- When the person who built it has gone— taking over a working process and documenting it against this standard.