1 / 12

Programme-level Multi-Year Funding Commitment

Discussion toward FY14 Budgeting Process. Programme-level Multi-Year Funding Commitment. Scope. The funds which have no specific donor restrictions on project allocation under the same Programme Mainly Sponsorship But not limited, e.g., PNS general funding which has no donor restrictions.

elon
Download Presentation

Programme-level Multi-Year Funding Commitment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Discussion toward FY14 Budgeting Process Programme-level Multi-Year Funding Commitment

  2. Scope • The funds which have no specific donor restrictions on project allocation under the same Programme • Mainly Sponsorship • But not limited, e.g., PNS general funding which has no donor restrictions. • Grants (Gov’t, Multi, PNS) are out of scope

  3. Background • When LEAP was introduced, Programme-Projects structure started. (previously it was Project-its components) • Methodologies of Programme/Project Planning/Designing and Management became well organized. • Programme/Project Financial System became complicated • Budget files, PBAS entries, C/F and Project Core and Logframe Financial Report became 5 times • But, Donor restriction (mainly SP) is not changed • If same Programme, it seems that many SOs have flexibility of fund allocation among Projects Not changing Programme-Projects structure in Development theory and accountability-level, change to Programme-level Commitment as one figure

  4. Pre-conditions & Directions • Pre-conditions • No design changes on IT systems such as • MyPBAS DB • SunSystem • Horizon • LEAP Budget Template • Project Core & Logframe Financial Report Template • No structure change on Programme and Project • Directions • Simplify, Reduce not-value-added work • Keep project-level accountability • Ensure the concept of Multi-Year Planning & Budgeting in Programme • Ensure more flexibility of annual cashflow and budget reallocation among projects under the same programme

  5. Key PBAS Activities

  6. Example Revised CY Budget

  7. 1st year in MyPBAS & C/F SO enter based on the agreed PDD/MY Budget at Programme-level NO enter based on the Revised CY Budget for CY, and agreed PDD/MY Budget for future years at Project-level

  8. 3-year in MyPBAS Project A (SMP) Project B This is real balance at Programme-level

  9. PCFR and NO CF Explanation Forms SunSystem Actual Revised CY Budget = NO Approved Request in MyPBAS = LEAP Budget Template (revised CY)

  10. New Year-End Entry • Transfer a part of SMP income to other projects to cover YTD Actuals • Transfer $130 from Project A(SMP) to Project B through A9/Project number • Sep-30 transaction (one time)

  11. Pros and Cons

  12. Feedback Q) In lifecycle, how many % is acceptable overspent?

More Related