Overview
Horizon Finance is built around the principle of standardized financial reporting, especially in environments with multiple entities using different local accounting systems. To achieve this, the platform uses two layers of reporting logic:
-
Global Reporting Master Data: A centralized "common data model" set by the ultimate customer.
-
Entity Reporting Master Data: A mapping layer used at the local entity level to align local GL codes with the global structure.
This article explains the role and structure of both components and how they interact to support accurate and consistent financial reporting.
π Global Reporting Master Data
What is it?
The Global Reporting Master Data represents the standardized financial framework adopted by the customer. It defines how all accounting data should be interpreted and structured across all entities, regardless of their source accounting system.
This master data can be accessed by navigating to:
Organisation / Fund Level β Settings β Reporting Master Data
Global Reporting Master Data Structure
| Column | Description | Level |
|---|---|---|
| Global Code | The most granular GL code defined globally. This is the base unit for mapping all entity-level GL codes. | Level 4 |
| Global Name | A description of what the Global Code represents. | Level 4 |
| Aggregate of Global Codes | A grouping of related Global Codes, summarizing them into a broader category. | Level 3 |
| Reporting Line Description | Aggregates Level 3 items. This is the label seen on financial statements. | Level 2 |
| GL Section | Top-level financial section in the Income Statement or Balance Sheet. | Level 1 |
β οΈ There are 11 predefined GL Sections, spread across two reports:
Income Statement
-
Revenue
-
Cost of Sales
-
Operational Costs
-
Below EBITDA
-
Other Comprehensive Income
Balance Sheet
-
Non-Current Assets
-
Non-Current Assets Depreciation
-
Current Assets
-
Current Liabilities
-
Non-Current Liabilities
-
Equity
Cash Flow Configuration Columns
| Column | Purpose |
|---|---|
| Indirect Cash Flow Tag | Identifies how the GL code impacts the Indirect Cash Flow Statement. There are 18 tagging options, including: |
-
Depreciation
-
Interest Paid
-
Purchase of Non-Current Assets
-
Foreign Exchange Gain/Loss
-
Repayment of Senior Debt, etc.
Note: Items already considered above EBITDA (e.g. Revenue) should be left blank. |
| Direct Cash Flow Category | Determines where tagged bank transactions appear in the Direct Cash Flow Statement. Categories include: -
Revenue
-
Operational Costs
-
Related Party Payments
-
Investing Activities
-
Financing Activities
-
Distributions and Transfers
-
Cash Flow from Operating Activities |
β Best Practice: Every Global Code should have a Direct Cash Flow Category assigned to ensure all tagged transactions contribute to the cash flow statement.
π’ Entity Reporting Master Data
What is it?
The Entity Reporting Master Data is where local chart of accounts (CoA) are imported by entity and mapped to the Global Codes defined in the Global Reporting Master Data.
This mapping process creates a bridge between local accounting systems and the centralized reporting logic.
How it Works:
-
A user imports the entityβs local GL codes into the system.
-
Each local GL code is then mapped to a Global Code.
-
Once mapped, all other columns (e.g. Reporting Line, GL Section, Cash Flow Categories) are automatically populated based on the Global Master structure.
π Changes to the Global Reporting Master Data will cascade down to the entity level, ensuring consistency.
π§© Summary
| Global Reporting Master Data | Entity Reporting Master Data |
|---|---|
| Set once by the customer | Set individually per entity |
| Standardizes financial structure | Aligns local CoA with global view |
| Used to generate statements and reports | Used to tag imported GL data |
| Editable only by Admin users | Editable by users with mapping permissions |
Comments
0 comments
Please sign in to leave a comment.