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 7 Next »

Introduction

A fund is a pool of money that is allocated for a specific purpose. A fund can be established for any purpose whatsoever, whether it is a city government setting aside money to build a new civic center etc.

Fund Accounting is a self-contained accounting with its own assets, liabilities, revenues, expenditures and fund balance.

Data Table

*Name

*Code

Identifier

*Level

Parent Fund

Isnotleaf

Municipal Fund

01

1

0

Nil

False

Grant Fund

02

2

0

Nil

False

Public Fund

03

3

0

Nil

False

Procedure

Data Definition

  • Name: To indicate the Fund name, if there is a multiple fund and by following the Fund Accounting method to record the transaction user can select a particular Fund.

  • Code: The unique code give to the individual fund name.

  • Identifier: A number allocated sequentially against the Fund name, if the ULB is using multiple Fund accounting to record the transaction this helps the user to identify by the number assigned to the individual fund.

  • Level: The Funds can be defined in the tree structure, so the Level indicates the structure in which the funds would be setup.

  • Parent Fund: If the ULB’s using multiple Funds then a Hierarchy of “Parent - Child “can be setup for the Fund, so under each Parent Fund a multiple child funds can be setup.

  • Isnotleaf: The Isnotleaf would be True or False base on the hierarchy of Parent - Child fund is setup. If the fund has a Parent - Child hierarchy setup then the Isnotleaf would be True, nor it would be False.

Steps to fill data

  • Identify Funds that exists at a ULB level.

  • Download both the attached template and to updated all the details as per the above information in the empty template provided. The sample data template can be used as a reference to fill in the data.

  • Read through all the information above before updating the template with relevant information.

Validations

  • All the fields with * sign are mandatory to be filled in. Without this information, the system configurations cannot be executed.

  • Fund Code should to be unique.

  • Isnotleaf indicate “True” or “False”

Attachments

  • Refer to “Fund” in the uploaded template.

  • For sample data reference, refer to the uploaded “sample date” file.

  • No labels