Billing Module – Training Script (RIA Academy Version)

Lesson: Billing Overview

🎤 Introduction

Hello everyone,
Welcome back to RIA Academy.
Today, we will begin our training on Billing within Oracle Revenue
Management and Billing (ORMB).

📘 Agenda

In this lesson, we will cover:

1. Billing Overview

2. Entity Relationship Diagram (ERD) for Bill

3. Bill Lifecycle and Workflow

4. Billable Charge & Bill Prerequisites

5. Bill Page Overview

6. Bill Generation Process

7. Algorithm Spot (High-level Overview)

🧾 1. Billing Overview

A Bill is a formal document that communicates a customer’s financial

obligations.
It summarizes charges incurred over a specific period—typically monthly—
ensuring that customers are kept fully informed.

✔ A Bill:

 Details services provided

 Shows associated costs

 Supports transparency

 Encourages timely payments

  Ensures uninterrupted service

 Provides a chronological record of financial activity

Customers may receive many bills over time as part of their recurring
billing cycle.

🧩 2. Bill Configuration Settings (Key Concepts)

These settings influence how bills are created, displayed, and processed.

a. Bill Correction Option

Determines how correction bills are handled:

 Correction Note → Allows reopening and reprocessing of bills when

changes are needed.

 Credit Note → Shows only cancellation information on a separate bill.

b. Accounting Date Freeze Option

Controls how the accounting date is populated on the financial transactions

of the bill.

c. Minimum Amount for Final Bill

If a final bill amount is below this threshold:

 The bill is still generated,

 But not printed.

d. Override Bill Date

When enabled, users can manually specify the bill date at completion.

e. Autopay Creation Option

Determines:

 When automatic payments impact customer balances, and

  When they impact the General Ledger.

f. Sequential Invoice Options

Allows configuration for:

 System-wide sequential invoice numbers, or

 Division-specific numbering

Includes:

 Sequence Generation Algorithm (defines numbering logic)

 Use Sequential Bill Numbers (adds an alternate unique bill number

in addition to the bill ID)

🧾 3. Prerequisites Before a Bill Can Be Created

To have a functional billing flow, the following entities must exist:

✔ Person

✔ Account
✔ Contract

These together define the customer and the services being billed.

🏗 4. Contract Type Settings Required for Billing

Navigate to:
Admin → C → Contract Type → Billing Tab

These configurations control bill creation:

a. Bill Segment Type

 Primary driver of how bill segments are created

 Determines financial transaction behavior (GL + customer debt impact)

 Must be set to CMB

b. Recurring Charge Settings

  Recurring Charge = Optional
→ Allows the user to create recurring billable charges

 Recurring Charge Amount Label

→ Defines label shown in UI for recurring charge amount

c. Eligible for Billing

 Must be turned ON

 Allows system to create bill segments for this contract type

d. Minimum Days for Billing

Defines minimum duration required before a bill segment can be generated.

e. Default Description on Bill

Determines text printed on the customer’s bill.

f. Billing Processing Sequence

Controls processing order of contracts during batch billing.

g. Bill Print Priority

Defines display order of bill segments on the printed bill.

h. Max Bill Threshold

If exceeded, system raises a bill error during batch processing.

i. Unit of Measure / Estimates

Handles:

 Estimated billing
  UOM definitions

 Consumption calculations

j. Initial Start Date Option

Controls consumption period calculation for the first bill.

k. Use Calendar Billing

Controls how billing aligns with calendar cycles.

Options include:

 Allow advanced billing

 Anniversary billing

 Future billing

 Past billing

l. Anniversary Bill Frequency

Defines length of time between bill segments.

m. Total Amount to Bill

Controls:

 Whether “Total Amount to Bill” can be used

 How it is labeled

n. Budget Billing Options

Flags for enabling:

 Budget billing

 Unbilled budget functionality

o. Adjustment Behavior

Under Adjustment Type configuration:

Influence Next Bill Balance

 When ON, adjustments posted before bill completion will affect the bill
total.

 All adjustments created before bill completion automatically impact

the generated bill.

📦 5. Billable Charges

Billable charges are the primary source of bill segments.

Characteristics:

 Represent charges outside normal billing behavior

 Always tied to Account + Contract

 Drive the creation of bill segments

Billable charges → Bill Segments → Bills → Financial Transactions

🎯 6. Understanding the Bill

Bills are generated from bill segments, which come from:

 Billable charges

 Recurring charges

 Adjustments (if affecting next bill)

The Bill page will show:

 Bill Information

 Bill Segments

 Financial Transactions

 Adjustment/Payment links

 Print and XML data

Billing Module – “Understanding the Bill”

RIA Academy Training Script (Polished Version)

🎯 Introduction

In this segment, we will deep-dive into the Bill page, focusing on:

 The Bill Main Tab

 Bill Segment Tab

 Bill Routing Tab

 Bill Messages Tab

 Different Bill Generation Methods

This lesson explains how bill data is presented, filtered, routed, and
generated in ORMB.

🧾 1. Bill Main Tab Overview

The Main Tab of the Bill page displays all key information about the Bill.

a. Bill Info

A concatenated summary containing:

 Bill Date

 Bill Status

 Due Date

 Bill Balance

 Other important bill information

This field quickly tells the user the bill’s overall status.
b. Bill ID

 A system-generated unique identifier.

 Used as the bill’s primary reference key.

c. Account ID

 Identifies the customer responsible for the bill.

 The name of the account holder is shown beside it for quick

reference.

d. Bill Status

 Shows the current life cycle stage of the bill.

 Possible statuses discussed in earlier lessons include:

Incomplete, Error, Feasible, Freeze Pending, Frozen, Cancelled, Waiting
for Billing...

📘 2. Bill Segment Tab

The Bill Segment tab shows all segments that compose the bill.

It displays:

 Bill Info (same as Main Tab)

 Bill ID

 List of Bill Segments

✔ Bill Segment Filters

a. Contract Filter

Allows user to filter segments by:

 All

 Account Address

 Contract
  Contract Type

 Price Item

 Bill Segment Type

b. Bill Segment Status Filter

Filters segments by their status (e.g., Incomplete, Error, Frozen, Corrected).

This helps users focus on specific segments for review or troubleshooting.

📬 3. Bill Routing Tab

The Bill Routing tab displays all recipients and routing rules for the bill.

💡 Important:
No routing data appears until the bill is completed.

✔ Bill Routing Information Includes:

Field Meaning

Bill Route
Online, Postal, or Both
Type

Sequence System-assigned order of routing

Identifies batch where routing was

Batch Control
extracted

Address ID The destination address for the bill

Extract Timestamp when bill was downloaded for

Date/Time routing

Format Detailed or Summary version of the bill

Reprint System-populated tracking flag

Prevents bill from being routed to the

Do Not Extract
recipient

Copies Number of copies to send

POID Customer purchase order ID

Field Meaning

Intercept User who reviews the bill before delivery

📢 4. Bill Messages Tab

Bills may contain messages from several potential sources:

💬 Message Sources:

 Account

 Customer Class

 Contract (Contract-level message appears on each applicable

segment)

 Bill-level Message (Ad Hoc)

✔ Bill Message Grid Includes:

Field Description

Bill Message
Unique identifier of the message
Code

Message on Text that appears on the printed

Bill bill

Priority Determines display order

Indicates if an envelope insert is

Insert Code
required

This is used for notices, reminders, regulatory messages, or announcements.

⚙ 5. How Bills Are Generated

Billing is essential for updating customer balances and providing official

documentation.
ORMB supports three methods of bill generation:
A. Manual Bill Generation

Performed through the UI.

Steps:

1. Go to the Account context menu.

2. Select Bill → Add.

3. Save the bill.

4. Generate Bill Segments (from billable charges).

5. Freeze / Complete the bill.

Once completed, charges update the account’s financial balances.

B. Batch Bill Generation (Regular Monthly Billing)

Used for mass billing — hundreds or millions of accounts.

Batch billing uses three sequential batch jobs:

1. C1-BILL – Bill Open

 Identifies accounts ready for billing

 Creates pending bills

2. C1-BSEG – Bill Segment Generation

 Generates bill segments from billable charges and recurring charges

3. C1-BILLCP – Bill Completion

 Freezes the bill

 Updates account balance

 Generates financial transactions

This is the standard billing run used in large implementations.

C. Ad Hoc Bill Generation (On-Demand)

Used for special, case-by-case billing.

Batch Jobs:
  C1-FABILL – Creates ad hoc bill + bill segments

 C1-FABIC – Freezes and completes the ad hoc bill

Useful for one-off adjustments, out-of-cycle billing, or emergency billing.

🎉 Summary

You now understand:

✔ The structure and fields in the Bill Main Tab

✔ How to filter and review Bill Segments
✔ The details of Bill Routing
✔ How Bill Messages appear and where they come from
✔ Different methods of Bill Generation (Manual, Batch, Ad Hoc)

This prepares you for the next lesson:

👉 Demonstration of Bill Creation, Correction, and Routing

Demonstration: Bill Creation & Bill Generation

RIA Academy – Billing Module Practical Walkthrough

🎬 Introduction

In this demonstration, we will walk through the process of creating and

generating a bill in ORMB.

Before a bill can be created, the following prerequisites must exist:

1. Person

2. Account

3. Active Contract

4. Billable Charge (A bill cannot be generated without charges to bill)

We will use test data that already contains the Person, Account, and
Contract.
Next, we begin by creating the Billable Charge.

🧩 Step 1 — Create a Billable Charge

Billable charges are always created at the contract level.

Steps:

1. From the Account context menu, select Billable Charge.

2. If the account has multiple contracts, ORMB will prompt you to

choose the specific contract for which the charge will be created.

3. Enter the required details for the billable charge.

4. Save.

This billable charge is what will later appear as a Bill Segment when we
generate the bill.

🧾 Step 2 — Create a Bill Header

Once the billable charge exists:

1. Go to the Account context menu

2. Select Bill → Add

The Bill page opens — at this stage:

 The Main Tab contains almost no values yet

 The Bill Segments Tab is still empty

 The Bill Routing Tab is not yet populated

This is expected until segments are generated and the bill is completed.

⚙️Step 3 — Generate Bill Segments

Now we must generate the segments that will compose the bill.

Steps:
 1. Click the Generate button.

2. Provide the Cutoff Date (this defines the billing period end date).

3. Click OK.

Result:

 The bill now contains 3 bill segments (from prior data), including the
correct billable charge we created.

 You may review each segment by selecting them individually or

through the Bill Segment Tab.

To avoid confusion during the demo, we will delete the other segments
and retain only the billable charge we created.

🔍 Step 4 — Review Bill Segments

Check each segment for:

 Description (e.g., Flat Charge Example)

 Amount

 Status (Feasible)

 Distribution Code (derived from Contract Type + Bill Segment Type)

 SQ Details / Calculation Lines (none in this example)

The segments are currently feasible — meaning ready to be frozen.

📭 Step 5 — Freeze the Bill

Freezing the bill applies the financial impact onto the account balance.

Before freezing, observe the account balance:

 Current Balance: 400 USD

Now:

1. Click Freeze.

After freezing:

 The account balance is now updated by the bill amount.

  However, the Bill Routing tab is still empty because routing details
appear only after bill completion.

🧊 Step 6 — Complete the Bill

A bill can only be completed when:

✔ All bill segments are Frozen or Cancelled

✘ A bill cannot be completed if any segment is in Error

After clicking Complete:

The bill now has:

 A Bill Summary (total charges)

 A Match Summary (only for open item accounting)

 Correct totals reflecting the newly generated charges

📬 Step 7 — Review Bill Routing

Now that the bill is completed:

1. Open the Bill Routing tab.

2. Routing information is now populated.

Routing Details Show:

 Bill Route Type: Postal & Online

 Recipient Address

 Format: Detailed

 Extract Information

 Sequence & Batch (auto-assigned)

How Address Is Determined:

Bill routing uses the Address Source:

 In this example, the Address Source = Person

 Therefore, the address on the Person page → Contact Information tab

is used for bill delivery.
Example:
Maple St. (from Person Contact Information)

🔄 Step 8 — Review Financial Transactions

Click on the Total Amount link on the bill.

This opens the Financial Transactions (FT) page, showing:

 Debit and Credit Lines

 Bill Segment FT (the 100 USD charge)

 Any previous cancellation FTs (if applicable)

 Frozen User (who froze the bill)

You will also see the Freeze / Unfreeze option, allowing you to perform a
revert if needed.

🔎 Step 9 — Bill Segment Filters

In the Bill Segment Tab, you can filter by:

Bill Segment Type:

 Regular

 Post-Processing

 Any contract-specific segment types

Contract Type Filter:

Useful when the bill has segments from multiple contract types.

Status Filter:

 Frozen

 Cancelled

 Error

 Feasible
And more.
Example:
Filter by Frozen → Shows only frozen segments.

💡 Step 10 — Correction Note Availability

The Correction Note option appears because the installation option is

configured as:

 Bill Correction Option = Correction Note

 Freeze Option = Freeze at Will

These settings are found in:

➡️Admin → Installation Options → Billing Tab

This allows:

 Bill re-open

 Correction bill generation

 Sending a separate correction note to the customer

🎉 End of Demonstration

You have now learned how to:

✔ Create a Billable Charge

✔ Create a Bill
✔ Generate Bill Segments
✔ Freeze a Bill
✔ Complete a Bill
✔ Review Routing Information
✔ Review Financial Transactions
✔ Understand Bill Filters
✔ Understand how Correction Notes apply

Billable Charges, Invoice Frequency & Bill Period

(Pre-demo theory recap)

1️⃣ What is a Billable Charge?

Billable charges are essential in billing because they represent the

specific amounts that should be billed to the customer, especially for
services outside the normal or automated billing flow.

 They are always linked to a Customer’s Account and Contract

 They are part of the prerequisites for bill creation, together with:

o Person

o Account

o Active Contract

Without a billable charge (or other charge source), a bill will have nothing to
compute.

2️⃣ Types of Billable Charges

There are two main types of billable charges:

A. Pass-Through Billable Charge

 Represents pre-calculated, fixed charges

 Typically directly reflect actual costs incurred by the business

 Characteristics:

o Transparent – no additional markup or adjustments

o Often used for items like:

 Third-party fees

 Taxes or external service costs

 One-off fixed fees

B. Recurring Billable Charge

 Charges that repeat on a regular basis

  Linked to ongoing services, subscriptions, or contractual
arrangements

 Customer agrees to pay a fixed or patterned amount at regular

intervals (e.g. monthly, weekly).

Examples:

 Monthly subscription

 Regular service fees

 Maintenance or membership charges

3️⃣ Additional Billable Charge Details

On the billable charge configuration, you may also see:

 Service Quantity Identifier

 Service Quantity

These are typically used when:

 You want the system to compute additional charges along with the
billable charge line

 Example: apply taxes or surcharges based on quantity/usage

When a billable charge is associated with a price item, the key required
fields are:

 Service Quantity Identifier

 Service Quantity

There is also Billable Charge Characteristics, where you can set:

 Characteristic Type

 Characteristic Value

These extend the attributes of the billable charge and are especially
important for pricing (price items and price lists). These are usually covered
in the Pricing module.

4️⃣ Bill Period vs Invoice Frequency

These two are related but not the same.

🕒 A. Bill Period

 Defines the time frame for which the customer is being charged

 It represents the start and end dates of the period covered by that
bill

 Example:

o Bill Period: Jan 1 – Jan 31

o All applicable charges within this range appear on the bill

📬 B. Invoice Frequency

 Defines how often bills are generated and sent

 It is the regular interval for bill creation, regardless of what

happens inside each period

 Examples:

o Monthly

o Quarterly

o Semi-annually

o Annually

o Every 7 days (weekly)

So:

 Bill Period → “What date range are we billing for?”

 Invoice Frequency → “How often do we send a bill?”

Both are optional, but they are typically used for recurring billable
charges.

5️⃣ Regular Billing vs Ad Hoc Billing

Billable charges can participate in:

✅ Regular Billing

 Follows a fixed, predefined schedule

  Examples:

o Monthly utility bills

o Subscription (Netflix, internet, etc.)

o Monthly rent

✅ Ad Hoc Billing

 Occurs on-demand, not on a fixed schedule

 Invoices are generated as needed

 Examples:

o Consulting projects

o Emergency services

o One-time setup or additional services

Related Fields in Billable Charge:

 Bill On or After Date

o Minimum date after which the bill may be generated

 Ad Hoc Bill (checkbox)

o Indicates if this billable charge should be considered during ad

hoc billing runs, regular billing, or both (depending on
configuration)

6️⃣ Invoice Frequency Configuration

Invoice Frequency defines how frequently bills are created from a scheduling
perspective.

Key fields:

 Invoice Frequency

o The code / ID of the frequency

 Description

o Human-readable label (e.g., “Monthly”, “Quarterly”)

 Daily Frequency
 o Number of days between bills (used when defining in days)

o Example: 7 = weekly

 Monthly Frequency

o Number of months between bills (used when defining in

months)

o Example:

 1 → Monthly

 6 → Semi-annual

Note:

 Daily Frequency is only required when the frequency is expressed in

days

 Monthly Frequency is only required when the frequency is expressed in

months

Also:

 Invoice frequency is based on the bill cut-off date.

 If the Bill On or After date is greater than the bill’s end date,
computation will adjust based on the bill’s end date.

7️⃣ Bill Period Configuration

Bill Period defines the date ranges that can be used as standard billing
windows.

Key fields:

 Bill Period Start Date

o The beginning of the billing window

 Bill Period End Date

o The end of the billing window

Notes:

 Bill Period is optional, but useful for recurring charge scenarios

  It is also based on the cut-off date used during bill generation

 If the cut-off date is greater than the bill period end date, computation
will adjust from the bill period end date

You can:

 Define flexible Bill Period schedules

 Exclude certain dates if needed

 After bill generation, delete or adjust bill segments that fall inside
unwanted Bill Periods.

✅ With that, your theory section on Billable Charges + Invoice Frequency

+ Bill Period is complete and clean.

Demonstration: Recurring Charges – Bill Period vs Invoice Frequency

(With UI steps + logic explanation + examples)

1️⃣ Navigate to the Billable Charge Creation Page

1. Open the Account page.

2. From the Account Context Menu, select:

Billable Charge → Add

3. The Billable Charge page opens.

2️⃣ Choose the Recurring Method

On the Billable Charge page, you will find the field:

🔹 Recurring Method

This controls how the system creates recurring bill segments.

You can choose:

Option Meaning

Uses custom date ranges set by the Bill

Bill Period
Period setup

Frequency (Invoice Uses a fixed interval (daily, weekly, monthly,

Frequency) etc.)

Think of it as:

 Bill Period → custom schedule (flexible)

 Invoice Frequency → fixed interval (simple)

3️⃣ EXAMPLE 1: Using BILL PERIOD

(You already showed this earlier—here’s a clean summary)

👉 When recurring method = Bill Period

 You must configure:

o Start Date

o End Date

o Optional: multiple Bill Period schedules in the Bill Period master

setup

Bill Period creates bill segments based on your defined date ranges.

4️⃣ EXAMPLE 2: Using INVOICE FREQUENCY (Daily Frequency = 3)

Now let’s show the detailed demonstration exactly as you explained it.

Step 1 — Configure a Recurring Billable Charge

 Recurring Method: Invoice Currency / Frequency

 Daily Frequency: 3 days

 Start Date: June 4

 End Date: July 4

Step 2 — Generate the Bill

1. Go to Bill → Add
 2. Click Generate

3. Enter a Cutoff Date

4. Click Calculate

Result

The system created 11 bill segments.

Why 11 bill segments?

 Total days from June 4 → July 4

→ 30 days

 30 days ÷ 3 days per bill segment = 10 full segments

 Include end date = 1 extra partial segment

Therefore: 11 bill segments

5️⃣ EXAMPLE 3: Invoice Frequency with Monthly Frequency = 1

This example explains “monthly” billing.

Step 1 — Configure the Billable Charge

 Recurring Method: Frequency

 Monthly Frequency: 1

 Start Date: June 4

 End Date: July 4

Step 2 — Generate the Bill

System creates 2 bill segments:

Bill
Coverage
Segment

June 4 → July 3 (30

Segment 1
days)

July 3 → July 4 (1
Segment 2
day)

Why?
  Because June has 30 days

 Monthly frequency uses the number of days in the month of the start
date

o Start date is June 4 → system uses 30 days

 So first segment = 30 days

 One remaining day → second segment

Verification

If you compute date difference:

✓ June 4 + 30 days = July 4

✓ Duration June 4 → July 3 (inclusive) = 30 days

This matches system behavior.

6️⃣ Comparison: Bill Period vs Invoice Frequency

Feature Invoice Frequency Bill Period

Fixed intervals (daily,

Schedule Type Custom date ranges
weekly, monthly, yearly)

Setup Flexible but more setup

Simple
Complexity work

Fixed subscriptions (gym, Academic billing, project

Best For
Netflix, monthly dues) phases, seasonal billing

Segments
Interval (ex: every 7 days, Exact bill period date
Created Based
every 1 month) ranges
On

7️⃣ When to Use Which?

✅ Use Invoice Frequency when:

 The billing cycle is consistent

 Example:

o Monthly subscription
 o Weekly service fee

o Daily recurring charges

✅ Use Bill Period when:

 The billing cycle changes, or is irregular

 Example:

o School terms

o Construction project phases

o Seasonal charges

8️⃣ Final Explanation for Trainees

To summarize:

 Invoice Frequency is best for fixed, predictable billing schedules.

→ The system automatically computes segments based on days or
months.

 Bill Period is best for custom, pre-defined billing windows.

→ The system uses your exact date ranges.

Each option affects:

 How many bill segments are created

 How the total charge is split

 How billing cycles appear in the final bill

1️⃣ Installation Options – Billing Tab

Path: Admin → I → Installation Options → Billing tab

Key field:

 Bill Segment Freeze Option

o Freeze at will
  User must click Freeze on the bill manually.

 Flow: Generate Bill → Freeze → Complete

o Freeze at bill completion

 Bill segment is frozen automatically when the bill is

completed.

 Flow: Generate Bill → Complete (auto-freeze)

This setting controls how and when bill segments get a Frozen status.

2️⃣ Bill Message & Division

Path to maintain Bill Messages:

Admin → (depends on setup, usually Message / Bill Message)

 You create Bill Messages (code, description, priority, etc.).

 Then you link Bill Messages to a Division.

 Only messages assigned to that Division can be used on bills for

accounts in that Division.

💡 Priority:
If multiple messages apply, priority controls display order on the bill
(highest priority shows first).

3️⃣ Account-Level Bill Settings

Path: Customer Management → Account → Main tab → Bill Settings

Fields:

 Bill Cycle

o Controls when a bill is produced for the account.

o Used by batch billing: the batch checks the Bill Cycle to decide
which accounts to bill.

o Must be defined under the Division first, then selectable on

the account.

 Bill On or After Date

 o If set, billing for this account is postponed until that date.

o Useful when:

 There is a batch scheduled,

 But you don’t want this account billed yet.

 Protect Bill Cycle

o If checked:

 Activating a contract with a different bill cycle will not

overwrite the account’s bill cycle.

o Similar idea to Protect Division.

 Trial Bill

o If enabled, bills created for this account are simulation only:

 They do not affect the customer’s balance.

 Used for testing / dry-run billing.

4️⃣ Customer Class – Billing Controls

Path: Admin → Customer Class → [Select Class]

Important areas:

 Bill Messages

o You can assign Bill Messages at Customer Class level.

o Any Account using this Customer Class can receive those

messages.

 Days Till Bill Due

o Field (e.g., Days Till Bill Due = 1)

o Logic:

 Due Date = Bill Date + Days Till Bill Due

o Example:

 Bill Date = 06/05

  Days Till Bill Due = 1

 → Due Date = 06/06

5️⃣ Contract Type – Billing Settings

Path: Admin → C → Contract Type → [Select Division + Contract Type] →

Billing tab

Key fields:

 Eligible for Billing

o If ON, contracts of this type will:

 Have bill segments generated

 Be included in billing.

 Bill Segment Type

o Controls how bill segments are created and how they

impact financials.

o This points to a Bill Segment Type configuration which

defines the algorithms.

6️⃣ Bill Segment Type – Algorithms

Path: Admin → Billing Management → Bill Segment Type → Add / Search

Important fields:

 Create Algorithm

o Responsible for creating the Bill Segment.

o Defines how the segment is calculated (charges, dates, etc.).

 Financial Algorithm

o Responsible for creating the Financial Transaction for that bill

segment.

o Defines how it affects:

 Current / Payoff balance

  General Ledger

 Get Consumption Algorithm (optional)

o Mostly used in Oracle Utilities (e.g., meter-based consumption).

o Not required for your ORMB use case.

7️⃣ How It All Connects (Mini Flow)

1. Installation Options (Billing tab)

o Controls freeze behavior and other global billing rules.

2. Division

o Holds allowed Bill Cycles and Bill Messages.

3. Customer Class

o Sets Days Till Bill Due and Class-level messages.

4. Account

o Uses Division, Bill Cycle, Bill On/After, Trial Bill.

5. Contract Type (Billing tab)

o Marks contracts as Eligible for Billing and links to Bill

Segment Type.

6. Bill Segment Type

o Uses Create and Financial algorithms to generate bill segments

and financial transactions.

Billable Charge – Admin Configuration (Clean Summary)

1️⃣ Where Billable Charge Templates Are Configured

Path:
Admin → C → Contract Type → [Select Contract Type] → BC Template tab

 This tab contains the list of Billable Charge Templates available for
the contract type.
  These templates pre-populate fields when creating a billable charge.

 You can assign multiple templates, but only ONE (1) can be marked
Default.

⚠️Important Rule

 Only one template can be set as default.

Setting more than one default causes an error.

2️⃣ How a Default Template Works During Billable Charge Creation

Path:
Account → Billable Charge → Add

When you click Create Billable Charge:

 ORMB auto-populates fields based on the default billable charge

template assigned to the contract type.

 Pre-filled values may include:

o Description on Bill

o Lines / Price Items

o Amounts

o Distribution Codes

o Currency Code

🔍 Example

Template has:

 Description on Bill → "Transaction Charges for Product"

Then when you create a billable charge, this text appears
automatically.

Replacing a Template

 If you switch to another template from the dropdown:

o All fields will update to those defined in the selected template.

3️⃣ Understanding Billable Charge Templates

Path:
Admin → V → Billable Charge Template

A Billable Charge Template contains:

Basic Fields

 Template Code

 Template Description

 Description on Bill

 Currency Code

Billable Charge Lines

Each template can have multiple lines, for example:

 Router Installation Fee

 First Month Subscription Fee

Each line can define:

 Amount

 Price Item

 Distribution Code

 Characteristics per line (optional)

Purpose of Templates

✔️Reduce manual entry

✔️Standardize charges
✔️Avoid errors
✔️Faster bill generation

4️⃣ Can You Create a Billable Charge WITHOUT a Template?

✅ Yes.
Templates are optional.

For unexpected or one-off charges, simply:

 Leave the template blank,

  Manually fill:

o Description on Bill

o Amount

o Distribution Code

o Currency Code

o etc.

The system still allows saving a billable charge without using any template.

5️⃣ Making a Template Available for Use

After creating a new template via:

Admin → V → Billable Charge Template → Add

You must also:

➡️Add it to the Contract Type → BC Template tab

Otherwise, the template will not appear during billable charge creation.

⭐ Training Notes Summary

Area What It Controls

Contract Type → BC Template What templates are valid for contracts

Tab of that type

Default Template Flag Auto-fills billable charge page

Billable Charge Template Setup Defines lines, description, distribution,

(Admin → V) amounts

Manual Charge Creation Possible without template

One Default Restriction Only one template can be defaulted

1. Two Types of Price Items in ORMB

In ORMB, every Price Item is either:

1. Non-bundled Price Item

2. Bundled Price Item (Bundle)

🟦 Non-Bundled Price Item

 Represents a single product or service.

 It stands alone – no grouping, no package concept.

 Pricing and billing are computed just for that one item.

 Example:

o “ATM Withdrawal Fee”

o “Single Wire Transfer Charge”

When we created a price item earlier, you saw a field: “Bundle?” (Yes/No).
For non-bundled items, this is set to No.

🟦 Bundled Price Item (Bundle)

 Represents a group of products/services treated as one package

for pricing and billing.

 Often used to:

o Group related services, and/or

o Give discounted or preferential pricing when services are

used together.

 Very common in financial services:

o Example: “Premium Current Account Bundle”

 Includes: checkbook, overdraft facility, debit card, online

banking, etc.

When we define a bundle price item:

 Bundle? = Yes
  We also choose a Bundle Type:

o Regular

o Phantom

o Ratio

2. Bundle Types

2.1 Regular Bundle

 The bundle has its own price/discount, and that bundle price is
applied to the total usage of the included products.

 Still considers total quantity across bundled products, but pricing is

controlled at the bundle level.

High level idea:

Sum up the usage of the bundle components → find the corresponding

range/row in the bundle pricing → apply that rate/discount.

2.2 Phantom Bundle

 Each product still has its own pricing table, but:

o The total volume across the bundle is used to determine

which tier to apply.

o Then, each product is priced using its own table, based on that
shared “total volume”.

So:

1. Compute total quantity of all bundle products.

2. Use that total to determine the tier (for each product’s table).

3. Apply the corresponding per-product rate to each product’s usage.

4. Sum all product charges.

It’s “phantom” because the bundle itself doesn’t have a distinct price – it
influences pricing of its children.
2.3 Ratio Bundle

 The most advanced bundle type.

 Pricing depends on the ratio between selected products, not just

total volume.

 Two key concepts:

o Numerator

o Denominator

Process overview:

1. Choose one or more products as Numerator and one as

Denominator.

2. Sum the usage for Numerator products → total numerator.

3. Sum the usage for Denominator product(s) → total denominator.

4. Compute the ratio:

total numerator
ratio=
total denominator
5. Use this ratio to:

o Decide which range/row to use in each product’s pricing table.

6. For each product:

o Apply its rate for that ratio band.

o Multiply by that product’s quantity.

7. Sum everything for the final bundle charge.

Important:

In a ratio bundle, pricing is defined at the product level, not at the

bundle header. The bundle defines the ratio logic; each product defines its
own rates for those ratio ranges.

3. Creating a Bundled Price Item

Step 1 – Create the Bundle Price Item

Navigate:
Menu → Pricing Management → Price Item → Add

On the Price Item main page:

1. Enter Price Item ID (e.g. CM_BUNDLE_X).

2. Enter Description (e.g. “SME Transaction Bundle”).

3. Fill in:

o Contract Type – which contracts can use this bundle.

o Division(s) – where this bundle is valid.

4. Set Bundle? = Yes.

5. Set Bundle Type:

o Regular, Phantom, or Ratio.

Save the price item.

(From this point, you’ve defined the bundle “header”, but not which products
are inside.)

4. Adding / Removing Price Items from a Bundle

For this we use the Product Relationship Maintenance Portal.

Step 2 – Open the Bundle in Product Relationship

1. Go to Menu → Pricing Management → Price Item.

2. Search for your bundle price item.

3. In the result grid, find your bundle row.

4. Click the link icon under the “Price Item Relationship” column.

This opens the Price Item Relationship Portal.

Step 3 – Add or Remove Child Price Items

In the Assigned Price Item zone:

 Click Add / Edit:

o Use the “+” (plus) icon to add a price item to the bundle.
 o Use the trash icon to remove an existing item.

 Each row will contain:

o Child Price Item

o Relationship Type

Relationship Type depends on Bundle Type:

 If Bundle Type = Regular or Phantom

→ Relationship Type must be Bundle

 If Bundle Type = Ratio

→ Relationship Type must be:

o Numerator or

o Denominator

Example:

 Bundle: BUNDLE_X

 Children:

o PI_X1 (Relationship Type = Bundle)

o PI_X2 (Relationship Type = Bundle)

For a ratio bundle:

 Bundle: RATIO_BUNDLE_Y

 Children:

o PI_A → Relationship Type = Numerator

o PI_B → Relationship Type = Denominator

Once done → Save.

5. Conceptual Summary for Learners

You can end the topic with something like this:

 A non-bundled price item is a standalone product/service.

 A bundled price item is a parent that groups several price items into
one pricing logic.
 Bundle Types:

o Regular – bundle has its own pricing, uses total usage.

o Phantom – total usage determines tiers; each member product

is priced using its own table.

o Ratio – pricing depends on the ratio of usage between products

(numerator vs denominator).

 Product Relationship Maintenance controls:

o Which child products belong to the bundle.

o How they behave (Bundle / Numerator / Denominator).