PortaOne Transaction By Account - Version 15.0

Overview

The PortaOne Transaction By Account - Version 15.0 collector retrieves account-level transaction data from a PortaOne billing and switching environment, covering transaction activity across Reseller, Reseller Customer, and Retail customer types.

This collector provides visibility into transaction volumes and costs at an account level, grouping records by customer account, transaction type, and date. This enables organizations to validate charges and allocate costs within Varibill based on specific transaction categories such as voice calls.

The collector retrieves rated data, meaning transaction cost values are supplied by PortaOne and submitted directly to Varibill. An optional VAT factor can be applied to adjust charged amounts before submission. Pricing markups can be applied within Varibill without requiring separate price lists.

This is a historically capable collector, meaning each execution retrieves transaction data for a configurable date range in the past, rather than a snapshot of the current state.

For general instructions on creating and running Source Collectors, see: Configuring a New Cloud Source Collector

Collector Summary

About PortaOne

PortaOne is a telecommunications software company that provides integrated billing and service management solutions for communication service providers worldwide. Founded in 2001, PortaOne serves over 500 telecom operators across more than 100 countries, ranging from wholesale carriers to retail service providers.

PortaOne’s core platform, PortaSwitch, is a unified service management and delivery platform covering voice, messaging, IoT/M2M, and data traffic. PortaBilling, its accompanying billing component, enables service providers to manage subscriber accounts, rating, and revenue collection.

PortaOne is used by a broad range of providers including Mobile Virtual Network Operators (MVNOs), cloud PBX operators, traditional carriers, and internet-based telephony providers.

Data Collected

The PortaOne Transaction By Account - Version 15.0 collector retrieves account-level transaction data from PortaOne for a configurable historical date range. The collector queries each customer’s accounts and retrieves transaction records (XDRs), filtering to only the transaction type specified by the Transaction Name Filter parameter.

Each record represents a single account’s transaction activity for a specific date, and includes:

• The total number of transactions (quantity) for the account on that date
• The total charged amount for the account on that date, adjusted by the configured VAT factor
• The transaction type name (for example, Voice Calls)
• The customer name and customer type (Reseller, Customer, or Retail)

The collector retrieves the customer and account data needed to scope collection — covering Reseller, Reseller Customer, and Retail customer types. Customer filtering options allow collection to be limited to or exclude specific customers.

The time window covered by each collection run is configurable, enabling the collector to align with your billing cycle and to recover data from prior periods where needed. A time zone offset parameter ensures that date boundaries align with your local time zone.

The identifiers submitted to Varibill for each record are constructed as follows:

• Product Identifier — the transaction type name as configured in the Transaction Name Filter parameter. For example: Voice Calls
• Client Identifier — the PortaOne customer ID
• Record Identifier — describes the transaction type, account, and date covered by the record. For example: Voice Calls for 27876540878 on 2026-06-28
• Unique Identifier — constructed as {customer ID}#{account ID}#{transaction name}#{date}

Prerequisites

Before configuring this collector, ensure that:

• You have access to a PortaOne environment (PortaSwitch / PortaBilling)
• You have a PortaOne user account with read access to customer and account transaction data
• You have an API token associated with that account
• You have noted the base URL of your PortaOne instance (for example, https://portaone.example.com)
• You have access to the Varibill Source Collector configuration screen

Configuration Parameters

The parameters below are entered when configuring the collector in Varibill. They are grouped by function.

Connection Parameters

These parameters identify and authenticate against your PortaOne instance.

Rating Parameters

Transaction Filter Parameters

Customer Filtering Parameters

These parameters control which PortaOne customers are included in or excluded from each collection run.

Customer Type Collection Switches

These parameters control which categories of PortaOne customer are included in each collection run. Set each switch to false to exclude that customer type.

Date Range Parameters

These parameters define the time window of transaction data collected on each run.

Operational Parameters

These parameters control API pagination and file management behavior.

Configuration Steps

Step 1: Prepare Your PortaOne Environment

1. Confirm that your PortaOne instance is accessible via HTTPS.
2. Identify the PortaOne user account that Varibill will use to connect. This account must have read access to customer and account transaction data for the customer scope you intend to collect.
3. Obtain or generate an API token for that user account.
4. Note the base URL of your PortaOne instance (for example, https://portaone.example.com).
5. Identify the exact transaction type name you want to collect (for example, Voice Calls).

Step 2: Configure the Collector in Varibill

1. In the Varibill User Interface, open the Source Collector configuration screen.

2. Enter the required field values under the Details tab:

   • Hosting Provider: Select Varibill Cloud
   • Source Collector Name: Select PortaOne Transaction By Account - Version 15.0

3. Enter the connection parameters:

   • Portaone Host: The base URL of your PortaOne instance
   • Portaone Username: The PortaOne user account name
   • Portaone Token: The API token for that account

4. Set the Vat Factor according to whether your PortaOne environment returns transaction costs inclusive or exclusive of VAT.

5. Set the Transaction Name Filter to the exact transaction type name you want to collect (for example, Voice Calls).

6. Configure the customer filtering and collection switch parameters to match the customer scope you want to collect.

7. Set the date range parameters (Days Offset and Days Range) to match your billing cycle.

8. Set the Time Zone Hourly Offset to reflect the UTC offset of your local time zone.

9. Save the collector configuration.

Step 3: Run the Collector

Run or schedule the collector according to your standard Source Collector execution process.

For detailed instructions, see: Configuring a New Cloud Source Collector

Troubleshooting

If the collector fails to connect to PortaOne, verify that:

• The Portaone Host URL is correct and includes https:// with no trailing slash.
• The Portaone Username is correct and the account is active.
• The Portaone Token is valid and has not expired or been revoked.
• The PortaOne instance is reachable from the Varibill Cloud environment. If your PortaOne instance restricts access by IP, ensure Varibill’s collector IP addresses are permitted.

If the collector connects successfully but returns no data, verify that:

• The Transaction Name Filter exactly matches a transaction type name in your PortaOne environment.
• The Days Offset and Days Range values cover a period in which transaction data exists.
• At least one customer type collection switch (Collect Reseller, Collect Reseller Customers, Collect Retail) is set to true.
• The Collect for Specific Customer value, if populated, corresponds to a valid PortaOne customer ID that has transaction data in the requested date range.

PortaOne References

The following resources may assist with locating values or understanding your PortaOne configuration.

PortaOne Documentation (External)

• PortaOne Website
• PortaOne Documentation Portal