Professional Documents
Culture Documents
Implementing Unit Based Budgeting in Defence v2
Implementing Unit Based Budgeting in Defence v2
Budgeting in Defence
Existing Manual Practice of Budget
Distribution in Defence (Army)
The Budget Directorate distributes pay and TA/DA budget among three accounts offices:
Finance Controller, Pay 1 (for payment of army officers)
Finance Controller, Pay 2 (for payment of JCO ORs)
Finance Controller, Misc (for payment of civilians)
Senior Finance Controller, Defence Purchase deals big purchases
Although pay and TA/DA budget is not distributed unit-wise, some other elements (like
Training Grant, small procurements) of the budget distributed among the units and
respective Area Finance Controller is notified.
Problem arises when one pay point spends more budget than manually allocated and the
other is deprived due to exceeding the total budget.
Existing Manual Practice of Budget
Distribution in Defence (Navy and Air)
Bangladesh Navy spends all pay related budget through Senior Finance Controller, Navy
Bangladesh Air Force spends all pay related budget through Senior Finance Controller, Air
Force
Although pay and TA/DA budget is not distributed unit-wise, some other elements (like
Training Grant, small procurements) of the budget distributed among the units/bases and
respective Area Finance Controller is notified.
Problem arises when one pay point spends more budget than manually allocated and the
other is deprived due to exceeding the total budget.
Key Design Issues
Disadvantages:
Units are created and dissolved frequently.
As classification is an open document, security may be an issue.
The same unit will have to be linked with multiple pay points for different types of
expenditures.
As payment is made centrally, it will be difficult for Budget Directorate to distribute pay
budget unit-wise.
Solution 2: Creating organizational codes for
units in side tables (outside BACS) and
implement use of contingency budget control
Key Features:
Shadow organization codes will be created against accounts offices.
Secrecy will be maintained through using, as code names for units
API will be established with Army database
Solution 2: Creating organizational codes for units in side tables
(outside BACS) and implement use of contingency budget control
Advantages:
Shadow organization codes will be created against accounts offices.
Unit-wise budget control can be implemented
Secrecy will be maintained, as code names will be used for units
Disadvantages:
Units are created and dissolved frequently.
The same unit will have to be linked with multiple pay points for different types of expenditures.
New functionality for budget distribution and control will have to be developed in iBAS++
API will need to be developed for Army systems
Solution 3: Creating organizational codes to
represent accounts offices and distribute
contingency budget among units
Shadow organization codes will be created against accounts offices.
For example, for under Bangladesh Army, new organization codes will be created for:
Officers’ Pay for Bangladesh Army
Staff Pay for Bangladesh Army
Civilian Pay for Bangladesh Army
For contingency heads, iBAS++ will provide option for distributing and controlling budget
among imprest holders (DDOs)
Existing Classification for Organization for Bangladesh Army (1)
Navy and Air Force does do not require new organization code
Proposed Workflow for Bangladesh Army
Advantages:
For pay and TA/DA, pay point wise budget control will be implemented.
Imprest holder-wise (in addition to pay point-wise) budget control will be implemented for
contingency
Disadvantages:
New functionality for imprest holder (DDO) wise budget distribution and control will have
to be developed in iBAS++.
Thanks You