Risk: Frequently Asked Questions

Possible reasons:

• The feature flag needs to be enabled by the Ripple Treasury Support team for it to be visible to you.

• Spotlights are currently only available for Interest Rate analyses, not FX analyses.

• All changes in your data are below the detection thresholds (e.g., rates changed by 0.9% when 1% or more is required).

• Charts may still be loading.

• There's missing data that prevents trends from loading.

• You don’t have policy limits. Policy limits are required for compliance spotlights to generate.

• The analysis period is too short. You need at least 2 periods for trend detection.

Not directly. Spotlight thresholds are pre-configured (e.g., 1% or more for rate changes, 1% or more for scenario risk) to ensure only significant issues are highlighted.

This happens when:

• You refreshed your analysis data and the trend no longer exceeds the detection threshold.

• Policy limits were adjusted, bringing them back into compliance.

• Forecast data was updated with new information.

Spotlights are generated fresh each time an analysis is viewed based on the current data.

No. Spotlight thresholds are pre-configured (e.g., 1% or more for rate changes, 1% or more for scenario risk) to ensure only significant issues are highlighted.

Typical loading times:

• Spotlights: Instant (generated when opening the page)

• Deep Dives: 5-15 seconds after clicking

• Executive Summary: 10-20 seconds (more content to process)

Yes. Your data is:

• Only used to generate your specific insights.

• Not shared with other users.

• Processed in compliance with data privacy regulations.

No. Ripple Treasury doesn’t automatically update holiday calendars, including federal holidays. This approach ensures flexibility for our global client base, as holiday schedules vary widely by country, region, and organization.

• Global complexity: There is no universal holiday standard. Automating updates could introduce errors or conflicts with your internal policies.

• Direct control: You have full control to maintain a holiday calendar that reflects your organization’s needs.

• Accuracy: This prevents unintended changes that could impact payment dates, settlements, or other time-sensitive processes.

Review and update your holiday calendar regularly to include all relevant holidays (e.g., federal, regional, and company-specific). Keeping this calendar current ensures accurate date calculations across your workflows.

We are exploring foundational improvements to make holiday calendar management more unified and easier for clients. We’ll keep you informed as these enhancements progress.

Refer to Holiday Centers and Holidays: Create and Edit or contact your Ripple Treasury support team for assistance.

Permissions for versioning a deal are the same as those for renegotiating a deal:

• Renegotiate

• Submit renegotiation

• Unsubmit renegotiation

Versioning is only an option for (IR) deals that don’t have a custom schedule. A custom schedule means the events for the deal are explicitly determined by the user.

The day you select the Version button becomes the effective date for that new version.

Only one version of a deal is allowed per day. If you need a new version on a day that already has a version, unwind the version to edit it.

Versioning only regenerate events occurring after the last Authorized, Settled, or Exported event. Future events that have been settled or exported need to be unwound if you want them to be regenerated by the versioning process.

You can’t unwind a version if an event has been Authorized or Settled since the version was created. You can unwind the event to unwind the current version or you can create a new version.

No. In facilities, a tranche's limit is the sublimit, and it must be greater than zero. The supported way to express "no sub-allocation" is Fixed Shared with each tranche limit set equal to the full facility limit, so only the single facility limit constrains total drawings. A facility without tranches isn’t offered in the facility picker on the deal and drawdown screen, so it can’t be drawn against.

The closest thing to not having a sublimit is the Fixed Shared behavior itself. It sets every tranche limit equal to the full facility limit. Each line is then individually uncapped relative to the facility, and only the shared facility limit constrains total drawings.

It it possible to create this configuration, but we strongly recommend against it. For Fixed and Fixed Shared facilities, if any tranche currency differs from the facility currency, Ripple Treasury stops calculating facility utilization and skips the facility-level breach validation. The shared limit silently stops being enforced. Use one currency per facility.

Not formally. A facility carries exactly one business unit and there is no way to share with additional business units. Each tranche does have its own editable business unit (defaulted from the facility), so one facility can technically hold tranches from multiple business units and shared-limit enforcement still works facility-wide. But the facility’s grid and facility-level reporting only show the one facility-level business unit.

One limit pool across the tranches of one facility. It doesn't pool across currencies, business units, counterparties, or facilities. Syndication is a separate lender-allocation feature, not a business-unit sharing mechanism.

You can only delete facilities before deals are drawn against them.

After drawing tranches or facility fees against a facility, don’t attempt to delete the facility. Instead, let it run off or shorten its maturity. If historic deals must be re-pointed to a new deal, it must be done by Ripple Treasury Support.

At our organization, if the accounts are custodial, we utilize MT950 and MT535 messages via SWIFT that are provided by our custodian banks to report cash and sweep balances and transactions. We have separate Account IDs setup to reflect the cash balance and sweep balance of the custodial account. For cash management banks, we have not been able to get reporting on the sweep account. We are exploring leveraging a worksheet to calculate a balance based on sweep activity reported from our previous day file. It may be difficult for banks to provided Investment Account activity that include balances, movements and interest, not to mention there may be additional bank fees in order to provide that detail. That said, for account sweeps, Ripple Treasury users have benefited by creating virtual accounts, like money market funds, savings accounts, and even CD’s. Since transactional movements occurs at the DDA and is recorded on the daily balance reporting, the reverse will occur at the investment account level (a movement from the DDA account to a money market account, then back to the DDA with interest). You can create this movement within the sweep transaction assignment rules under “Actions Field Assign”. Note that a Sweep Debit on the DDA would be a Sweep Credit (User Code to Assign) to the investment account. You can also use the same action field assign section for Interest.

Please reach out to your Account Manager if you would like someone to walk you through this process. We have other ways of producing this activity if data is unavailable, including purchases, redemptions, and interest/accrual calculations.