PEPFAR's annual planning process is done either at the country (COP) or regional level (ROP).
PEPFAR's programs are implemented through implementing partners who apply for funding based on PEPFAR's published Requests for Applications.
Since 2010, PEPFAR COPs have grouped implementing partners according to an organizational type. We have retroactively applied these classifications to earlier years in the database as well.
Also called "Strategic Areas", these are general areas of HIV programming. Each program area has several corresponding budget codes.
Specific areas of HIV programming. Budget Codes are the lowest level of spending data available.
Expenditure Program Areas track general areas of PEPFAR expenditure.
Expenditure Sub-Program Areas track more specific PEPFAR expenditures.
Object classes provide highly specific ways that implementing partners are spending PEPFAR funds on programming.
Cross-cutting attributions are areas of PEPFAR programming that contribute across several program areas. They contain limited indicative information related to aspects such as human resources, health infrastructure, or key populations programming. However, they represent only a small proportion of the total funds that PEPFAR allocates through the COP process. Additionally, they have changed significantly over the years. As such, analysis and interpretation of these data should be approached carefully. Learn more
Beneficiary Expenditure data identify how PEPFAR programming is targeted at reaching different populations.
Sub-Beneficiary Expenditure data highlight more specific populations targeted for HIV prevention and treatment interventions.
PEPFAR sets targets using the Monitoring, Evaluation, and Reporting (MER) System - documentation for which can be found on PEPFAR's website at https://www.pepfar.gov/reports/guidance/. As with most data on this website, the targets here have been extracted from the COP documents. Targets are for the fiscal year following each COP year, such that selecting 2016 will access targets for FY2017. This feature is currently experimental and should be used for exploratory purposes only at present.
Years of mechanism: 2008 2009
This is a continuing activity under COP09.
Per guidance in NTTF 10.17.08, this activity will not be funded in FY09.
This is the activity narrative from COP08
USAID Administrator Fore has directed new policy regarding USAID administrative costs under PEPFAR.
Administrative costs associated with supporting program implemention by USAID should be applied to
PEPFAR. Many of USAID's PEPFAR FTEs are still funded through the agency's administrative (OE)
account. In FY 2008, USAID, OMB and OGAC agreed to cover a larger share of the administrative costs
incurred to implement PEPFAR. To meet this requirement, USAID/Mozambique is asked to reprogram the
amount of $1,000,000 from other program areas to Management and Staffing. This will help cover the costs
of USDH FTEs that are currently OE funded to now be funded directly through PEPFAR.
Once the reprogramming request is approved, the USAID Management Bureau will bill Mozambique
programs for staff listed within the Staffing for Results (SfR) database for USAID US direct hire non-
PEPFAR funded Salary and Benefits (S&B). The bill for USDH S&B for each individual will include the full
year of funding necessary for FY08. The Management Bureau will bill only up to $1,000,000. The USAID
Management Bureau will copy USAID Global Health on the bills that they send USAID/Mozambique for
reimbursement of direct hire salary and benefits.
USAID Global Health will set up a mechanism using field support so that USAID/Mozambique can obligate
PEPFAR administrative funds to reimburse the Agency's OE account for those staff that are now direct hire
OE funded staff.
New/Continuing Activity: Continuing Activity
Continuing Activity: 19732
Continued Associated Activity Information
Activity Activity ID USG Agency Prime Partner Mechanism Mechanism ID Mechanism Planned Funds
System ID System ID
19732 19732.08 U.S. Agency for To Be Determined 8786 8786.08 M&S
International
Development
Table 3.3.19:
