--- sourceDocument: Australia Governance, Risk, and Compliance sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/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 aggregation # Currency conversion and third-party aggregation {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 aggregation Starting with Digital Operational Resilience Management (sndoraaccel) version 22.x.x, ServiceNow supports currency conversion and third-party expense aggregation for DORA reporting. These features enable users to convert contractual expenses from multiple currencies into a regulator-designated base currency using automated daily exchange rates and to aggregate expenses across multiple contracts per provider. Show full answer Show less ## Key Features * **Independent Enablement:** Currency conversion and third-party aggregation can be enabled separately or together based on your reporting needs. * **Expense Aggregation:** Raw contract amounts are summed across contracts for each provider before rounding to the nearest whole unit of the base currency. * **Report Generation:** Supports creation of Microsoft Excel downloads for analysis and Plain-CSV packages for regulatory submissions, including Level 3 validation and required fields (Competent authority, Reference date, Date of reporting). * **Automated Currency Rates:** Daily scheduled jobs automatically populate currency rates; administrators can update rates or add historical values as needed. * **Validation Rules Maintenance:** Administrators must keep business validation rules current to comply with regulator requirements; new rules can be added without waiting for platform releases. * **Non-destructive Reporting:** Conversion and aggregation affect only report outputs and do not modify underlying contract or third-party records. ## Administrator Responsibilities * Verify and maintain the DPM business validation rules table to reflect current regulatory requirements. * Ensure system currency conversion rates table is populated and accurate; add historical rates as necessary. ## Practical Impact for ServiceNow Customers This functionality streamlines the preparation of DORA reports by automating currency conversions and consolidating third-party expenses, ensuring compliance with regulatory standards. Users can generate comprehensive, validated reports suitable for submission, while administrators retain control over currency rates and validation rules to align with evolving regulations. Beginning with Digital Operational Resilience Management (sn_dora_accel), version 22.x.x, currency conversion and third-party aggregation capabilities are supported for DORA reporting of third-party expenses. As a DORA application user, you can convert and aggregate contractual expenses from multiple currencies to a regulator-required designated base currency using automated daily exchange rates. ## Supported capabilities {#currency-conversion-aggregation__section_psl_wsm_m3c} Currency conversion and third-party total expense aggregation are independently optional. You can enable either feature on its own or together, depending on your DORA reporting requirements. When both are enabled, aggregation uses the converted (base-currency) values. Note: Raw (un-rounded) contract amounts are summed first across all contracts for a given provider; the total is then rounded to the nearest whole unit of base currency. When creating an Excel download and upload request for DORA reporting, you can configure currency conversion and third-party aggregation settings to generate consolidated reports. Third-party aggregation consolidates expenses across multiple contracts associated with the same provider. You can enable both currency conversion and aggregation features independently as optional features, providing flexibility based on DORA reporting requirements. When creating a Plain-CSV reporting package (for regulatory submission), the following fields are required in addition to the standard entity details: Competent authority (for example, "CA"), Reference date (for example, 2025-12-31), Date of reporting (for example, 2026-01-28). ## Report outputs {#currency-conversion-aggregation__section_oc1_ysm_m3c} The application generates two types of reports to support regulatory conformance. The Primary download report provides Microsoft Excel based analysis, while the CSV package is designed for regulatory submission and includes Level 3 validation. Summary reports generated with both types display conversion and aggregation success or failure details with explanatory messages when issues occur. Currency conversion and aggregation apply to generated report outputs and do not modify underlying contract or third-party records. ## Currency rates and validation rules {#currency-conversion-aggregation__section_q1b_ysm_m3c} Once you activate the instance, currency rates populate automatically via a daily scheduled job. Administrators or DORA administrators can update currency rates and validation rules to align with regulator requirements. If specific date rates aren't available, the system uses fallback default rates. The validation rules table must be maintained to stay current with regulatory requirements. Administrator prerequisite: Before generating reports, a DORA administrator must verify two maintenance areas: 1. DPM business validation rules table --- must be kept current with regulator requirements; new rules can be added by the administrator without waiting for a platform release. 2. System currency conversion rates table --- populated automatically by a daily scheduled job once the instance is activated. Administrators can add historical rates via background script. If rates are unavailable for the reference date, the system falls back to default rates. The following examples illustrate business validation rules and system currency conversion rates. ## Related documentation {#currency-conversion-aggregation__section_otb_ysm_m3c} For information on creating a Microsoft Excel download and upload request and generating the reports, see [Create Microsoft Excel download and upload request](https://servicenow-prod.fluidtopics.net/zLC_ZfjztxC1koXsH~PdlA "Create a Microsoft Excel upload and download request to upload and download the records from and into the Digital resilience third-party registers for auditing purposes."). For steps on converting and aggregating contractual expenses to regulator-required currencies, see [Convert and aggregate contractual expenses](https://servicenow-prod.fluidtopics.net/7uwah8KcKYLoMbsMmBtyvw "Convert and aggregate contractual expenses to regulator-required currencies and generate consolidated reports for reporting submissions. Beginning with Digital Operational Resilience Management (sn_dora_accel), version 22.x.x, these currency conversion and third-party aggregation capabilities are supported for DORA reporting."). * **[Convert and aggregate contractual expenses](https://servicenow-prod.fluidtopics.net/7uwah8KcKYLoMbsMmBtyvw)** Convert and aggregate contractual expenses to regulator-required currencies and generate consolidated reports for reporting submissions. Beginning with Digital Operational Resilience Management (sn_dora_accel), version 22.x.x, these currency conversion and third-party aggregation capabilities are supported for DORA reporting.