Introduction

This document gives the required information for integrating a third party receipt with the DIGIT Finance. In the situation wherein a state or city, there are various third applications been used along with DIGIT Finance,  and all the revenues need to be accounted to the Finance application, it is required to do a system to system integration.

High-Level Design

Finance system exposes a REST API to create the voucher which is authenticated. This API needs to be called after the creation of a collection receipt. This will push a voucher in the Finance system with relevant information like - source module, the amount collected, mode of collection and so on.

Low-Level Design

For the creation of a receipt voucher, one should call the  /rest/voucher/_create endpoint which is referred to in this contract. One receipt voucher will be created in the Finance system in approved status for a receipt that is pushed. In order to make sure multiple vouchers are not created for a receipt, pass the reference number and billing service appropriately. There is another API /rest/voucher/_search to search for any voucher.

...

For Online collections, the money will be either directly debited to the bank or to a cash in transit account. Configuration needs to be done based on the state/city requirement.

Steps to configure

• Make sure all the common masters that are used for voucher creation are in sync with the two systems.
• If a city has a specific bank account to which the money needs to be accounted for online collection, configure the bank account in DIGIT Finance as well as in third-party application with the account code kept same.
• Write a kafka consumer to post the voucher to DIGIT Finance when collection happens. Keeping the two asynchronous is better.
• Back update the source system for voucher reference if required.

...