Appraisal billing comes in three shapes, and the difference between them is when money moves relative to the report. Prepay collects before work starts. COD collects at delivery. Net terms invoice at delivery and collect later. Each changes what the delivery gate does, and each has to know who to bill, which is the requester or payer captured at intake rather than the borrower or the property owner. A billing system carries terms per client and issues the invoice without anyone rekeying the fee.
How appraisal fees leak between order and deposit
The invoice is built from the order a second time
Someone opens accounting and retypes the address, the fee, the file number, and the client. The fee agreed in the engagement letter and the fee on the invoice are now two separate typings of the same number.
The bill goes to the wrong party
The order came from a loan officer, the fee is borrower-paid, and the invoice went to the AMC. Every wrong recipient costs a billing cycle before anyone notices.
COD is enforced by somebody remembering
The client is supposed to pay at delivery. The report goes out because it was finished, and the invoice follows days later to a client with no particular reason to hurry.
Trip fees and complexity additions never reach the invoice
A no-access trip, a second inspection, a rush request, or an acreage upcharge gets agreed verbally, then invoiced only if whoever writes the invoice hears about it.
Nobody can list what has been delivered but not paid
Aging by invoice date exists. Aging by delivered-and-unpaid, per client and per product, does not, so the conversation with a slow-paying client starts with a spreadsheet somebody builds that morning.
Billing triggers and their effect on the delivery gate
Six arrangements, each with a different relationship between payment and the report leaving the building. Build the gate column deliberately: it is the only place software should ever hold a completed report.
| Billing arrangement | Invoice issued | Who is billed | Effect on the delivery gate | On non-payment |
|---|---|---|---|---|
| Prepay by card at order | At order submission, before acceptance | The requester who placed the order, taken from the intake record | Order cannot reach Accepted until payment clears, so no appraiser is assigned | Order held and the requester notified. Nothing has been scheduled, so nothing is lost |
| Prepay by invoice before assignment | On acceptance, payable before scheduling | The billing party named on the order, which may not be the requester | Inspection cannot be scheduled until payment posts | Aging notice to the requester and the client contact; the assignment stays unassigned |
| COD at delivery | On completion of the report, immediately before transmission | The billing party on the order | Report is packaged and held; delivery releases when payment is received | Held report appears on a queue with the client contact notified, escalating to a named person |
| Net terms | At delivery, on the terms held on the client record | The client of record under their master agreement | None. Delivery proceeds and the invoice follows the report | Standard aging and dunning per client, with a flag on new orders once your threshold is crossed |
| Borrower-paid at closing | At delivery, referenced to the file and the closing | The lender or settlement agent per the client’s arrangement | None. Delivery proceeds | Tracked against the file until the closing settles or the file dies, then re-billed per your policy |
| Split appraisal and management fee | At delivery, as separate line items | The party each line is owed by under the client agreement | Follows whichever term governs that client | Each line ages independently, so a paid appraisal fee is not hidden behind an unpaid management fee |
What the billing build consists of
The fee is captured once, at the order
Product fee, any complexity or trip addition, and the billing party are set on the order record and carried through to the engagement letter and the invoice. One number, one place it gets entered.
Billing party resolved from intake rather than assumed
Who placed the order, who the client of record is, and who pays are three separate fields, because they are frequently three separate parties. The invoice routes to whoever is marked as payer, with the requester copied where the client allows it.
Terms attached to the client, not chosen per invoice
Prepay, COD, or net sits on the client record along with any exception by product or branch. New orders inherit those terms, so nobody selects terms order by order and nobody selects them wrong.
The gate is a state, not a script
A held report sits in a Held for payment state on a visible queue showing the client contact and the amount. Payment posting releases it. A named person can also release it manually, recorded under their name.
Accounting receives the invoice, not the data entry
Invoices, customers, and payments post into your accounting system directly. Additions made after the order, such as a second trip, attach to the assignment when they happen and flow through the same path instead of being remembered later.
What billing plugs into
- QuickBooks automation for invoicing — Invoices, customers, and payments post to QuickBooks Online from the assignment record with no re-entry.
- workflow automation for gates and escalation — The delivery gate, aging escalations, and the manual release path with its recorded approval.
- form automation for payment capture — Card collection at order and the payment link that travels with a COD invoice.
Is this a fit for your business?
A good fit when
- You run more than one payment arrangement across your client base
- Reports go out ahead of payment on terms that were meant to be COD
- Trip fees, second inspections, and upcharges get invoiced inconsistently
- Your order system and your accounting system do not talk to each other
Probably not a fit when
- Every client is on the same terms and one person handles all billing in an afternoon
- You want a full accounting platform rather than a connection into the one you have
- You are looking for advice on what to charge or how to structure your fees
What to have ready
- Your fee schedule by product, property type, and coverage area
- Payment terms by client, including anyone on a standing exception
- Which accounting system you use and who enters invoices into it today
Questions we get asked
Is holding a finished report for payment appropriate?
That is a business decision your firm makes with your clients. Plenty do it on COD terms and others never would. Two things about the build: the hold applies only to transmission of a completed report, and someone should always be able to release it. The system never touches the report, and payment status has no relationship to anything inside it.
Can the invoice issue automatically to whoever placed the order?
Yes, and that is usually the default worth having. The requester is captured at intake with their email and organization, and the invoice issues to them unless the client record names a different payer. Where the two differ, the requester is copied so nobody has to ask whether it went out.
How do second trips and upcharges get billed?
They are added to the assignment when they happen, by the appraiser or the coordinator, with a reason attached. A no-access trip logged from the field carries a fee line where your rule for that client says it should. At invoice time the additions are already there rather than reconstructed.
Does this replace our accounting system?
No, it feeds it. QuickBooks or your equivalent stays the book of record for revenue and receivables. What we build is the path from the order to the invoice, so the fee is entered once, routes to the right party, and carries whatever additions accumulated along the way.
Related
- report delivery and client status visibility
- appraisal order intake by property type
- QuickBooks automation for invoicing
- workflow automation for appraisal firms
Tell us what the process looks like now and we will map what a system would need to do. No obligation, and you keep the map either way.