iFIX specification details


iFIX is a fiscal data exchange platform that enables the exchange of standardized fiscal data between various agencies. iFIX is designed to enable the exchange of fiscal data between various agencies and ensure the visibility of fiscal data. iFIX makes it possible to chain the fiscal data with each other and establish a chain of custody for the entire lifecycle from budgeting to accounting.

From the iFIX perspective, there are two types of agencies

  1. Fiscal Data Provider - posts the fiscal data into iFIX using well-defined formats.

  2. Fiscal Data Consumer - can query the fiscal data.

Both these roles are interchangeable.


Providers and consumers need to register on iFIX before they can post or query fiscal data. To register the concerned person from the agency must be provided with the following information on the iFIX portal - Name of the Agency, Contact Person, Name, Contact Person’s Phone Number, and Contact Person’s Official Email Address. The OTP is sent to the registered email address of the person.

System Registration & Access Key Generation

Registered users -

  • logs in to the iFIX portal using the official email address

  • registers one or more systems as a provider, consumer or both

  • provides the name of the system

  • a unique ID is generated for each system (example: mgramseva@punjab.ifix.org)

  • a secret API key is also generated for each system - use this key to post or query fiscal data

  • The API key can be regenerated if required - only one API key is active at a given point in time

The portal provides the ability to generate new keys for each system.


Fiscal data providers post the fiscal data in two ways.

  • A fiscal message - is directed to a specific consumer and is delivered to intended consumers. These messages are available for query by intended consumers only.

  • A fiscal event - iFIX stores the events for consumers to query

Fiscal Event consists of

  • Header

    1. From

    2. To

    3. Date of Posting

  • Body

    1. Fiscal Event Type e.g. Revenue, Expenditure, Debt

    2. Fiscal Event Subtype

      • Revenue - Estimate, Plan, Demand, Receipt, Credit

      • Expenditure - Estimate, Plan, Bill, Payment, Debit

      • Debt - in progress - will be provided later.

    3. Array of fiscal line items

      • Amount

      • CoA

      • Location Code - from Location Registry

      • Program Code - from Program Registry

      • Project Code - from Project Registry

      • Administrative Hierarchy Code from Administrative Hierarchy Registry

      • Start Date of Period

      • End Date of Period

      • ….

      • ….

    4. Attachment - Attachments consist of additional attributes like key-value pairs e.g. Account Number, Correlation ID or Documents

    5. Signature - Fiscal messages can be signed by multiple agencies and add the signature to the Signature Array that contains the below-mentioned values -

      • Array of Signature

        1. System

        2. eSign - Signed Value of the Fiscal Event/Message Body using the System Key

        3. Purpose - Acknowledgement or Approval or Rejection


        5. Date of Signing


Data providers can reverse a previous fiscal message or event. The data provider reverses the data by posting the same event with a negative amount in the line item(s). The data consumers should handle reversals appropriately.


Data consumers can query fiscal data. They can query Messages - the unread messages delivered to them. When consumers read the unread messages, these messages are marked as read. Events - Consumers can also query fiscal events posted by other data providers.

Reference Data Management

  1. Location

  2. Administrative

  3. Chart of Account …. … …

Last updated

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.