Why AP approvals get messy in a real estate business
In a real estate agency, accounts payable rarely means a neat stack of invoices that one person can approve in order. Bills arrive through shared inboxes, property management software, supplier portals, paper mail, and messages sent directly to an agent or property manager. The person who receives a bill may know what the work was for, but not who has authority to approve it.
That creates familiar friction. A property manager forwards a plumber’s invoice to the office manager. The office manager asks which property it belongs to. The property manager is out on inspections. Meanwhile, the supplier sends a reminder, and the bill sits in an inbox without a clear owner.
Across an agency and property management operation, the same pattern repeats with photography, advertising, cleaning, repairs, utilities, software, and office expenses. Some invoices are straightforward. Others need a job reference, owner approval, a budget check, or confirmation that the work was completed.
The problem isn’t simply that someone has to type invoice details into a system. It’s that the agency needs a dependable way to capture each bill, identify the right approver, deal with missing information, and show what happened before payment.
For an owner, partner, or GM, approval delays can obscure the actual cost of operations. It’s worth checking where duplicate payments, missed credits, late fees, unapproved spend, and staff rework are accumulating.
If you’re comparing the workflow with other agency processes, this guide to automating agency accounts payable covers the broader pattern. Here, the focus is the real estate detail: bills tied to properties, owners, jobs, and different approval rights.
Map the current approval path before automating it
Start by listing the places invoices arrive and the people who handle them. Include shared email addresses, individual inboxes, property management platforms, supplier portals, and paper bills. Don’t assume the accounts team sees every invoice first. In many agencies, the first recipient is the person who ordered the service or manages the property.
Then map the decisions needed before a bill can be approved. A maintenance invoice might need to be matched to a property and work order, checked against an owner’s spending limit, and confirmed by the property manager. A campaign invoice might need sign-off from the listing agent or sales manager. An office expense may go to the GM or finance lead.
Write down the actual rules, not just the job titles. For example:
- Who can approve an invoice for a repair, and up to what amount?
- Does the property manager approve work completed, or does the owner also need to approve it?
- Which invoices need a purchase order, work order, listing reference, or property code?
- Who handles an invoice when the named approver is away?
- What happens when the invoice amount differs from the quote?
- Which bills are recurring and can be checked against a known supplier and amount?
- Who is allowed to release a payment after approval?
Approval rules can differ by spend type, property, owner instruction, or entity. Don’t flatten these into one universal limit. In particular, keep payment release separate from invoice approval where your controls require it. Property trust accounting also has specific legal and operational requirements. An automated workflow should not blur client funds and agency operating funds, or replace the controls your jurisdiction requires.
Once the rules are visible, set a baseline. Count invoices received in a typical month, note how many arrive outside the main AP channel, and measure the time from receipt to approval. Also record the common exceptions and how often invoices are sent back for clarification. You’re looking for the points where work gets stuck, not a perfect data set.
What an automated AP approval workflow does
A useful workflow has four jobs: capture the bill, identify what it relates to, send it to the right approver, and preserve the decision trail. It should not approve everything automatically. The goal is to handle routine processing consistently and route uncertainty to a person with the authority to resolve it.
1. Capture every bill in one queue
The workflow watches agreed intake points, such as an AP email inbox or an approved supplier portal connection. When an invoice arrives, it creates a record and stores the original document. It can extract the supplier, invoice number, date, due date, total, tax, and line items, then check whether those fields are present.
If a property manager forwards an invoice from their personal inbox, the workflow can still bring it into the same queue. The original message and attachment should remain attached to the record, so the team can see where the bill came from and what was communicated with it.
For paper invoices, the process starts with scanning or photographing the document into the agreed intake channel. A workflow can’t capture a bill it never receives. Setting a clear rule for agents and property managers, such as “send all supplier bills to this address,” matters as much as the automation itself.
2. Match the bill to the right context
The workflow checks what the invoice relates to. Depending on the agency’s systems and records, that could be a property address, owner, work order, listing, supplier contract, or office cost centre.
A maintenance invoice with an address but no work order may be easy to identify but still need confirmation that the work was completed. A photography bill may need a listing code and confirmation that the photos were ordered. The workflow can compare what it finds with available records and identify what’s missing.
It should not guess when the evidence is unclear. If an invoice could relate to two properties, or the supplier name doesn’t match the expected vendor, the bill needs review. A good process flags that uncertainty instead of quietly attaching the invoice to the wrong record.
3. Select the approver using defined rules
Once the bill has enough context, the workflow applies the agency’s approval matrix. That may route a maintenance cost to a property manager, a campaign cost to a sales manager, and an office expense to the GM. Amount thresholds, property assignments, and approval limits can be part of those rules.
The workflow should also check for conditions that change the route. A bill above a threshold might need a second approval. A variance from an accepted quote might go back to the property manager. A missing owner instruction could pause the approval request rather than trigger an assumption.
Approvers need a clear request with the invoice, the reason it was routed to them, relevant supporting records, and simple choices: approve, reject, or request information. A vague email that says “please review” shifts the investigation back to the approver and tends to slow the process down.
4. Route exceptions, reminders, and decisions
Not every bill will follow the standard path. Common exceptions include duplicate invoice numbers, missing property references, a total that doesn’t match the quote, a new supplier, an invoice sent to the wrong entity, and approval requests that have gone unanswered.
Give each exception a named owner and a next action. For example, the workflow can ask the property manager to confirm the work order, flag a possible duplicate for AP, or send an overdue approval reminder to the correct manager. If the approver doesn’t respond after the agreed interval, it can escalate to a designated backup.
Keep the exception visible until it’s resolved. A bill should not disappear into a person’s inbox just because a reminder was sent. The record should show who has it, what information is missing, and what happens next.
5. Keep a usable approval trail
For each invoice, preserve the original document, extracted details, linked property or job, approval requests, responses, changes, and timestamps. If someone changes a coding field or corrects a supplier reference, keep the earlier value and the reason for the edit where the system supports it.
That trail is useful when an owner asks why a repair was charged, when finance checks a payment, or when a manager reviews spend by property. It also helps distinguish “approved” from “paid.” Approval authorizes the next step under your policy. Payment release remains subject to the agency’s finance controls.
An AI agent, end to end
An AI agent can operate this workflow by reading incoming bills, checking them against the records and rules you define, and taking the next permitted action. A typical invoice might arrive by email from a contractor after a maintenance visit. The agent extracts the invoice details, matches the address and work order, checks for a similar invoice already in the queue, and verifies that the amount is within the applicable approval route.
If the record is complete and the amount falls within the property manager’s authority, the agent sends that manager a request containing the bill and work order. The manager approves or asks a question. The agent records the response, updates the invoice status, and sends it to the appropriate finance queue for payment processing.
If the invoice has no property address, the amount differs from the quoted work, or the work order shows a different supplier, the agent doesn’t force it through. It asks the relevant person for the missing information or flags the invoice for AP review. The person resolving the exception can see the bill and its history in the same record.
The boundary matters. The agent should follow documented approval rules, not create new ones. It should not approve an invoice on behalf of an owner or manager unless that authority has been explicitly granted and your policies allow it. It should not release payment simply because an approver clicked approve. Keep unusual suppliers, high-value invoices, trust-related transactions, and unclear evidence on a human review path.
A separate workflow can help with other agency operations, but don’t confuse those jobs with AP. For instance, enquiry-handling and listing follow-up workflows address response and follow-up work, while AP automation handles bills and approvals. If you’re exploring agency operations beyond finance, see Omni for real estate agencies.
Start with a small, controlled rollout
Choose one invoice category with enough volume to test the workflow, but not so much risk that a mistake would be hard to contain. Maintenance invoices are often a sensible starting point if property references and work orders are reasonably consistent. Another agency might begin with routine office suppliers or listing photography.
Run the new process alongside the existing one for a defined period. Compare the captured invoices with what arrives in the source inbox. Check whether the supplier, amount, property, and approver are correct. Review every exception and see if the agent asked the right person for the right missing detail.
Track a few practical measures:
- Time from invoice receipt to approval
- Share of invoices that arrive through the agreed intake route
- Number of invoices returned for missing information
- Duplicate or mismatched invoices flagged
- Approval requests that need escalation
- Staff time spent chasing or coding bills
Don’t set a target based on a vendor’s best-case demo. Establish the current baseline first, then decide what improvement would make the workflow worthwhile for your team. Also confirm who owns the approval matrix when staff roles, owner instructions, or spending limits change.
For a broader view of costs and implementation considerations, read what it costs to automate a real estate agency. If your approval process also includes marketing materials and listing campaigns, the guide to automating creative approvals covers a related but distinct workflow.
Find the right starting point for your agency
The first question isn’t which software to buy. It’s where invoices enter, which decisions delay them, and what evidence people need to approve them confidently. In a small operation, the bottleneck may be one director who approves every bill. In a larger agency, it may be the lack of consistent property coding or several different approval practices across offices.
An Omni Audit can help you review your current workflow, explore potential automation opportunities, and discuss practical next steps.
Use the session to bring real examples: a routine supplier invoice, a bill that needed several follow-ups, and one that was disputed or sent to the wrong person. That makes it easier to separate the straightforward cases from exceptions that should stay with a human. Book an Omni Audit and we’ll work through the process with you. You can also review the AI audit for real estate agencies before the session.
If your team is also tightening enquiry handling, the Speed-to-Lead Script for Real Estate Teams is a practical worksheet for making the first response and follow-up steps clearer. It focuses on buyer enquiries, not AP approvals, so treat it as an adjacent operations resource. Download the script.
The right AP workflow won’t remove every query or approval decision. It should make the routine path easier to follow, surface exceptions while there’s time to act, and leave a clear record of who approved what. For an agency, even a focused review of invoice handling can show whether there may be opportunities to address late fees, duplicate bills, missed credits, or the hours spent chasing answers. Book your Omni Audit to identify the best place to start.
Your guide is ready
Check your downloads folder. If it did not open automatically, use the button below.
Download the GuideYour guide is ready
Check your downloads folder. If it did not open automatically, use the button below.
Download the GuideTalk it through
Talk it through with Sam
30 minutes on what a Command Centre would look like for your business.
Book a call