Whitelabel Billing Support

Whitelabel Billing Frequently Asked Questions

High-level operational answers for partners evaluating or deploying Apeiron as their branded billing engine.

FAQ Scope

  • Account model and branding
  • Invoices, taxes, and payments
  • API and service catalog control

Platform Model

How the whitelabel account structure works and what the partner controls.

What is a Whitelabel Billing Account?

It is the parent account structure Apeiron provisions for a partner. That parent holds the partner's brand identity, product table, pricing logic, payment settings, tax treatment, and operational preferences.

How are end customers represented?

Each end customer is created as a child account beneath the partner's parent account. Child accounts inherit the partner's catalog and branding while keeping customer data, services, and billing logically isolated.

Can the platform operate fully under the partner brand?

Yes. The operating model supports branded invoices, branded dashboard experiences, branded service portals, communication templates, and partner-facing catalog presentation so the end customer experiences the partner identity rather than Apeiron.

Billing Operations

Core billing behavior and operational controls available inside the platform.

Invoice Workflows

Apeiron can generate branded invoices on monthly, quarterly, annual, or custom schedules. Partners can review and approve billing runs before invoices are finalized and delivered.

Payments and Collections

The platform supports payment acceptance, balance reconciliation, credit application, aging visibility, and dunning workflows for overdue accounts.

Does the billing engine support one-time and non-standard charges?

Yes. Generic charge and order functions allow partners to bill installation fees, equipment, professional services, project work, activation fees, or other ad hoc events directly into the next invoice cycle.

Can Apeiron handle telecommunications taxes and surcharges?

Yes. The taxation engine is designed for telecom billing complexity, including jurisdiction-aware calculation, tax exemptions, and regulatory or carrier-related surcharges such as E911 and universal service fees.

Can one partner account support different customer billing schedules?

Yes. The same whitelabel partner account can run multiple bill cycles concurrently, which is useful when different customer segments require different invoice timing.

Service Catalog and API Control

How partners extend the billing engine into their own ordering, support, and provisioning workflows.

Can partners define their own products and retail pricing?

Yes. Partners control product tables, plan definitions, pricing tiers, bundles, promotions, and rate structures inside the platform, allowing margin control and differentiated go-to-market offers.

What can be done through API?

Partners can create accounts, manage catalog data, submit orders, trigger invoice generation, retrieve invoices, and query account or billing history so Apeiron can sit behind external CRM, ERP, ecommerce, or partner portal workflows.

Which Apeiron product lines can use the whitelabel billing model?

The model can support cellular and MVNE services, wireless data, hosted voice, SIP trunking, messaging, fax, POTS replacement, and Microsoft Teams voice services under a unified branded billing environment.

Customer Experience

What end users can access when the partner deploys the broader whitelabel platform model.

Do customers get a self-service portal?

Yes. Customers can access a branded dashboard for ordering, invoice viewing, payment actions, subscription management, and account administration.

Can voice features be exposed to end users?

Yes. Depending on the deployed services, partners can expose branded call forwarding, voicemail, fax, communicator, and related service portals so common moves, adds, and changes are self-service.

Next step: if the requirement is a branded catalog plus operational billing under one identity, start with the overview page and service brief, then map which Apeiron service categories should sit inside the initial product table.