OWNER WORKFLOW GUIDE
From Maintenance Request to Accounting Expense: A Better Commercial Property Workflow
A narrative walkthrough of how one $275 plumbing repair travels from a tenant's 9 a.m. complaint to a categorized expense in QuickBooks — and what gets lost when nothing connects the two.
A maintenance expense doesn't start as a number. It starts as a tenant noticing something is wrong and telling someone about it. Here's what actually happens, step by step, to the dollars in between — and what's missing when nothing carries the story forward.
9:14 a.m. — a tenant's email, not yet a dollar amount
At 9:14 a.m., a tenant in Suite 4 emails the property manager: the bathroom sink won't drain. Whoever handles maintenance intake logs it as a work order — tied to the tenant, the unit, and the property — inside the same system that already knows that space's lease and CAM allocation.
At this point there is no dollar amount anywhere in the record. This is purely operational: a problem reported, a location identified, a category assigned. It has no accounting weight yet, and it shouldn't, because nothing has been spent.
- The work order carries the tenant, unit, and property from the moment it's created
- A category (plumbing) is assigned before a vendor is even chosen
- The original complaint — what the tenant actually wrote — stays attached to this record permanently, not just in an email thread
- No invoice, no bank activity, no accounting entry exists yet
2:00 p.m. — a plumber, an invoice, still not an accounting event
The property manager dispatches a plumber. By 2:00 p.m., the vendor — Roto-Rooter, in this walkthrough — has snaked the line and invoiced $275. That invoice attaches to the same work order: vendor name, amount, date, a one-line description of the job.
This still isn't an accounting event. No money has left the property's bank account yet. What exists so far is a complete operational record of a repair — who reported it, who fixed it, what it cost — sitting entirely on the maintenance side, with nothing yet posted anywhere that resembles a general ledger entry.
- The vendor, amount, and invoice date are now attached to the same work order as the original complaint
- The work order status reflects that the job is done and awaiting payment
- $275 exists as a number on a maintenance record, not yet as a bank transaction or an expense
- None of this has touched the bank account yet — that happens on its own timeline, set by the vendor's own invoicing and payment terms
Four days later — $275 leaves the bank with no name on it
Four days later, the $275 clears the property's bank account as an ACH debit. On the bank statement — and in TenantPoint's own bank feed, built on a live, read-only connection the owner set up once from the Banking screen — the line reads something like "ROTO-ROOTER ACH DEBIT." There's no mention of Suite 4, no mention of a work order, no reference number tying it back to anything.
This is the moment where, in a lot of property accounting workflows, the connection quietly breaks. The bank doesn't know what the money was for. If the same plumber did work at two different properties that month, both debits would look identical sitting side by side in the feed — same payee, similar amount, zero distinguishing detail.
- The transaction description carries the vendor's name and nothing else — no unit, no property, no work order reference
- Two similar debits from the same vendor at two different properties look identical in the raw feed
- The $275 is real, already-spent money — but it isn't categorized as anything yet
- Left alone, it would sit in the feed as an unexplained line indefinitely
The reconciliation — where the anonymous line becomes a maintenance expense
This is where a person closes the loop. A property manager or bookkeeper opens the bank feed, finds the $275 debit, and manually reconciles it — tying it to the original Suite 4 work order. This match is deliberate, not automatic: TenantPoint doesn't guess which work order an unlabeled bank line belongs to, even when there's only one open job for that vendor that week. Someone has to look at both records and confirm they're the same event.
The moment that tag is made, the anonymous $275 becomes a categorized maintenance expense — attached to the right property, filed under the right category, and permanently linked back to the 9:14 a.m. email that started it. Once it's pushed, it posts to QuickBooks as a Purchase rather than a Bill, since the money had already left the account by the time anyone recorded it there — there's no unpaid-obligation stage left to represent.
- Reconciling and tagging a bank transaction to a work order is a manual step performed by a person, every time — never inferred automatically
- Once tagged, the $275 carries the property, the expense category, and the original work order reference as one connected record
- The push to QuickBooks happens exactly once per transaction; a retried or interrupted sync doesn't create a duplicate $275 entry
- The deeper mechanics of how that record is structured in QuickBooks are a more technical question, covered separately from this walkthrough
The version of this story without a throughline
Now run the same $275 through a workflow where that reconciliation step doesn't happen, or happens in a spreadsheet disconnected from the original request. The bank debit still clears. It still says "ROTO-ROOTER" and nothing else. But nothing ties it back to Suite 4, and nothing ties it back to the tenant's original email. Six months later, during a year-end review or a CAM true-up, someone finds that $275 line and has to guess: which property was this, which unit, was it billable to a tenant or an owner cost? The original complaint, meanwhile, is sitting in an inbox that may or may not still have that thread.
That's the actual value of the throughline, not any single step in it. One tenant request, traceable in a straight line to one dollar amount in the books — forward, from the 9:14 a.m. email to the categorized Purchase, and backward, from that same $275 line in QuickBooks all the way to the original complaint. Neither direction requires anyone to remember, search an inbox, or reconstruct what happened from a vendor name alone.
- Without the connection: a $275 debit with a vendor name and nothing else, months after the fact
- Without the connection: a tenant's original complaint living only in an email thread nobody thinks to search
- With the connection: the property, unit, tenant, vendor, and dollar amount are all one record
- With the connection: answering "what was this $275 for" takes one lookup, not an investigation
Frequently asked questions
Does TenantPoint automatically match the bank debit to the work order?
No. Tying a bank transaction to a work order is a deliberate, manual step a property manager or bookkeeper performs. TenantPoint never guesses which work order an unlabeled expense belongs to, even when the match looks obvious from the amount or timing alone.
What happens if nobody reconciles the bank transaction to the work order?
The $275 just sits in the bank feed as an uncategorized debit. It never becomes a QuickBooks Purchase and never links back to the original maintenance request. The throughline only forms when someone actually completes that reconciliation step — there's no fallback that builds it for you.
Does this same path apply to a repair that hasn't been paid yet?
Not this one specifically. Everything in this walkthrough starts once money has actually left the bank account. An invoice sitting unpaid lives only on the work order and hasn't triggered any push toward QuickBooks yet — the accounting mechanics on either side of that line are a more technical question, covered in depth elsewhere on this site.
Is the tenant's original email preserved anywhere besides the inbox?
Yes. Once it's logged as a work order, that complaint becomes a permanent part of the work order record — attached to the same object as the vendor, the invoice, and eventually the QuickBooks entry, rather than depending on someone finding an old email thread six months later.
USE THIS WITH ONE REAL PROPERTY
Stop rebuilding the operating record every month.
Start a 15-day trial, add one property, and bring the lease, rent, CAM, and tenant communication into the same workspace.