Using Bill Sending Run Definitions

Owned by Persia Xenopoulou (Deactivated)
Last updated: Apr 20, 2017
5 min read

Back to Bills Main Page

Table of Contents

Navigating to Bill Sending Run Definitions

BILLING > BILLING > PERFORM BILL SENDING RUNS

WhatareBill Sending Run Definitions?

Bill Sending Run Definitions are used to determine the business rules applied in order to identify Bills that should be sent to customers directly by the System.

Run Definitions, must be submitted once created and will be executed once or on a recurring basis, based on the defined Scheduling Settings. Once a Definition is executed, a Process Run is logged and once the Run is completed, the information is available in the Process Runs tab.
The user has the option to delete the specific run as long as it is not yet executed (still in a 'Draft' state).
For a Definition to be submitted it needs to have an 'Effective' Life Cycle State. The Life Cycle State can be changed between 'Effective' and 'Not Effective' using the dedicated action.

  • Navigate to Bill Sending Run Definitions and explore existing records via the Summary page. 

  • Click on the link (name or number) of the record of your interest to access the Data Entry page and see more detail, or submit the Definition. 

  • Use the Actions Menu to create a NEW Definition or modify (EDIT) an existing one

  • Use BACK to return to the Summary page and CANCEL to revert any unwanted changes made to the Definition. 

Check the Validations & Restrictions Table below for a list of available Actions when working with Bill Sending Runs, including each Action's related validations and restrictions. View the Attributes Table for a comprehensive description of the Bill Sending Run fields.

BILL SENDING RUN DEFINITION

Validations & Restrictions

ActionValidationsRestrictionsAdditional Information
Create
  • Mandatory Fields must be defined
  • Name and Alternative Code must be unique
  • You cannot add the same segment in Included and Excluded segments criteria
  • NotApplicable
  • Not Applicable
Edit
  • Mandatory Fields must be defined
  • Name and Alternative Code must beunique
  • Not Applicable
  • If there is at least one scheduled Run using the same Definition, then a new Run Definition instance is created.  The new Definition will have the same values and Unified Code as the first one, an augmented version number and all the modified information.
Delete
  • Not Applicable
  • Bill Sending Run Definitions cannot be deleted
  • Not Applicable
Submit

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 that specified in the Presentment Preferences conditions
  • The Bill meets the Definition criteria
  • NotApplicable
  • Not Applicable

 

Attributes

An * indicates a field is mandatory 

Name

Description

Main Information

Name*

The name of the Definition
Alternative Code*The alternative code of the Definition
DescriptionA description of the Definition
Life Cycle StateThe state of the Definition which can be 'Effective' or 'Not effective'
Unified CodeAn auto-generated code which is used to group the various instances of each Bill Sending Run Definition
VersionAn auto-generated number which is used to specify the version of each Run Definition. If the version is already in use by a Run, a new Run Definition Version is created each time the Definition is edited.

"VIEW PREVIOUS VERSIONS" link allows you to search and view any previous versions of the Definition

Scheduled DateA Read-only field which is available once a Run is scheduled and designates the latest date that the Run is scheduled to be executed or has been executed

Logging Method

AVAILABLE FROM CRM.COM R12.0.0

Defines the method to be used for logging process run's results. Two options are available:

  • Log Processed Successfully and Processed with Errors: If selected, both entities successfully processed and failed ones will be logged in the Process Run Log.
  • Log Only Processed with Errors: If selected then only entities which failed to be processed will be logged in the Process Run Log.

Input Settings

Defines the Settings that will be used in order to create the Communications to send Bills

Communication Settings
Communication Media*

The media that will be used to communicate the Bills. The following media are supported:

  • Email: Applicable only if the Criteria>Presentment Preference Type is set to Email or one of the 'Custom' Types
  • SMS: Applicable only if the Criteria>Presentment Preference Type is set to SMS or one of the 'Custom' Types
  • Device: Applicable only if the Criteria>Presentment Preference Type is not set to Email or SMS
Communication Template*The 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.

Communication Queue External System*

Used to determine which external system will send the Communication.

Mandatory on Conditions: Mandatory if the Communication Template is set to 'Device' and optional for any other types of Communication Templates

AVAILABLE FROM CRM.COM R11.0.0 As fromR11.0.0 the queue external System is not available to be defined. It is only set by the System if one is specified on the selected Communication Template. 

Criteria

Bills

Defines the Criteria that will be used to retrieve the Bills to be sent

Bills Filter Method*

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 available:

  • Process Only Failed and Not Sent: Chose to retrieve only Bills which were already processed but rejected (i.e. the communication queue was rejected) or not processed yet
  • Process Only Failed: Chose to retrieve only Bills which were already processed but were rejected (i.e. the communication queue was rejected)
  • Process Only Not Sent: Chose to retrieve only Bills which have yet to be processed
Billing Run Filter Method*

Determines the method that will be used to filter the Bills. The available options are the following:

  • Bills Included in the Latest Normal Billing Run
  • Bills Included in Specific Billing Runs

Included Billing Runs *

 

A set of Normal Billing Runs that will be considered in order to retrieve the Bills to 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

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 available Types are:

  • Post
  • Email
  • SMS
  • F2F
  • Other
  • Custom (Types)

DEPRECATED FROM CRM.COM-R11.0.0 ONWARDS

Segment Criteria:

Determines the Criteria used to identify the Bills to be sent. At least one Segment must be specified from one of two sections (Included and Excluded)

Only Bill-related Segments will be loaded in the drop down lists.

 

Included Segments

A list of Segments which are used to filter Bills to be sent

Excluded Segments

A list of Segments which are used to exclude Bills

Process Runs
Process RunsDisplays the Runs that were executed for this Definition. Each Run includes the Bills that were processed. In case of an error, the error code and description are displayed
Scheduling Settings
Determines when the Definition will be executed after being submitted
Settings*Method - The following options are available:
  • Run Now
  • Run on Specific Date / Time
  • Run Repeatedly
  • Advanced Scheduling

Check out Scheduler Task - Global to find out how you can configure them

Log Information
Log DetailsThe standard set of Log Details information available in all entities  

View Understanding Bills for business examples related to Bill Sending Runs

Related Areas

Helpful Links