Most hotel finance teams already know paper checks are a risk. What’s harder to find is a clear answer to the next question: once you’ve decided to move off checks, how do you actually decide which vendor gets paid which way? How do you prove, in numbers, that the switch is working?
That’s the gap this article fills. Rather than re-litigate why checks are dangerous, it’s built around two things hotel controllers and AP leaders actually need to execute a transition: a practical framework for routing each vendor to the right digital payment method, and a scorecard for measuring whether your new hotel AP payment controls are delivering the control, speed, and cost benefits they’re supposed to.
The Real Question: Control
Check fraud is well documented at this point, and if you want the full picture, we’ve covered that ground in detail here.
The short version for this piece: the risk isn’t the paper itself, it’s the absence of control around it. A check run with no segregation of duties, no vendor-change verification, and no real-time visibility is risky regardless of what payment instrument sits at the end of it. Moving to ACH or virtual cards only solves the problem if the move comes with governance like a defined approval chain, payment-method rules by vendor, and an audit trail that holds up without reconstruction.
Hotel AP payment controls, at minimum, require:
- Structured, tiered approval: invoices routed by amount, vendor, department, or property, with real authority behind each sign-off, not a rubber stamp.
- A verified vendor master: banking and remittance detail changes locked behind a confirmed process, closing the door on impersonation fraud regardless of payment method.
- Payment-method governance: a documented rule set for which method each vendor type uses, and who can approve an exception.
- A native audit trail: who initiated, who approved, when it processed, how it reconciled, available on demand.
If you want the mechanics of vendor master control and approval-chain design at the portfolio level, that’s covered in depth in our multi-property AP automation piece. What’s less often addressed is the decision that actually determines whether those controls work in practice: which digital payment method belongs on which vendor.
The ACH vs. Virtual Card Decision Framework for Hotel Vendors
Hotel finance teams evaluating digital payments tend to ask “ACH or virtual card?” as if it’s a single, portfolio-wide decision. It isn’t. The right method varies by vendor relationship, and the strongest hotel AP payment controls treat method selection as a rule applied consistently per vendor segment, not a one-time platform choice.
Here’s how the two methods actually differ in a way that matters for routing decisions, not just in the abstract:
| Factor | ACH | Virtual Card |
| Best-fit vendor type | Recurring, contracted, stable relationships (utilities, service contracts, landlords, long-term suppliers) | One-off, urgent, new, or infrequent vendors; project-based or emergency spend |
| Settlement speed | Typically 1–2 business days | Often same-day; funds available as soon as the card is used |
| Control granularity | Account-level; authorization happens at approval, before the transfer is sent | Transaction-level; the card itself is capped to a specific vendor, amount, and window |
| Reversibility if something goes wrong | Difficult; ACH transfers are virtually impossible to claw back once processed | Easier; unused or misdirected credentials simply expire and can’t be reused |
| Fraud exposure it closes | Removes the physical theft and check-washing risk entirely | Removes physical theft and limits exposure even if credentials are somehow exposed, since the number is single-use |
| Vendor cash flow benefit | Predictable deposit timing supports the vendor’s own forecasting | Fast access to funds plus full remittance detail attached to the transaction |
| Cost profile | Low processing cost | Often no cost to the hotel, and can generate rebate income on volume |
| Where it fits weakest | New or unverified vendors, urgent one-off payments, situations needing a hard dollar cap | Vendors who do not accept Virtual Card payments |
A practical routing rule of thumb
- Recurring, verified, contracted vendors → ACH. If the relationship is stable, the banking details are confirmed, and the invoice amount is predictable, ACH gives you low cost and full digital audit trail without the operational overhead of generating a new credential every cycle.
- Vendors who explicitly require paper → check, with Positive Pay, as a documented exception. Some suppliers will insist. That’s fine as long as it’s a deliberate exception with fraud controls layered on, not the default path for every vendor your team hasn’t gotten around to migrating.
This is the layer that turns “we adopted digital payments” into an actual hotel AP payment control: a rule, applied by vendor segment, that a controller can defend in an audit, not a vague preference for “mostly ACH now.”
Operationalizing the Framework Inside DP Finance
A routing rule is only useful if it’s enforced automatically, at the point of payment, rather than left to whoever is running that week’s payment batch. This is where DP Pay, embedded directly in DP Finance, does the enforcement work: it applies smart payment routing that recommends the lowest-cost, most secure method per vendor while respecting the buyer’s and supplier’s preferences, and it does so without leaving the accounting system to initiate or approve a payment.
Hotels running DP Pay typically shift around 80% of payment volume to ACH or virtual card, cutting processing costs 70–80% and saving an estimated $3–5 per payment eliminated from the check run. These are figures that track directly with the vendor-segmentation logic above, since it’s the recurring, low-risk vendors that make up most payment volume and are the easiest to move to ACH first.
For the fuller picture of how DP Pay, DP Invoice, DP Finance, and DP Supply share a single data model see our breakdown of the connected AP workflow here. The short version relevant to this piece: because approval, GL posting, and payment execution happen in one system, the vendor-routing rule above gets enforced consistently across every property in a portfolio, not just the ones with a diligent AP clerk.
Measuring Whether the Transition Is Actually Working
Most conversations about ditching checks stop at “we moved to digital payments.” That’s an activity metric, not a control metric. The following scorecard is what actually tells a CFO or controller whether the new hotel AP payment controls are delivering:
| Metric | What it tells you | Target to watch for |
| % of payment volume on ACH/virtual card vs. check | How much exposure has actually left the check run, not just how many vendors were “migrated” | 75–80%+ of volume on digital methods within the first year is achievable with disciplined vendor segmentation |
| Cost per payment | Whether the routing rule is capturing the low-cost/no-cost methods it’s supposed to | A meaningful drop (often 70–80%) versus your prior blended check-processing cost |
| Days to close | Whether faster reconciliation is actually shortening month-end, not just changing where the manual work happens | 5–7 days faster is a realistic benchmark once reconciliation is automated rather than manually matched |
| Hours spent on manual payment matching monthly | The labor cost hiding inside a “successful” digital rollout | Should trend toward zero as payments post and reconcile automatically |
| Fraud and attempted-fraud incidents | The metric that actually validates the control thesis, not just the cost thesis | A clear downward trend vendor-by-vendor as check volume declines and vendor master verification tightens |
| Vendor payment cycle time | Whether the transition is helping or straining vendor relationships | Should hold steady or improve — a sign the migration isn’t creating friction with suppliers |
| Exception rate (vendors still on check) | Whether “check” is a deliberate, documented exception or a default nobody revisited | A shrinking, explainable list — not a growing one |
For context on what “good” looks like at scale, independent AP research (Ardent Partners’ 2025 benchmarking) puts the all-buyer average around $10.89 and 10.9 days to process a single invoice, against roughly $2.78 and 3.1 days for top-performing AP teams.
Track this scorecard quarterly, by property if you operate a portfolio, and you have a defensible answer to the question every audit committee eventually asks: how do we know the new payment process is actually safer than the one it replaced?
If you want to see what this looks like translated into real portfolio results rather than target ranges, our AP automation case study walks through the before-and-after numbers for a multi-property group.
Getting Started
The fastest path to a working hotel AP payment control framework isn’t a big-bang cutover. It’s:
- Segment your existing vendor file into recurring/verified, one-off/urgent, and check-required categories.
- Lock down vendor master change control before migrating anyone, so the fraud vector closes regardless of payment method.
- Route the recurring/verified segment to ACH first. It’s the largest share of volume and the lowest lift.
- Move new, urgent, and high-risk vendors to virtual card as they come up, rather than waiting for a full-portfolio rollout.
- Start tracking the scorecard above from day one, so you have a baseline to measure the transition against.
DP Pay is built to enforce exactly this kind of vendor-by-vendor routing automatically inside DP Finance, so the rule you set is the rule that runs at every property, on every payment, without relying on manual judgment call after manual judgment call.
Schedule a demo to see how DP Pay applies vendor-level payment routing and controls inside your existing DP Finance workflow.
