Skip to content

For SaaS, cloud services and digital business models

Subscription Management & Billing for SaaS

Manage customers, plans, subscriptions, add-ons, billing models, invoices and payments in one platform. tebio connects subscription management and billing with your SaaS product — via Hosted Pages, Business Portal, API and Webhooks.

SaaS billing quickly becomes more complex than the subscription itself

A simple monthly plan is easy to bill at first. But with different plans, add-ons, product changes, B2B customers, annual contracts, usage, invoices, payment status and finance processes, complexity grows quickly. If this logic is implemented directly in the SaaS product, you end up with a second product inside your product: your own subscription, billing and payment stack.

  • Terms, changes, cancellations and billing rules are implemented directly in the SaaS backend and have to be maintained permanently.
  • Product data, subscription status, invoice and payment often live in different systems.
  • Credit card payment at checkout is not enough for many B2B business models.
  • Plans, add-ons, one-time fees, usage and different billing cycles have to work together.
  • Upgrades, downgrades or add-ons have to be integrated into the subscription lifecycle correctly from a commercial standpoint.
  • Invoices, incoming payments, open items, reports and accounting processes have to stay traceable.
  • Plan changes, cancellations, invoices and payment information increasingly need to be available digitally.
  • Changes to a subscription have to be reliably reflected in the SaaS product.

tebio takes over the commercial subscription and billing layer

tebio separates commercial subscription processes from the SaaS product itself. Customers, products, subscriptions, options, billing, invoices, payments and finance processes are managed in tebio. The SaaS backend stays connected via API and Webhooks.

This means not every pricing, billing or lifecycle rule has to be built directly into the product code. Product teams can focus on the SaaS application, while tebio structures the commercial processes around the recurring business model.

For different SaaS business models

SaaS isn't always a monthly credit card subscription. tebio supports different commercial models and lets you map them within one shared subscription platform.

Monthly Subscription

Monthly base fee with regular billing.

Annual Subscription

Annual contracts and billing cycles for B2B or B2C customers.

Plans & Add-ons

Base packages can be extended with additional options or services.

Prepaid

Services or access are paid for before use.

Postpaid

Services or usage are billed afterwards.

Usage-based

Usage-based components can be included in addition to base fees.

Hybrid Pricing

Recurring base fee plus add-ons, one-time fees or usage.

B2B Contract Billing

Contract-based SaaS offerings with invoice, payment terms and bank transfer.

From plan to active subscription

tebio maps the commercial lifecycle of a SaaS subscription in a structured way and connects it with the product backend.

1. Customer signs up or is created

The customer is created via a hosted page, the Business Portal or the API.

2. Select a plan

A product with price, term, options and billing logic is selected.

3. Create a subscription

The subscription links customer, product, payment method, term and billing configuration.

4. Provide product access

API and Webhooks can notify the SaaS backend about the new or changed subscription.

5. Change a subscription

Options, product changes, pauses or cancellations can be handled in the subscription lifecycle.

6. Run billing

Recurring, one-time or usage-based items are billed.

7. Invoice and payment

Invoice, payment status and downstream processes stay linked to the subscription.

8. Finance and reporting

Reports, journal, DATEV-ready processes and exports support downstream accounting workflows.

The commercial processes behind your SaaS product

  • Manage customers

    Manage B2B and B2C customers, contacts, addresses, properties and documents centrally.

  • Account for products, options and prices

    Product, option and pricing logic can be integrated into external frontends, offer flows or internal processes.

  • Manage subscriptions

    Manage status, terms, billing cycles, payment methods and lifecycle changes in the subscription context.

  • Offer add-ons

    Model additional features or services as options.

  • Add one-time fees

    Bill setup, onboarding or other one-time fees in addition to the subscription.

  • Automate recurring billing

    Bill recurring fees via defined billing processes.

  • Account for usage

    Usage-based components can be included in billing, depending on the business model.

  • Support prepaid and postpaid

    Support different charging models within the platform.

  • Create invoices

    Turn billing processes into invoices, payment documents and downstream processes.

  • Connect payments

    Support gateway-based and bank-based payment processes.

  • Provide Self-Care

    Offer digital customer processes for subscription, invoice and payment information.

  • Integrate your SaaS backend

    Pass subscription events to product and provisioning systems via API and Webhooks.

Change plans and add-ons without spreading billing logic across your product

SaaS offerings evolve constantly. Customers switch plans, book additional services or end individual options. tebio manages these commercial changes in the context of the subscription.

Upgrade

Switch to a higher-tier plan.

Downgrade

Switch to a different plan according to the configured change rules.

Book an add-on

Add a feature or service to an existing subscription.

Switch an add-on

Replace an existing option with a different one.

Cancel an add-on

End an additional service independently of the main subscription, if the product model allows it.

Pause a subscription

Temporary pauses can be used for suitable business models.

Cancel a subscription

Manage cancellations with the appropriate term and contract rules.

Billing that fits your pricing model

SaaS pricing can consist of several components. tebio combines recurring fees, one-time items and usage-based components within one shared billing process.

Recurring Fee

Regular base fee for the subscription.

One-Time Charge

One-time fees for setup, onboarding or additional services.

Add-on Fee

Recurring or supplementary fees for options.

Usage

Usage-based fees for suitable business models.

Prepaid

Billing before use or service delivery.

Postpaid

Billing after the service or usage period.

B2B SaaS needs more than credit card payments

Many B2B SaaS providers sell through quotes, contracts and individual sales processes. Customers expect invoices, payment terms, bank transfer, SEPA, e-invoices and a clean connection to finance and accounting.

tebio combines these established B2B processes with modern subscription automation.

Pay by invoice

Business customers can be billed by invoice.

Payment terms

Due dates and payment terms are taken into account in the invoicing process.

SEPA via your own bank

Recurring payments can be processed via the house bank procedure.

Bank transfer

Classic B2B payments by bank transfer remain possible.

E-invoices

For suitable B2B scenarios, structured e-invoicing processes can be supported.

DATEV export

Billing and financial data can be provided for downstream DATEV processes.

Combine online payments and classic B2B payment methods

tebio supports different payment methods depending on the business model. This lets you map self-service SaaS offerings and sales-led B2B contracts within the same platform.

  • Credit card
  • PayPal
  • Apple Pay
  • Google Pay
  • Klarna
  • Amazon Pay
  • SEPA direct debit
  • Bank transfer

Payment gateways

Depending on the configuration, Stripe, PayPal or Computop, for example, can be used.

SEPA via your own bank

SEPA direct debit can be used via the SaaS provider's own bank.

Bank transfer

B2B customers can pay invoices by bank transfer.

  • Hosted checkout

    Customers can choose SaaS offerings, enter their data and complete the ordering process digitally.

  • Self-Care

    Depending on the configuration, customers can view and manage their own data, subscriptions, invoices or payment information.

  • Your own frontend

    Alternatively, existing SaaS interfaces can be integrated directly with tebio via API and Webhooks.

Checkout and self-service without building everything yourself

Hosted Pages can help SaaS providers launch digital customer processes quickly. They complement your own frontends and can be connected directly to customer, subscription, billing and payment processes in tebio.

Connect subscription status with your SaaS product

A commercial subscription alone doesn't grant product access. The SaaS backend needs to know which customer has which plan, which options and which status. API and Webhooks form the connection between tebio and the SaaS product.

  • SaaS backend
  • User management
  • Tenant management
  • Provisioning
  • CRM
  • ERP
  • Data warehouse
  • BI
  • Finance system
  • Support system
const customer = await tebio.customers.create({
  email: "kunde@example.de"
});

await tebio.subscriptions.create({
  customerId: customer.id,
  productCode: "EPAPER",
  billingCycle: "MONTHLY"
});

await tebio.webhooks.create({
  url: "https://app.example.de/tebio",
  topics: ["subscriptions", "invoices", "payments"]
});

Connect subscription billing with finance

Recurring SaaS revenue creates downstream accounting processes. tebio connects billing, invoices, payment status, reports, journal and DATEV-ready processes so finance teams can track and process subscription revenue.

  • Invoice overviews
  • Payment status
  • Open items
  • Recurring revenue
  • Financial reports
  • Journal
  • DATEV export
  • Export and reconciliation processes
  • Data for downstream finance systems

Typical SaaS scenarios with tebio

Self-service SaaS

A customer chooses a plan online, pays digitally and then automatically gets access to the SaaS product.

B2B SaaS with invoicing

A business customer gets an annual subscription with invoice, payment terms and payment by bank transfer.

SaaS with add-ons

Customers can book additional features or services as options on their existing subscription.

SaaS with usage

A recurring base fee is combined with usage-based billing components.

SaaS with a sales contract

Sales closes an individual B2B contract. The subscription is created in the Business Portal or via the API and then billed automatically.

SaaS with an existing product backend

The existing SaaS product stays as it is and receives subscription changes via API and Webhooks.

Frequently asked questions

Which SaaS business models is tebio suited for?

tebio is suited for SaaS providers with recurring, one-time or usage-based revenue models. These include, for example, monthly or annual subscriptions, add-ons, prepaid and postpaid models, and combinations of base fee and usage.

Can tebio manage SaaS plans and add-ons?

Yes. SaaS plans can be modeled as products with prices. Additional features or services can be added as options and managed in the context of the subscription.

Can a customer change their SaaS plan?

Product changes can be mapped in tebio via defined change rules. This lets you control upgrades or downgrades, for example, within the subscription lifecycle.

Does tebio support usage-based SaaS billing?

Yes. Depending on the business model, usage-based components can be included in billing and combined with recurring or one-time fees.

Does tebio support prepaid and postpaid?

Yes. tebio can support business models billed both in advance and in arrears. Which variant is used depends on the respective product and billing model.

Can tebio be connected to our existing SaaS backend?

Yes. Via API and Webhooks, tebio can be connected to existing SaaS backends, provisioning systems, CRM, ERP, finance or data systems.

Does tebio handle provisioning for our SaaS application?

tebio manages the commercial subscription status and can pass changes to the SaaS backend via API and Webhooks. How user accounts, tenants, features or product access are technically provisioned remains the responsibility of the respective SaaS product or connected system.

Do we need our own checkout?

Not necessarily. SaaS providers can use tebio Hosted Pages for digital ordering processes or connect their own frontend via API and Webhooks.

Can customers manage their subscription themselves?

Yes. Depending on the configuration, Self-Care can provide and manage customer data, subscriptions, invoices or payment information digitally, for example.

Is tebio also suitable for B2B SaaS?

Yes. tebio supports typical B2B processes such as recurring contract billing, pay by invoice, payment terms, SEPA via your own bank, bank transfer, e-invoices for suitable scenarios and DATEV-ready processes.

Do SaaS customers have to pay by credit card?

No. In addition to gateway-based online payments, typical B2B payment methods such as SEPA direct debit via your own bank or payment by bank transfer can also be used.

Can tebio create invoices automatically?

Yes. Billing processes can automatically generate invoices or suitable payment documents and link them to customers, subscriptions and payment processes.

Is tebio a payment service provider?

No. tebio connects billing and payments but is not a payment service provider itself. Online payments can be processed via connected payment gateways.

Is tebio part of our SaaS application?

tebio forms the commercial subscription management and billing layer. The SaaS product itself, its user interface, features and technical product logic remain in the SaaS system.

Can tebio be connected to DATEV?

tebio can provide billing and financial data for DATEV export and downstream DATEV-ready processes.

Ready to move subscription management and billing out of your SaaS product?

Start with tebio for free or talk to us about how you can connect plans, subscriptions, add-ons, billing, payments, Self-Care and your existing SaaS backend in a flexible architecture.