Partner billing reports

Partners receive summary billing reports that provide aggregated daily counts of billable events, grouped by agent, event type, and carrier. This serves as a high-level summary of all billable traffic, providing you with valuable analytics and necessary visibility into your traffic data.

File generation and access

Reports are generated daily in CSV format and delivered using the Google SFTP Service.

SFTP access

Access to the reports is protected by public/private key pairs. The SFTP credentials ensure secure and isolated access.

How to get SFTP access

To receive billing reports, you must first set up your SFTP credentials:

1. Generate an SSH key pair: Follow the instructions to generate a Secure Shell (SSH) key pair for an SFTP dropbox.
2. Initiate onboarding: If you are interested in receiving partner reports, reach out to your Google business representative or primary Google contact. They will guide you through the initial setup and registration of your partner account for billing reporting.
3. Submit your public key: Provide your public key (PUB file) to your Google contact. Google will then provision your account, assign your unique <partner_id>, and notify you when access is ready.

4. Access the server: Once notified, you can access your reports on the SFTP server at partnerupload.google.com using port 19321. Use the following command to connect:

   sftp -i <path_to_private_key> -P 19321 rbmreports-partner-<partner_id>@partnerupload.google.com
   

File naming convention

All carrier reports are split per carrier.

The directory and file naming structures are as follows:

rbmreports-partner-<partner_id>/
  <YYYY>/<MM>/<DD>/
     summary_<short_carrier_id>/
        summary_<short_carrier_id>_<YYYY-MM-DD>.csv
     ...
     <prefix>_<short_carrier_id>/
        <prefix>_<short_carrier_id>_<YYYY-MM-DD>.csv

The <prefix> identifies the specific type of report being delivered.

Standard prefixes include:

Report type	Filename prefix
Summary report	summary

An additional custom filename prefix may optionally be added if multiple reports exist for the same carrier and partner (for instance, during format migrations). You should always scan all files recursively under the dated directory.

CSV report structure

The following sections define the fields, data formats, and column definitions used in the partner billing reports.

For additional questions, reach out to your carrier.

Summary report format

Field	Format	Description	Example
type	string	Type of billing event	a2p_session
agent_id	string	Unique ID for agent	[e-mail]
agent_name	string	Name of the agent that participated in the event	ACME Brand
carrier_id	string	Carrier ID for the traffic	super-carrier
carrier_name	string	Carrier name	Super Carrier
carrier_country	string	ISO 3166-1 alpha-2 country code	US
start_date	string	Date when the event started (YYYY-MM-DD format)	2026-05-07
billing_date	string	Date when the billing report was generated	2026-05-08
event_count	number	# of aggregated events per type (SUM)	150
segment_count*	number	The calculated segment count for US billing model events (SUM) *US only	5