Vendor payment methods in multifamily: ACH, digital check, paper check

Most portfolios pay every vendor the same way, usually by paper check, because that is what the process does.

Three rails exist, they settle at very different speeds, and the fee lands in different places. Choosing per vendor rather than per portfolio removes a meaningful share of the calls your AP team fields.

The three rails, with the actual numbers

Two things in that table surprise people.

ACH carries a vendor-side fee. It is faster and it is not free to the recipient, which is why some small trades genuinely prefer a check.

Physical check is roughly 20 business days end to end. That is not the mail. That is print, mail, deposit, and clear, and it is a month of float from the vendor's point of view.

The vendor's cash position decides the right rail, not your preference

A landscaping company with four employees and a payroll on Friday cares about 5 days versus 20 far more than about 0.9%.

A large supplier with a credit department and net-30 terms is indifferent to speed and notices the fee.

That is the whole decision. It is a vendor attribute, not a portfolio policy, and it is why a vendor self-service portal matters more than it sounds: letting vendors set their own method and banking details removes both the guessing and the data entry.

Reconciliation has to post back onto the same invoice

This is the part that separates a payments feature from a payments product.

Status needs to land on the invoice record itself: scheduled, sent, paid, reversed. Not in a separate payments report somebody reconciles against the AP ledger at close.

If payment status lives in a second system, month-end includes a matching exercise between two lists, which is exactly the work automation was supposed to remove. Every invoice that was paid but not marked, or marked but not paid, becomes a question.

Batch runs matter for the same reason. A payment run across many vendors from approved invoices, with exportable payout detail for reserve draws, keeps the whole thing inside one audit trail.

What we are and are not

BillRoute Pay moves money through Stripe, with funds held in FDIC-insured accounts at Fifth Third Bank N.A. More than $30M processed and 24,000+ units served.

We are not a bank and we do not hold your funds ourselves. Payment approvals are also separate from invoice approvals, deliberately: approving what something costs and authorizing money to leave are different decisions and the same person should not necessarily make both.

Daily processing cutoffs are surfaced in the app rather than buried, because a payment submitted after cutoff settles a day later and the most common support question is why.

Three questions before you consolidate payments

Which of your vendors would actually change behavior at 5 days versus 20? If the answer is "most of the small trades," rail choice is worth the setup.

Where does payment status live today, and does month-end include reconciling two lists? If yes, that is recoverable time.

Who authorizes money movement, and is that the same person who approves the invoice? If it is, separating them is a control worth having before volume grows.

The honest limit

Faster payment does not fix a slow approval.

If an invoice takes six days to get approved, moving settlement from 20 days to 5 changes the vendor's experience from 26 days to 11. Real, and worth having. But the six days is the larger and more fixable number, and it lives upstream in routing rather than in the payment rail.

Fix approvals first. Then choose rails.

Which of your vendors have asked to be paid faster?