Home > Cloud Cruiser 3 > Administering > Managing customers > Customer activities and attributes > Working with transactions

Working with transactions

A transaction enables you to process charges or credits for any resource that is not contained in a collected resource usage file. These can include resources like a base subscription fee, or a monthly maintenance fee, or a credit for an overage for a previous period. Consider defining a set of resources to use specifically for common transactions.

This section of articles contains the following:

Transactions are processed by a batch job. During processing, Cloud Cruiser creates a CC Record file for each defined transaction with the appropriate identifiers and resource and loads it into the database.

There are two types of transactions: recurring and non-recurring.

Recurring transactions

Recurring transactions are scheduled as either monthly or daily. Monthly recurring transactions are only processed on the last day of the accounting period. For example, if the following are true:

  • Customer A’s accounting periods are set to the default (match monthly calendar)
  • You add a recurring transaction to Customer A
  • The transaction’s frequency is monthly

Then when you run your batch transaction processing job, the monthly recurring transaction for Customer A will be processed only on run dates of January 31, February 28 (or 29 in a leap year), March 31, April 30, and so on.

After a recurring transaction is processed for a specific accounting period, it will not be processed in subsequent runs for the same Selection Date unless the reProcess property is set to true . For more information, see Processing transactions.

Deselecting the Active option for a recurring transaction prevents the transaction from being processed by any run, regardless of the value of reProcess . You can later make the transaction active to resume processing it.

Non-recurring transactions

Non-recurring transactions, also known as miscellaneous transactions , are processed only once on their defined transaction date. These can be credits for past overages or a one-time charge.

After a non-recurring transaction has been processed, it is not processed on subsequent runs of the transaction processing job unless the reProcess property is set to true .

Last modified

Tags

This page has no custom tags.

Classifications

This page has no classifications.
© Copyright 2018 Hewlett Packard Enterprise Development LP