Somewhere in last quarter's bank statement there is a plumber's bill you approved in under a minute, because the job was real and the price was fair. It was paid on time, and the plumber would take your call tomorrow. What the statement does not say is which building the plumber was standing in.
Paying a bill feels like finishing it. The money leaves, the vendor is satisfied, the line lands under repairs, and the office moves on to the next thing that needs doing, which is the right order of priorities for an office with forty other things to do. The trouble is that nobody asks about a bill on the day it is paid. They ask in March, when the owner wants to know why repairs at one building doubled; in June, when a buyer's accountant wants three years of maintenance by address; in the week a contractor says the last invoice was never settled. Each of those questions is answered from the same pile, and the pile was built to pay bills, not to answer questions.
The first cost is the search. The job description is in the contractor's email subject line, the approval is in a reply, the PDF is in a downloads folder, the payment is on the bank statement, and the building is in your head. Assembling what one building cost this year means visiting all five places for every bill and trusting your memory for the ones the subject line does not name. It takes an afternoon, it is done once a year, and it is short by the bills that were paid on a card at the counter.
The second cost is the recharge. The owner's invoice for the repair is a second document built by hand from the first, so two descriptions of one job exist and only one of them was written by the person who did the work. The owner sees a round number, asks what it was for, and the answer is a forwarded email. Nothing about that is careless. It is the invoice being made after the job instead of from it.
The third cost is the one figure. On the income statement, repairs is a single line for the whole portfolio, and a line for the portfolio cannot tell a bad quarter at one building from a bad quarter everywhere. The split by building happens in a spreadsheet at year end, from memory and subject lines, and one bill filed under the wrong address moves that building's margin by the size of the bill. The owner statement inherits whatever the spreadsheet decided.
A bill is paid once and asked about for years. The record of what it bought is the asset.
Handled differently, the bill never loses the job. The work order exists before the contractor does, linked to the building and to the request that started it. The contractor's invoice is recorded on that work order the day it arrives, with the PDF attached and the lines as billed. The owner's invoice is raised from the same job, so the recharge is the job seen from the other side, and the entry that posts carries the invoice number on every line. The question in March becomes a list of jobs with their bills beside them. The question in June becomes a report run by date.
What stays yours is the judgment: whether the bill matches the quote, whether the work was a repair or an improvement, whether the owner should see it this month or next. None of that gets easier. It just stops being done from memory, on a deadline somebody else set.
Scaalr puts an Invoices tab on every work order: a contractor's bill is recorded there as a payable invoice, addressed to the contractor from your directory with the PDF attached, and it posts to the books the moment it is saved, with the invoice number on every line, while the owner's repair invoice is raised from the same job. How to run that from the first work order to the building's statement, step by step, is in Track Maintenance Costs per Property With Work-Order Invoices.
For the complete guide to tracking maintenance spend per property, see: Track Maintenance Costs per Property With Work-Order Invoices.
$99 covers your first 50 units, Alex included. Cancel anytime.