Welcome to the Consumer Data Right Support Portal

Check out our guides, browse through our FAQs, and post your own questions for Support.

New to the Consumer Data Right? Learn more

Guidance on BankingProductLendingRateV2 fields Follow

Comments

2 comments

  • Avatar
    Rod Dalrymple

    Just some minor corrections:

    • Example product data structure (subset) > ... three fixed rates with different criteria and conditions
      Each bullet point similar to "... from $50K-$25MM" should use a single M for million and should be either  "... from $50K to $25M" or "... $50K-$25M"
    • FIXED lending rate period
      '... additionalValue should contain "PY30" ' should have the value "P30Y" as per ISO 8601 Durations (and the example itself eg. "additionalValue": "P4Y")

    0
    Comment actions Permalink
  • Avatar
    Rod Dalrymple

    The example JSON in the new section 'Example product data structure (subset)' applies a still-open change proposal (#614 Definition of PERCENT in BankingProductRateTierV3) by applying the RateString datatype to tiers[].minimumValue and maximumValue:

    • "tiers": [{ "name": "Loan-to-Value Ratio (LVR)", "unitOfMeasure": "PERCENT", "minimumValue": 0, "maximumValue": 0.8

    ANZ's comment in #614 contends that the proposed change is unnecessary as the common Unit of Measure pattern is deliberately generic, with the simple Number datatype for unitOfMeasure - irrespective of the unitOfMeasure enumeration value. The current standards with PERCENT = 80 is the natural and literal interpretation of the data, whereas a value of 0.8 should have a new/changed unitOfMeasure enumeration of 'RATE' or 'RATIO' to align with the RateString datatype. Removing this consistency would complicate consumption implementations.

    #614 was also referenced in the answer to ticket #2407 in the 8/8/24 implementation meeting with the statement "The intent is that rates (percentages) are generally described as a RateString across the Standards for consistency". The current use of PERCENT is for loan-to-value ratios (LVR). These are true ratios of distinct financial concepts, not simple rates (ie. a mathematical expression that can be applied to any numerical figure, typically for interest rates for monetary amounts) as supported by the RateString datatype.

    Guidance articles should use the existing standards. If #614 is adopted (hopefully it's not) this article could then be updated.

    0
    Comment actions Permalink

Please sign in to leave a comment.