Appendix C: Jobs List

Category	Job Name	Description
Billing	Bill Print	Once invoice and statement details have been generated, they must be organised for printing by a third-party print bureau. The bureau will generate the bills according to the format and delivery preferences of individual subscriptions, for example email, print, or large font. The Bill Print job is responsible for organising the invoice and statement details into logical documents that correspond to the artefacts generated by the print bureau. The Bill Print job is part of the scheduled Billing process, which coordinates the activities of charge calculation, bill presentation and transmission. The Billing process is typically scheduled to run daily.
Billing	Invoice Posting	Once invoices have been generated, they must be posted to the sales (accounts receivable) ledger so that customer balances reflect the amounts due. These invoices also must be posted to the general (nominal) ledger to facilitate compilation of company accounts. This job is responsible for creating two batches: Sales Ledger Batch and General Ledger Batch. The Sales Ledger Batch contains a single record each for invoice with the invoice gross amount used to update the related account balance. The General Ledger Batch contains multiple records per invoice. The invoice taxable amount is broken down by tax rate and the invoice net amount is broken down by nominal code. Downstream daemons extract these batches, convert them to the required external system format and transmit them to the required destination. This job is part of the scheduled Billing process which coordinates the activities of charge calculation, bill presentation and transmission. The Billing process is typically scheduled to run daily.
Billing	Invoice Production	This job calculates charges (for example, monthly line rental, insurance and usage) and credits and applies discounts for selected subscriptions and accounts. Subscriptions are selected for invoicing if they are either due to be billed or have requested an off-cycle bill. Subscriptions are ignored from invoicing if they are not connected, have had their final invoice produced or have been explicitly excluded, pending review, from invoicing. The following types of invoices are produced FIRST: Produced shortly after subscription connection and includes only non-usage advance charges. NORMAL: The cyclical subscription invoice that contains both usage and non-usage charges. FINAL: Produced when the subscription has terminated and may result in a credit back to the subscription when changes have been paid in advance. This job is part of the scheduled Billing process, which coordinates the activities of charge calculation, bill presentation and transmission. The Billing process is typically scheduled to run daily.
Billing	Rated Charges	While CMP calculates the price of the majority of non-usage items that appear in an invoice, it is possible to include non-usage items whose price has already been calcualted by an external system. When CMP receives files containing rated charge records, these are automatically detected by a dedicated daemon which creates a rated charge batch in CMP for each file received. This job is responsible for performing the necessary updates in CMP to allow these charges to be available to the Billing process. This job is automatically triggered whenever a new rated charge batch has been created.
Billing	Statement Production	A statement in CMP is snapshot of the transactions ‐ invoices, adjustments and payments ‐ that have been posted to the sales ledger for a given account. A statement is not an invoice. An invoice has a tax aspect to it; whereas a statement consists of an opening balance, closing balance, amount in query and transactions on an account at a point in time. When this job produces a statement, it calculates an opening balance, closing balance and a list of transactions. An opening balance is derived from the last statement closing balance, if one existed; otherwise the opening balance is zero. The closing balance is the opening balance plus any charges this period. If there are open amounts in query on the account, these are excluded from the balance calculations. In a corporate scenario, CMP allows for suppression of statements at lower levels in a CMP hierarchy and for them to be consolidated at either corporate account or group account. This job is part of the scheduled Billing process that coordinates the activities of charge calculation, bill presentation and transmission. The Billing process is typically scheduled to run daily.
Billing	Usage Archiving	Every time a subscription uses their handset to make a call, send a text or browse the web, the network will record this activity and make the information available for collection, typically in batches. CMP receives many rated usage batches every day and over time the database will contain a large volume of usage records. In order to speed up access to unbilled usage during invoicing, billed and unbilled usage are separated by transferring usage details to the archive after they have been billed. This job creates a new rated usage archive and transfers newly invoiced usage into that archive. This job is part of the scheduled Billing process which coordinates the activities of charge calculation, bill presentation and transmission. The Billing process is typically scheduled to run daily.
Billing	Receipt Print	This job allows for an extract of prepaid bolt-ons to be produced for a print bureau. The bureau will then produce a receipt invoice that will allow the customer to claim back the tax paid. The job deals specifically with one-off bolt-ons that were purchased outside of CMP, i.e. those that do not appear on a post paid invoice. Each invocation of the job produces an audit of the prepaid bolt-ons that were included in the extract. This is a scheduled job.
Billing	General Ledger	A general ledger is a set of numbered accounts a business uses to keep track of its financial transactions and to prepare financial reports. Each account is a unique record summarizing each type of asset, liability, equity, revenue and expense. This job creates a batch detailing the daily breakdown of all payment, invoice, purchase and bond redemption information (along with an associated nominal code) for a particular calendar month. The job provides an additional breakdown for certain items e.g. recurring payments by payment type and invoices by tax rate. Downstream daemons extract these batches, convert them to the required external system format and transmit them to the required destination.
Bulk Action	Cross Structure Monitor	The Cross Structure Monitor Job checks the validity of organisational structure updates at different group, corporate and account levels.
Bulk Action	Edit Subscription	The Edit Subscription Job allows certain attributes of a Subscription to be changed in bulk. Inbound Excel files are uploaded for processing to CMP via the Bulk Action UI and converted by the Bulk Action Transformation Daemon to a CSV file, which is then loaded into CMP by a dedicated daemon.
Bulk Action	Manage Plan Tariff Change	This job allows for the change of price plan/tariff for multiple subscriptions.
Bulk Action	Manage Sales Ledger Adjustment	This job allows for the creation of sales ledger adjustments for multiple accounts.
Bulk Action	Manage Subscription Feature	This job allows for the enabling or disabling of features for multiple subscriptions.
Bulk Action	Manage Workflow	This job allows for the creation, processing and resolution of workflows for multiple subscriptions.
Bulk Action	Structure Expansion Monitor	The Structure Expansion Monitor job expands the Bulk Action Interface Batch Details to include all subscriptionsfor the organisation structure specified for group corporate, agreement, and/or account level.
Bulk Action	Workflow Resolution Monitor	The Workflow Resolution Monitor job is triggered once all primary workflows associated with a bulk action have ended. It updates the Report Status and Report Requested Timestamp to trigger the creation of a report and the sending of an email. It also updates the status of the bulk action to 'Completed' so that the job is not picked up again.
Comms	Advance Notifications	This job issues communications to subscriptions about upcoming events that are of interest to the subscriber, such as when credit/debit cards and contracts are due to expire or payments due to be taken. Job properties track when the last communication was issued to prevent sending the subscription multiple communications about the same thing. Each invocation of the job produces an audit of what type of communications were issued and to whom. The job would typically be scheduled to run at regular intervals.
Comms	Comms Email Monitor	Communications to customers are controlled by Communication (Comms) Requests, which are created in CMP via workflows or automatically on receipt of notifications from external systems. Email communications require additional processing to merge data gathered from CMP with document templates to generate the required document type. The Comms Monitor job gathers the data; the Comms Email Monitor job merges the data. The Comms Email Monitor job is triggered automatically when the Comms Monitor job has finished gathering data for Comms Requests relating to emails. This job uses external frameworks ‐ for example, Velocity and Prince XML ‐ to generate documents. Generated documents are subsequently detected by downstream daemons for transmission to the customer.
Comms	Comms Letter Monitor	Communications to customers are controlled by Communication (Comms) Requests, which are created in CMP via workflows or automatically on receipt of notifications from external systems. Letter communications require additional processing to merge data gathered from CMP with document templates to generate the required document type. The Comms Monitor job gathers the data; the Comms Letter Monitor job merges the data. The Comms Letter Monitor job is triggered automatically when the Comms Monitor job has finished gathering data for Comms Requests relating to letters. This job uses external frameworks ‐ for example, Velocity and Prince XML ‐ to generate documents. Generated documents are subsequently detected by downstream daemons for transmission to the customer.
Comms	Comms Monitor	CMP supports sending communication directly to customers (by letter, email, text, SMS, or push notifications) and indirectly (third party or online account). Communication to customers is controlled by Communication (Comms) Requests, which are created in CMP via workflows or automatically upon receipt of notifications from external systems. The Comms Monitor job is triggered automatically when new Comms Requests are generated. This job gathers the details to be included in each individual communication and determines the delivery mechanism, destination and delivery time. Downstream jobs and daemons monitor the output of this job. For example, the Comms Letter Monitor job merges the details with document templates and dedicated daemons distribute communications to the appropriate third parties.
Comms	Notification Monitor	Third parties, for example an Online Charging System (OCS) can generate notifications that may of interest to CMP and cause it to send a communication (Comms) to a subscription. This job converts notifications received from external systems into Comms Requests, which are the main avenue for generating Comms in CMP. Depending on configuration, this job may also raise a workflow instead of or in addition to the Comms Request. This job is triggered automatically when a notification is created.
Credit Management	Credit Control	When subscription invoices are produced, payment is generally required within a configurable number of days from the date of invoice. If payment is not made within this timeframe, the subscription usually enters a credit control procedure. These procedures typically involve generating reminders to pay and usually applying a service bar if payment is not forthcoming. The Credit Control job checks for accounts newly in arrears, existing arrears that need to be escalated and accounts in credit control that have payed and thus must be taken out of the credit control process. This job is a scheduled job and typically runs daily.
Credit Management	Credit Control Monitor	If an invoice has not been paid within the configured timeframe, the account usually enters a credit control procedure, which can include reminders and service bars. The Credit Control Monitor job evaluates accounts that are in credit control to determine whether the conditions for them to exit credit control have been met. The job is triggered only when the following are made against an account in credit control: • An Add or Edit of an Amount in Query • A non-recurring payment • A sales ledger adjustment • A payment recorded in CMP using the Record One Off Payment Web Service When one of these actions is performed and the account meets the criteria for exiting credit control, this job removes the account from credit control and reverses any service bars.
Credit Management	Credit Reference	A Credit Reference Agency (CRA) is an organisation that collects information to determine peoples’ credit ratings. CRAs then make this information available to organisations providing credit, such as banks and credit card, loan and finance companies. This job allows an extract of customer data to be generated and sent to such an organisation. All postpaid accounts in CMP can be included in the extract, but certain accounts, for example V.I.P accounts, can be manually excluded. In addition, once the CRA has been notified that an account has reached a certain state (for example, account holder deceased, or debt settled), that account is excluded from all subsequent extracts. This is a scheduled job and typically runs once per month.
Credit Management	Debt Recovery	After an account has been through the credit control process and the operator is still unable to recover the unpaid debt, the collection of that debt can be assigned to a third party known as a Debt Recovery Agency (DRA). This job is responsible for generating a batch that includes accounts to be referred to a DRA. The batch includes details of the debts be recovered and customer contact information. This is a scheduled job and typically runs once a month.
Credit Management	Debt Recovery Response	After an account has been through the credit control process and the operator is still unable to recover the unpaid debt, the collection of that debt can be assigned to a third party known as a Debt Recovery Agency (DRA). The DRA can provide feedback such as amount recovered and/or payment plans. When CMP receives debt recovery response files, these are automatically detected by a dedicated daemon that creates a debt recovery response batch for each file received. This job is responsible for updating account details to reflect the debt recovery progress. This job is automatically triggered whenever a new debt recovery response batch has been created.
Data Warehouse	Account Analytics	This job allows for accounts to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality.
Data Warehouse	Agreement Analytics	This job allows for agreements to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Each invocation of the job produces an audit outlining the number of usage records that were included in the extract. Typically, this a scheduled and run daily.
Data Warehouse	Billed Usage Analytics	This job extracts billed usage information and makes it available for a third party to analyse . Each invocation of the job produces an audit that outlines the billed usage records that were included in the extract as well as the extract file itself.
Data Warehouse	Hierarchy Analytics	CMP allows for information to be extracted from its database and made available for third party analysis. Hierarchy information changes over time, for example subscriptions can move to different accounts, or accounts to a different corporate. While CMP stores only the current hierarchy, it is important that a historical view of the hierarchy is also available. This job gathers the customer hierarchy information (subscription, account, corporate and group) that was in effect at the time of the most recent billing process. This job is typically scheduled to run once per day after a billing process.
Data Warehouse	Invoice Analytics	CMP allows for information to be extracted from its database and made available for third party analysis. This job gathers details of invoices generated during the most recent billing process. This job is typically scheduled to run once per day after a billing process.
Data Warehouse	Invoice Detail Analytics	This job allows for invoice detail information to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Typically, this a scheduled and run daily.
Data Warehouse	Payment Detail Analytics	This job allows for payment information to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality.
Data Warehouse	Purchase Analytics	This job extracts package purchase information makes it available for a third party to analyse. Each invocation of the job produces an audit outlining the purchase records that were included in the extract.Typically, this job would be on a schedule and run daily.
Data Warehouse	Statement Analytics	The Statement Analytics job extracts statement details and writes the information extracted to a CSV file, which can then be encrypted based on the encryption requirements configured. The job can run in both Full mode and Partial mode.
Data Warehouse	Subscription Analytics	This job allows for subscription information to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Each invocation of the job produces an audit outlining the subscription records that were included in the extract. Typically, this job would be on a schedule and run daily.
Data Warehouse	Subscription Feature Analytics	This job allows for subscription feature information to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Each invocation of the job produces an audit outlining the subscription service records that were included in the extract. Typically, this job would be on a schedule and run daily.
Data Warehouse	Subscription Service Analytics	This job allows for subscription service information to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Each invocation of the job produces an audit outlining the subscription service records that were included in the extract. Typically, this job would be on a schedule and run daily.
Data Warehouse	Transaction Detail Analytics	This job allows for sales ledger transaction information to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Each invocation of the job produces an audit outlining the transaction records that were included in the extract. Typically, this job would be on a schedule and run daily.
Data Warehouse	Unallocated Usage Analytics	This job allows for unallocated usage information to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Typically, this job would be on a schedule and run daily.
Data Warehouse	Unbilled Usage Analytics	This job allows for unbilled usage to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Each invocation of the job produces an audit outlining the number of usage records that were included in the extract. Typically, this a scheduled and run daily.
Device Enrolment	Device Enrolment Request	After device information has been loaded into CMP as part of an Order Dispatch Response, it may be necessary to send the device information to the Device Enrolment Provider in order to perform Device Enrolment Provisioning. This job identifies sales orders that require device enrolment and prepares batches for sending these instructions to the Device Enrolment Provider. This job also handles requests for device unenrolment, for which they send a request with a type of RE(Return).
Device Enrolment	Device Enrolment Response	This job processes a response from the Device Enrolment Provider for a Device Enrolment Request and updates CMP with the outcome.
External Data	External Reference Upload	Some customers may require external references to be mapped to CMP entities such as invoice numbers, subscription numbers and account numbers. This job loads the external numbers and the CMP entities with which they are associated into the CMP database. Each invocation of the job produces an audit outlining the external references that were loaded. This is a triggered job.
Ledger	Ledger Monitor	The Sales Ledger is record of sales, whether or not payment has been received and how much is owed. Various CMP processes create records in the Sales Ledger, for example to record the generation of new invoices, the receipt of a payments or the reversal of payments. These records have no impact on the balance of an account until they have been posted ‐ that is, validated and processed ‐ by this job. This job matches transactions (for example, payments to invoices), updates the open amount of matched transactions and maintains an audit of all changes to transaction open amounts. Once a record has been processed successfully, its status is updated and only then impacts on the related account balance. A sales ledger record is validated and processed only once. However, a successfully processed record can have its open amount subsequently modified by new transactions. This job is automatically triggered when new records have been created in the CMP Sales Ledger.
Number Management	Managed Number Monitor	Numbers in the CMP managed serial number repository can be configured so that they cannot be used or reused before or after a particular date. This job checks the managed number repository to determine the appropriate status of available numbers. Managed serial numbers that are not assigned to a subscription are expired if the Use By date of the number has been exceeded. Previously used numbers that are eligible for reassignment (numbers in a cooling-off state that have reached their allowed re-use date) are reverted to a Not Allocated state, which allows these to be re-used for connections and number changes.
Number Management	Managed Numbers	When subscriptions are created in CMP, up to five managed serial numbers can be assigned to an individual subscription. The first three numbers typically represent a Mobile/MSISDN number, a SIM number and an IMEI number, but this is configurable per implementation. The repository of available managed numbers is populated by uploading files containing individual numbers or ranges of numbers. Each file contains only one type of number. These numbers can be restricted to particular accounts or sales people. Optionally, a charge can be associated with a number which is applied on subscription creation or number change. A charge is typically applied to numbers that contain many repeating digits and are thus deemed more valuable. When CMP receives files containing serial numbers, these are automatically detected by a dedicated daemon, which creates a serial number batch in CMP for each file received. This job creates a record in the CMP managed serial number repository for each number in the uploaded batch. If a number range has been supplied, a record for each number in the range is created in the repository and, if applicable, each number in a particular range is assigned the same charge and account or salesperson. This job is automatically triggered whenever a new serial number batch has been created.
Number Management	SIM Profiles	A SIM profile - or SIM card - is an integrated circuit that is intended to securely store International Mobile Subscriber Identity (IMSI) details, which are used to identify and authenticate subscriptions on mobile telephony devices such as mobile phones or laptops. The SIM card has its own unique reference known as an Integrated Circuit Card Identifier (ICCID), which cannot be changed. CMP allows for a primary and secondary profile to be stored for a given ICCID. When CMP receives files containing SIM profiles records, these are automatically detected by a dedicated daemon which creates a SIM Profile batch in CMP for each file received. This job loads the SIM Profiles into CMP for use by provisioning jobs and for resolving agent queries, for example a customer contacting the call centre to request a Personal Unlocking Key (PUK) to unlock their phone. This job is automatically triggered whenever a new SIM Profile batch has been created.
Payments	Mandate Registrations	A direct debit is an instruction from a customer (debtor) to their bank or payment services provider, authorising an organisation (creditor) to collect variable or fixed amounts from their account, providing the customer is given notice of the collection amounts and dates. This job is responsible for generating a batch of new direct debit instructions for transmission to external systems, which in turn transfer these instructions to the paying banks and building societies. Downstream daemons extract this batch, convert the instructions to the required external system format and transmit them to the required destination. This job is typically scheduled to run once per day, excluding non-banking days.
Payments	Mandate Revisions	When new direct debit instructions are sent to an external payments system, some instructions can fail, for example, due to incorrect bank details. Successful instructions may also subsequently be amended or cancelled by the customer. When CMP receives files containing rejected, amended or cancelled instructions, these are automatically detected by a dedicated daemon, which creates a mandate revisions batch in CMP for each file received. This job updates or cancels the relevant mandate records in CMP. Cancellation in CMP typically involves reverting the account to a manual payment type, which often involves charging an administration fee. This job is automatically triggered whenever a new mandate revisions batch has been created.
Payments	Non Recurring Payments	Non-recurring payments occur when, rather than opting to pay their bill automatically each month, a subscription chooses to pay on their own terms, a payment by cash, for example. Records of these payments must be loaded into CMP and reconciled against the subscription’s account. When CMP receives non-recurring payment files, these are automatically detected by a dedicated daemon, which creates a non-recurring payments batch in CMP for each file received. This job is matches payments to accounts and creates a batch to post the payments to the Sales Ledger. Once the posting batch has been created, it is detected by dedicated daemons that format the batch and transmit the payment information to the target sales ledger. This job is automatically triggered whenever a non-recurring payments batch has been created.
Payments	Recurring Payments Rejections	When recurring payment and refund transactions are sent to an external payment system, some transactions can fail, for example due to insufficient funds or lost and stolen cards. These rejected transactions must be processed by CMP. When CMP receives files containing rejected transactions, these are automatically detected by a dedicated daemon, which creates a rejected payment batch in CMP for each file received. This job generates a batch that contains records to reverse each failed transaction from the sales ledger. Once this batch has been created, it is detected by dedicated daemons that format the batch and transmit it to the target sales ledger. This job also generates workflows (for example, to send a communication to the customer), processes soft declines to temporarily exclude the account from the automated payment process and processes hard declines to revert the account to the default (manual) payment to make alternative arrangements for collection of amounts due. This job is automatically triggered whenever a new rejected payment batch has been created
Payments	Recurring Payments	Customers can opt to pay their bills automatically, a defined number of days after the bill date, based on their payment terms. Automatic payment methods include direct debit and credit/debit cards. This job creates a batch of payment and refund records that are due for settlement. Once this batch has been created, it is detected by dedicated daemons that format the batch and transmit it to the appropriate external payments system. This job runs in two modes to distinguish between direct debit transactions and credit/debit card transactions. This job also creates a second batch to post the extracted payments and refunds to the sales ledger. Once this batch has been created, it is detected by dedicated daemons that format the batch and transmit it to the target sales ledger. This job is typically scheduled to run daily
Payments	Recurring Pre Payments	This job creates a batch of payments that are due for settlement. Once this batch has been created, it is detected by dedicated daemons that format the batch and transmit it to the appropriate external payments system. This job runs in two modes - Card or Balance - to distinguish between balance transactions and credit/debit card transactions. Each invocation of the job produces an audit of the accounts that were included in the extract. This is a scheduled job.
Payments	Recurring Pre Payments Rejections	Dedicated daemons detect files containing details of rejected payments and load those details into CMP. This job detects batches of rejected payments and for each rejected payment, the status of the payment is updated, the associated package allowances are expired and a Comms is generated to inform the customer of the rejected payment.
Provisioning	Provisioning	Provisioning actions, initiated via the creation of workflow events, progress to a status of Awaiting Network Services as the Workflow Monitor job processes the relevant workflows. This job detects the provisioning actions and, when appropriate, writes to a Network Request table, which is monitored by daemons responsible for generating a target-specific command and transmitting the command to the external system.
Provisioning	Bill Cycle Change	In a real-time charging (RTC) environment, when a post-paid subscription's bill cycle day is changed, the external RTC system creates new allowance and spend cap records that take effect at the start of the subscription's new bill cycle. These new records must be synchronised with CMP records in order to allow for real-time enquiry of allowance and spend cap balances from CMP. Following a bill cycle change, new records generated by the RTC system are stored in CMP. When the new records are due to come into effect, this job is triggered to update CMP allowance and spend cap records to refer to the new records.
Purge	Account Purge	Under data protection legislation, an organisation must not retain customer data any longer than necessary. This job removes personal customer information, such as contact names or account passwords, for accounts that are no longer in use. This job does not delete records. Instead, it obfuscates personal data elements using asterisks for character values or zeros for numeric values. This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. Only data from accounts changed on or before the calculated purge date will be obfuscated. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions will be sufficient.
Purge	Address Purge	Under data protection legislation, an organisation must not retain customer data any longer than is necessary. This job removes address information that is no longer in use; that is, there is no longer a reference to the address in any table in CMP. There is no input parameter for this job; an address is simply in use or it is not. No archiving takes place prior to the deletion of the records. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions of this job will be sufficient.
Purge	Consumer Purge	This job removes personal customer information, such as contact names or account passwords for terminated single subscription accounts. The job deletes records where possible and obfuscates data where it is not possible to delete records. Certain data cannot be deleted (e.g. usage) as legally there is a requirement for store this a certain period of time. This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. The calculated purge date is worked out by deducting this number of months from the current date. This parameter is optional. If you do not provide a value, a default value of six month is used. Only subscriptions who have terminated on or before the calculated purge date will be considered by the job. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions will be sufficient.
Purge	Direct Debit Purge	Under data protection legislation, an organisation must not retain customer data any longer than is necessary. This job removes direct debit information that is no longer in use, that is, cancelled. This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. Only data from accounts created on or before the calculated purge date will be removed and no archiving takes place prior to the deletion of data. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions of this job will be sufficient.
Purge	Payment Card Purge	Under data protection legislation, an organisation must not retain customer data any longer than is necessary. This job removes credit and debit card information that is no longer in use, that is, cancelled cards. This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. Only data from accounts created on or before the calculated purge date will be removed and no archiving takes place prior to the deletion of data. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions of this job will be sufficient.
Purge	Refund Purge	Under data protection legislation, an organisation must not retain customer data any longer than is necessary. This job removes refund information that is no longer in use, that is, those refunds with a status of cancelled, complete or rejected. This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. Only data from accounts created on or before the calculated purge date will be removed and no archiving takes place prior to the deletion of data. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions of this job will be sufficient.
Usage	Rated Usage	Every time a subscription uses their handset to make a call, send a text or browse the web, the network records this activity and makes the information available for collection, typically in batches. When CMP receives files containing rated usage records, these are automatically detected by a dedicated daemon, which creates a rated usage batch in CMP for each file received. This job processes rated usage batches to include these records in a detailed bill of a subscription. This job does not perform any usage rating itself; usage is already priced when it arrives in CMP. This job is designed to work in conjunction with a network that supports a real time engine that rates the usage as it happens. This job is automatically triggered whenever a new rated usage batch has been created.
Usage Reconciliation	Usage Aggregation	This job aggregates of both rated and wholesale usage records. It groups usage records by usage date, type, origin and destination and calculates totals for usage charges and usage units for each of these groups. It creates a usage reconciliation record for each usage group.
Usage Reconciliation	Usage Reconciliation	This job reconciles retail and wholesale usage records. It collects aggregated usage records between the dates specified in the job parameters for both retail and wholesale usage. The job then compares the records are against each other and calculates variances between usage charges, units and number of events. It exports the results of the reconciliation as a CSV file. A daemon transports the CSV file to storage.
Utility	Batch Error Management	When CMP is receiving json files (e.g. rated usage, rated charges etc) , the jobs that process these are triggered automatically by the presence of a record on the Interface Batch Header table with a stage of 'Extract/Load' and stage status of 'Complete' If the jobs are able to process all the data in these files, the stage and stage status will be set to 'Batch' and 'Complete'. If the jobs are unable to process some records due to missing CMP configuration, the stage and stage status will be set to 'Batch' and 'Error'. Batch Error Management job is an automated approach to reprocess individual batches in the event there are large numbers of files to reprocess once the missing configuration has been rectified.
Utility	Data Fix	This job allows operators to run pre-packaged SQL to resolve issues with data records in the CMP database. Each pre-packaged SQL contains three distinct elements: Verification SQL - to identify the records to be fixed. Execution SQL - to fix the records. Validation SQL - to verify that the fix executed as intended. The pre-packaged SQL has a unique data fix identifier and this is passed to the job as a parameter. This job would normally run from a scheduler for a specific data fix identifier
Workflow	Action Monitor	Customer requests to add or change service features often require interaction with a third-party network. The network actions, such as connections, disconnections and tariff changes, that are initiated by the processing of workflows are communicated to the appropriate network by the CMP Network Interfaces Framework (NIF). A success/failure response is sent back to CMP. The NIF collects and interprets the responses and updates CMP with the results. The Action Monitor job is triggered automatically when the results become available. The job updates subscription attributes and statuses based on the results. For a successful network action, it updates subscription attributes depending on the type of action, for example updating a connection or disconnection date. For an unsuccessful action, it updates the status of the subscription to reflect the type of network activity that has failed.
Workflow	Workflow Monitor	Workflows events are created by processes to initiate configured activities known as actions. Actions include: change of account type; application of a service (charge) to a subscription; initiation of network command generation and initiation of customer communication generation. Once a workflow has been created, it remains in a Pending state until it has been processed by this job on the requested date/time. When a workflow is processed, account type changes and subscription service actions are applied in full immediately. Network commands and communication generation actions involve initiating further downstream processing. Once processed, the status of the workflow is updated to indicate success, error or pending network activity. This job is automatically triggered when workflow records in a pending state that are due for processing are detected. These workflows are processed in order of priority.

Billing

Bill Print

Once invoice and statement details have been generated, they must be organised for printing by a third-party print bureau. The bureau will generate the bills according to the format and delivery preferences of individual subscriptions, for example email, print, or large font. The Bill Print job is responsible for organising the invoice and statement details into logical documents that correspond to the artefacts generated by the print bureau. The Bill Print job is part of the scheduled Billing process, which coordinates the activities of charge calculation, bill presentation and transmission. The Billing process is typically scheduled to run daily.

Billing

Invoice Posting

Once invoices have been generated, they must be posted to the sales (accounts receivable) ledger so that customer balances reflect the amounts due. These invoices also must be posted to the general (nominal) ledger to facilitate compilation of company accounts. This job is responsible for creating two batches: Sales Ledger Batch and General Ledger Batch. The Sales Ledger Batch contains a single record each for invoice with the invoice gross amount used to update the related account balance. The General Ledger Batch contains multiple records per invoice. The invoice taxable amount is broken down by tax rate and the invoice net amount is broken down by nominal code. Downstream daemons extract these batches, convert them to the required external system format and transmit them to the required destination. This job is part of the scheduled Billing process which coordinates the activities of charge calculation, bill presentation and transmission. The Billing process is typically scheduled to run daily.

Billing

Invoice Production

This job calculates charges (for example, monthly line rental, insurance and usage) and credits and applies discounts for selected subscriptions and accounts. Subscriptions are selected for invoicing if they are either due to be billed or have requested an off-cycle bill. Subscriptions are ignored from invoicing if they are not connected, have had their final invoice produced or have been explicitly excluded, pending review, from invoicing. The following types of invoices are produced FIRST: Produced shortly after subscription connection and includes only non-usage advance charges. NORMAL: The cyclical subscription invoice that contains both usage and non-usage charges. FINAL: Produced when the subscription has terminated and may result in a credit back to the subscription when changes have been paid in advance. This job is part of the scheduled Billing process, which coordinates the activities of charge calculation, bill presentation and transmission. The Billing process is typically scheduled to run daily.

Billing

Rated Charges

While CMP calculates the price of the majority of non-usage items that appear in an invoice, it is possible to include non-usage items whose price has already been calcualted by an external system. When CMP receives files containing rated charge records, these are automatically detected by a dedicated daemon which creates a rated charge batch in CMP for each file received. This job is responsible for performing the necessary updates in CMP to allow these charges to be available to the Billing process. This job is automatically triggered whenever a new rated charge batch has been created.

Billing

Statement Production

A statement in CMP is snapshot of the transactions ‐ invoices, adjustments and payments ‐ that have been posted to the sales ledger for a given account. A statement is not an invoice. An invoice has a tax aspect to it; whereas a statement consists of an opening balance, closing balance, amount in query and transactions on an account at a point in time. When this job produces a statement, it calculates an opening balance, closing balance and a list of transactions. An opening balance is derived from the last statement closing balance, if one existed; otherwise the opening balance is zero. The closing balance is the opening balance plus any charges this period. If there are open amounts in query on the account, these are excluded from the balance calculations. In a corporate scenario, CMP allows for suppression of statements at lower levels in a CMP hierarchy and for them to be consolidated at either corporate account or group account. This job is part of the scheduled Billing process that coordinates the activities of charge calculation, bill presentation and transmission. The Billing process is typically scheduled to run daily.

Billing

Usage Archiving

Every time a subscription uses their handset to make a call, send a text or browse the web, the network will record this activity and make the information available for collection, typically in batches. CMP receives many rated usage batches every day and over time the database will contain a large volume of usage records. In order to speed up access to unbilled usage during invoicing, billed and unbilled usage are separated by transferring usage details to the archive after they have been billed. This job creates a new rated usage archive and transfers newly invoiced usage into that archive. This job is part of the scheduled Billing process which coordinates the activities of charge calculation, bill presentation and transmission. The Billing process is typically scheduled to run daily.

Billing

Receipt Print

This job allows for an extract of prepaid bolt-ons to be produced for a print bureau. The bureau will then produce a receipt invoice that will allow the customer to claim back the tax paid. The job deals specifically with one-off bolt-ons that were purchased outside of CMP, i.e. those that do not appear on a post paid invoice. Each invocation of the job produces an audit of the prepaid bolt-ons that were included in the extract. This is a scheduled job.

Billing

General Ledger

A general ledger is a set of numbered accounts a business uses to keep track of its financial transactions and to prepare financial reports. Each account is a unique record summarizing each type of asset, liability, equity, revenue and expense. This job creates a batch detailing the daily breakdown of all payment, invoice, purchase and bond redemption information (along with an associated nominal code) for a particular calendar month. The job provides an additional breakdown for certain items e.g. recurring payments by payment type and invoices by tax rate. Downstream daemons extract these batches, convert them to the required external system format and transmit them to the required destination.

Bulk Action

Cross Structure Monitor

The Cross Structure Monitor Job checks the validity of organisational structure updates at different group, corporate and account levels.

Bulk Action

Edit Subscription

The Edit Subscription Job allows certain attributes of a Subscription to be changed in bulk. Inbound Excel files are uploaded for processing to CMP via the Bulk Action UI and converted by the Bulk Action Transformation Daemon to a CSV file, which is then loaded into CMP by a dedicated daemon.

Bulk Action

Manage Plan Tariff Change

This job allows for the change of price plan/tariff for multiple subscriptions.

Bulk Action

Manage Sales Ledger Adjustment

This job allows for the creation of sales ledger adjustments for multiple accounts.

Bulk Action

Manage Subscription Feature

This job allows for the enabling or disabling of features for multiple subscriptions.

Bulk Action

Manage Workflow

This job allows for the creation, processing and resolution of workflows for multiple subscriptions.

Bulk Action

Structure Expansion Monitor

The Structure Expansion Monitor job expands the Bulk Action Interface Batch Details to include all subscriptionsfor the organisation structure specified for group corporate, agreement, and/or account level.

Bulk Action

Workflow Resolution Monitor

The Workflow Resolution Monitor job is triggered once all primary workflows associated with a bulk action have ended. It updates the Report Status and Report Requested Timestamp to trigger the creation of a report and the sending of an email. It also updates the status of the bulk action to 'Completed' so that the job is not picked up again.

Comms

Advance Notifications

This job issues communications to subscriptions about upcoming events that are of interest to the subscriber, such as when credit/debit cards and contracts are due to expire or payments due to be taken. Job properties track when the last communication was issued to prevent sending the subscription multiple communications about the same thing. Each invocation of the job produces an audit of what type of communications were issued and to whom. The job would typically be scheduled to run at regular intervals.

Comms

Comms Email Monitor

Communications to customers are controlled by Communication (Comms) Requests, which are created in CMP via workflows or automatically on receipt of notifications from external systems. Email communications require additional processing to merge data gathered from CMP with document templates to generate the required document type. The Comms Monitor job gathers the data; the Comms Email Monitor job merges the data. The Comms Email Monitor job is triggered automatically when the Comms Monitor job has finished gathering data for Comms Requests relating to emails. This job uses external frameworks ‐ for example, Velocity and Prince XML ‐ to generate documents. Generated documents are subsequently detected by downstream daemons for transmission to the customer.

Comms

Comms Letter Monitor

Communications to customers are controlled by Communication (Comms) Requests, which are created in CMP via workflows or automatically on receipt of notifications from external systems. Letter communications require additional processing to merge data gathered from CMP with document templates to generate the required document type. The Comms Monitor job gathers the data; the Comms Letter Monitor job merges the data. The Comms Letter Monitor job is triggered automatically when the Comms Monitor job has finished gathering data for Comms Requests relating to letters. This job uses external frameworks ‐ for example, Velocity and Prince XML ‐ to generate documents. Generated documents are subsequently detected by downstream daemons for transmission to the customer.

Comms

Comms Monitor

CMP supports sending communication directly to customers (by letter, email, text, SMS, or push notifications) and indirectly (third party or online account). Communication to customers is controlled by Communication (Comms) Requests, which are created in CMP via workflows or automatically upon receipt of notifications from external systems. The Comms Monitor job is triggered automatically when new Comms Requests are generated. This job gathers the details to be included in each individual communication and determines the delivery mechanism, destination and delivery time. Downstream jobs and daemons monitor the output of this job. For example, the Comms Letter Monitor job merges the details with document templates and dedicated daemons distribute communications to the appropriate third parties.

Comms

Notification Monitor

Third parties, for example an Online Charging System (OCS) can generate notifications that may of interest to CMP and cause it to send a communication (Comms) to a subscription. This job converts notifications received from external systems into Comms Requests, which are the main avenue for generating Comms in CMP. Depending on configuration, this job may also raise a workflow instead of or in addition to the Comms Request. This job is triggered automatically when a notification is created.

Credit Management

Credit Control

When subscription invoices are produced, payment is generally required within a configurable number of days from the date of invoice. If payment is not made within this timeframe, the subscription usually enters a credit control procedure. These procedures typically involve generating reminders to pay and usually applying a service bar if payment is not forthcoming. The Credit Control job checks for accounts newly in arrears, existing arrears that need to be escalated and accounts in credit control that have payed and thus must be taken out of the credit control process. This job is a scheduled job and typically runs daily.

Credit Management

Credit Control Monitor

If an invoice has not been paid within the configured timeframe, the account usually enters a credit control procedure, which can include reminders and service bars. The Credit Control Monitor job evaluates accounts that are in credit control to determine whether the conditions for them to exit credit control have been met. The job is triggered only when the following are made against an account in credit control: • An Add or Edit of an Amount in Query • A non-recurring payment • A sales ledger adjustment • A payment recorded in CMP using the Record One Off Payment Web Service When one of these actions is performed and the account meets the criteria for exiting credit control, this job removes the account from credit control and reverses any service bars.

Credit Management

Credit Reference

A Credit Reference Agency (CRA) is an organisation that collects information to determine peoples’ credit ratings. CRAs then make this information available to organisations providing credit, such as banks and credit card, loan and finance companies. This job allows an extract of customer data to be generated and sent to such an organisation. All postpaid accounts in CMP can be included in the extract, but certain accounts, for example V.I.P accounts, can be manually excluded. In addition, once the CRA has been notified that an account has reached a certain state (for example, account holder deceased, or debt settled), that account is excluded from all subsequent extracts. This is a scheduled job and typically runs once per month.

Credit Management

Debt Recovery

After an account has been through the credit control process and the operator is still unable to recover the unpaid debt, the collection of that debt can be assigned to a third party known as a Debt Recovery Agency (DRA). This job is responsible for generating a batch that includes accounts to be referred to a DRA. The batch includes details of the debts be recovered and customer contact information. This is a scheduled job and typically runs once a month.

Credit Management

Debt Recovery Response

After an account has been through the credit control process and the operator is still unable to recover the unpaid debt, the collection of that debt can be assigned to a third party known as a Debt Recovery Agency (DRA). The DRA can provide feedback such as amount recovered and/or payment plans. When CMP receives debt recovery response files, these are automatically detected by a dedicated daemon that creates a debt recovery response batch for each file received. This job is responsible for updating account details to reflect the debt recovery progress. This job is automatically triggered whenever a new debt recovery response batch has been created.

Data Warehouse

Account Analytics

This job allows for accounts to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality.

Data Warehouse

Agreement Analytics

This job allows for agreements to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Each invocation of the job produces an audit outlining the number of usage records that were included in the extract. Typically, this a scheduled and run daily.

Data Warehouse

Billed Usage Analytics

This job extracts billed usage information and makes it available for a third party to analyse . Each invocation of the job produces an audit that outlines the billed usage records that were included in the extract as well as the extract file itself.

Data Warehouse

Hierarchy Analytics

CMP allows for information to be extracted from its database and made available for third party analysis. Hierarchy information changes over time, for example subscriptions can move to different accounts, or accounts to a different corporate. While CMP stores only the current hierarchy, it is important that a historical view of the hierarchy is also available. This job gathers the customer hierarchy information (subscription, account, corporate and group) that was in effect at the time of the most recent billing process. This job is typically scheduled to run once per day after a billing process.

Data Warehouse

Invoice Analytics

CMP allows for information to be extracted from its database and made available for third party analysis. This job gathers details of invoices generated during the most recent billing process. This job is typically scheduled to run once per day after a billing process.

Data Warehouse

Invoice Detail Analytics

This job allows for invoice detail information to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Typically, this a scheduled and run daily.

Data Warehouse

Payment Detail Analytics

This job allows for payment information to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality.

Data Warehouse

Purchase Analytics

This job extracts package purchase information makes it available for a third party to analyse. Each invocation of the job produces an audit outlining the purchase records that were included in the extract.Typically, this job would be on a schedule and run daily.

Data Warehouse

Statement Analytics

The Statement Analytics job extracts statement details and writes the information extracted to a CSV file, which can then be encrypted based on the encryption requirements configured. The job can run in both Full mode and Partial mode.

Data Warehouse

Subscription Analytics

This job allows for subscription information to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Each invocation of the job produces an audit outlining the subscription records that were included in the extract. Typically, this job would be on a schedule and run daily.

Data Warehouse

Subscription Feature Analytics

This job allows for subscription feature information to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Each invocation of the job produces an audit outlining the subscription service records that were included in the extract. Typically, this job would be on a schedule and run daily.

Data Warehouse

Subscription Service Analytics

This job allows for subscription service information to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Each invocation of the job produces an audit outlining the subscription service records that were included in the extract. Typically, this job would be on a schedule and run daily.

Data Warehouse

Transaction Detail Analytics

This job allows for sales ledger transaction information to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Each invocation of the job produces an audit outlining the transaction records that were included in the extract. Typically, this job would be on a schedule and run daily.

Data Warehouse

Unallocated Usage Analytics

This job allows for unallocated usage information to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Typically, this job would be on a schedule and run daily.

Data Warehouse

Unbilled Usage Analytics

This job allows for unbilled usage to be extracted and made available for a third party to analyse. It is part of the Data Warehouse suite of functionality. Each invocation of the job produces an audit outlining the number of usage records that were included in the extract. Typically, this a scheduled and run daily.

Device Enrolment

Device Enrolment Request

After device information has been loaded into CMP as part of an Order Dispatch Response, it may be necessary to send the device information to the Device Enrolment Provider in order to perform Device Enrolment Provisioning. This job identifies sales orders that require device enrolment and prepares batches for sending these instructions to the Device Enrolment Provider. This job also handles requests for device unenrolment, for which they send a request with a type of RE(Return).

Device Enrolment

Device Enrolment Response

This job processes a response from the Device Enrolment Provider for a Device Enrolment Request and updates CMP with the outcome.

External Data

External Reference Upload

Some customers may require external references to be mapped to CMP entities such as invoice numbers, subscription numbers and account numbers. This job loads the external numbers and the CMP entities with which they are associated into the CMP database. Each invocation of the job produces an audit outlining the external references that were loaded. This is a triggered job.

Ledger

Ledger Monitor

The Sales Ledger is record of sales, whether or not payment has been received and how much is owed. Various CMP processes create records in the Sales Ledger, for example to record the generation of new invoices, the receipt of a payments or the reversal of payments. These records have no impact on the balance of an account until they have been posted ‐ that is, validated and processed ‐ by this job. This job matches transactions (for example, payments to invoices), updates the open amount of matched transactions and maintains an audit of all changes to transaction open amounts. Once a record has been processed successfully, its status is updated and only then impacts on the related account balance. A sales ledger record is validated and processed only once. However, a successfully processed record can have its open amount subsequently modified by new transactions. This job is automatically triggered when new records have been created in the CMP Sales Ledger.

Number Management

Managed Number Monitor

Numbers in the CMP managed serial number repository can be configured so that they cannot be used or reused before or after a particular date. This job checks the managed number repository to determine the appropriate status of available numbers. Managed serial numbers that are not assigned to a subscription are expired if the Use By date of the number has been exceeded. Previously used numbers that are eligible for reassignment (numbers in a cooling-off state that have reached their allowed re-use date) are reverted to a Not Allocated state, which allows these to be re-used for connections and number changes.

Number Management

Managed Numbers

When subscriptions are created in CMP, up to five managed serial numbers can be assigned to an individual subscription. The first three numbers typically represent a Mobile/MSISDN number, a SIM number and an IMEI number, but this is configurable per implementation. The repository of available managed numbers is populated by uploading files containing individual numbers or ranges of numbers. Each file contains only one type of number. These numbers can be restricted to particular accounts or sales people. Optionally, a charge can be associated with a number which is applied on subscription creation or number change. A charge is typically applied to numbers that contain many repeating digits and are thus deemed more valuable. When CMP receives files containing serial numbers, these are automatically detected by a dedicated daemon, which creates a serial number batch in CMP for each file received. This job creates a record in the CMP managed serial number repository for each number in the uploaded batch. If a number range has been supplied, a record for each number in the range is created in the repository and, if applicable, each number in a particular range is assigned the same charge and account or salesperson. This job is automatically triggered whenever a new serial number batch has been created.

Number Management

SIM Profiles

A SIM profile - or SIM card - is an integrated circuit that is intended to securely store International Mobile Subscriber Identity (IMSI) details, which are used to identify and authenticate subscriptions on mobile telephony devices such as mobile phones or laptops. The SIM card has its own unique reference known as an Integrated Circuit Card Identifier (ICCID), which cannot be changed. CMP allows for a primary and secondary profile to be stored for a given ICCID. When CMP receives files containing SIM profiles records, these are automatically detected by a dedicated daemon which creates a SIM Profile batch in CMP for each file received. This job loads the SIM Profiles into CMP for use by provisioning jobs and for resolving agent queries, for example a customer contacting the call centre to request a Personal Unlocking Key (PUK) to unlock their phone. This job is automatically triggered whenever a new SIM Profile batch has been created.

Payments

Mandate Registrations

A direct debit is an instruction from a customer (debtor) to their bank or payment services provider, authorising an organisation (creditor) to collect variable or fixed amounts from their account, providing the customer is given notice of the collection amounts and dates. This job is responsible for generating a batch of new direct debit instructions for transmission to external systems, which in turn transfer these instructions to the paying banks and building societies. Downstream daemons extract this batch, convert the instructions to the required external system format and transmit them to the required destination. This job is typically scheduled to run once per day, excluding non-banking days.

Payments

Mandate Revisions

When new direct debit instructions are sent to an external payments system, some instructions can fail, for example, due to incorrect bank details. Successful instructions may also subsequently be amended or cancelled by the customer. When CMP receives files containing rejected, amended or cancelled instructions, these are automatically detected by a dedicated daemon, which creates a mandate revisions batch in CMP for each file received. This job updates or cancels the relevant mandate records in CMP. Cancellation in CMP typically involves reverting the account to a manual payment type, which often involves charging an administration fee. This job is automatically triggered whenever a new mandate revisions batch has been created.

Payments

Non Recurring Payments

Non-recurring payments occur when, rather than opting to pay their bill automatically each month, a subscription chooses to pay on their own terms, a payment by cash, for example. Records of these payments must be loaded into CMP and reconciled against the subscription’s account. When CMP receives non-recurring payment files, these are automatically detected by a dedicated daemon, which creates a non-recurring payments batch in CMP for each file received. This job is matches payments to accounts and creates a batch to post the payments to the Sales Ledger. Once the posting batch has been created, it is detected by dedicated daemons that format the batch and transmit the payment information to the target sales ledger. This job is automatically triggered whenever a non-recurring payments batch has been created.

Payments

Recurring Payments Rejections

When recurring payment and refund transactions are sent to an external payment system, some transactions can fail, for example due to insufficient funds or lost and stolen cards. These rejected transactions must be processed by CMP. When CMP receives files containing rejected transactions, these are automatically detected by a dedicated daemon, which creates a rejected payment batch in CMP for each file received. This job generates a batch that contains records to reverse each failed transaction from the sales ledger. Once this batch has been created, it is detected by dedicated daemons that format the batch and transmit it to the target sales ledger. This job also generates workflows (for example, to send a communication to the customer), processes soft declines to temporarily exclude the account from the automated payment process and processes hard declines to revert the account to the default (manual) payment to make alternative arrangements for collection of amounts due. This job is automatically triggered whenever a new rejected payment batch has been created

Payments

Recurring Payments

Customers can opt to pay their bills automatically, a defined number of days after the bill date, based on their payment terms. Automatic payment methods include direct debit and credit/debit cards. This job creates a batch of payment and refund records that are due for settlement. Once this batch has been created, it is detected by dedicated daemons that format the batch and transmit it to the appropriate external payments system. This job runs in two modes to distinguish between direct debit transactions and credit/debit card transactions. This job also creates a second batch to post the extracted payments and refunds to the sales ledger. Once this batch has been created, it is detected by dedicated daemons that format the batch and transmit it to the target sales ledger. This job is typically scheduled to run daily

Payments

Recurring Pre Payments

This job creates a batch of payments that are due for settlement. Once this batch has been created, it is detected by dedicated daemons that format the batch and transmit it to the appropriate external payments system. This job runs in two modes - Card or Balance - to distinguish between balance transactions and credit/debit card transactions. Each invocation of the job produces an audit of the accounts that were included in the extract. This is a scheduled job.

Payments

Recurring Pre Payments Rejections

Dedicated daemons detect files containing details of rejected payments and load those details into CMP. This job detects batches of rejected payments and for each rejected payment, the status of the payment is updated, the associated package allowances are expired and a Comms is generated to inform the customer of the rejected payment.

Provisioning

Provisioning actions, initiated via the creation of workflow events, progress to a status of Awaiting Network Services as the Workflow Monitor job processes the relevant workflows. This job detects the provisioning actions and, when appropriate, writes to a Network Request table, which is monitored by daemons responsible for generating a target-specific command and transmitting the command to the external system.

Provisioning

Bill Cycle Change

In a real-time charging (RTC) environment, when a post-paid subscription's bill cycle day is changed, the external RTC system creates new allowance and spend cap records that take effect at the start of the subscription's new bill cycle. These new records must be synchronised with CMP records in order to allow for real-time enquiry of allowance and spend cap balances from CMP. Following a bill cycle change, new records generated by the RTC system are stored in CMP. When the new records are due to come into effect, this job is triggered to update CMP allowance and spend cap records to refer to the new records.

Purge

Account Purge

Under data protection legislation, an organisation must not retain customer data any longer than necessary. This job removes personal customer information, such as contact names or account passwords, for accounts that are no longer in use. This job does not delete records. Instead, it obfuscates personal data elements using asterisks for character values or zeros for numeric values. This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. Only data from accounts changed on or before the calculated purge date will be obfuscated. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions will be sufficient.

Purge

Address Purge

Under data protection legislation, an organisation must not retain customer data any longer than is necessary. This job removes address information that is no longer in use; that is, there is no longer a reference to the address in any table in CMP. There is no input parameter for this job; an address is simply in use or it is not. No archiving takes place prior to the deletion of the records. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions of this job will be sufficient.

Purge

Consumer Purge

This job removes personal customer information, such as contact names or account passwords for terminated single subscription accounts. The job deletes records where possible and obfuscates data where it is not possible to delete records. Certain data cannot be deleted (e.g. usage) as legally there is a requirement for store this a certain period of time. This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. The calculated purge date is worked out by deducting this number of months from the current date. This parameter is optional. If you do not provide a value, a default value of six month is used. Only subscriptions who have terminated on or before the calculated purge date will be considered by the job. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions will be sufficient.

Purge

Direct Debit Purge

Under data protection legislation, an organisation must not retain customer data any longer than is necessary. This job removes direct debit information that is no longer in use, that is, cancelled. This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. Only data from accounts created on or before the calculated purge date will be removed and no archiving takes place prior to the deletion of data. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions of this job will be sufficient.

Purge

Payment Card Purge

Under data protection legislation, an organisation must not retain customer data any longer than is necessary. This job removes credit and debit card information that is no longer in use, that is, cancelled cards. This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. Only data from accounts created on or before the calculated purge date will be removed and no archiving takes place prior to the deletion of data. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions of this job will be sufficient.

Purge

Refund Purge

Under data protection legislation, an organisation must not retain customer data any longer than is necessary. This job removes refund information that is no longer in use, that is, those refunds with a status of cancelled, complete or rejected. This job derives a calculated purge date based on how long data should be retained before it can be purged ‐ the Months to Retain parameter. Only data from accounts created on or before the calculated purge date will be removed and no archiving takes place prior to the deletion of data. This is a scheduled job. This job can be scheduled to run daily; however, it is more likely that monthly or quarterly executions of this job will be sufficient.

Usage

Rated Usage

Every time a subscription uses their handset to make a call, send a text or browse the web, the network records this activity and makes the information available for collection, typically in batches. When CMP receives files containing rated usage records, these are automatically detected by a dedicated daemon, which creates a rated usage batch in CMP for each file received. This job processes rated usage batches to include these records in a detailed bill of a subscription. This job does not perform any usage rating itself; usage is already priced when it arrives in CMP. This job is designed to work in conjunction with a network that supports a real time engine that rates the usage as it happens. This job is automatically triggered whenever a new rated usage batch has been created.

Usage Reconciliation

Usage Aggregation

This job aggregates of both rated and wholesale usage records. It groups usage records by usage date, type, origin and destination and calculates totals for usage charges and usage units for each of these groups. It creates a usage reconciliation record for each usage group.

Usage Reconciliation

This job reconciles retail and wholesale usage records. It collects aggregated usage records between the dates specified in the job parameters for both retail and wholesale usage. The job then compares the records are against each other and calculates variances between usage charges, units and number of events. It exports the results of the reconciliation as a CSV file. A daemon transports the CSV file to storage.

Utility

Batch Error Management

When CMP is receiving json files (e.g. rated usage, rated charges etc) , the jobs that process these are triggered automatically by the presence of a record on the Interface Batch Header table with a stage of 'Extract/Load' and stage status of 'Complete' If the jobs are able to process all the data in these files, the stage and stage status will be set to 'Batch' and 'Complete'. If the jobs are unable to process some records due to missing CMP configuration, the stage and stage status will be set to 'Batch' and 'Error'. Batch Error Management job is an automated approach to reprocess individual batches in the event there are large numbers of files to reprocess once the missing configuration has been rectified.

Utility

Data Fix

This job allows operators to run pre-packaged SQL to resolve issues with data records in the CMP database. Each pre-packaged SQL contains three distinct elements:

Verification SQL - to identify the records to be fixed.
Execution SQL - to fix the records.
Validation SQL - to verify that the fix executed as intended.

The pre-packaged SQL has a unique data fix identifier and this is passed to the job as a parameter. This job would normally run from a scheduler for a specific data fix identifier

Workflow

Action Monitor

Customer requests to add or change service features often require interaction with a third-party network. The network actions, such as connections, disconnections and tariff changes, that are initiated by the processing of workflows are communicated to the appropriate network by the CMP Network Interfaces Framework (NIF). A success/failure response is sent back to CMP. The NIF collects and interprets the responses and updates CMP with the results. The Action Monitor job is triggered automatically when the results become available. The job updates subscription attributes and statuses based on the results. For a successful network action, it updates subscription attributes depending on the type of action, for example updating a connection or disconnection date. For an unsuccessful action, it updates the status of the subscription to reflect the type of network activity that has failed.

Workflow

Workflow Monitor

Workflows events are created by processes to initiate configured activities known as actions. Actions include: change of account type; application of a service (charge) to a subscription; initiation of network command generation and initiation of customer communication generation. Once a workflow has been created, it remains in a Pending state until it has been processed by this job on the requested date/time. When a workflow is processed, account type changes and subscription service actions are applied in full immediately. Network commands and communication generation actions involve initiating further downstream processing. Once processed, the status of the workflow is updated to indicate success, error or pending network activity. This job is automatically triggered when workflow records in a pending state that are due for processing are detected. These workflows are processed in order of priority.