ACSO 80/20 Budget Envelope Setup & Tagging

1. Overview & Business Value#

This comprehensive operational guide details the architecture, business workflows, configuration parameters, and execution steps for ACSO 80/20 Budget Envelope Setup & Tagging within SmartERP.

Configure project budget envelopes, map general ledger accounts to ACSO statutory categories, and prevent non-compliant budget allocation.

{screenshot:acso-80-20-budget-envelope-setup-and-tagging-overview-dashboard}

2. Prerequisites & Security Access Groups#

• Required Modules: smarterp_ngo_grants, smarterp_humanitarian, smarterp_fund_accounting
• Security Groups:
  • Grant Officer (Technical ID: smarterp_ngo.group_grant_user)
  • Finance Director (NGO) (Technical ID: smarterp_ngo.group_grant_manager)
  • Field Relief Distribution Officer (Technical ID: smarterp_ngo.group_field_officer)
• Master Data Dependencies: Donor profiles (USAID, EU, UN, FCDO), multi-currency grant agreements, restricted fund accounts, ACSO 80/20 cost allocation categories, and beneficiary rosters.

3. Step-by-Step Configuration & Execution#

Step 1: Navigating to the Module Interface#

1. Log into your SmartERP instance at https://smarterp.et/odoo.
2. Open the main App Switcher (grid icon in the top-left corner).
3. Select the NGO & Grants app icon.
4. From the top navigation bar, open NGO & Grants → Grants & Projects → Donor Agreements / Budget Burn / Relief Distributions.

{screenshot:acso-80-20-budget-envelope-setup-and-tagging-app-switcher-navigation}

Step 2: Creating and Parameterizing Records#

1. Click the New button in the top-left control panel.
2. Complete the mandatory fields in the record form:
   • Grant Agreement Reference (Mandatory): Official donor contract number and co-funding arrangement
   • Funding Currency & Budget (Mandatory): Donor currency (USD/EUR) and restricted ETB counterpart account
   • Start & End Dates (Mandatory): Contractual grant operational window and closeout timeline
   • ACSO Cost Ratio Classification (Mandatory): Operational program expenditure vs. administrative overhead allocation
3. Configure optional operational parameters and localized tags as required:
   • Co-Funding Share (Optional): Percentage split across multiple donors or institutional match
   • Target Beneficiary Woreda / Kebele (Optional): Geographic location of humanitarian intervention
   • Relief Item Voucher (Model 20) (Optional): Distribution schedule for emergency food or non-food items (NFI)
4. Click the Save icon in the control bar to commit the record.

{screenshot:acso-80-20-budget-envelope-setup-and-tagging-record-creation-form}

Step 3: Validating and Processing Transactions#

• State Transitions: Execute operational state progression (Draft Agreement → Approved / Funded → Active Implementation → Budget Burn Monitored → Grant Closed).
• Ledger & System Impact: Expenditures debit grant-restricted project accounts and credit vendor payables/cash; foreign currency conversions record realized and unrealized FX variance.
• Audit Verification: Automated recording of author ID, timestamp, and immutable revision history.

{screenshot:acso-80-20-budget-envelope-setup-and-tagging-transaction-processing-state}

Setting Up Project Budget Envelopes#

Before any operational expenditure can be committed, project managers and finance teams structure detailed budget breakdown lines:

1. Open the project record in NGO Grants > Projects > All Projects.
2. Click Create Budget Envelope.
3. Group budget lines by Work Breakdown Structure (WBS) activity:
   • Activity 1.1: Maternal Nutrition Workshops.
   • Activity 1.2: Shallow Well Drilling & Pump Installation.
   • Activity 2.1: Community Livelihood Seed Grants.
   • Support Activity 3.1: Project Office Rent & Internet.

Enforcing Statutory ACSO Tagging#

For every line item:

1. Select the mandatory ACSO Category Tag:
   • Direct Program Cost (80%)
   • Administrative & Support Cost (20%)
2. The system checks cumulative ratios dynamically: $$\text{Total Program Budget} = \sum \text{Program Lines}$$ $$\text{Total Admin Budget} = \sum \text{Admin Lines}$$
3. If the ratio violates the 80/20 rule (e.g., 75% Program / 25% Admin), the system locks the Approve Budget button and flags: "Budget Non-Compliant: Administrative costs exceed 20.0% statutory ceiling".

4. Advanced Configuration Points#

• Automated Actions & Scheduled Tasks (Crons):
  • NGO: Calculate ACSO 80/20 cost ratio compliance (smarterp_ngo.ir_cron_acso_ratio): Runs weekly to flag any operational overhead drift above 20% limit
  • Grants: Reconcile foreign currency funding variance (smarterp_ngo.ir_cron_fx_reconcile): Runs monthly to revalue restricted foreign currency bank accounts
• Custom Print Templates & Reports:
  • ACSO Statutory Annual Financial Statement (80/20 Rule)
  • Donor Financial Expenditure Report (Multi-Currency)
  • Beneficiary Relief Distribution Voucher (Model 20 SIV)
  • Time-and-Effort Personnel Timesheet Allocation Summary
• Multi-Company Rules: Record-level security isolation under Company 1 (Ashewa Technology Solutions S.C.), preventing cross-company ledger leakage across parent and subsidiary legal entities.

5. Comprehensive Troubleshooting Matrix#