Visits: 1
Requirements for XBRL-GL SRCD Taxonomy Using XBRL-CSV with Hierarchical Tidy Data Structure
1. Prerequisite Understanding XBRL-GL
SRCD Taxonomy with XBRL-CSV
1.1. Difference Between FR and GL
XBRL Financial Reporting (FR) and Global Ledger (GL) serve distinct purposes:
-
XBRL FR: Used for high-level financial reporting like balance sheets and income statements for external stakeholders. Elements in XBRL FR summarize financial data.
-
XBRL GL: Captures detailed, transaction-level information for internal use, such as audit trails and operational reporting. It requires a finer granularity of ata, with elements capturing every minute detail of financial transactions.
1.2. Role of SRCD in XBRL-GL
The SRCD module connects detailed GL data with FR summaries:
-
It ensures that every transaction in XBRL-GL can be mapped to a summarized element in XBRL-FR, providing traceability and transparency in financial reporting.
-
In the context of XBRL-GL and XBRL-FR, the SRCD (Summary Reporting Contextual Data) module acts as a connector that maps detailed transactions to summary-level data for financial reporting.
-
Taking the salary payment example, here’s how SRCD would facilitate its reporting to an FR taxonomy and instance:
GL Level (Detailed Transaction):
-
At the GL level, the transaction is recorded with all specifics: date (2024-01-25), amount (10,000 USD), debit entry to “Salary Expense” (Account 4001), and credit entry to “Bank Account” (Account 5001).
SRCD Usage:
-
SRCD would then be used to define how this GL entry detail relates to the FR taxonomy. It would specify that the “Salary Expense” account at the GL level corresponds to a particular “Salary Expense” element within the FR taxonomy.
FR Level (Summarized Reporting):
-
In the FR instance, instead of listing individual transactions, the data would be aggregated to show total salary expenses for a period. SRCD ensures that the aggregated amount in the FR instance is directly traceable to individual transactions in the GL, maintaining the relationship between the detailed data and the summary report.
By using SRCD, stakeholders can see not just the summarized figures in the financial statements but also have the capability to drill down to the transactional details if necessary, enhancing the transparency and usability of financial data.
1.3. Hierarchical Tidy Data in XBRL-CSV
A hierarchical tidy data structure using XBRL-CSV might look like this for a salary payment:
| header | line | entry date | header comment | dr/cr indicator | account number | account name | amount | entry comment |
|---|---|---|---|---|---|---|---|---|
|
1 |
2024-01-25 |
Payment for monthly salary for John Doe |
||||||
|
1 |
1 |
Debit |
4001 |
Salary Expense |
10000 |
Salary payment to John Doe |
||
|
1 |
2 |
Credit |
5001 |
Bank Account |
10000 |
Payment from Bank Account |
In this structure:
-
Header Layer: Contains the date and a description of the overall
transaction. -
Line Item Layer: Breaks down the transaction into debits and credits,
specifying accounts and amounts.
|
Note
|
In the context of the XBRL-GL to XBRL-FR data mapping, the ‘Salary’ account (with the account number 4001) represents the transaction detail at the GL level. This account number corresponds to a ‘Salary Expense’ element within the FR taxonomy. However, there is no direct ‘Salary’ element in GL; it’s an element in FR where such expenses are summarized for reporting purposes. This distinction is crucial for understanding the data structure and the mapping process between detailed ledger entries (GL) and summarized financial statements (FR). |
Further details can be found at the following link; The New Era of Data Conversion: Semantic and Syntactic Binding through Hierarchical Tidy Data
Another blog page to be checked: Why Consider a Dimension Only Approach For XBRL GL – Part 2 –
2.
Requirements for XBRL-GL SRCD Taxonomy Using XBRL-CSV with Hierarchical Tidy Data Structure
-
Element Differentiation: Define distinct elements for XBRL Financial Reporting (FR) and Global Ledger (GL), with FR focusing on summary financial data and GL on detailed transactional data.
-
SRCD Module Implementation: Utilize the SRCD module to link detailed XBRL-GL data with summarized XBRL-FR data, ensuring traceability from transaction-level details to summarized data.
-
XBRL-CSV Format Utilization: Adopt XBRL-CSV for efficient handling of large datasets, incorporating a hierarchical tidy data structure to represent complex types, such as tuples in XBRL-GL standards.
-
Data Integrity and Compliance Standards: Establish rules and protocols for maintaining data integrity and ensuring compliance with financial reporting standards.
-
Comprehensive Documentation: Provide detailed documentation and user guidelines for implementing and using the XBRL-GL SRCD taxonomy.
-
User-Friendly Interface and Accessibility: Develop intuitive tools for easy access and manipulation of XBRL-GL SRCD taxonomy data.
-
ISO Audit Data Services Standards Integration: Incorporate classes and properties from ISO standards to enhance representation of financial data in a structured, dimensional format.
-
Taxonomy Structure Definition: Clearly outline the structure of the XBRL-GL SRCD taxonomy, detailing all necessary financial elements, attributes, and relationships.
-
Dimensional Modeling: Specify the interaction of different dimensions such as time periods, geographical locations, or organizational units with financial elements.
-
Hierarchical Tidy Data Structure Requirement: Ensure data is organized hierarchically to represent complex relationships within the financial data accurately.
-
XBRL-CSV Format Specification: Clearly describe how XBRL-GL data should be
formatted within XBRL-CSV files, including layout and tag associations. -
Linkbase Utilization: Explain the use of dimension linkbase to establish relationships between taxonomy elements and facilitate multidimensional analysis.
-
Validation Rules for Compliance and Accuracy: Implement validation rules to ensure XBRL-GL data accuracy within the SRCD taxonomy.
-
Use Cases and Examples: Illustrate the XBRL-GL data structure in XBRL-CSV format using practical examples, such as the payment of a salary. For instance, an entry dated 2024-01-25 with the header comment “Payment for monthly salary for John Doe” could include debit lines for “Salary Expense” and credit lines for “Bank Account” transactions, demonstrating the hierarchical relationship between the entry header and individual line items.
-
Documentation and Support: Offer comprehensive support materials to facilitate the effective use of the taxonomy.
Q.E.D.
Nobuyuki SAMBUICHI
Advisor at XBRL Japan
ISO/TC295 Audit data services
Convener at SG1 Semantic model
Co-project leader at WG1 AWI 21926 Semantic data model for audit data services
Liaison representative from XBRL International Inc.
