Where LastPay Is Headed: Sage, NetSuite, Xero, and a Bigger Bet

LastPay will spend its second year doing the thing it spent its first year preparing for. The company is rolling out integrations with Sage, NetSuite, Xero, and Go High Level. Each one is a step in the same direction. The processor follows the customer’s stack, not the other way around.

Co-founder Austin Diaz frames the strategy in plain terms. A small business should not have to change its accounting platform to access better processing. A growing business should not have to change its processor when it migrates from QuickBooks to NetSuite. The processor should be invisible across the journey. The accounting tool should be the source of truth. The savings should be visible from day one.

QuickBooks built the foundation for that argument. LastPay’s bidirectional integration with QuickBooks Online has been the centerpiece of the product since launch. Customers create invoices in their existing environment. Payments route through LastPay. Reconciliation writes back into the ledger on its own. The Friday morning reconciliation ritual disappears.

Sage and NetSuite extend the reach into the upper tier of the small business and lower mid-market. Customers in those tiers tend to outgrow QuickBooks at a predictable point. The roadmap means LastPay does not lose them at the migration. The processor moves with the customer.

Xero is the international hedge. The platform’s user base skews outside the United States, and its growth in North America has been steady for years. Building the integration is a recognition that LastPay’s customer base will not stay homogeneous, and that the product needs to support multiple accounting standards as the company grows.

Go High Level is the agency play. Marketing agencies and service providers running on Go High Level have a payment problem that mirrors the one LastPay started solving in QuickBooks. High volume of invoices, low tolerance for friction, and a strong preference for tools that talk to each other. The integration brings LastPay into a customer base that is currently underserved by the legacy processors.

What unites the four integrations is the bet underneath them. Diaz and co-founder Max Umlas believe that the next decade of fintech will be won by processors that disappear into the customer’s existing tools. Umlas has been building the operational infrastructure to support that bet, backend systems, onboarding flows, and the growth engine that turns each new integration into revenue. The product surface that owners interact with will be the accounting platform. The processor will be the invisible layer that makes the money move at a fair price.

What the integration roadmap enables in practice is portability. A small business that starts on QuickBooks can keep the same processor when it migrates to NetSuite at the next stage. An agency on Go High Level can plug LastPay into its existing client billing flows without replacing tools. A Xero user in Australia or the United Kingdom can use the same product as a customer in Texas. Portability is the feature, even if it does not show up in a marketing tagline.

The team has set internal milestones around customer adoption rather than launch dates. An integration is considered shipped when the first ten customers on the new platform have completed a full month of clean reconciliation. The standard sounds simple. It is enough to keep the team from declaring victory before the product earns it.

Diaz has been clear that the company will not chase integrations for their own sake. Each new platform has to clear three tests. The customer base on the platform has to overlap with LastPay’s existing customer profile. The integration has to support the bidirectional reconciliation pattern the company set in QuickBooks. The platform has to be willing to share the technical work that keeps the integration stable through API changes. Platforms that fail any of the three do not make the cut.

LastPay is building for that world. The integrations are the vehicle. The thesis has been consistent since the first month. Customers will not change their stack to save on processing. The processor has to fit the stack. The next year will test how well that thesis scales.

For a closer look at the platform, watch Sending Invoices On QuickBooks With LastPay on the LastPay YouTube channel.

Latest from Blog