Small-Business Fintech Is Moving Beyond Subscription Revenue
Small-Business Fintech Is Moving Beyond Subscription Revenue
Small-business financial software is increasingly monetized when money moves, not merely when a user logs in. BILL’s latest results make the shift visible: transaction fees are now far larger than subscription fees. That model can expand revenue with customer activity, but it also places payment mix, fraud, network cost, support and settlement performance at the center of product economics.
The lesson is not that subscriptions are disappearing. It is that the subscription has become one layer in a broader financial relationship. Operators need to manage that relationship at the level of each workflow and payment method, not celebrate total volume in the abstract.
What the evidence shows
In its fiscal third quarter ended March 31, 2026, BILL processed $89 billion in total payment volume, up 12% year over year. The company, which says its platform is trusted by nearly half a million businesses, reported total revenue of $406.6 million, up 13%, in results released May 7.
The mix is the revealing part. BILL reported core revenue of $371.1 million. Subscription fees were $74.5 million, up 9%, while transaction fees reached $296.6 million, up 18%. Transaction fees were nearly four times subscription fees. Float revenue contributed another $35.4 million. The full breakdown appears in the company’s Q3 fiscal 2026 earnings release.
Profitability improved alongside growth. Non-GAAP operating income rose 50% to $79.8 million, while the GAAP operating loss narrowed to $0.4 million from $28.9 million a year earlier. These are company-reported results, and the non-GAAP figure excludes specified expenses, but they show that transaction growth and operating leverage can coexist.
One quarter from one company does not establish an industry law. It does illustrate the commercial logic pulling SMB software toward payments: software creates the workflow, the workflow creates payment events and payment events create a larger monetization surface than seats alone.
The operating consequence
A subscription monetizes access. A transaction model monetizes use. If a customer sends more invoices, pays more suppliers or uses a card more often, revenue can rise without an equivalent increase in customer count. The product can also become harder to replace because it sits inside approvals, vendor records, cash controls and daily financial routines.
But transaction revenue is not simply higher-quality software revenue. Its margin depends on tender type, network and processing costs, rebates, fraud, disputes, cross-border activity and the labor required to resolve exceptions. A dollar of payment volume routed through one method can have very different economics from a dollar routed through another. Total payment volume can therefore grow while contribution per transaction weakens.
Float introduces a separate sensitivity. Earnings on customer funds can benefit from higher balances and interest rates, but that revenue can move with monetary conditions rather than product execution. Operators that blend float, transaction and subscription revenue into one growth narrative may miss a deterioration in the core workflow.
The customer experience changes too. A low software price can coexist with transaction fees, card economics, expedited-payment charges or financing costs. If the total cost is difficult to anticipate, the platform risks losing trust precisely because it has become central to the customer’s cash flow.
What operators should do now
Manage contribution margin by workflow and payment method. Track revenue, direct processing cost, losses, support contacts and settlement exceptions for ACH, card, check, cross-border and expedited payments. Review those measures by customer cohort and use case. Volume is an input; profitable, reliable volume is the outcome.
Design the subscription and transaction schedule together. The subscription should reflect predictable software and service value. Variable charges should reflect variable cost, risk or speed. Customers should be able to understand what changes their bill before they initiate a payment. Transparency is not merely a compliance exercise; it reduces disputes and makes expansion revenue more durable.
Fund controls as product capabilities. Vendor verification, role-based permissions, approval policies, audit logs, anomaly detection and recovery operations determine whether payment volume can scale without a parallel rise in losses and service cost. Growth teams should not be rewarded for increasing transaction adoption while risk and operations absorb the consequences off-screen.
Separate rate-sensitive revenue in planning. Model subscription growth, transaction yield and float independently, then stress payment mix and interest rates. That exposes whether the platform is generating durable operating leverage or leaning on a favorable rate environment.
Finally, measure customer value after the first transaction. The useful cohort view includes payment frequency, product adoption, retention, complaints and realized customer savings or control. A payment workflow should earn its place by making the business easier to run, not simply by creating another fee event.
The decision
SMB fintech is becoming financial infrastructure with software attached. The model can grow faster than seat-based SaaS, but it demands a different discipline: prove that every additional workflow creates value for the customer and contribution for the platform after network cost, risk and service are paid.