Generating Itemized Usage Statements for Multi-Tenant Accounts

Generating Itemized Usage Statements for Multi-Tenant Accounts.

Configuring Sub-Tenant Billing Profiles

To maintain white-label integrity, you must isolate usage data per sub-tenant. Navigate to the Partner Portal and define unique billing profiles for each client. By assigning specific sub-accounts, you ensure that all traffic—including OTP, SMS, and DLR events—is tagged correctly. This JIT allocation prevents data leakage between tenants. Ensure your sub-tenants maintain a minimum USD 20 prepaid floor to keep services active. If a sub-tenant exceeds USD 1,000/month, the system triggers a soft review to verify traffic patterns and prevent potential fraud.

Automating Usage Exports

Use the reporting engine to generate automated CSV or JSON exports at the end of each billing cycle. These reports aggregate E.164 formatted numbers and associated MRC charges. By filtering via sub-tenant ID, you generate a clean statement that reflects only the services consumed by the specific client. This process ensures that your internal margins remain hidden while providing the client with a clear breakdown of their communication expenses.

Handling Webhook and DLR Reconciliation

Accurate billing relies on precise DLR tracking. Ensure that your sub-tenants have configured their webhooks to receive real-time delivery status updates. When a message is sent, the system logs the event against the sub-tenant ledger. If a message fails, the system automatically adjusts the ledger to prevent incorrect charges. This automated reconciliation is critical for maintaining trust with your end-users and ensuring that every billed event is verified.

Managing Number Assignments

Numbers are assigned to sub-tenants via JIT provisioning. When a client requests a number, the system pulls it from the available pool and binds it to their specific account. This prevents the need for manual stock management. Once assigned, the MRC is automatically calculated and added to the sub-tenant invoice. If a number is released, the system immediately stops the billing cycle for that asset, ensuring the invoice remains accurate.

Integrating Reporting Workflows

To streamline your operations, use the following documentation for advanced ledger and export management:

• Partner invoice week: isolation still holds on the export
• Partner ledger isolation edge cases
• API invoice week: idempotency gaps that duplicate debit

These resources provide the technical foundation for handling complex billing scenarios and ensuring data consistency across your white-label platform.

Start with IOSOR

Navigate to the Partner Console and select the Sub-Tenant Billing Profile section to configure isolated client profiles. Set up automated billing-cycle reporting filters to strip internal baseline costs from all exported CSV and JSON statements. Test the webhook status tracking on a single sub-account to confirm that usage logs and MRC charges align perfectly before cycle end.

IOSOR takeaway

Generating clean, sub-tenant usage summaries ensures white-label security while maintaining strict accounting alignment across complex multi-client setups. Isolating events per sub-account ID prevents margin leakage and eliminates manual ledger reconciliation when invoices are generated.

Do automate end-of-cycle usage exports using specific sub-tenant filters and verified DLR ledger records. Don't share unmasked platform log exports that expose baseline unit pricing or aggregate distinct sub-client traffic into a single report.