Which price components can Relationship Pricing change?

Interest, charges, fees, commission and exchange rate spreads. Charges, fees and commission can be waived. Interest gets a fixed or variance rate or a percentage, within minimum and maximum limits.

How are customers assigned to a package?

Manually, or by the Relationship Pricing batch at end of day, which checks the eligibility plan at the revision frequency set in the scheme. Benefits apply from the next working day of the branch.

What happens when a customer stops qualifying?

It depends on the scheme's validity. A one-time scheme expires, a renewable scheme comes back when the customer qualifies again, and a perpetual scheme keeps the benefits.

How do we check that a package works?

FLEXCUBE keeps the availed benefit details for each transaction, with the original computed price and the final price. That gives every test scenario its evidence.

Oracle FLEXCUBE · Relationship Pricing

Price the relationship, not the product.

Give selected customers better rates, waived fees and free transactions based on their whole relationship with the bank, inside FLEXCUBE's own pricing.

InterestChargesFeesCommissionFX spreads

Try it

Build a package and see what the customer pays

1 · Eligibility plan: who qualifiesUDE_AVG_BAL >= 2500 AND CUST_AVGSAL > 0

2 · Benefit plan: what they get

3 · What the customer paysCustomer qualifies for the package

Price component	Standard	Final
Monthly account fee	€5.00	€0.00
Consumer loan rate	12.0%	11.0%
Outgoing transfers	€0.50 each	€0.50 each

Illustrative numbers. In FLEXCUBE every transaction keeps its original computed price and its final price, so each test scenario has evidence.

Pricing by relationship, not by product

Relationship Pricing prices a service on the customer's whole business with the bank, current or potential. Selected customers get a special price on top of the standard product price: a discount, a waiver, free transactions or several products in one package.

The module is flexible, and that is the risk. Eligibility plans, variance rules, benefit plans and schemes depend on each other, and a mistake shows up as a wrong fee on a real account. Our team has implemented Relationship Pricing preference packages for a European bank, and we set it up the same way every time: rules first, then the package, then tests on real scenarios.

How it works in FLEXCUBE

Six elements, set up in a fixed order

Step 2Eligibility plan

The condition that selects customers for a scheme, written in the expression builder on those data elements.

Example

UDE_AVG_BAL >= 2500
AND UDE_ACC_CNT >= 2

An illustrative condition on balance and number of accounts.

When a customer stops qualifying

The scheme’s validity decides what happens next

QualifiesBenefits
Stops qualifyingPaused
Qualifies againBenefits
LaterBenefits

The linkage is marked expired / renewable, and the benefits come back when the customer qualifies again.

How we implement it

01DesignSegments, eligibility criteria and benefits agreed with the business and accounting teams.
02DataUser data element queries, relationship value tag feeds and the customer flags that switch Relationship Pricing on.
03ParameterizationVariance rules, benefit plans, schemes and priorities, authorized through maker-checker.
04LinkageManual linkage and the RP batch at end of day, revision frequency and validity per scheme.
05Package feesThe package tariff and how the service fee is collected from the customer's account.
06Testing and handoverScenario tests with the original and final price for every transaction, then a runbook for the business team.

What the bank receives

Pricing schemes, benefit plans and eligibility plans configured and authorized
Data elements and external value feeds in place
Test evidence for every scenario: original price against final price
A runbook for the business team: adding a scheme, changing a benefit, checking a customer's price

After go-live

New packages become a business task, not a project. We hand over the runbook and stay available for SLA-based support by the same team.

Frequently asked questions

More FLEXCUBE services

Upgrade to 14.8

12.x to 14.8 — customization register, migration factory, rehearsed cutover.

Learn more →

GAP analysis

Fit-to-Standard, module by module: your scenarios run on the target version, with evidence, in 6–8 weeks.

Learn more →

All FLEXCUBE services

Upgrades, new modules and integrations, and SLA-based managed support.

Learn more →

Plan your pricing packages

Tell us which segments and benefits you have in mind. We will map them to FLEXCUBE's Relationship Pricing setup.