Billing Actions

Billing actions are part of Gotransverse's Action Framework. A billing action is an optional feature that triggers events using email notifications or HTTP posts that are based on configured thresholds. For example, billing actions can make HTTP calls that send information to an external web service when an invoice is created. Another billing action could be configured to send customized notifications to customers who have overdue invoices. Both HTTP and email calls are automated and configurable.

Notification actions are managed in the Setup application’s Notification Management Module. Refer to Notification Operations for more information about the different email, HTTP, approval, and FTP operations that can be configured for various features.

Gotransverse has the following two billing action categories related to invoices:

• Distribute Invoice — This action is triggered by the distribution of an invoice. When an invoice is made available by a bill cycle run, Gotransverse can send a notification to a specified recipient that the invoice has been generated. In addition, you can use this action to remind customers that they will be invoiced soon.

• Invoice Overdue — This action is triggered by a customer's payment failure so that you can begin dunning management (Delinquent User Notification). This process involves customer communication at configurable intervals.

To enable an action, the Enable Action checkbox must be selected on the Configure Action Details window. Otherwise, the billing action is not enabled and is not used. Refer to Edit Payment Action Details for instructions.

You can configure specific billing management tasks to an action with two types of operations:

• Email — Email notifications are sent to your customer or another individual. Use the email operation to send customized notifications at specified intervals based on a template. For dunning purposes, you can configure multiple email operations so that a customer is notified at set intervals. For example, an action can be configured to send emails at 30, 60, and 90 days before or after payment is due. Refer to Add or Edit Email Operations for Billing Actions for more information. Email operations for a payment are based on Invoice notification templates.

• HTTP Request — HTTP calls send information or requests to a defined URL. You can configure a URL with a User ID and password to enable integration with web services outside Gotransverse. Refer to Add or Edit HTTP Request Operations for Billing Actions for more information.

Refer to the following topics for additional information about managing billing actions:

 

 

 

 

Topic updated: 04/2024.