Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

General Instructions


Sl No

Instructions

1

Please navigate each of the sections and fill in the relevant information
2Page Title will bear the name - BPA Integration for - << Service/Scenario Name>>
3All examples are indicative, they should be replaced with actual information.
4Add rows in the tables as per the volume of data.
5Sections with no entries can be marked Not Applicable or Deleted
6The purpose of this section is to provide general guidance in using the template. This section can be deleted once the document composition is complete

Introduction

The main objective of the Demand framework is to maintain Tax head and Tax Period wise demand (Tax/Fee/Charges) for every revenue entity and provide a Bill for a demand.

Prerequisites 

Below masters has to be defined

  • Tax Head: The different type of tax heads to be defined under the right category (Tax/Fee/Charges) for your module
  • Tax Periods: The different type of tax periods has to be defined for your module
  • Tax head and period mapping: Define what are all the tax heads are valid for defined periods

Functionality

  • Create/Update/View demand and demand details (Tax head and Tax Period wise demand)
  • Create/Update/View Bill for your business entity
  • Bill XML for collection, here all the validations and other required configurations can be set for collection
  • A standard hook and allow implementing from the Business module side for a back update of collection. This is very much useful when the Business module requirement is to do some activity on a successful collection or canceling the payment receipt.

Configurations and Setup



Support Information

References and Notes

  • No labels