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


---

# Overview of regulatory taxonomy

# Regulatory taxonomy overview {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Regulatory taxonomy simplifies identifying necessary changes in a customer's regulatory library by enabling algorithms to match incoming regulatory intelligence to existing content using taxonomy terms.

Regulatory change management products can integrate intelligence data from multiple vendors. However, these vendors differ in:

1. Delivery mode: File-based feeds vs. stream-based feeds.
2. Data format: XML, JSON, CSV, and so on
3. Taxonomy information: Contextual metadata added to regulatory intelligence, such as geography, sector, or regulatory body.

{#regulatory-taxonomy-overview__ol_s4m_5nf_ndc}  
Note:  
To integrate with any regulatory intelligence provider, you need an active subscription and a connector to ingest the provider's data. You can use connectors from the ServiceNow Store or build your own.

Some examples of taxonomy are as follows.

* Geography: Identifies applicable regions, for example, North America, Paris, or New Delhi.
* Sector: Defines relevant industries, for example, Banking, IT, or Logistics.
* Regulatory Body: Lists regulatory organizations, for example, NIST, European Central Bank.

{#regulatory-taxonomy-overview__ul_t4m_5nf_ndc}  
Some vendors include additional categories like regulatory themes or topics.  
Note:  
Access to external content requires an end-user license to authorize the credentials granted by technology partners.

## Benefits of mapping taxonomy {#regulatory-taxonomy-overview__section_l3c_d4f_ndc}

Users of Regulatory Change Management often use their own terms for business reasons, creating mismatches between external and internal taxonomies. For example, the vendor term could be North America while the users may term it as USA
and Canada or vendor term could be Singapore and the user term could be Southeast Asia. To ensure accurate mapping, administrators must manually align external taxonomy terms with their internal taxonomy. This process is known as
taxonomy mapping. Mapping taxonomies can sometimes be a challenge for many users. Regulatory Change Management provides the ability to integrate taxonomy-mapping capabilities. For more information, refer to [Map the taxonomy](https://servicenow-prod.fluidtopics.net/DwFto2jVC69yKZooePXq7g "Create an internal taxonomy when you are setting up the Regulatory Change Management application. Map the external taxonomy to the internal taxonomy so that the Regulatory Change Management application refers to only one taxonomy.").