--- sourceDocument: Australia Governance, Risk, and Compliance sourceDocumentLink: https://www.servicenow.com/docs/r/australia/governance-risk-compliance Release : - australia ft:locale : - en-US ft:publication_title : - Australia Governance, Risk, and Compliance ft:clusterId : - grc bundleId : - grc workflow : - Technology --- # Currency conversion and third-party expense aggregation # Currency conversion and third-party expense aggregation {#ariaid-title1} Release version: Australia Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Currency conversion and third-party expense aggregation The Register of Information (RoI) under the Digital Operational Resilience Act (DORA) requires converting contract annual expenses to a base currency and aggregating totals by third-party providers or engagements. This functionality is supported by the Digital Resilience Third-party Information Register within the Vendor Management Workspace application in ServiceNow. Show full answer Show less During report generation, two optional features---currency conversion and third-party total expense aggregation---can be enabled to standardize and consolidate expense data in export reports (Plain-CSV and Excel Master Template). These options do not affect underlying records and must be enabled per export request. ## Currency Conversion * Converts contract expenses into a single base currency using historical exchange rates from the European Central Bank (ECB), based on the report's Reference Date. * Converted values appear only in the exported reports; original contract records remain unchanged. * Useful when contracts have multiple currencies or when standardized currency reporting is required. * Disabling is recommended if all contracts are already in the base currency or if original currency values must be preserved. * Currency rates are updated automatically daily and can be managed by administrators to comply with regulatory rules. * Conversion success and failure are documented through summary and detail reports included in export packages. * If conversion fails for a contract, the original currency and amount are retained in the output. ## Third-party Total Expense Aggregation * Aggregates annual expenses across all contracts linked to the same third-party provider or engagement into a single total in exported reports. * Aggregation only occurs if eligibility criteria are met, including defined contract structures and currency alignment (all in base currency or successfully converted). * If any contract fails eligibility or conversion, manual entry values appear instead, serving as a fallback. * Aggregation results and ineligible cases are detailed in summary and skipped contracts reports within the exports. * Maintaining up-to-date manual entry values is important for providers not qualifying for aggregation. ## Interaction and Reporting * Currency conversion and aggregation operate independently but can be combined; successful conversion enables aggregation for multi-currency contracts. * Failed currency conversion for any contract prevents aggregation for that provider. * Exports generate ZIP packages with CSV files structured per regulatory specifications, including consolidated reports summarizing conversion, aggregation, and validation outcomes when these features are enabled. ## Practical Considerations for ServiceNow Customers * Enable currency conversion and aggregation only as needed per report export to ensure compliance with DORA requirements. * Validate currency rates and exchange dates before generating reports to avoid conversion errors. * Review generated summary and detail reports to verify successful conversions and aggregations. * Keep manual entry data current for providers that cannot be aggregated automatically. * Use the platform's administrative tools to maintain exchange rate data and validation rules aligned with regulator demands. During report generation, the Register of Information (RoI) converts contract annual expenses to a base currency. It then aggregates totals per eligible third-party provider or engagement. The RoI is a regulatory reporting requirement under the Digital Operational Resilience Act (DORA) and is supported by the Digital Resilience Third-party Information Register application in the Vendor Management Workspace application. ## Currency and aggregation overview {#tprm-dora-currency-aggregation__overview} The DORA Register of Information Digital Resilience Third-party Information Register provides two optional features during report generation: currency conversion and third-party total expense aggregation. These features standardize and consolidate annual expense data in the Plain-CSV reporting package and the Excel Master Template. You enable these options per export request on the Excel download/upload request page when generating an Excel Master Template or a Plain-CSV Reporting Package. Both features are disabled by default and apply only to exported reports, not to the underlying contract or third-party records. Administrators maintain the currency rates and validation rules. Currency rates populate automatically using a daily scheduled job once the instance is activated. Administrators or DORA administrators can update currency rates and validation rules to align with regulator requirements by navigating to AllDigital Operational Resilience ManagementDigital Resilience Choices or DPM Business Validation Rules. ## Currency conversion {#tprm-dora-currency-aggregation__currency-conversion} Currency conversion converts each contract's annual expense into a single base currency using historical exchange rates from the European Central Bank (ECB). The Reference Date on the report determines which exchange rate is used. Converted amounts appear only in the generated reporting package; source records remain unchanged. Enable conversion when contracts span multiple currencies, when reporting requires a standardized currency, or when you plan to aggregate provider totals but contract currencies are inconsistent. Disable it when all amounts already use the base currency or when preserving original currencies is required. When conversion is enabled, the system produces a Currency Conversion Summary Report. If any conversion fails (for example, because a rate is unavailable or a currency code is invalid), the system also produces a Currency Conversion Detail Report. General guidelines: * Set the Reference Date to the last day of the reporting period (for example, 2025‑12‑31). * Ensure ECB exchange rates are available in the platform for the selected date. * Validate results with a small test export before running large data sets. Note: If a conversion fails for a contract, the original currency and amount are retained for that contract in the exported output. ## Third-party total expense aggregation {#tprm-dora-currency-aggregation__third-party-aggregation} Aggregation consolidates annual expenses across all contracts that belong to the same third-party provider or third-party engagement. The result appears as a single combined value in the exported reporting output. Aggregation runs only when all eligibility criteria for a provider are satisfied. Eligibility rules: * Contract structure: Certain contract configurations, such as multi-provider contracts, can make a provider ineligible for aggregation (for example, when split ratios are not defined). * Currency alignment: All contract amounts must be in the base currency or successfully converted. * If conversion is enabled, every required conversion must succeed. * If conversion is disabled, all contracts must already use the base currency. If aggregation is disabled on the request or if any eligibility rule is not met, the system reports manual entry values for that provider. Manual entry serves as the fallback for providers that do not aggregate. When aggregation is enabled, the system produces an Aggregation Summary Report and, when providers are ineligible, a Skipped Contracts Detail Report explaining why aggregation did not occur. Important: Keep manual entry values current for providers that may not qualify for aggregation. ## Relationship between conversion and aggregation {#tprm-dora-currency-aggregation__relationship} Currency conversion and aggregation operate independently but can be combined. Successful conversion can enable aggregation when a provider's contracts use different currencies. Any failed conversion for a provider prevents aggregation for that provider. ## Reports and exports {#tprm-dora-currency-aggregation__reports-and-outputs} When you generate a Plain-CSV reporting package, the platform produces a ZIP package structured to regulator specifications, containing the required CSV files and supporting metadata. When enabled, the package also includes consolidated reports that summarize currency conversion results, aggregation outcomes, and validation findings. Conversion-related reports appear only when currency conversion is enabled. Aggregation-related reports appear only when aggregation is enabled. **Related concepts** * [Register of information regulatory packages](https://www.servicenow.com/docs/KJKt1InLPwVQr8A6g18ZqA "The Register of Information (RoI) is a regulatory reporting requirement under the Digital Operational Resilience Act (DORA) and is supported by the Digital Resilience Third-party Information Register application in the Vendor Management Workspace.") **Related tasks** * [Aggregate contractual expenses in required currencies](https://www.servicenow.com/docs/VD5QlDz2BDqGXD2JcX6vuA "Convert and aggregate contractual expenses to regulator-required currencies and generate consolidated reports for reporting submission.") *[\>]: and then