Where the story behind a statement gets lost
Picture the first week of the month. The statement goes out, and an owner calls within the hour: "What is this four-figure charge on the triplex?" It is the water heater replacement she approved three weeks ago. But her approval sits in one manager's inbox, the quote is a PDF in a vendor thread, the photos of the leaking tank are on a maintenance tech's phone, and the statement line just says "Repairs, Unit B." The money is right. The story behind it is scattered.
Property managers do not need a new accounting system to fix this. The ledger, trust accounting, and owner disbursements should stay in the property management or accounting software you already use. What is missing is the record around the numbers: what was proposed, what the owner approved, when, at what amount, and which statement line it became. TwoQM develops custom software, owner portals, CRM workflows, and connected systems for property management companies that need that shared record.
Here is an original example, not a TwoQM client and not a measured result. A small company manages single-family homes and a few small multifamily buildings for about twenty owners. In one quarter, a roof repair on a duplex turns into a partial replacement, a water heater fails, and a parking lot needs resealing on a building with two co-owners. Approvals arrive by text, by phone, and by a "sounds good" reply to a forwarded quote. When statements go out, the office spends days digging through threads.
The gaps tend to repeat:
Approvals live in email, texts, and phone notes instead of with the work.
The approved amount and the final invoice differ, and nobody explains why.
Capital projects and routine repairs look the same on the statement.
Owners cannot see what is proposed or pending until it shows up as a charge.
Co-owners each hear a slightly different version of the story.
Separate routine repairs from capital decisions
Not every expense needs the same path. Write the rules down, per owner where they differ:
Approval threshold. The amount a manager may approve without asking, as stated in the management agreement.
What counts as a capital project. Replacements and improvements versus routine repairs, defined the way you and your accountant already categorize them.
Bids. When you collect more than one quote, and how you present them.
Who must approve. A single owner, every co-owner, or an owner's designated representative.
Emergencies. What you may do first and report afterward, as your agreement allows.
Software applies these rules consistently. Your management agreement and your accountant define them; nothing here is accounting, tax, or legal advice.
Give every capital item one record
A capital approval request should be a record with a clear lifecycle:
Proposed. Scope, reason, photos, quote or quotes attached, and estimated amount.
Sent to owner. A clear question and a requested response date, delivered through the owner portal.
Decision. Approved, declined, or questions, with the owner's name, time, and comment. Each co-owner's approval is collected separately.
Scheduled. Vendor and dates.
Completed and invoiced. Final invoice attached, with any difference from the approved amount explained.
On statement. Linked to the statement period and the line item it became.
Now "Unit B water heater replacement" on the statement leads to the whole story: the photo, the quote, the approval, and the invoice. The manager opens one record instead of five inboxes.
An owner view that answers questions before the phone rings
An owner portal does not have to replace the statements your accounting software already produces. It can sit beside them and show what owners ask about:
Current and past statements, pulled from your accounting system
Approvals waiting on their decision
Approved projects in progress, with status
Completed projects with invoices and photos
Messages tied to a specific project, not a general inbox
Permissions matter more than features. Each owner sees only their own properties, co-owners see the properties they share, and vendors see none of it. Agree on roles before anyone builds. When your platform's built-in owner portal cannot show approvals next to statements, that is a case for focused custom software.
Connect the accounting instead of retyping it
Statement figures should come from the system that holds the ledger. That is connected systems work: pulling statement data or documents from your property management platform, and passing the approved project reference back so the bill is coded consistently. What your platform allows through an integration or export is confirmed during scoping. Sometimes the right answer is a monthly upload plus a task for the bookkeeper, logged on the same record.
Automation first, then AI drafts a person reviews
Ordinary business automation covers the routine: sending approval requests, reminding owners before the response date, alerting a manager when an approval is overdue, notifying the owner when an invoice is attached, and flagging invoices that exceed the approved amount by more than your tolerance.
AI fits where the language is messy and a person still decides. It can turn a vendor's long scope of work into a plain-language draft request for the owner, draft an explanation of a cost difference, or draft a Spanish version for an owner who prefers Spanish. A manager reviews every draft before it is sent, and AI never approves spending, changes amounts, or posts to the ledger.
Where to start this week
Pick your last three capital projects and trace each one from first quote to statement line. Count the places you had to look and the approvals you could not find in writing. Then put each owner's approval threshold and co-owner rule on one page.
If you want owner statements and capital approvals on one record your team and your owners can trust, TwoQM can scope it around your agreements and the platform you already use. Pricing explains how business apps, systems, and custom software are scoped.
Describe Your Owner Approval Workflow · Explore TwoQM custom software