ACH, wire transfer, and virtual card are all "payments." They also have fundamentally different cost profiles, timing characteristics, fraud risk profiles, and supplier relationship implications. Treating them as interchangeable — defaulting to ACH for everything because it's familiar — means leaving money on the table and creating friction in supplier relationships that a deliberate payment strategy would avoid.
Supplier payment orchestration is the practice of selecting the right payment method for each payment based on explicit criteria: transaction size, supplier preferences, timing requirements, cost optimization, and fraud controls. It sounds like treasury strategy, and it is — but it's also an operational capability that lives in the AP workflow, not in a spreadsheet on the CFO's desk.
ACH: The Workhorse Payment Rail
Automated Clearing House payments are the backbone of B2B payment in the United States. They're cheap (typically $0.25–$1.50 per transaction for outbound ACH), widely supported by supplier bank accounts, and process reliably through NACHA's network.
Standard ACH settles in 1–2 business days, though Same-Day ACH is available for time-sensitive payments at a modest premium (typically $0.50–$2.00 additional per transaction). For mid-market companies processing hundreds of vendor payments monthly, the ACH fee structure is highly favorable — the total payment cost at scale is a small fraction of check-based payment costs when printing, mailing, check stock, and reconciliation labor are included.
ACH is the right choice for: recurring vendor payments where timing predictability matters more than speed, payments to established vendors with good banking relationships, and high-volume payment batches where per-transaction cost efficiency is the priority.
ACH is a poor choice for: payments requiring same-day arrival when Same-Day ACH isn't available (Federal Reserve's FedACH network has cutoff times), payments to vendors that don't have U.S. bank accounts, and time-sensitive payments where wire transfer's finality provides contractual certainty.
ACH Returns and What to Do About Them
ACH returns — where a payment bounces back because of incorrect bank account information, insufficient funds, or account closure — are a persistent operational nuisance. Return rate targets for well-maintained vendor master files should be below 0.5% of ACH transactions. If you're seeing return rates above 1%, your vendor bank account data has a data quality problem.
The most common cause of ACH returns in mid-market AP is stale bank account information — a vendor changed banks, closed an account, or updated their ACH routing information without notifying AP. Supplier portal self-service, where vendors can update their own payment information subject to an approval workflow, dramatically reduces return rates by shifting the maintenance burden to the supplier who has the current information.
Wire Transfer: Finality at a Cost
Wire transfers are irrevocable, same-business-day settled payments that communicate directly between banks. Unlike ACH (which is a batch settlement system), wires are settled individually and immediately. Once sent, a wire cannot be recalled — that finality is both the feature and the risk.
Wire costs typically run $15–$35 for domestic outbound wires and $25–$50 for international wires, depending on your banking relationship. At those per-transaction costs, wires are economically appropriate for high-value, time-sensitive payments where the cost is immaterial relative to the payment amount — real estate transactions, large purchase order down payments, international supplier settlements, or payments where the vendor's contract specifically requires wire transfer.
A sensible policy for most mid-market organizations: domestic wires for payments above $50,000 where same-day certainty is required, and for all international vendor payments. ACH for everything below that threshold unless there's a specific timing or contractual reason to wire.
Wire transfers require heightened fraud controls precisely because they're irrevocable. Business email compromise (BEC) fraud most commonly targets wire payments — a fraudster impersonating a vendor sends a "banking change" request, and if the AP team processes it without verification, the payment goes to a fraudulent account with no recovery path. We'll address the fraud control framework in more detail in a separate article, but the operational principle is: never change a wire beneficiary account based on email instruction alone. Every wire beneficiary change requires a verified callback to a phone number obtained independently from the banking change request.
Virtual Cards: Revenue Generation from Payments
Virtual cards are single-use or limited-use card numbers that work on the Visa or Mastercard network. They're issued by your AP platform or bank, transmitted to the supplier (who processes them as a standard card payment), and auto-reconcile back to your AP records.
The defining feature of virtual cards from a buyer's perspective is that they generate interchange rebate revenue. When your company pays a supplier via virtual card, the card network charges the supplier an interchange fee (typically 2–3% of the transaction amount). A portion of that interchange flows back to you as a rebate — typically 1–2% on commercial virtual card programs. A $10,000 vendor payment via virtual card generates $100–$200 in rebate revenue. At sufficient volume, this becomes a meaningful financial benefit.
The operational tradeoff is that not all suppliers accept virtual cards. Suppliers with thin margins — industrial commodities, utilities, government vendors — may decline virtual card acceptance because the interchange cost eats their margin. Suppliers that primarily deal with consumers (who pay by card routinely) are generally comfortable with virtual card payment. Suppliers that have historically received ACH or check payments may need to be onboarded to card acceptance, which requires some relationship management.
A virtual card program works best when selectively applied: identify the suppliers in your vendor base who accept card payments without friction, segment them by transaction size and frequency, and route those payments through virtual card to capture rebate revenue while continuing ACH for suppliers who prefer it. This selective approach typically captures rebate on 20–35% of payment volume, which on a $10 million annual AP spend generates $40,000–$70,000 in annual rebates at 1.5% average rebate rate.
The Orchestration Decision: Building the Logic
Payment orchestration is the automated application of payment method selection rules based on transaction and vendor attributes. Instead of the AP clerk deciding payment method per invoice, the system applies a decision tree:
- Is this a foreign currency or international payment? → Wire transfer (international ACH if available and vendor bank is in a supported country)
- Is the payment amount above $50,000? → Wire transfer if same-day certainty required, ACH otherwise
- Is this vendor enrolled in virtual card acceptance? → Virtual card if transaction is between $500 and $25,000
- Is there an early payment discount available within the next 5 days? → Prioritize same-day ACH or virtual card to hit the discount window
- Default → ACH, scheduled for next payment batch
This decision tree is configurable and should reflect your specific vendor mix, banking costs, and rebate program terms. The point is that it's explicit, consistent, and applied automatically — not ad hoc at the discretion of whoever is running the payment batch that week.
1099 Reporting Implications
Payment method affects 1099 reporting. Payments made by check or ACH are subject to standard 1099-MISC and 1099-NEC reporting thresholds for applicable vendor categories ($600 annual threshold for most services). Payments made by credit card or virtual card are reported to the IRS by the card network on Form 1099-K, not by the buyer. This means your AP system's 1099 logic needs to correctly exclude card payments from your Form 1099 calculations — double-reporting is an IRS compliance issue.
Most mid-market AP systems handle this correctly for traditional corporate card programs. Where it sometimes breaks down is in virtual card payment orchestration, where the card payment flows through the AP system but the 1099 exclusion flag may not be set correctly. Verify with your AP platform vendor that virtual card payments are correctly excluded from 1099 aggregation before year-end.
Why "Just Use ACH for Everything" Is a Missed Opportunity
We're not saying ACH is wrong for the majority of payments — it's often the right answer. The argument against defaulting to ACH for everything is that it ignores available financial optimization. Virtual card rebate revenue is real money. Early payment discounts require fast payment execution. International supplier relationships have specific needs that ACH can't address. The AP function that actively manages payment method selection rather than accepting defaults is generating financial value that the organization's income statement doesn't otherwise capture.
Payment orchestration is one of the less-discussed capabilities in AP automation, which means it's often underimplemented. Teams that take it seriously — setting up explicit payment method rules, enrolling vendors in virtual card acceptance programs, and tracking rebate capture rates — frequently find it's one of the highest-return optimizations in their AP program. The payments were going out anyway. The question is whether they're generating the best possible financial outcome on the way out.
