Skip to main content

Xero's $2.5 Billion Melio Deal: What Bundled Bill Pay Means for Your AP Workflow in 2026

13 min readMike ThriftMike Thrift
Xero's $2.5 Billion Melio Deal: What Bundled Bill Pay Means for Your AP Workflow in 2026

If you still pay vendors by logging into your bank, exporting bills from your accounting software, and retyping amounts into a bill-pay portal, you are paying a hidden tax on every invoice. Small businesses spend roughly 20 hours a week on accounting tasks, and accounts payable is one of the biggest leaks — toggling between systems, fixing typos, chasing approvals over email, and then reconciling it all at month-end. Xero just placed a $2.5 billion bet that you will not have to toggle anymore.

In June 2025, New Zealand-based Xero announced it will acquire Melio, the U.S. bill-pay platform, for $2.5 billion plus up to $500 million in earn-out. The deal is the largest in Xero's history and signals a broader shift that matters whether you use Xero, QuickBooks, NetSuite, or a spreadsheet: bill pay is being swallowed into accounting software, and how you choose your AP workflow next will affect fees, cash flow, and how audit-ready your books are.

This guide explains what Melio does, why Xero paid that price, what bundled versus standalone AP looks like in practice, and how to evaluate your own workflow before you switch — with the bookkeeping details that most product announcements skip.

Why $2.5 Billion? The Gap Between Accounting and Money Movement

Xero has over 4 million subscribers, but only about 7% of its revenue comes from the United States — its biggest growth opportunity and also where it faces entrenched competition. Melio gives Xero three things it could not build quickly:

A U.S. payments footprint. Melio handled more than $30 billion in business payments in the year to March 2025, with about $153 million in revenue and roughly 80,000 active U.S. customers. Its technology is also white-labeled by partners including Fiserv, Capital One, and Shopify, reaching more than 3,500 banks through Fiserv's network. That distribution is hard to replicate.

Transaction revenue, not just subscriptions. Accounting software has trained customers to expect $15 to $90 per month. Payments add a second monetization path: fees on card-funded bill pay, FX on international wires, and float on faster payouts. Xero is explicit that it wants to capture the flow of money, not just the ledger of it.

A bundled workflow story. Xero's pitch is simple: "pay bills without ever leaving the Xero app." Instead of approve in Xero, pay in your bank, and reconcile back in Xero, you capture, approve, pay, and reconcile in one place. For a business processing 40 to 80 bills a month, eliminating the swivel chair between systems saves hours and cuts keying errors — the kind that create duplicate payments or missed early-pay discounts.

You do not need to be a Xero customer for this to affect you. When the two largest small-business accounting platforms — Xero and Intuit — both embed payments, every competitor must answer: will your AP vendor keep up as a standalone portal, or will you need to pick an integrated suite to stay efficient?

What Melio Actually Does

Strip away the press-release language and Melio is a small-business accounts payable hub with four core capabilities:

Bill capture. Forward an invoice by email, snap it in a mobile app, or drag a PDF in. Melio extracts vendor, amount, and due date so you are not hand-keying every bill. The time saving compounds: a 50-bill month at 3 minutes per manual entry is 2.5 hours just in data entry before anyone has approved anything.

Flexible funding. Pay vendors by ACH bank transfer even if you fund with a credit card, pay internationally in local currency, or use "pay over time" where Melio pays your vendor now and you repay on a schedule. The flexibility matters for cash flow: you can keep cash in your operating account longer or earn card rewards where vendors do not accept cards directly.

Approval workflows. Route bills above a threshold to an owner or manager for approval, maintain an audit trail of who approved what and when, and enforce separation of duties even on a team of two or three. That trail is what an accountant or auditor asks for when a duplicate payment question comes up months later.

Accounting sync. Sync bills, payments, and fees to QuickBooks, Xero, and NetSuite so the ledger matches what cleared the bank. Melio lists integrations with QuickBooks, Xero, NetSuite, and via API partners — a reminder that most AP tools are designed to live next to your ledger, not replace it.

What Melio does not do is free: card-funded payments carry fees, international wires carry FX spreads, and faster payouts cost more. The convenience premium is real, and it belongs in your bookkeeping as a distinct cost — not buried in "bank fees."

Bundled vs. Standalone: Three Ways to Run AP in 2026

Most small businesses land in one of three patterns. Naming yours helps you evaluate Xero-Melio against what you already have.

1. Bank bill pay + accounting software (the classic split)

You enter or sync bills in your accounting system, then pay through your bank's bill-pay portal or by writing checks. It is cheap per transaction, but you maintain two sources of truth. Reconciliation is manual, approval is often over email, and early-pay discounts get missed because the approval chain lives outside the payment rail.

Best for: very low bill volume (under 15 per month), single approver, vendors who accept ACH.

Watch out for: duplicate entry, no centralized approval log, and month-end surprises when the bank feed and the ledger disagree by a few payments still in transit.

2. Standalone AP automation (Melio, Bill.com, Ramp Bill Pay as a portal)

You capture and approve in a dedicated AP platform, pay from there, and sync the result to your ledger. You get better capture, workflows, and funding options than bank bill pay, without moving your accounting system. You still toggle between two apps, but the sync is tighter and the AP audit trail is stronger.

Best for: businesses that like their current ledger but need better AP controls, businesses that want card-funded payables without asking vendors to accept cards, or firms with 20 to 100 bills per month and at least one approver beyond the owner.

Watch out for: per-transaction fees on card-funded payments, FX on international, and a second subscription to manage. Your month-end checklist must include "AP portal reconciled to ledger reconciled to bank" — three-way, not two-way.

3. Embedded bill pay (Xero with Melio, QuickBooks Bill Pay, NetSuite native)

Capture, approve, pay, and reconcile without leaving the accounting app. The ledger is the workflow, so approval status, payment status, and bank reconciliation live in one dashboard. For distributed teams, this is the cleanest separation of duties: the person who enters the bill cannot also release the payment without a second approval inside the same system.

Best for: businesses that want one login for the back office, teams that need mobile approvals, and owners who measure "hours to close the books" not just "dollars in subscription."

Watch out for: platform lock-in, pricing changes once payments are bundled, and data portability. If you leave the suite, how easily does the payment history and vendor W-9 archive export?

There is no universally right answer. The right answer is the one where the total cost — subscriptions plus transaction fees plus hours spent — goes down while control goes up.

Fees, Timing, and Cash Flow: The Bookkeeping Details Most Announcements Skip

Product pages emphasize time saved. Your books need to capture what was spent to save that time.

Book transaction fees where they belong. Card-funded bill pay fees, wire fees, and rush fees are not "bank fees" in the generic sense and are not part of the vendor's invoice. Create a dedicated account such as Expenses:Bank Fees:AP Transaction Fees or Expenses:Payment Processing:Bill Pay Fees and post the fee separately from the bill payment. That keeps your vendor cost accurate and makes the convenience premium visible — if you spent $340 last month to put $18,000 of payables on a card for points, you can decide whether the points earned were worth it.

Example postings for a $2,000 vendor bill paid by card with a 2.9% fee:

2026-08-14 * VendorCo # INV-1842
  Expenses:Contractors:VendorCo         2000.00 USD
  Liabilities:AP
 
2026-08-14 * VendorCo # INV-1842 payment via card
  Liabilities:AP                       2000.00 USD
  Expenses:Payment Processing:Bill Pay Fees  58.00 USD
  Liabilities:CreditCard:Chase Ink

When the card is paid from checking, that is a separate transfer — not an expense.

Match funding method to cash position. Paying by card delays the cash outlay until the card due date, which can smooth a tight week. Melio's "pay over time" and similar installment options delay it further. Book the liability correctly: the vendor is paid when the platform marks it paid, even if you have not yet paid the platform. Your AP aging should show zero for that vendor and a new liability to the AP provider or card — otherwise you double-count.

Do not confuse payment speed with due date. A bill due August 30 that you pay August 10 "to be safe" costs you 20 days of cash float. An embedded workflow should let you schedule payment for the optimal date — on time, not early — and capture a 2/10 net 30 discount only when the math works. The relevant KPI is not "bills paid quickly" but "bills paid on the date that maximizes available cash after discounts."

International payables need two lines. If you pay a €3,000 invoice when the FX rate implies $3,240 and the vendor receives €3,000, book the vendor settlement at the spot rate and the FX spread as a separate fee. At scale, FX spreads become a line item worth negotiating or routing through a lower-cost rail.

Approval Workflows and the Audit Trail on a Team of Two

Small businesses rarely have a full segregation of duties, but even a light workflow prevents the costliest AP errors: duplicate payments, payments to the wrong vendor, and payments the owner never saw.

A practical setup for a 2- to 5-person team:

  • Thresholds. Bills under $500: one approver (owner or operations manager). Bills $500 to $2,500: owner approval. Bills over $2,500: owner plus one more set of eyes, even if the second approver is the external bookkeeper.
  • Maker-checker. The person who creates or edits a bill never approves it for payment. This one rule stops most internal error and fraud.
  • Evidence. Keep the bill PDF, the approval timestamp, and the payment confirmation linked to the transaction. In a plain-text ledger like Beancount, you can attach document: "bills/2026-08-14-vendorco-inv1842.pdf" metadata so the audit trail is reconstructable years later without hunting through email.
  • Vendor master hygiene. Add new vendors in one place with a W-9 on file, verify banking details by phone for any change request, and lock the vendor master so only the owner can edit payout details. AP fraud rarely starts with a fake invoice — it starts with "please update our wire instructions."

If your current process is "the owner approves everything by responding to a Slack message," you have an approval workflow — it is just not auditable. Moving that workflow into a system that logs who did what when turns a conversation into evidence.

What to Do in the Next 30 Days

You do not need to migrate this week, but you should measure what you have. A short exercise reveals whether bundled bill pay would actually help.

1. Count the true cost of your current AP. For the last 30 days, tally: number of bills paid, hours spent capturing, approving, paying, and reconciling, transaction fees paid, early-pay discounts captured versus offered, and late fees incurred. Divide total cost (fees plus hours valued at a realistic owner or admin rate) by bills paid. That is your fully loaded cost per bill.

2. Map your current flow. Draw the path a bill takes from inbox to "paid and reconciled." Where does it wait for approval? How many logins? Where do errors enter? If the map has three systems and two manual re-entries, any consolidation helps — whether bundled or standalone.

3. Audit vendor terms. List your top 10 vendors by spend. What are their payment terms, do any offer 1% or 2% for early payment, and how often do you capture it? Bills on 2/10 net 30 where you routinely pay on day 30 are a 36% annualized cost of not taking the discount — often far more than the fee to pay by card on day 10.

4. Pressure-test fees. Model a typical month both ways: ACH-funded versus card-funded. Include subscription delta, transaction fees, FX, and the value of points or cash back at your actual redemption rate, not the headline earn rate. If the bundled option costs $220 more in fees but saves 6 hours at $75 per hour loaded cost, the fee premium is buying back time.

5. Check data portability before you commit. Export a vendor list, a bill history, and an audit log from any platform you consider. If a clean export takes a support ticket, that is information about how the platform treats your data on the way out.

The Bigger Trend: Payments Are Becoming Part of the Ledger

Xero is not alone. QuickBooks has embedded bill pay, Bill.com has pushed into spend and expense, and bank-embedded options like Autobooks have added bill pay to serve more than 60,000 small businesses through bank channels. The pattern is clear: accounting systems want to own the payment, not just record it.

For owners, that consolidation can be genuinely helpful — fewer places to log in, tighter controls, clearer cash visibility — as long as you keep two disciplines. First, keep fees visible in your chart of accounts so convenience never becomes an invisible margin leak. Second, keep your payment history portable so the switching cost stays low.

Both disciplines are bookkeeping disciplines. How you pay is a workflow decision. Whether you can see what it cost and prove what happened is an accounting decision.

Simplify Your Financial Management

As you revisit how bills move from inbox to paid — and whether a bundled or standalone workflow is the better fit — keeping a clear, auditable record of every fee, approval, and funding choice is what keeps the time you save from turning into reconciliation you dread. Beancount.io offers plain-text, double-entry accounting that is version-controlled and fully transparent, so your payment history, vendor costs, and cash decisions stay readable and portable no matter which AP platform you choose. Learn more at Beancount.io or explore the pricing to get started.

Share this article