Changing a product’s term

A term is a value the customer signed up to, such as a card’s minimum payment of 5%. Each account keeps its own copy of its terms, taken when it opened. This article explains what happens to existing accounts when you change a term on the product.

Terms and calculations

A product holds two kinds of thing. They behave differently when you change them.

Kind Example When you change it on the product
Calculation The order a payment pays off fees, interest and balance Every account follows on its next run
Term The minimum payment of 5% You choose who follows, as below

Past postings never change. Each one keeps the figures it was made with.

New accounts only, or existing accounts too

When you change a term’s value on a product, you answer one question.

Answer What happens
New accounts only (the default) Accounts opened from publish start on the new value. Existing accounts keep theirs.
Existing accounts too New accounts start on the new value. Existing accounts on the old value move to the new one from a date you choose.

If an account is on any other value, it is left alone. Someone set that value on purpose, either at opening or by changing the account’s term.

If you choose Existing accounts too, you give an effective date. It cannot be before today’s trading date. A New accounts only change takes no date.

flowchart LR
  A[Change submitted] --> B[Approver reads the effect]
  B -->|approved| C[Published]
  C --> D[New accounts start on the new value]
  C -->|existing accounts too| E[Run waits for the effective date]
  E --> F[Accounts on the old value move]

What the approver sees

A second person approves every product change. The approval card carries an Effect block, worked out when the change is submitted.

The list shows at most 50 accounts. The counts always cover every account.

These accounts are not listed: closed, discarded and pending accounts, and accounts already on the new value. The block shows no money, because a term change posts nothing.

If someone edits the change after approval, the approval is void. A second person must approve it again.

Worked example

Woodgrove Bank’s credit card has a minimum payment of 5%. Cards A and B are on 5%. Card C was changed to 4%. Alex changes the minimum payment to 3%, for existing accounts too, from 1 July 2026.

Card Today From 1 July Why
A 5% 3% On the old value
B 5% 3% On the old value
C 4% 4% Set on purpose, so left alone

The approver reads: 2 moving from 2026-07-01, and 1 left alone.

Following the run

Publishing an Existing accounts too change opens a run. The run is listed on the Reference data changes page, as for a rate change. It is already approved, and it names the change that published it.

On the effective date, the run works out its list again, then moves each account.

If the effective date is the publish day, the run applies at publish.

To stop a waiting run, reject it on the Reference data changes page. That needs a second person. The product’s value stays changed. To change it back, make a new change for new accounts only.

When the change is refused

The change is refused, with the reason, in these cases.

Situation What to do
The effective date is before today’s trading date Pick today or a later date
The effective date passed before the change was published Edit the date in the open change, then publish again
The term’s value on the product is a formula, not a plain value Only plain values, such as 5%, can reach existing accounts
The term is a rate priced by a rate card The card moves its accounts by its own setting
A run for the same term is still waiting Wait until it applies, or reject it first

If the change is one of several in a change set, the others wait with it. They publish together or not at all.

What your organisation configures

From the LedgerTM product guide, as shipped with the software and written with it. Copied from the platform repository on 2026-11-11.