Flow of the explanation in this lesson.
Currency and Amount: Decimal Precision and Minor Units
What you will learn
Your objective. By the end of this lesson, you will be able to explain currency and amount: decimal precision and minor units. An ISO 20022 amount is carried as a decimal value together with a three letter currency code from ISO 4217, for example EUR 10000.00 or JPY 125000.
Why it matters. A business analyst should check the currency table in the requirements, because a missing currency or a wrong exponent is a defect that only appears for certain currencies.
Chapter objective: How the standard is built, read and validated in real systems
Key learning points
- ISO 20022 amount
- Decimals store the value exactly
- Decimal place validation
- Interbank settlement amount
- Rounding after conversion
- Amount decimal place validation
Key terms
Reconciliation: The process of comparing records from two sources, such as a bank statement and an internal ledger, to confirm they agree.
Settlement: The final movement of funds between banks to discharge obligations created by cleared payments. Settlement is usually made in central bank money or through correspondent accounts.
ISO 20022: An international standard for financial messaging that defines XML message formats for payments, securities and trade.
Payment flow diagram showing Currency and Amount: Decimal Precision and Minor Units.
Insights and practice scenarios
Worked insights and practice scenarios for this lesson. Each one is a reusable PaymentForge case, so the same case may appear in more than one lesson.
Practise this lesson
Exercise
Work out what the beneficiary receives for a EUR 10000.00 payment under OUR, SHA and BEN.
Use the charge arrangement rules in this lesson and the correspondent and beneficiary bank fees named in the lesson.
- What to do. Calculate the amount credited under each of the three arrangements and state who pays each fee.
Correct result. Under OUR the sender pays all charges and the beneficiary receives the full amount. Under SHA the sender pays the sending charges and the beneficiary pays the receiving charges. Under BEN the beneficiary pays all charges and receives the amount less all fees.
Why. The charge arrangement decides who pays and how much arrives. A customer who was promised the full amount and receives less will complain, and the complaint lands on the analyst.
Check your understanding
Practice question
Which of the following best describes currency and amount: decimal precision and minor units?
Takeaway and next step
What to remember
The screen must show the amount with the correct decimal places for the currency and must not let the user type a third decimal for a euro payment.
Open the message type from this lesson and inspect its fields, then find the field that carries the amount.
Open the ISO 20022 Message Explorer →
Builds on "Reading an ISO 20022 Schema: XSD Patterns".
Transcript and full text
Show transcript
An ISO 20022 amount is carried as a decimal value together with a three letter currency code from ISO 4217, for example EUR 10000.00 or JPY 125000. The amount type is ActiveOrHistoricCurrencyAndAmount, and it stores the value as a decimal with a fixed number of fraction digits, not as a binary float. A float stores numbers in binary, and many decimal values cannot be represented exactly in binary, so 0.1 plus 0.2 can become 0.30000000000000004. In a payment system, that tiny error can grow across thousands of payments into a real loss, or it can cause a control sum to fail and a whole file to be rejected. Decimals store the value exactly, which is why every payment standard uses them. Minor units are the smallest unit of a currency, and the number of minor units decides how many decimal places an amount may have. The euro and the US dollar have two minor units, so EUR 10,000.00 is valid and EUR 10,000.005 is not, because the third decimal place does not exist. The Japanese yen has zero minor units, so JPY 125000 is valid and JPY 125000.50 is not. The Bahraini dinar has three minor units, so BHD 100.250 is valid. A system must validate the decimal places against the currency, because an amount with too many decimals is invalid and must be rejected. A business analyst should check the currency table in the requirements, because a missing currency or a wrong exponent is a defect that only appears for certain currencies. The message carries several amounts, and each one has a different meaning. The instructed amount is the amount the debtor asked to be paid, in the currency of the instruction. The equivalent amount is the same value converted into another currency, and it carries the exchange rate used. The interbank settlement amount is the amount that actually settles between the banks, which may differ from the instructed amount when charges are deducted or a conversion happens along the chain. For a EUR 10,000 payment from Paris to Tokyo, the instructed amount may be EUR 10,000, the equivalent amount JPY 1,625,000 at the agreed rate, and the settlement amount JPY 1,625,000 after charges. The message must make each amount clear, because the creditor reconciliation depends on it. Rounding and conversion are where amount errors usually appear, and the rules must be written down. When a conversion produces more decimal places than the currency allows, the system rounds using a defined rule, usually half up, and it must record the rate and the rounded result. When charges are deducted, the system must state whether the charge is taken from the principal or added on top, because a EUR 10,000 payment with a EUR 15 charge can settle as EUR 9,985 or as EUR 10,000 with a separate charge of EUR 15. A tester should check rounding for every currency the system supports and confirm the group header control sum equals the sum of the transaction amounts. The screen must show the amount with the correct decimal places for the currency and must not let the user type a third decimal for a euro payment.
An ISO 20022 amount is carried as a decimal value together with a three letter currency code from ISO 4217, for example EUR 10000.00 or JPY 125000. The amount type is ActiveOrHistoricCurrencyAndAmount, and it stores the value as a decimal with a fixed number of fraction digits, not as a binary float. A float stores numbers in binary, and many decimal values cannot be represented exactly in binary, so 0.1 plus 0.2 can become 0.30000000000000004. In a payment system, that tiny error can grow across thousands of payments into a real loss, or it can cause a control sum to fail and a whole file to be rejected. Decimals store the value exactly, which is why every payment standard uses them.
Minor units are the smallest unit of a currency, and the number of minor units decides how many decimal places an amount may have. The euro and the US dollar have two minor units, so EUR 10,000.00 is valid and EUR 10,000.005 is not, because the third decimal place does not exist. The Japanese yen has zero minor units, so JPY 125000 is valid and JPY 125000.50 is not. The Bahraini dinar has three minor units, so BHD 100.250 is valid. A system must validate the decimal places against the currency, because an amount with too many decimals is invalid and must be rejected. A business analyst should check the currency table in the requirements, because a missing currency or a wrong exponent is a defect that only appears for certain currencies.
The message carries several amounts, and each one has a different meaning. The instructed amount is the amount the debtor asked to be paid, in the currency of the instruction. The equivalent amount is the same value converted into another currency, and it carries the exchange rate used. The interbank settlement amount is the amount that actually settles between the banks, which may differ from the instructed amount when charges are deducted or a conversion happens along the chain. For a EUR 10,000 payment from Paris to Tokyo, the instructed amount may be EUR 10,000, the equivalent amount JPY 1,625,000 at the agreed rate, and the settlement amount JPY 1,625,000 after charges. The message must make each amount clear, because the creditor reconciliation depends on it.
Rounding and conversion are where amount errors usually appear, and the rules must be written down. When a conversion produces more decimal places than the currency allows, the system rounds using a defined rule, usually half up, and it must record the rate and the rounded result. When charges are deducted, the system must state whether the charge is taken from the principal or added on top, because a EUR 10,000 payment with a EUR 15 charge can settle as EUR 9,985 or as EUR 10,000 with a separate charge of EUR 15. A tester should check rounding for every currency the system supports and confirm the group header control sum equals the sum of the transaction amounts. The screen must show the amount with the correct decimal places for the currency and must not let the user type a third decimal for a euro payment.
Full lesson text (all scenes)
Completing a lesson updates your progress dashboard on the homepage.
Scene timestamps are estimated by allocating the narration text proportionally across the real audio length. The audio playback position is the source of truth: pause freezes the visual, seeking restores the correct scene, replay restarts the scene animation.