Currency conversion and third-party aggregation

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
  • Summarize
    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 aggregation for DORA (Digital Operational Resilience Act) reporting of third-party expenses. These features enable users to convert expenses from multiple currencies into a regulator-required base currency using automated daily exchange rates and to aggregate expenses across multiple contracts for the same provider.

    Show full answer Show less

    Key Features

    • Independent enablement: Currency conversion and third-party expense aggregation can be enabled independently or together, providing flexibility based on your specific DORA reporting requirements.
    • Aggregation logic: When both features are enabled, aggregation is performed on converted base-currency values. Raw contract amounts are summed before rounding to the nearest whole unit of the base currency.
    • Report generation: You can configure currency conversion and aggregation settings when creating Excel download and upload requests to produce consolidated reports.
    • Report outputs: The application generates two report formats:
      • Primary download report: Microsoft Excel analysis for internal use.
      • Plain-CSV package: Designed for regulatory submission with Level 3 validation, including fields such as Competent Authority, Reference Date, and Date of Reporting.
    • Validation and messages: Reports include conversion and aggregation success or failure details with explanatory messages to aid troubleshooting.
    • Non-destructive processing: Currency conversion and aggregation apply only to reports and do not alter underlying contract or third-party data.
    • Automated currency rates: Currency rates are populated automatically daily after instance activation, with fallback default rates if specific date rates are unavailable.
    • Administrator controls: DORA administrators are responsible for maintaining up-to-date business validation rules and can manually add historical currency rates if needed.

    Administrator Prerequisites

    • Ensure the DPM business validation rules table is current and aligned with regulator requirements; new rules can be added without waiting for platform upgrades.
    • Verify currency conversion rates are populated automatically; administrators can add historical rates using background scripts as necessary.

    Practical Benefits for ServiceNow Customers

    • Streamlines compliance with DORA regulatory reporting by automating multi-currency expense conversion and third-party expense aggregation.
    • Supports accurate, consolidated financial reporting for third-party contractual expenses across providers and currencies.
    • Provides configurable reporting outputs tailored for both internal analysis and official regulatory submissions.
    • Reduces manual effort and errors through automated currency rate updates and validation rules management.

    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 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

    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

    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.

    Business validation rules.System currency conversion rates.

    Related documentation

    For information on creating a Microsoft Excel download and upload request and generating the reports, see Create Microsoft Excel download and upload request.

    For steps on converting and aggregating contractual expenses to regulator-required currencies, see Convert and aggregate contractual expenses to regulator-required currencies.