AP cost and benchmarks
Slow vendor payments cost the vendor first and your AP team second
A vendor offering 2/10 net 30 prices 20 days of waiting at 2%. That is their number for payment speed. Your AP team pays for the same wait in phone calls.
Blog
BillRoute is built inside a property management company that processes thousands of vendor invoices a month. These are the things we had to work out, written down.
AP cost and benchmarks
What invoice processing actually costs, how to benchmark it, and where the money goes.
Coding, close, and accuracy
GL coding, three-way match, and closing the month without waiting on AP.
Intake, documents, and vendors
Getting invoices in the door, including the handwritten and batched ones.
Systems, PMS, and buying
How AP fits your PMS and ERP, and how to evaluate software for it.
AP cost and benchmarks
A vendor offering 2/10 net 30 prices 20 days of waiting at 2%. That is their number for payment speed. Your AP team pays for the same wait in phone calls.
Systems, PMS, and buying
The useful comparison for a multifamily AP team is not feature counts. It is the billing unit, how the PMS sync works, and what happens to a batch PDF. Six questions to ask.
AP cost and benchmarks
Most AP cost-per-invoice numbers are built to sell software. Here is the arithmetic with the assumptions visible, including the lines vendors leave off the slide.
AP cost and benchmarks
If your AP tool bills per page, you pay for every certificate of insurance, every multi-page statement, and every document a vendor attached to be helpful. Here is the arithmetic.
AP cost and benchmarks
A 2/10 net 30 discount is a 36% annualized return on paying early. Most portfolios cannot take it, because approval takes longer than ten days.
AP cost and benchmarks
The same invoice arrives by email and gets re-sent on a statement. Both get paid. Getting the money back takes a vendor's cooperation you may not have.
AP cost and benchmarks
The benchmarks say 1,000 to 2,000 a month. That range is useless without knowing the document mix, because exceptions cost 2.5x a clean invoice.
Coding, close, and accuracy
Coding automation learns from your history, so an inconsistent chart of accounts produces a faster inconsistent chart. Fix the GL first, then automate it.
Coding, close, and accuracy
Period expense is set by when the service happened, not when the invoice showed up. Slow AP makes that gap large enough to distort a property's month.
Intake, documents, and vendors
An invoice with no property identifier cannot be coded by anyone but the person who ordered the work. Requiring seven fields removes most exception handling.
Coding, close, and accuracy
Close is late for two reasons: AP is still coding, and nobody can see what has not posted. Six things have to be true on the last day, and each is a query rather than a conversation.
Coding, close, and accuracy
Purchase order, goods receipt, invoice. Most multifamily portfolios run a two-way match and call it three, which is why price variances surface after payment.
Intake, documents, and vendors
High volume, low variance, hard due dates, and an approval chain that adds nothing. Utilities are the clearest case for routing around your own workflow.
Intake, documents, and vendors
A field vendor's handwritten invoice is a real payable. Generic OCR treats it as a bad scan, which is why it ends up in a pile somebody keys by hand.
Intake, documents, and vendors
Payment redirection fraud does not need a forged invoice. It needs one email asking to update banking details, arriving at a moment when a callback feels excessive.
Coding, close, and accuracy
Approvers spend about 90 seconds on an invoice. The invoice waits days. Those are different problems and only one of them is about diligence.
Systems, PMS, and buying
AI coding learns from history keyed to a vendor. Four records for one vendor means four thin histories instead of one good one, and no automation fixes that.
Systems, PMS, and buying
ResMan is the system of record. It was built for accounting rather than for document intake, which is exactly the gap an AP layer fills.
Systems, PMS, and buying
Extraction works on day one. What takes weeks is deciding who approves what, at which threshold, and what happens when that person is on vacation.
Intake, documents, and vendors
Three rails, three settlement times, three fee structures. The right one depends on the vendor, and paying everyone the same way is what makes vendors call your AP team.
Systems, PMS, and buying
Every vendor in this category has OCR and an approvals module. These eleven questions separate them, and they work on us too.