> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/public-finance/v2.3/exemplar/ifix-dashboard/architecture.md). # Architecture Fiscal Event services flatten each fiscal event line item and post them into Druid via the Kafka Druid connector. The raw events are stored in the fiscal-events dataset in Druid. [Metabase ](https://www.metabase.com/)is used for visualisations. The flattened fiscal event consists of the following attributes | Attribute | Description | | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | version |

string
example: 1.0.0

Version of the Data Model Definition

| | id |

string
example: 51c9c03c-1607-4dd5-9e0e-93bbf860f6f7

System generated UUID of Line Item

| | eventId |

string
example: fecbbf1d-d6e3-4f24-9935-02c33b9248e0

Fiscal Event Reference Id

| | tenantId |

string
nullable: false
example: pb

Tenant Id

| | government.id |

string
example: pb

| | government.name |

string
example: Punjab

| | department.id |

string
example: 5d664a9f-9367-458a-aa5f-07fb18b90adc

Unique system generated UUID

| | department.code |

string
example: DWSS

Unique department code

| | department.name |

string
example: Department of Water Supply & Sanitation

Name of the department

| | expenditure.id |

string
example: d334d99a-b5c1-426c-942b-f11b5b5454fe

Unique system generated UUID

| | expenditure.code |

string
example: JJM

Unique Expenditure code

| | expenditure.name |

string
example: Jal Jeevan Mission

Name of the Expenditure

| | expenditure.type |

string

Type of the Expenditure Enum:
Array \[ 2 ]

| | project.id |

string
example: 6ab1b1d2-e224-46fa-b53b-ac83b3c7ce95

Unique system generated UUID

| | project.code |

string
example: PWT

Unique Project code

| | project.name |

string
example: Peepli Water Tank

Name of the Project

| | eventType |

string
nullable: false
example: Appropriation

Captures the event type e.g Demand, Receipt, Bill, Payment

| | eventTime |

integer($int64)
example: 1628177497000

when the event occurred at source system level

| | referenceId |

string
example: 013e9c56-8207-4dac-9f4d-f1e20bd824e7

reference unique id(transaction id) of the caller system

| | parentEventId |

string
nullable: true
example: 7d476bb0-bc9f-48e2-8ad4-5a4a36220779

If this is a follow up event then it will refer to the parent event using this reference id.

| | parentReferenceId |

string
nullable: true
example: 77f23efe-879d-407b-8f23-7b8dd5b2ecb1

If this is a follow up event then it will refer to the parent event in source system using this reference id.

| | amount |

number
example: 10234.5

Transaction Amount

| | coa.id |

string
example: e9f940d4-69aa-4bbb-aa82-111b8948a6b6

Unique system generated UUID

| | coa.coaCode |

string
example: 1234-123-123-12-12-12

Chart of account concatenated string

| | coa.majorHead |

string
example: 1234

Major head code

| | coa.majorHeadName |

string

Major head name

| | coa.majorHeadType |

string
example: Revenue

Major head code type

| | coa.subMajorHead |

string
example: 123

Sub-Major head code

| | coa.subMajorHeadName |

string

Sub-Major head name

| | coa.minorHead |

string
example: 123

Minor head code

| | coa.minorHeadName |

string

Minor head name

| | coa.subHead |

string
example: 12

Sub-Head code

| | coa.subHeadName |

string

Sub-Head name

| | coa.groupHead |

string
example: 12

Group head code

| | coa.groupHeadName |

string

Group head name

| | coa.objectHead |

string
example: 12

Object head code

| | coa.objectHeadName |

string

Object head name

| | fromBillingPeriod |

integer($int64)
example: 1622907239000

Start date of the billing period for which transaction is applicable

| | toBillingPeriod |

integer($int64)
example: 1628177643000

Start date of the billing period for which transaction is applicable

| > [![Creative Commons License](https://i.creativecommons.org/l/by/4.0/80x15.png)*​*](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation*](https://egov.org.in/) *is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)*.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digit.org/public-finance/v2.3/exemplar/ifix-dashboard/architecture.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.