Business Operations
Topics in this document:
To access this section in Monetization, from the Menu, click Business operations.
Jobs
To access this section, click Jobs. Scheduled jobs (tasks) or currently executing jobs are shown in this section.
There are nine different jobs in Monetization, namely:
- Billing job
- Invoicing job
- Purchase verification job
- Plan transition job
- Activate deferred purchases job
- Payment collection job
- Dunning job
- Finance reporting job
- Exporting job
Billing job
The billing job is configured to execute billing for any billing profile that match the job criteria, and it is in a state where billing can be executed.
Information:
Billing closes the previous billing cycle and starts a new one. For example, for customers who have their billing day set to the 1st day of the month, the billing job can be scheduled to run on the 1st to shift their billing cycle.To create a billing job, click Create new. Provide a name and description. Also, set the billing job schedule. To schedule the job to run only once, select One-off; to run repeatable based on configured period, select Repeatable; to run the job by another job, select Chain.
Note:
A job configured as a Chain can only be executed by another job.If the One-off schedule is selected, the job must be configured to run at a particular date-time.
If the Repeatable schedule is selected, the job must also be configured to run at a particular date-time. In addition, you must configure how often the job should be executed. It could be yearly, monthly, weekly, daily, hourly, or in minutes.
Note:
Selecting Test mode means that the job will run as a test, which will not mutate the database.Specific criteria for the billing job can be configured; it is designed to determine the particular element(s) the job will affect. The elements include the customer type, customer IDs, groups, custom attribute, and payment types. For instance, the billing job applied only to customers with a post-paid payment type.
To add a criteria, under Criteria, click Create new. To delete a criteria, under Criteria, click Delete.
Note:
The billing job will affect ALL entities if no criteria are provided.Information:
When Monetization executes billing for a customer billing profile, the job will also run billing for group members in that customer’s group. To disable, under Criteria, select Groups, and select value.To chain other jobs, under Chain jobs, click Create new; select the Job type and the Job.
Note:
Only a job configured as a chain job can be shown under Chain jobs.Information:
The Offset parameter specifies the time that should pass before the chained job is executed.To delete a chain job, click Delete.
Once the billing job has been configured, the status, name, criteria, and next run at variables for the job are displayed. To pause the job, click Pause; to resume the job, click Resume; to delete the job, click Delete.
Note:
When a job is paused, it will not execute, irrespective of the schedule. Resuming the job unpauses the job.Invoicing job
The invoicing job is configured to generate the corresponding invoice for any bill(s) with the billing status. The bills will be shown on the invoice, which the customer can pay.
To create an invoicing job, click Create new. Provide a name and description. Also, set the invoicing job schedule. To schedule the job to run once, select One-off; to run repeatable based on configured period, select Repeatable; to run the job by another job, select Chain.
Note:
A job configured as a Chain can only be executed by another job.If the One-off schedule is selected, the job must be configured to run at a particular date-time.
If the Repeatable schedule is selected, the job must also be configured to run at a particular date-time. In addition, you must configure how often the job should be executed. It could be yearly, monthly, weekly, daily, hourly, or in minutes.
Note:
Selecting Test mode means that the job will run as a test, which will not mutate the database.Specific criteria for the invoicing job can be configured; it is designed to determine the particular element(s) the job will affect. The elements include the customer type and customer IDs. For instance, the invoicing job applied only for a specific customer type.
To add a criteria, under Criteria, click Create new. To delete a criteria, under Criteria, click Delete.
Note:
The invoicing job will affect ALL entities if no criteria are provided.To chain other jobs, under Chain jobs, click Create new; select the Job type and the Job.
Note:
Only a job configured as a chain job can be shown under Chain jobs.Information:
The Offset parameter specifies the time that should pass before the chained job is executed.To delete a chain job, click Delete.
Once the invoicing job has been configured, the status, name, criteria, and next run at variables for the job are displayed. To pause the job, click Pause; to resume the job, click Resume; to delete the job, click Delete.
Note:
When a job is paused, it will not execute, irrespective of the schedule. Resuming the job unpauses the job.Purchase verification job
The purchase verification job is configured to check if your customers should have any of their products renewed or canceled, then it will execute that action.
To create a purchase verification job, click Create new. Provide a name and description. Also, set the purchase verification job schedule. To schedule the job to run once, select One-off; to run repeatable based on configured period, select Repeatable; to run the job by another job, select Chain.
Note:
A job configured as a Chain can only be executed by another job.If the One-off schedule is selected, the job must be configured to run at a particular date-time.
If the Repeatable schedule is selected, the job must also be configured to run at a particular date-time. In addition, you must configure how often the job should be executed. It could be yearly, monthly, weekly, daily, hourly, or in minutes.
Note:
Selecting Test mode means that the job will run as a test, which will not mutate the database.Specific criteria for the purchase verification job can be configured; it is designed to control the element(s) the job will affect. The elements include the customer type and customer IDs. For instance, the purchase verification job applied only for a specific customer type.
To add a criteria, under Criteria, click Create new. To delete a criteria, under Criteria, click Delete.
Note:
The purchase verification job will affect ALL entities if no criteria are provided.To chain other jobs, under Chain jobs, click Create new; select the Job type and the Job.
Note:
Only a job configured as a chain job can be shown under Chain jobs.Information:
The Offset parameter specifies the time that should pass before the chained job is executed.To delete a chain job, click Delete.
Once the purchase verification job has been configured, the status, name, criteria, and next run at variables for that job are displayed. To pause the job, click Pause; to resume the job, click Resume; to delete the job, click Delete.
Note:
When a job is paused, it will not execute, irrespective of the schedule. Resuming the job unpauses the job.Plan transition job
The plan transition job is configured to handle migrating a customer from one plan to another. For instance, if the plan transition job is configured to execute once daily at midnight, then any customer waiting for their plan to be changed on that day will have their plan changed at midnight.
To create a plan transition job, click Create new. Provide a name and description. Also, set the plan transition job schedule. To schedule the job to run once, select One-off; to run repeatable based on configured period, select Repeatable; to run the job by another job, select Chain.
Note:
A job configured as a Chain can only be executed by another job.If the One-off schedule is selected, the job must be configured to run at a particular date-time.
If the Repeatable schedule is selected, the job must also be configured to run at a particular date-time. In addition, you must configure how often the job should be executed. It could be yearly, monthly, weekly, daily, hourly, or in minutes.
Note:
Selecting Test mode means that the job will run as a test, which will not mutate the database.Specific criteria for the plan transition job can be configured; it is designed to control the element(s) the job will affect. The elements include the customer type and customer IDs. For instance, the plan transition job applied only for a specific customer type.
To add a criteria, under Criteria, click Create new. To delete a criteria, under Criteria, click Delete.
Note:
The plan transition job will affect ALL entities if no criteria are provided.To chain other jobs, under Chain jobs, click Create new; select the Job type and the Job.
Note:
Only a job configured as a chain job can be shown under Chain jobs.Information:
The Offset parameter specifies the time that should pass before the chained job is executed.To delete a chain job, click Delete.
Once the plan transition job has been configured, the status, name, criteria, and next run at variables for that job are displayed. To pause the job, click Pause; to resume the job, click Resume; to delete the job, click Delete.
Note:
When a job is paused, it will not execute, irrespective of the schedule. Resuming the job unpauses the job.Activate deferred purchases job
Customers can schedule purchases in advance. When configured and executed, the activate deferred purchases job would enable and charge the customer for those purchases.
Note:
The purchases must be valid at that time.To create an activate deferred purchases job, click Create new. Provide a name and description. Also, set the activate deferred purchases job schedule. To schedule the job to run once, select One-off; to run repeatable based on configured period, select Repeatable; to run the job by another job, select Chain.
Note:
A job configured as a Chain can only be executed by another job.If the One-off schedule is selected, the job must be configured to run at a particular date-time.
If the Repeatable schedule is selected, the job must also be configured to run at a particular date-time. In addition, you must configure how often the job should be executed. It could be yearly, monthly, weekly, daily, hourly, or in minutes.
Note:
Selecting Test mode means that the job will run as a test, which will not mutate the database.Specific criteria for the activate deferred purchases job can be configured; it is designed to control the element(s) the job will affect. The elements include the customer type and customer IDs. For instance, the activate deferred purchases job applied only for a specific customer type.
To add a criteria, under Criteria, click Create new. To delete a criteria, under Criteria, click Delete.
Note:
The activate deferred purchases job will affect ALL entities if no criteria are provided.To chain other jobs, under Chain jobs, click Create new; select the Job type and the Job.
Note:
Only a job configured as a chain job can be shown under Chain jobs.Information:
The Offset parameter specifies the time that should pass before the chained job is executed.To delete a chain job, click Delete.
Once the activate deferred purchases job has been configured, the status, name, criteria, and next run at variables for that job are displayed. To pause the job, click Pause; to resume the job, click Resume; to delete the job, click Delete.
Note:
When a job is paused, it will not execute, irrespective of the schedule. Resuming the job unpauses the job.Payment collection job
The payment collection job is configured to automatically collect payments for any due bill if the customer has added a default payment method (credit/debit card).
To create a payment collection job, click Create new. Provide a name and description. Also, set the payment collection job schedule. To schedule the job to run once, select One-off; to run repeatable based on configured period, select Repeatable; to run the job by another job, select Chain.
Note:
A job configured as a Chain can only be executed by another job.If the One-off schedule is selected, the job must be configured to run at a particular date-time.
If the Repeatable schedule is selected, the job must also be configured to run at a particular date-time. In addition, you must configure how often the job should be executed. It could be yearly, monthly, weekly, daily, hourly, or in minutes.
Note:
Selecting Test mode means that the job will run as a test, which will not mutate the database.Specific criteria for the payment collection job can be configured; it is designed to control the element(s) the job will affect. The elements include the customer type and customer IDs. For instance, the payment collection job applied only to a specific customer type.
To add a criteria, under Criteria, click Create new. To delete a criteria, under Criteria, click Delete.
Note:
The payment collection job will affect ALL entities if no criteria are provided.To chain other jobs, under Chain jobs, click Create new; select the Job type and the Job.
Note:
Only a job configured as a chain job can be shown under Chain jobs.Information:
The Offset parameter specifies the time that should pass before the chained job is executed.To delete a chain job, click Delete.
Once the payment collection job has been configured, the status, name, criteria, and next run at variables for that job are displayed. To pause the job, click Pause; to resume the job, click Resume; to delete the job, click Delete.
Note:
When a job is paused, it will not execute, irrespective of the schedule. Resuming the job unpauses the job.Dunning job
The dunning job is configured to run actions set up at the dunning configurations. For more information, see Dunning.
To create a dunning job, click Create new. Provide a name and description. Also, set the dunning job schedule. To schedule the job to run once, select One-off; to run repeatable based on configured period, select Repeatable; to run the job by another job, select Chain.
Note:
A job configured as a Chain can only be executed by another job.If the One-off schedule is selected, the job must be configured to run at a particular date-time.
If the Repeatable schedule is selected, the job must also be configured to run at a particular date-time. In addition, you must configure how often the job should be executed. It could be yearly, monthly, weekly, daily, hourly, or in minutes.
Note:
Selecting Test mode means that the job will run as a test, which will not mutate the database.Specific criteria for the dunning job can be configured; it is designed to control the element(s) the job will affect. The elements include the customer type, customer IDs, and custom attribute. For instance, the dunning job applied only to a specific customer type.
To add a criteria, under Criteria, click Create new. To delete a criteria, under Criteria, click Delete.
Note:
The dunning job will affect ALL entities if no criteria are provided.To chain other jobs, under Chain jobs, click Create new; select the Job type and the Job.
Note:
Only a job configured as a chain job can be shown under Chain jobs.Information:
The Offset parameter specifies the time that should pass before the chained job is executed.To delete a chain job, click Delete.
Once the dunning job has been configured, the status, name, criteria, and next run at variables for that job are displayed. To pause the job, click Pause; to resume the job, click Resume; to delete the job, click Delete.
Note:
When a job is paused, it will not execute, irrespective of the schedule. Resuming the job unpauses the job.Finance reporting job
The finance reporting job is configured to collect all the financial journals for a designated period.
To create a finance reporting job, click Create new. Provide a name and description. Also, set the finance reporting job schedule. To schedule the job to run once, select One-off; to run repeatable based on configured period, select Repeatable; to run the job by another job, select Chain.
Note:
A job configured as a Chain can only be executed by another job.If the One-off schedule is selected, the job must be configured to run at a particular date-time.
If the Repeatable schedule is selected, the job must also be configured to run at a particular date-time. In addition, you must configure how often the job should be executed. It could be yearly, monthly, weekly, daily, hourly, or in minutes.
Note:
Selecting Test mode means that the job will run as a test, which will not mutate the database.Specific criteria for the financial reporting job can be configured; it is designed to control the element(s) the job will affect. The elements include general ledgers, general ledger groups, revenue types, and account types. For instance, the financial reporting job applied only to a specific account type.
To add a criteria, under Criteria, click Create new. To delete a criteria, under Criteria, click Delete.
Note:
The financial reporting job will affect ALL entities if no criteria are provided.The Period duration specifies the period for which the financial report will be created—for example, a financial report from March 2022 or a report from the previous month.
To chain other jobs, under Chain jobs, click Create new; select the Job type and the Job.
Note:
Only a job configured as a chain job can be shown under Chain jobs.Information:
The Offset parameter specifies the time that should pass before the chained job is executed.To delete a chain job, click Delete.
Once the dunning job has been configured, the status, name, criteria, and next run at variables for that job are displayed. To pause the job, click Pause; to resume the job, click Resume; to delete the job, click Delete.
Note:
When a job is paused, it will not execute, irrespective of the schedule. Resuming the job unpauses the job.Exporting job
The exporting job is configured to export multiple components, such as invoices, financial reports, payment transactions, usage events, etc., in various formats to different locations.
To create an exporting job, click Create new. Provide a name and description. Also, set the exporting job schedule. To schedule the job to run once, select One-off; to run repeatable based on configured period, select Repeatable; to run the job by another job, select Chain.
Note:
A job configured as a Chain can only be executed by another job.If the One-off schedule is selected, the job must be configured to run at a particular date-time.
If the Repeatable schedule is selected, the job must also be configured to run at a particular date-time. In addition, you must configure how often the job should be executed. It could be yearly, monthly, weekly, daily, hourly, or in minutes.
Note:
Selecting Test mode means that the job will run as a test, which will not mutate the database.Under Configuration, configure the type of data to be exported, which could be an invoice, financial report, payment transaction, or event. Furthermore, configure the destination: email, SFTP, or webhook.
If email is configured as the destination, provide the mail template. The mail template is configured under Business configuration Template Mail templates.
If SFTP is configured, provide the location and format. The location specifies where the exported file will be transferred.
Tip:
Download and install an SFTP/FTP client/software, for example, FileZilla . Run it as a server on your computer, and provide the URL to Monetization as the location. This will download the file to the server.Specific criteria for the exporting job can be configured; it is designed to control the element(s) the job will affect. The elements include the customer type, custom attribute, and payment types. For instance, the exporting job applied only to customers with a post-paid payment type.
To add a criteria, under Criteria, click Create new. To delete a criteria, under Criteria, click Delete.
Note:
The exporting job will affect ALL entities if no criteria are provided.The Period duration specifies the period for which the export will be created—for example, exporting usage events from March 2022 or invoices from the previous month. The Period field specifies the field to search by.
To chain other jobs, under Chain jobs, click Create new; select the Job type and the Job.
Note:
Only a job configured as a chain job can be shown under Chain jobs.Information:
The Offset parameter specifies the time that should pass before the chained job is executed.To delete a chain job, click Delete.
Once the exporting job has been configured, the status, name, criteria, and next run at variables for that job are displayed. To pause the job, click Pause; to resume the job, click Resume; to delete the job, click Delete.
Note:
When a job is paused, it will not execute, irrespective of the schedule. Resuming the job unpauses the job.Job history
To access this section, click Job history. The job history shows a paginated list of executed jobs for each job in a tabular format from a specific period. It includes the date-time the job last ran, with the total number of errors and successes.
For each executed job, the Name refers to the name of the job; the Time shows when the job started and ended and the execution duration of the job; the Processed shows the number of successes and errors.
To see the full details of the error message for each failed job, as well as the successes, click Details.
Information:
You can filter the job history by date-time.Usage
To access this section, click Usage. This section shows usage events that cannot be rated due to a rating or input field problem. Such events can be corrected and then re-rated.
