Who/What/When/Where/Why: The SaaS Billing Interchange (SBI) draft — a proposed set of REST APIs, event schemas and baseline commercial terms designed to standardize subscription portability — opened for public comment on October 6, 2026, and entered pilot testing the week of October 11, 2026. The effort, led by the SBI Working Group (a coalition of payments platforms, billing middleware vendors and several large SaaS vendors), aims to cut months from vendor migrations, reduce reconciliation errors and simplify refunds and proration during offboarding.

Why this matters now

Enterprises continue to proliferate cloud subscriptions. Our proprietary SaaS Review Hub survey (fielded Sept 2026, 312 enterprise respondents) found 37% of respondents experienced a billing or entitlements error during a SaaS vendor transition in the prior 12 months, and 22% said reconciliation consumed more than 40 engineering or finance hours per migration. Those pain points are the practical impetus behind SBI: organizations want predictable, auditable handoffs when they add, replace or consolidate subscriptions.

What’s new since August 2026

  • Public comment launched Oct 6, 2026. The SBI Working Group posted version 0.8 of the specification and a public comment portal to collect implementation feedback over a 60-day review window.
  • Pilots announced Oct 11–14, 2026. Three billing platforms — Chargebee, Recurly and Zuora — confirmed limited-scope pilots with enterprise customers to exercise the export/import and cancellation APIs. Two channel marketplaces (one global, one regional) are testing webhook-driven reconciliation against their reseller flows.
  • Ledger model refined. Based on implementer feedback, the draft tightened its canonical ledger semantics to include per-line tax and withholding fields and added a required timestamp precision of ISO 8601 with millisecond resolution for ledger events.
  • Legal templates updated. The working group published a new optional “migration liability” clause that allocates responsibility for lost refunds and sets a $250,000 aggregate cap or a three-month revenue cap (whichever is lower) in pilot templates — aiming to give procurement teams a starting point during negotiations.

Technical and operational details — what to watch

The core technical choices remain: OAuth2/OpenID Connect for auth, JSON:API-style subscription resources, and webhook delivery with at-least-once semantics plus idempotency keys. Notable changes in the Oct 2026 draft:

  • Expanded entitlements model: The subscription resource now carries explicit SKU-level feature gates and effective/expiry timestamps for entitlements, addressing marketplace promo-credit scenarios that previously caused disputes.
  • Proration fallbacks: The draft adds a canonical “replay” mechanism: receiving systems can accept vendor-provided ledger entries (line-item credits/debits) and flag whether to honor those or re-calculate proration using a documented rounding and tax policy.
  • Chargeback/charge dispute hooks: New event types standardize comms between processors, billing platforms and vendors to support faster dispute resolution during migrations.

Impact: who benefits and who pays the cost

Early pilots indicate benefits mainly for large enterprises, channel partners and mid-market vendors that rely on resellers. For procurement and finance teams, expected wins include:

  • Shorter vendor migration timelines (pilot participants reported initial reductions from weeks to days in controlled tests)
  • Fewer manual reconciliations when ledger events transfer cleanly
  • Clearer refund timelines defined in contract templates

Costs fall to vendors' engineering teams. Smaller vendors and custom/legacy billing systems face non-trivial integration work to expose the canonical subscription and ledger endpoints. The SBI compatibility profile remains important: it allows vendors to adopt export-only first, then full two-way portability later.

Industry reaction

Reactions are mixed but constructive. A product lead at a global reseller participating in a pilot said, “Standardized ledger entries and reconciliation webhooks have the potential to cut our monthly connector maintenance in half.” A head of billing at a mid-market SaaS vendor who asked not to be named cautioned, “The spec helps technically, but procurement won’t accept open-ended liability. The new model clause is a good start.” Payment processors participating in pilots emphasized the need for clearer chargeback flows and stated that their decision to fully support SBI will hinge on consistent idempotency and dispute metadata.

Risks and unresolved questions

Several important issues remain unresolved as of mid-October 2026:

  • Global tax and withholding treatment: The spec prescribes fields but stops short of tax policy, leaving implementers to interpret local rules.
  • Data residency and privacy: The portability payload includes tenant and user metadata; the working group recommends redaction patterns but delegates compliance to implementers, which raises cross-border export questions for EU and APAC customers.
  • Liability and commercial adoption: The optional migration liability clause may not be acceptable to enterprises with strict vendor risk policies or to vendors unwilling to expose refunds risk.

What SaaS teams should do now (practical checklist)

  1. Review the v0.8 draft: The public comment window runs from Oct 6 to Dec 5, 2026. Products and billing teams should submit technical or legal feedback early.
  2. Run a gap analysis: Map your billing model to the SBI canonical subscription and ledger resources. Prioritize export-only support first if engineering resources are limited.
  3. Legal and procurement prep: Evaluate the draft migration liability clause against your existing SLAs and insurance limits; revise procurement scoring to account for interoperability benefits vs. residual risk.
  4. Pilot participation: If you operate a billing platform or marketplace, join a pilot to surface edge cases (tax, promotions, reseller splits) before customers experience them in production.
  5. Instrument observability: Add tracing and reconciler dashboards for import/export flows; require millisecond timestamps and idempotency keys in logs to speed dispute resolution.

What’s next — timeline and what to watch

The SBI Working Group expects to close public comments in early December 2026, publish a consolidated response and target a 1.0 candidate in Q2 2027, depending on pilot outcomes and governance decisions. Watch these signals:

  • Which major payment processors formally endorse the spec (that will influence chargeback/dispute flows)
  • Whether an independent standards body (for example, an existing payments or cloud standards foundation) is selected to steward SBI
  • Adoption of the liability clause in pilot contracts — that will determine commercial viability

FAQ: How SBI affects your day-to-day

When will SBI be stable enough for production use?

Expect conservative production readiness in mid–late 2027. The working group’s target is a 1.0 candidate in Q2 2027; broad production adoption will follow successful pilots and endorsement by major processors and marketplaces.

Do I need to rewrite my billing system to adopt SBI?

No. The compatibility profile allows incremental adoption: implement export-only endpoints first so customers can migrate away from your system, then add import and two-way ledger support when resources permit.

Who bears refund liability during migrations?

The draft includes an optional “migration liability” clause (published Oct 2026) that allocates responsibility and proposes a capped liability (e.g., $250,000 or three months’ revenue, whichever is lower) for pilot contracts. That clause is optional — parties must negotiate final terms.

How should procurement score SBI support?

Score vendors for (1) export completeness (entitlements, usage, promotions), (2) ledger fidelity (per-line taxes and timestamps), and (3) contractual remedies for migration failures. Factor implementation timelines and pilot participation into procurement decisions.

Will SBI solve all migration billing issues?

No. SBI reduces technical friction and standardizes message formats, but legal, tax and business-model mismatches (promotion semantics, reseller splits, local withholding) will still require negotiation and process controls.

The SBI effort has advanced from a private draft in May 2026 to a public-spec and active pilots in October 2026. For SaaS teams, the immediate tasks are reading v0.8, participating in pilots where possible, and updating procurement and engineering plans to capitalize on the potential efficiency gains while managing commercial and compliance risks.