// Property and HOA management · The one job
Vendor invoices, coded to the right property and GL account.
One AP job, run on copies of bills your team has already entered. Your reviewer checks each draft's property, GL account, owner or association, fund and approval flag against what was actually posted.
- Posted invoices
- 20 to 30
- Logins to AppFolio or Yardi
- None
- Resident ledgers
- Never
// The one job
An invoice arrives. A coded bill is drafted.
A vendor emails a PDF: the landscaper's monthly invoice, a clubhouse water bill, a plumber's invoice for a work order in unit 12. Today someone in AP decides which property or association it belongs to, which GL account it hits and whether an owner or board must approve it, then keys the bill.
For the test, AI reads the same invoice and drafts the coded bill: payee, property, GL account, each property's share, the fund, the work order and an approval flag. Nothing posts anywhere. We call this step the sandbox, and your reviewer judges it against the bills your team posted.
for review
// What makes it hard
Where property AP coding goes wrong
One vendor, several properties, one invoice. A landscaper that services six of your communities often sends one monthly invoice, sometimes listing each site, sometimes only a total and a contract number. The draft splits it the way your team does, by line or by each property's contract amount. In Yardi Voyager each detail line on a payable carries its own property and GL account, so your reviewer checks every share, not just the total.
Utility bills. Water, electric, gas and trash bills arrive per account number, and the service address or meter decides the property and sometimes the unit: a clubhouse, irrigation, a vacant unit between residents. The amount to post is the current charges, not the past-due balance printed above them. Late fees often go to a different GL account than usage, and a billing period that spans two months raises the post-month question.
Work orders and maintenance invoices. A plumber's or HVAC invoice usually cites a work order, a unit and the work done. The draft ties it to the work order your team opened and separates a repair from a replacement, which often codes to a different account. A part meant to be billed back to a resident is flagged and stops there.
The association's chart of accounts and its funds. Each HOA or condo association has its own chart of accounts and budget, with an operating fund kept apart from its reserve fund. Routine repairs come from operating; a roof or repaving project in the reserve study comes from reserves. The stakes are real: California's Civil Code 5510 limits reserve money to major components and requires two signatures, from directors or a director and an officer, to withdraw it. That is one state's rule, given as context, not legal advice.
Approval limits set by owners and boards. A management agreement usually sets a repair limit above which the owner must approve, emergencies aside. Each association sets its own board threshold, and AppFolio lets board members approve invoices in its online portal. The draft flags every invoice over the limits you give us, plus credits, duplicates and vendors with no W-9 or insurance on file. It approves, pays and creates nothing.
// What you send
What we need from your AP team
20 to 30 entered bills
Vendor invoices your AP team has already keyed, with the bill detail showing where each landed. Include the awkward ones, like a multi-property invoice or a utility bill with a past-due balance.
Properties, accounts and limits
A spreadsheet of properties and associations, the GL accounts and reserve components each one uses, and each owner's repair limit and board's approval threshold.
An NDA, then names blacked out
Both sides sign the NDA first. Unit numbers help the coding; resident names don't, so black them out.
Look-alikes, if needed
If no invoice may be copied out, your reviewer helps us make realistic stand-ins.
// Before it starts
What the owner decides up front
The owner makes these calls before a single invoice leaves your office.
- Reviewer
- The owner's pick, often whoever runs AP or closes the association books
- Success criteria
- Agreed in writing: which fields count, and what a pass is
- Price
- A range for the live job
- Invoices
- Chosen by your reviewer, messy ones in
- NDA
- Signed first
// How the test is judged
Seven checks, invoice by invoice
| Across your 20 to 30 bills | Your team's posting | The draft |
|---|---|---|
| Property or association on each bill | Filled in from your invoices | Filled in from your invoices |
| GL account, and fund on association bills | Filled in from your invoices | Filled in from your invoices |
| Multi-property invoices split the same way | Filled in from your invoices | Filled in from your invoices |
| Work order and unit on repair invoices | Filled in from your invoices | Filled in from your invoices |
| Owner or board approvals flagged | Filled in from your invoices | Filled in from your invoices |
| Invoices a person had to fix | Filled in from your invoices | Filled in from your invoices |
| Minutes to code one invoice | Filled in from your invoices | Filled in from your invoices |
// After a yes
A month of live bills, each one approved
Once your reviewer signs off, the job moves to live vendor invoices for about 30 days, inside the system you already use.
Nothing posts until someone on your team approves the drafted bill. Owner and board approvals work as they do today; the draft only flags which invoices need them. Nothing else is added that month.
// Later, ranked
Where AP coding leads
- 01Next
Board packets
The treasurer's monthly package for each association, built from bills already coded: variance notes, reserve activity, invoice backup. Homeowner delinquency stays off it.
- 02Then
Owner statements
Notes for each rental owner at month-end: repairs that ran long, bills past the repair limit, work orders still open.
- 03After that
Acquired doors
When you sign a new association or buy a portfolio, its vendors, accounts and unpaid bills get mapped to your setup.
// By system
This job in the software you run
AppFolio Property Manager
Yardi Voyager
QuickBooks Online and QuickBooks Desktop
Buildium
AP automation
// One hard limit
No resident ledgers.
It never sees or drafts anything on a tenant's or homeowner's account: no balances, rent or assessment payments, late fees or collections. Bill-backs to residents are flagged and handed to your team. It reads copies of vendor invoices and writes draft bills to a sheet your reviewer checks.
Priced on its own. A range is quoted before any invoice is coded, and a fixed number before you sign.
Your range depends on invoice volume and on how many separate sets of books the invoices land in. Rob sets it on the call.
// Questions
AP automation questions
We run AppFolio. Does that change the test?
Does this work if we run Yardi Voyager?
How do you handle reserve versus operating for our associations?
Will it approve invoices over an owner's repair limit?

Rob Eason, founder
// Book a proof-of-concept call
See your posted invoices coded side by side.
Thirty minutes with Rob. He'll want your company, your role, the job to test and your rough monthly count of vendor invoices. Keep the invoices until the NDA is in place.
- Co-owned a 60-employee financial services firm and sold his share to his partner.
- Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
- 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
- 4.3/5 from 6 Google reviews of Massmarket AI.
- Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
- Takes every proof-of-concept call himself.
