{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":18484,"path":"governance-risk-compliance/third-party-risk-management/tprm-dora-currency-aggregation.md","title":"Currency conversion and third-party expense aggregation","bundle":null,"doc_type":null,"release":"australia","body":"\n# Currency conversion and third-party expense aggregation\n\nDuring 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.\n\n## Currency and aggregation overview\n\nThe 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.\n\nYou 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.\n\nAdministrators 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 **All** > **Digital Operational Resilience Management** > **Digital Resilience Choices** or **DPM Business Validation Rules**.\n\n## Currency conversion\n\nCurrency 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.\n\nEnable 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.\n\nWhen 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.\n\nGeneral guidelines:\n\n-   Set the Reference Date to the last day of the reporting period \\(for example, 2025‑12‑31\\).\n-   Ensure ECB exchange rates are available in the platform for the selected date.\n-   Validate results with a small test export before running large data sets.\n\n**Note:** If a conversion fails for a contract, the original currency and amount are retained for that contract in the exported output.\n\n## Third-party total expense aggregation\n\nAggregation 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.\n\nEligibility rules:\n\n-   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\\).\n-   Currency alignment: All contract amounts must be in the base currency or successfully converted.\n    -   If conversion is enabled, every required conversion must succeed.\n    -   If conversion is disabled, all contracts must already use the base currency.\n\nIf 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.\n\nWhen 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.\n\n**Important:** Keep manual entry values current for providers that may not qualify for aggregation.\n\n## Relationship between conversion and aggregation\n\nCurrency 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.\n\n## Reports and exports\n\nWhen 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.\n\nWhen enabled, the package also includes consolidated reports that summarize currency conversion results, aggregation outcomes, and validation findings.\n\nConversion-related reports appear only when currency conversion is enabled. Aggregation-related reports appear only when aggregation is enabled.\n\n**Related topics**  \n\n\n[Aggregate contractual expenses in required currencies](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/third-party-risk-management/tprm-create-report-aggregate-expenses.md)\n\n[Register of information regulatory packages](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/third-party-risk-management/tprm-dora-roi.md)\n\n"}}