Pricing and Packaging Agent
Models plan structures and price changes.
- Industry
- Banking
- Department
- Product
- Team
- Strategy and Roadmap
- Kind
- Decision-maker
- Approver
- Pricing Committee
- Code
- PRD-05
It models changes to the bank's product pricing and packaging, such as a savings rate move after a policy rate change, a new current-account fee tier or a card annual fee, and forecasts the effect on net interest margin, balances and attrition. It checks fair value and notice duties and sends the proposal to the pricing committee.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the risk data warehouse: balances, margins, rate sensitivity and attrition history for the product, and competitor rates..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Pricing Committee with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the core banking system's pricing tables: it queues the approved rate or fee change with its effective date and customer notice. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The pricing policy: the pricing committee terms of reference, fair value assessments, pass-through targets for rate changes, notice periods for existing customers, fee caps and the treatment of customers in vulnerable circumstances.
Reads from
the risk data warehouse: balances, margins, rate sensitivity and attrition history for the product, and competitor rates.
Acts in
the core banking system's pricing tables: it queues the approved rate or fee change with its effective date and customer notice.
Hands back
An object with product, change, effective_date, nim_effect_bps, balance_effect, attrition_percent, pass_through_percent (or null), fair_value (pass, review or fail), notice_days, customers_affected and recommendation.
Asks a person when
This agent always sends a pricing change to the Pricing Committee, and also to ALCO when the NIM effect is 5 bps or more.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Least pass-through of a rate rise to savers (%) | 50 | A savings repricing after a policy rate rise that passes on less than this is flagged for fair value. |
| Notice to existing customers (days) | 60 | Unfavourable changes to existing customers need at least this much notice. |
| Most projected balance attrition (%) | 3 | A change projected to lose more balances than this needs the pricing committee's explicit approval. |
| NIM effect that needs ALCO (bps) | 5 | A change moving the bank's net interest margin by this much or more also goes to ALCO. |
| Most fee increase in a year (%) | 10 | A larger fee increase needs a fair value reassessment. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Forecast the effect on net interest margin, balances and attrition, and say what assumptions it used.
- A savings repricing that passes on less than 50 percent of a policy rate rise is flagged for fair value review.
- An unfavourable change to existing customers needs 60 days' notice; the effective date is moved if it does not allow that.
- A fee increase above 10 percent needs a fair value reassessment, and no new fee may fall mainly on customers in vulnerable circumstances.
- A projected attrition above 3 percent needs the pricing committee; a NIM effect of 5 bps or more also goes to ALCO.
- Every pricing change goes to the Pricing Committee; it never changes a live rate itself.
See the Pricing and Packaging Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.