Checking owner statements takes longer than building them
Technology · Vancouver, BC · Member since 2026 · 258 posts · 65 votes
Most management software can build a month of owner statements in a few minutes. What eats the afternoon is checking them, because one wrong charge on one statement is enough to make an owner question all the others.
Zac Thompson's thread on owner statements last week got me thinking about this, and the approach that made the most sense there was to stop checking every statement and only check the ones that look off. Set a few rules, and anything that trips one gets a person's eyes:
1. The payout doesn't match the reservation or rent roll total.
2. A refund or adjustment landed after the close date.
3. A charge crosses month end.
4. A repair or owner charge is over a set amount, or has no invoice attached.
5. A repair is billed to a property with no open work order.
Everything that passes goes out. Most months that leaves a short list to review, not the whole stack.
The person still owns the judgment calls: whether a charge is fair, a disputed repair, and anything an owner is likely to push back on.
For the managers here: what's the mistake you still catch most often when you check statements by hand?
From the owner's side of that statement, the one I still catch most is a repair billed to the wrong house — or billed with no invoice and no work order behind it.
At 236 houses the dollar amounts are not the problem. A wrong-house charge is. Rent is $1,395 to $1,950 on a 3BR here, so one mis-billed repair can eat a house's whole month and nobody notices, because the total payout still looks about right.
That is why your rules 4 and 5 are the two I would never automate away. No invoice, no open work order, no pay — that one check catches more than re-adding the columns ever will. The math errors are loud. The wrong-house errors are quiet, and quiet errors repeat every month until somebody matches the charge to the house by hand.
From the owner's side of that statement, the one I still catch most is a repair billed to the wrong house — or billed with no invoice and no work order behind it.
At 236 houses the dollar amounts are not the problem. A wrong-house charge is. Rent is $1,395 to $1,950 on a 3BR here, so one mis-billed repair can eat a house's whole month and nobody notices, because the total payout still looks about right.
That is why your rules 4 and 5 are the two I would never automate away. No invoice, no open work order, no pay — that one check catches more than re-adding the columns ever will. The math errors are loud. The wrong-house errors are quiet, and quiet errors repeat every month until somebody matches the charge to the house by hand.
Hi James,
The wrong-house charge is a great example, and you're right that it's the quiet errors that do the damage. A math mistake jumps off the page. A repair billed to the wrong address looks perfectly normal on a statement that still adds up.
Your point about rules 4 and 5 is the part I'd underline too. No invoice and no open work order means no payment, and that one habit protects the owner and the manager at the same time.
At 236 houses, do you match every charge to a work order yourself, or does your team flag the ones that don't line up? Really glad you jumped in on this one.
Appreciate the perspective,
Lee
James's "no invoice, no open work order, no pay" is the rule, and the quiet wrong-house charge is the one I see most on the in-house labor side too. A vendor at least sends an invoice with an address on it. A tech's hours get written down at the end of the day and coded to a house from memory, so the charge is wrong-house before anyone has a chance to check it.
The fix that worked for the property managers I work with was to make the labor charge start at the house instead of at the desk. The tech picks the work order when they start the job, GPS stamps where they actually were and for how long, and the owner line comes off that record. There is nothing to re-match because the charge was never separated from the work order. Lee, that is the version of rule 5 that doesn't need an afternoon.
I built Orca, which is what they use for that part, so grain of salt. For AppFolio shops the labor goes in as a bill import with the work order on the line, so the statement check is just reading it.
Hi Stephen,
That's a great point about in-house labor, and one I hadn't fully thought through. A vendor at least sends an invoice with an address on it, but a tech's hours coded from memory at the end of a long day can be wrong before anyone even looks at them.
Starting the charge at the job instead of at the desk makes a lot of sense. When the work order is picked at the start of the visit, there's nothing to re-match later, and checking the statement goes from an afternoon of work to a quick read.
For the managers you work with, how long did it take the techs to get used to opening the work order before they start? That's usually where new habits either stick or quietly fade.
Thanks for adding this to the discussion,
Lee
From the owner side, the thing that made statement-checking faster for me was keeping my own simple record alongside it, not trying to re-audit every line.
I keep one row per unit per month with rent due, rent paid, any late fee, and the balance left. Expenses get logged the day they happen, with a fixed category list I choose at purchase time — not at year-end when I have forgotten what half of them were. Deposits sit in their own column and never get mixed into rent income, so a deposit move does not make a month look better than it was.
With that in hand, checking a statement becomes an exceptions job, just like you describe. If my row says rent was paid in full and the statement shows something different, that is the line I chase. If a repair shows up with no matching work order, or on the wrong property, it stands out immediately because my own log does not have it.
The discipline is really the timing. Logging it the day it happens takes a minute; reconstructing it a month later is what turns statement-checking into an afternoon.
Hello John,
Keeping your own record alongside the statement is such a smart way to handle it. Instead of re-auditing every line, you're simply comparing two records and looking at the places where they disagree. That turns hours of checking into a few minutes, and it means the questions you send your manager are specific ones they can answer quickly.
What I find particularly interesting is your point about choosing expense categories at purchase time. Most owners end up sorting receipts months later, when half of them have lost their context, and that's how a repair and an improvement land in the same bucket. Deciding up front keeps every month comparable, so you can see how each property is really doing across the year.
I imagine the same habit carries over nicely when something doesn't match. Writing down what you asked and when the answer came back gives you a simple history of which issues keep returning, and that makes your next conversation with the manager a lot more productive.
Really glad to have an owner's voice in this one!
Lee
Lee, I do not match every charge myself — at 236 houses that would be the whole job. The team flags exceptions only: any charge with no invoice attached, no open work order, or billed to a house with no work scheduled that week. Those come to me as a short list. Everything else pays in the normal run. I spot-check a few clean statements each month so the flagging stays honest. The rule stays simple: no invoice and no work order, no pay — and a wrong-house charge gets reversed the same day it is caught, not at month end.
Hey James,
That's a really smart setup. The team only brings you the exceptions, and the spot-checks on a few clean statements keep the whole system honest. A lot of owners skip that last part, and that's usually how a good rule quietly stops being followed without anyone noticing.
Reversing a wrong-house charge the same day it's caught matters more than it sounds, too. If it waits until month end, it has already landed on an owner's statement, and that's when trust takes the hit, not when the mistake was made.
At 236 houses, a short exceptions list and a same-day fix is about as clean as it gets.
Appreciate you walking through it,
Lee
No invoice, no open work order, no payment is the whole game. One check I'd add before anything else: tie the total payout back to the rent roll first. A wrong-house charge can hide inside a total that still adds up. Math errors are loud, but wrong-house errors are quiet and repeat every month until somebody matches each charge to the property.
What makes it stick is not counting the job as done until the invoice, an after photo, and the address are all in. Until then the work order stays open, and a Friday sweep chases anything missing instead of a scramble on the 1st.
Full disclosure: I build offline document tools for property managers (invoice-to-work-order matching that runs on your own computer, so tenant files never hit ChatGPT). If anyone wants to see it on 10 redacted invoices, I'm happy to run it free.
Afternoon @Kevin McDermott,
Tying the total back to the rent roll first is a great addition. You're right that a math error usually jumps out at you, but a charge sitting on the wrong house can look perfectly normal inside a total that still balances, and it can quietly repeat for months before anyone matches it to the property.
I also really like the idea of not counting a job as finished until the invoice, an after photo and the address are all attached. It moves the checking to the moment the work is closed, while the tech still remembers the job, instead of leaving it for whoever reads the owner statement weeks later.
For a manager running a few hundred doors, I think that one habit probably does more to protect an owner's trust than any amount of checking at month end.
Thanks for adding to this one,
Lee