What does this section cover?
What are Bill Sending Runs?
Bill Sending Run Definitions are used to determine the business rules that will be used in order to identify bills that should be sent through Email, SMS or an external system.
Bill Sending runs are used to log the execution of bill sending run definitions, that were performed in order to identify the bills that should be send, create a communication and a communication queue entry, and if an external system is not specified, then process those communications, by sending them through email or SMS.
Bill sending runs can be performed only within an effective bill sending run definition. When executing a Bill Sending Run Definition the bills that should be sent are identified based on the following criteria
- The related accounts receivable is active
- The related accounts receivable includes an active presentment preference having a type equal to the type specified in the presentment preferences conditions
- The bill meets the definition criteria
A new bill sending run is created each time a recurring Bill Sending Run Definition is submitted. Whenever a run has been submitted, the bill sending run is added to the scheduler to be executed based on the specified run definition scheduling.
Creating, Editing & Deleting Validations & Restrictions
Action | Validations | Restrictions | Additional Information |
---|---|---|---|
Edit |
|
|
|
Save |
|
|
|
Delete |
|
|
|
Bill Sending Run attributes
Name | Description |
---|---|
Name* | The name of the definition |
Alternative code* | The alternative code of the definition |
Description | A description of the definition |
Life cycle state | The life cycle state of the definition. The supported values are effective and not effective |
Unified code | An auto generated code which is used to group the various instances of each Bill Sending Run Definition |
Version | An auto generated number which is used to specify the version of each Bill Sending Run Definition. New Bill Sending Run Definition versions are created each time they are edited, if they are already been used by any bill sending runs |
Input Settings: It defines the settings that will be used in order to create the communications that will be used to send the bills | |
Communication Media* | The media that will be used to communicate the bills. The following media is supported:
|
Communication template* | The communication template that will be used to create the communication for each bill. The available communication templates are effective and filtered based on the media specified above. The media are equal to one of the following:
|
Communication Queue External System* | Used to determine the external system that will actually send the communication. Mandatory on Conditions: Mandatory if the communication template is set to device and optional for any other types of communication templates |
Criteria | |
Billing Run Criteria: It defines the criteria that will be used to retrieve the bills that will be sent | |
Bills filter method* | It determines which bills will be retrieved, based on if they were already sent, rejected during sending or not processed at all. The following options are supported:
|
Billing Run Filter Method* | It determines the method that will be used to filter the bills. The supported options are the following:
|
Billing Run Selection*
| A set of normal billing runs that will be considered in order to retrieve the bills that will be sent. Mandatory on Conditions: Mandatory only if the "Bills included in specific billing runs" option is selected as a Billing Run Filter Method |
Presentment Preference Criteria: It defines the settings that will be used in order to retrieve the accounts receivable that will be processed | |
Type* | The type of presentment preference that will be used to retrieve the accounts receivable. The supported types are
|
Segment Criteria: Determines the criteria that are used to identify the bills that will be sent. At least one segment will be specified, in one of the two options | |
Included in Segment | A list of segments which are used to filter the bills that will be sent. |
Not Included in Segment | A list of segments which are used to exclude bills. |
Configuring a Bill Sending Run tailored to your company's needs
- Navigate to BILLING APPLICATION > BILLING > PERFORM BILL SENDING RUNS
- Either search for an existing one or from the Top Menu click on NEW
MAIN INFORMATION
Provide the related information
- Name
- Alternative Code
- Description
INPUT SETTINGS
- Define the required values
- Email: Select from the drop down list
- Communication Template: Quick Search or use modal search to find the communication template to be used
- Communication Queue External System: Quick Search or use modal search to find the communication template to be used
- Define the required values
CRITERIA
- Presentment Preferences:
- Click on ADD and select the preferences you would like to include from the dropdown
- Bills:
- Bills Filter Method: Select from the drop down the option that will filter the bills you would like to send
- Billing Run Filter Method: Select from the drop down list the option that will filter from which Billing Runs the Bills will be retrieved
- Included Billing Runs: If you have selected a specific option then
- Click on ADD and search for the desired billing Runs
- Click on ADD and search for the desired billing Runs
- Included Billing Runs: If you have selected a specific option then
- Segments
- For both Included and excluded segments the process is the same
- Click on ADD
Select from the drop down list the segments that will be used as conditions
Only BILL related segments will be loaded in the drop down lists.
- Presentment Preferences:
SCHEDULING SETTINGS
- Select from the available options according to what you would like to achieve
- RUN NOW: Will be executed once, now
- RUN ON SPECIFIC DATE/TIME: Will be executed once, at the date defined
- RUN REPEATEDLY: Will be executed, starting and ending at a defined date/time and will be repeated every X UOT where UOT can be from seconds to Years
- ADVANCED SCHEDULING: Will be executed, starting and ending at a defined date with powerful repetition options from daily to yearly
Run Now
Run On Specific Date / Time
- Start Process
- Click on the calendar select the date and time the run should start being executed.
- Once selected click on "DONE"
- Click on the calendar select the date and time the run should start being executed.
- Start Process
Run Repeatedly
- Start Process - On a Specific Date
- Click on the calendar select the date and time the run should start being executed.
- Once selected click on "DONE"
- OR Start process - After a period of time
- Provide how long after current date/time the process should begin
- Provide how long after current date/time the process should begin
- Repeat Process
- EVERY: Type a number (INTEGER)
- UOT: Select between
- Seconds
- Minutes
- Hours
- Days
- Weeks
- Months
- Years
- End Process
- Select between
- Never End
- On a specific date (define the date)
- After a period of time (define period of time)
- Select between
- Start Process - On a Specific Date
Advance Scheduling
- Start Process
- Click on the calendar select the date and time the run should start being executed.
- Once selected click on "DONE"
- Repeat Process
- Select between
- Daily : Define every how many days
- Weekly: Select specific days of the week
- Monthly:Define every how many months or on a specific day of the month
- Yearly: Define a specific date/month or a specific day of a month, such as the 1st Sunday of every January
- Select between
- End Process
- Select between
- Never End
- On a specific date (define the date)
- Select between
- Start Process
- Select from the available options according to what you would like to achieve
- From the Top Menu click on SAVE
LOG INFORMATION
Log information section keeps all the logging information related to the specific record
- Basic set of information available in all entities
- Created By User: The user that created the entity
- Created By Unit: The unit of the user that created the entity
- Updated By User: The user that last updated the entity
- Updated by Unit: The unit of the user that last updated the entity
- Date Created: The date the account was entity
- Date Updated: The date the account was last entity
- Basic set of information available in all entities
Executing a Bill Sending Run
- Navigate to the definition
- Search for the definition you would like to execute
- Click on the number of the definition to go to the data entry page
- Confirm that SCHEDULING SETTINGS are correctly configured
- From the Actions Menu click on ACTIONS > "SUBMIT"
- The job will be submitted to the scheduler and will become available under PROCESS RUNS
- Once completed the Life Cycle State will be changed from Draft to Completed
- If the Run fails then the Life Cycle State will be updated to Failed
- Check Process Successfully and Processed with Errors for a closer look of individual results
Modifying a Bill Sending Run
When you edit a definition that already has completed or scheduled runs then the system will automatically update the Version of the definition, by increasing its number by 1. Essentially, the system will create a new definition and will carry over all the information and configuration, apart from the Version number.
Accessing a definition with multiple versions, you will always see the latest version, while you have the option to View configuration and Runs of Previous versions by using th "VIEW PREVIOUS VERSIONS" link found in the Main Information tab
- Click on the VIEW PREVIOUS VERSIONS link
- Search from the modal for the version you would like to see
- Select the version
- The system will now show the configuration and the process runs of the version you have selected.
- To go back to the current version click on the CURRENT VERSION link under Main Information
Deleting a scheduled Bill Sending Run
If you have scheduled (submitted) a Run by mistake or you want to change the definition before execution, you have the option to delete the current job that was sent to the scheduler, given that it has not been executed yet. i.e., Life Cycle State is still Draft.
In order to delete the job follow the steps below:
- Navigate to the definition, for which you have scheduled a job
- Click on the number of the definition to move in the data entry page
- Go to Process Runs tab
- Find the job and check the left box next to the Run
- Click on "DELETE"
- A modal will open with the job information
- Click on "DELETE"
- Click "OK" on the confirmation message
- Close the modal
The job will be removed from the Process Runs
Changing the Life Cycle State of a Bill Sending Run Definition
Definitions Life Cycle State can be changed between Effective and Not Effective by following the steps below
- Go to the data entry page of the definition'
- If the definition's Life Cycle State is set to "Effective"
- From the Actions Menu click ACTIONS > SET AS NOT EFFECTIVE
- If the definition's Life Cycle State is set to "Not Effective"
- From the Actions Menu click ACTIONS > SET AS EFFECTIVE
- From the Actions Menu click ACTIONS > SET AS EFFECTIVE
Visit Understanding Bills for business examples related to Bill Sending Runs
Related Areas
-
Creating and Sending Bill Details Printout — Find out how to create and send a Bill Details Printout via email
-
Using Bill Sending Run Definitions — Learn to configure Bill Sending Run Definitions that will dictate overallbehaviorof Bill Sending Runs
-
Managing Bills — Learn to work with Bills
-
Understanding Bills — Understand the usage of Bills within CRM.COM
Popular Labels
- accounts-receivable
- accounts-receivable-admin
- accounts-receivable-advanced
- accounts-receivable-advanced-r7
- accounts-receivable-basics
- activities
- activities-admin
- activities-admin-r7
- activities-basics
- activities-basics-r7
- additive-discounts-admin
- additive-discounts-advanced
- additive-discounts-basics
- billing-application
- billing-engine
- communication-centre
- communications-admin-r7
- communications-advanced-r7
- conax-web-services
- conax-web-services-advanced
- contact-information-admin
- contact-information-admin-r7
- crm-application
- crm-application-r7
- customer-events-basics-r7
- dashboards
- dashboards-advanced
- finance-application
- financial-transactions-admin
- financial-transactions-admin-r7
- financial-transactions-advanced
- financial-transactions-advanced-r7
- foundation-application
- foundation-application-r7
- global
- inventory-management-advanced
- inventory-management-basics
- inventory-management-basics-r7
- jobs
- jobs-admin
- jobs-admin-r7
- jobs-advanced
- jobs-basics
- jobs-basics-r7
- leads
- leads-admin
- leads-admin-r7
- leads-advanced
- network-management-basics
- network-management-basics-r7
- normal-billing-admin-r7
- normal-billing-r7
- normal-billing-run-admin
- normal-billing-run-basics
- notifications
- notifications-basics
- panaccess_advanced
- platform-basics
- prepaid-billing-basics
- prepaid-billing-r7
- products-admin-r7
- rated-billing-items-advanced
- rated-billing-items-basics
- reports-basics
- resource-scheduling
- resource-scheduling-advanced
- rewards-admin
- rewards-admin-r7
- rewards-advanced
- rewards-advanced-r7
- rewards-basics
- rewards-basics-r7
- security-management-advanced
- segmentation-basics
- service-requests
- service-requests-admin
- service-requests-admin-r7
- service-requests-advanced
- service-requests-advanced-r7
- stripe
- subscription-actions-r7
- subscriptions
- subscriptions-advanced
- subscriptions-advanced-r7
- subscriptions-basics
- subscriptions-basics-r7
- udrs-admin-r7
- usage-service-r7
- user-management
- user-management-basics
- vouchers-advanced
- vouchers-basics
- wallets
- wallets-advanced
- wallets-basics
- warranty-policies-advanced-r7
- workflows-admin-r7
- workflows-advanced-r7
- workflows-r7
- zapier-basics-r7