eGov Foundation
Search…
v2.0-alpha
iFIX
Specification
Platform
Exemplar
Ecosystem
Community
Roadmap
Discussions
Issues
Powered By GitBook
Specification
Work in Progress
iFIX is a fiscal data exchange platform that enables exchange of standardized fiscal data between various agencies. iFIX should be designed to enable exchange of fiscal data between various agencies as well as ensuring visibility of fiscal data. Using fiscal data in iFIX, it should be possible to chain the fiscal data with each other and establish a chain of custody for the entire lifecycle from budgeting to accounting.
From iFIX’s perspective, there are two types of agencies
  1. 1.
    Fiscal Data Provider
  2. 2.
    Fiscal Data Consumer
Fiscal Data Provider will be able to post fiscal data into iFIX using well defined formats. Fiscal Data Consumers will be able to query fiscal data. Both these roles can be interchangeable.
Registration Providers and Consumers will need to register on iFIX before they can post or query fiscal data. To register the concerned person from the agency must be provided the following information on the iFIX portal Name of the Agency Contact Person Name Contact Person’s phone number Contact Person’s official email address OTP will be sent to the email address for the person to be able to register.
System Registration and Access Key Generation A registered user can login to the iFIX Portal using the official email address. They can then register one or more systems by providing the name of the system. System can be registered as a provider or consumer or both(?). On registration, each system is provided a unique ID e.g. [email protected] and secret API key. The secret API key can be used by the system to post or query fiscal data from iFIX using the iFIX APIs. The API key can be regenerated but only 1 API key will be active at a time. Portal will provide the ability to generate new keys for each system.
Posting Fiscal Data Data providers can post fiscal data in two ways Fiscal Message - directed to a specific consumer and which will be delivered to intended consumers. These are not available for querying by consumers other than the intended consumers. Fiscal Event - iFIX stores the events stored into iFIX for consumers to query
Fiscal Event consists of
  1. 1.
    Header
    1. 1.
      From
    2. 2.
      To
    3. 3.
      Date of Posting
  2. 2.
    Body
    1. 1.
      Fiscal Event Type e.g. Revenue, Expenditure, Debt
    2. 2.
      Fiscal Event Subtype
      1. 1.
        Revenue - Estimate, Plan, Demand, Receipt, Credit
      2. 2.
        Expenditure - Estimate, Plan, Bill, Payment, Debit
      3. 3.
        Debt - in progress - will be provided later.
    3. 3.
      Array of Fiscal Line Items
      1. 1.
        Amount
      2. 2.
        CoA
      3. 3.
        Location Code - from Location Registry
      4. 4.
        Program Code - from Program Registry
      5. 5.
        Project Code - from Project Registry
      6. 6.
        Administrative Hierarchy Code from Administrative Hierarchy Registry
      7. 7.
        Start Date of Period
      8. 8.
        End Date of Period
      9. 9.
        ….
      10. 10.
        ….
    4. 4.
      Attachment - Attachments can consist of Additional Attributes of Key Value Pairs e.g. Account Number, Correlation ID or Documents
    5. 5.
      Signature - Fiscal messages can be signed by multiple agencies by adding the signature to the Signature Array. This can indicated
      1. 1.
        Array of Signature
        1. 1.
          System
        2. 2.
          eSign - Signed Value of the Fiscal Event/Message Body using the System Key
        3. 3.
          Purpose - Acknowledgement or Approval or Rejection
        4. 4.
          Comments
        5. 5.
          Date of Signing
Reversal Fiscal Data To reverse a previous fiscal message or event, the data provider may post the same event with a negative amount in the line item(s). The data consumers should handle reversals appropriately.
Querying Fiscal Data Data consumers can query fiscal data. They can query Messages - the unread messages that have been delivered to them. When consumers read the unread messages, these messages are marked as read. Event - Consumers can query fiscal events posted by other data providers.
Reference Data Management
  1. 1.
    Location
  2. 2.
    Administrative
  3. 3.
    Chart of Account …. … …
Previous
iFIX
Next
Platform
Last modified 23d ago
Copy link