Value-Based Weighting (VBW): How Business Activity Enters Risk Accounting
- 1. Why does business scale need its own measure?
- 2. What is the Value Table in the published method?
- 3. How is VBW used to calculate inherent Risk Units?
- 4. Worked example: selecting VBW for Commercial Loans
- 5. VBW versus raw turnover or transaction counts
- 6. What would an auditor check in a VBW calculation?
- 7. Frequently asked questions
- 8. Related terms, publications and research
Value-Based Weighting (VBW) is the method-defined factor used in Risk Accounting to represent a product's level of business activity in inherent-risk calculations. In Hughes's published banking method, VBW is selected from a discrete value-band table using daily new business. It scales Exposure Uncertainty Factors (EUFs); it is not the transaction amount itself.
1. Why does business scale need its own measure?
Consider a bank that offers a comparatively simple product through an established operational process. If new-business volumes rise, the bank may carry more activity-related exposure even when the structural properties of the product have not changed. A different product may involve fewer transactions but more complex delivery and processing arrangements. Counting transactions alone cannot distinguish the two circumstances.
Risk Accounting separates structural exposure, represented by the Exposure Uncertainty Factor (EUF), from the business-activity scale, represented in the published banking method by VBW. Both contribute to inherent Risk Units. Risk mitigation is subsequently considered through an E-RCSA-based Risk Mitigation Index (RMI). [1, pp. 138–140]
The published banking method does not define VBW as an arbitrary percentage, a direct cash-loss estimate or simply the number of transactions processed. Instead, it maps the source activity value to one of the weights specified in an approved Value Table. The choice of table, definition of daily new business, currency normalization and reporting period must all be governed.
2. What is the Value Table in the published method?
Hughes provides a discrete schedule of daily US-dollar new-business value bands and associated VBWs. The weights rise as activity increases, but not proportionally to the monetary amount. The source describes this as a decelerating, logarithmic-style weighting relationship, associated with an assumed tendency toward greater operational automation and sophistication as throughput grows. That motivation is a methodological design assumption, not proof that any individual bank's losses increase at the same rate. [1, pp. 139, 161]
The following is a short excerpt from the published table, sufficient to explain the assignment used in the worked example; it is not a new, RASB-approved revision of the table.
| Daily new-business band (USD, published 2023 table) | Band | Published VBW |
|---|---|---|
| 32,000,000 to below64,000,000 | 11 | 21.9 |
| 64,000,000 to below128,000,000 | 12 | 27.0 |
| 128,000,000 to below256,000,000 | 13 | 33.1 |
| 256,000,000 to below512,000,000 | 14 | 40.4 |
| 512,000,000 to below1,024,000,000 | 15 | 49.1 |
The method's approved boundary convention governs exactly what happens at a threshold. The relevant governed banking rule treats the lower bound as included and the upper bound as excluded; this article uses “to below” to make that explicit. Do not extrapolate a weight between listed VBWs or apply the 2023 US-dollar table to an unnormalized dataset without an approved conversion and time-basis rule.
An important data distinction: a recorded, verified zero amount is not the same as an absent, incomplete or failed activity feed. Under the governed calculation, missing data must be identified and resolved; it must not be silently put into the lowest band.
3. How is VBW used to calculate inherent Risk Units?
For a defined product p and principal-risk family r:
where EUF is the versioned family-specific structural exposure factor; VBW is the approved table weight corresponding to that product's daily new business; and IR is the resulting inherent exposure in Risk Units. [1, pp. 138–140]
For compatible risk families in the published product example:
Importantly, VBW = 33.1 does not mean the bank has 33.1 transactions, is likely to lose 33.1% of business value, or has US$33.10 of exposure. VBW is a method-defined weight. No expected monetary loss can be inferred without separate empirical calibration to loss outcomes.
The complementary mitigation step remains independent:
The reporting perimeter and assessment dates for the numerator, denominator and inherent RUs must match. [1, pp. 140–141, 164–168]
4. Worked example: selecting VBW for Commercial Loans
The figures below are taken from Hughes's fictitious, simplified 2023 banking example, not actual bank transactions. [1, pp. 144, 148–149, 161, 163, 166]
Step 1 — Identify the activity value and reporting basis
The example's Commercial Loans (Trade Receivables) product has US$147 million in daily new business. This is the input to the published product value-band lookup.
Step 2 — Select the discrete value-band weight
US147 million falls within the published US128 million to below US256 million band. The corresponding VBW is 33.1. It is not calculated by dividing US147 million by the dollar value of one RU, and it is not rounded to a preferred whole number.
Step 3 — Calculate the inherent exposure contributions
The same published example assigns EUFs of 10 (processing), 8 (lending), 2 (selling), 6 (funding), and 6 (interest-rate management). The compatible family calculations are:
| Risk family | EUF | VBW | Inherent RUs |
|---|---|---|---|
| Processing | 10 | 33.1 | 331.0 |
| Lending | 8 | 33.1 | 264.8 |
| Selling | 2 | 33.1 | 66.2 |
| Funding | 6 | 33.1 | 198.6 |
| Interest-rate management | 6 | 33.1 | 198.6 |
| Total | 32 | — | 1,059.2 |
Step 4 — Calculate residual exposure with the correct mitigation scope
For the whole product, the published aggregates are ASA = 28,956,542 and MSA = 42,593,080, implying RMI 67.9841% and residual exposure approximately 339.1 RU:
The 2023 source prints roughly 1,059 inherent and 339 residual RUs. This is a reproducible calculation under the example's specified inputs, not a financial-loss forecast. [1, p. 166]
Management interpretation: this formulation makes the role of business activity visible. If activity shifts to a different governed band, the VBW input changes; whether that leads to a useful or predictive exposure signal remains an empirical question.
5. VBW versus raw turnover or transaction counts
| Criterion | Raw monetary volume or transaction count | Risk Accounting's VBW |
|---|---|---|
| What it represents | Observed activity on its own measurement scale | Discrete weight assigned to an activity-value band |
| Unit | Currency or number of transactions | Method-defined weighting factor |
| Relationship with activity | Directly proportional by construction | Stepwise, non-proportional under the published value table |
| Structural complexity | Not specified by the measure alone | Explicitly accounted for separately via EUF |
| Control effectiveness | Not represented by activity alone | Added separately via E-RCSA and RMI |
| Can it predict monetary loss on its own? | No | No |
Both types of data remain necessary. The raw activity record is the verifiable input; the VBW is the governed transformation used by Risk Accounting. A stepwise weight may be well-defined and auditable without proving that its functional shape is optimal. That empirical question should be tested rather than assumed.
6. What would an auditor check in a VBW calculation?
An audit trail should identify: the product and time window; source transactions and exclusions; whether the activity amount is daily new business as defined for the selected version; original and normalized currency; the approved Value Table version; the selected band; exact threshold treatment; reviewer approval; and the resulting EUF–VBW calculation.
Particular attention is warranted where an institution substitutes outstanding balances, cumulative annual volume, payment counts or gross cash movements for the published banking method's defined daily-new-business input. Those metrics may be relevant under separately documented methods, but are not interchangeable by assumption. Similarly, a novel VBW chosen “between” two published values would break reproducibility unless a new version formally authorizes it.
The Basel Committee's operational-risk management principles and BCBS 239 risk data principles support the broader case for traceable risk data, governance and reporting. Neither specifies this particular VBW table or requires the use of Risk Units. [2][3]
7. Frequently asked questions
Is Value-Based Weighting the same as transaction volume?
No. A transaction amount or volume is the input used to select the weight under a defined model. VBW is the discrete table value associated with that input's approved band.
How is VBW calculated for $147 million of daily business?
In Hughes's published 2023 banking table, US147 million falls in the US128 million to below US$256 million band. That corresponds to VBW 33.1; the figure is looked up, not multiplied by the dollar amount.
Does a higher VBW mean greater expected financial losses?
Not necessarily. The model assigns higher inherent exposure weight to greater activity scale under its prescribed schedule, but an empirical mapping from resulting RUs to monetary-loss outcomes would require separate validation.
What happens if daily-new-business data is missing?
The calculation is incomplete until the missing input is resolved according to the governing rules. An unknown amount must not be treated as verified zero or automatically mapped into the lowest band.
8. Related terms, publications and research
Read Exposure Uncertainty Factor (EUF) for the structural half of the inherent-exposure calculation, followed by Inherent Risk vs. Residual Risk for its subsequent mitigation adjustment. The full measurement unit is introduced in What Is a Risk Unit?, and the control input is described in Risk Mitigation Index.
For the wider context see The Method. RASB's Payment Orders Risk-Exposure Study presents a separate synthetic demonstrator. Institutions interested in method testing can collaborate with RASB.
Return to the Risk Accounting Knowledge Base for the full glossary.
Additional perspectives: See Risk Accounting vs ERM and FAIR for the relationship to other risk methodologies, and Transaction-Level Risk Accounting for how exposure measurement relates to identifiable banking activity.
Sources
- Hughes, Peter J. Risk Accounting: The Complete Guide to Quantifying and Accounting for Non-Financial Risks (2023), especially pp. 138–140, 144, 148–149, 161, 163, 166–168. Bibliographic record. The banking example is fictitious and simplified.
- Basel Committee on Banking Supervision. Principles for the Sound Management of Operational Risk — FSI summary.
- Basel Committee on Banking Supervision. BCBS 239: Risk Data Aggregation and Risk Reporting.
- RASB. The Method. General overview; a distinct live-site payment example requires version reconciliation before serving as a governed example.
Explore Methodology & Empirical Research
Compare these definitions with the mathematical specifications on The Method or examine transaction-level operational risk quantification in the Payment Orders Study.
