Overview
This document explains setting up billing for Google’s Billable Transactions and testing required to go-live with Google Mobility Services. It is assumed Mobility Services have been enabled and implemented (for more information on Mobility Services, click here.)
Mobility Services Billing Overview
Mobility Services and subsequent billing are split into the following two categories (refer to this link for details on billing.)
Mobility Billing Categories
- Mobility Services (Activate, Optimize, and Accelerate)
- Shipment Task Model using Fleet Engine
After being onboarded to Mobility Services, a billing test must be passed to go live with Mobility Solutions. The detailed billing test steps for the above two categories are explained below.
Consumption Versus Billable Transaction Billing Models
The following diagram illustrates the difference between Consumption and Billable Transaction billing models. For a more detailed diagram, click here.
Mobility Services Billing Test & Go-live
These steps assume successful onboarding and implementation of Mobility Services.
- Billing Overview
Review this article to understand how billing works. - Billing Setup
Follow these instructions for the proper way to set up billing to meet the Reporting Requirements of the Mobility Activate, Optimize, and Accelerate services. - Integrate & Implement Billing
Follow these instructions to implement billing and add billing service API calls.
Note: when adding the billableEventId and Mobility Billing API call to the solution, this can be done via two methods: 1) in the production project (no charges are incurred) or 2) a sandbox project with either Consumption or Mobility billing enabled. - Perform Billing Test
Follow these Validate Billing instructions to test and validate billing integration.
The output of this test is a CSV to provide to Woolpert and Google (explained in the next steps). Contents and format of the CSV are defined here in the Validate Billing instructions. - Provide Test CSV to Woolpert
After performing the Billing Test and capturing the results to a CSV, send the CSV to your Woolpert contact (Field Sales Rep or Customer Engineer). See example CSV. - Submit CSV to Google for Approval
Woolpert submits the CSV to Google (see email template) for approval with an expected turnaround time of no more than three business days from time of submission. - Go-live with Billing
Once Google approves the Billing Test, the following steps are performed. Refer to this article for detailed instructions.
- Woolpert creates a billing account for the customer in the Woolpert organization
- Woolpert provides the customer an order form to approve Mobility Services
- Woolpert sends the signed form to Google
- The customer’s project is moved to this new billing account and is then live
Shipment Task Model Billing Process
- Billing Overview
Review this article to understand how billing works. - Billing Setup
Follow these instructions for the proper way to set up billing to meet the Reporting Requirements when using Fleet Engine Deliveries API.
Note: if you are using Mobility Activate, Optimize, or Accelerate, follow these Mobility Billing Setup and Testing instructions. - Integrate & Implement Billing
Follow these instructions to conform to billing requirements - Go-live with Billing
Once ready to go live, the following steps are performed. Refer to this article for detailed instructions.
- Woolpert creates a billing account for the customer in the Woolpert organization
- Woolpert provides the customer an order form to approve Mobility Services
- Woolpert sends the signed form to Google
- The customer’s project is moved to this new billing account and is then live
Additional Notes / References
- Refer to this article when migrating from legacy ODRD Billable Trips to new Mobility Billing
Comments
0 comments
Please sign in to leave a comment.