4.3 Funding Awards, Disbursement Schedules & Post-Award Reporting

4.3 Funding Awards, Disbursement Schedules & Post-Award Reporting

In public sector grant administration, adjudicating proposals and selecting winners is only the midpoint of the grantmaking lifecycle. The most complex, fiduciary-intensive phase begins once an award is executed. Government agencies must track legal grant agreements, issue disbursements across scheduled fiscal tranches, enforce strict milestone deliverables, monitor financial expenditures, and ensure rigorous closeout with the de-obligation of unused funds.

Public Sector Solutions provides a comprehensive post-award architecture anchored by the FundingAward and FundingDisbursement standard objects. Integrated with Experience Cloud grantee portals and state enterprise resource planning (ERP) accounting backends, PSS ensures that public dollars are disbursed prudently and accounted for down to the penny. Understanding these post-award mechanisms is a heavily weighted area of the AP-222 credential.

---

The Funding Award Standard Object: The Legal Contract

Once an IndividualApplication successfully navigates multi-stage scoring and receives final approval from the agency director, the relationship transitions from a competitive proposal into an executed legal contract. In Public Sector Solutions, this contract is represented by the FundingAward standard object.

┌─────────────────────────────────────────────────────────────────────────┐
│                         FundingAward Record                             │
├─────────────────────────────────────────────────────────────────────────┤
│  • Award Number / FAIN: FA-2026-ENV-00892                               │
│  • FundingOpportunityId: FY26 Municipal Solar Grants                    │
│  • IndividualApplicationId: APP-2026-X94J2                              │
│  • RecipientAccountId: City of Springfield Green Council                │
│  • Total Awarded Amount: $600,000.00                                    │
│  • Period of Performance: October 1, 2026 – September 30, 2028          │
│  • Matching Fund Obligation: $120,000.00 (20% Non-Federal Match)       │
│  • Status: Active (Executing Tranches)                                  │
└────────────────────────────────────┬────────────────────────────────────┘
                                     │ 1:N Payment Tranches
       ┌─────────────────────────────┼─────────────────────────────┐
       ▼                             ▼                             ▼
┌───────────────────────────┐ ┌───────────────────────────┐ ┌───────────────────────────┐
│    FundingDisbursement    │ │    FundingDisbursement    │ │    FundingDisbursement    │
│  Tranche 1: Advance       │ │  Tranche 2: Milestone A   │ │  Tranche 3: Final Close   │
│  • Amount: $150,000       │ │  • Amount: $300,000       │ │  • Amount: $150,000       │
│  • Status: Paid           │ │  • Status: Approved (ERP) │ │  • Status: On Hold        │
│  • Date: Oct 15, 2026     │ │  • Date: Apr 30, 2027     │ │  • Date: Sep 30, 2028     │
└───────────────────────────┘ └───────────────────────────┘ └───────────────────────────┘

Core Attributes of the Funding Award Object

• Award Number & Identifiers: Captures official statutory identifiers, such as the Federal Award Identification Number (FAIN) or state contract reference number.
• Committed Award Amount: The total legal liability committed by the government agency (e.g., $600,000.00).
• Period of Performance: Strictly defines the legal expenditure window through StartDate and EndDate. Grantees cannot incur allowable project costs before the start date or after the end date without a formal grant amendment.
• Matching / Cost-Share Commitment: Specifies the grantee's legally binding co-investment obligation.
• Terms & Conditions / Special Award Conditions: Documents standard state/federal compliance covenants, alongside high-risk grantee covenants (such as mandatory monthly financial check-ins or mandatory invoice pre-approvals).

Award Lifecycle Status Progression

1. Draft: The award record is generated automatically by an approval Flow upon application adjudication, staging preliminary budget allocations.
2. Notice of Award (NOA) Issued: The agency formally transmits the legal award package to the grantee via the Experience Cloud portal. The recipient's Authorized Organization Representative (AOR) reviews terms and executes an electronic signature.
3. Accepted / Executed: Bilaterally signed by both the agency grant officer and grantee leadership, legally obligating agency funds.
4. Active: The grant is operational. Periodic disbursements are executed against verified milestones and performance reports.
5. Suspended / Under Review: Temporarily halted due to compliance infractions, audit findings, or unsubmitted expenditure reports.
6. Closed: Final performance deliverables verified, financial reconciliations completed, unused funds de-obligated, and legal release confirmed.

---

Funding Disbursements: Modeling Payment Tranches

Governments rarely hand over hundreds of thousands of dollars in a single unrestricted lump sum. Instead, funding is released in tranches modeled through the FundingDisbursement standard object.

Payment Tranche Methodologies

Public Sector Solutions supports three primary disbursement models:

Anatomy of a Funding Disbursement Record

• Amount Requested vs. Amount Approved: Tracks discrepancies between what the grantee claimed and what the compliance officer approved after disallowing unallowable expenses.
• Scheduled Disbursement Date: The planned date for payment release according to the award agreement.
• Actual Disbursement Date: Stamped when the financial system confirms the electronic funds transfer (EFT/ACH).
• Disbursement Status Lifecycle: Scheduled -> Pending Verification -> Approved -> Paid (or Cancelled / On Hold).
• Payment Reference / Transaction ID: Stores the external state treasury warrant number, check reference, or ACH tracing identifier returned by the financial system.

Automated Disbursement Holds

A critical exam concept is how PSS prevents improper payments. If a grantee has a scheduled disbursement of $100,000 set for July 1st, the system must not allow payment release if the grantee failed to submit their June Quarterly Progress Report.

Using Salesforce Flow Builder and validation rules, PSS implements Automated Disbursement Holds:

• When an expenditure report or milestone deliverable becomes overdue, a record-triggered flow immediately flags pending FundingDisbursement records with Status = On Hold.
• Agency staff cannot manually advance a disbursement to Approved while blocking conditions exist, safeguarding public funds from non-compliant distribution.

---

Enterprise Financial & State ERP System Integration

A paramount architectural distinction on the AP-222 exam is the Separation of Concerns between Salesforce Public Sector Solutions and government Enterprise Resource Planning (ERP) accounting backends.

┌────────────────────────────────────────┐         ┌────────────────────────────────────────┐
│      Salesforce Grantmaking (PSS)      │         │   State Financial ERP / Treasury SoR   │
│   "Grant Program Operational Engine"   │         │     (SAP, Oracle Financials, Workday)  │
├────────────────────────────────────────┤         ├────────────────────────────────────────┤
│ • Manages NOFOs, Intake, and Scoring   │         │ • Official General Ledger (GL)         │
│ • Manages Terms, Milestones & Reports  │         │ • Federal Drawdown & Fund Accounting   │
│ • Evaluates Compliance & Deliverables  │         │ • Vendor Master & Bank Account Routing │
│ • Authorizes Disbursement to "Approved"│         │ • Issues Warrants / ACH Transfers      │
└───────────────────┬────────────────────┘         └───────────────────▲────────────────────┘
                    │                                                  │
                    │ 1. Outbound Payment Request (Approved Tranche)    │
                    ├──────────────────────────────────────────────────┤
                    │    Integration Procedure / MuleSoft API Call     │
                    │                                                  │
                    │ 2. Inbound Payment Confirmation (ACH Warrants)   │
                    │    Updates Disbursement to "Paid" + Warrants #   │
                    └──────────────────────────────────────────────────┘

Separation of Concerns Architecture

• Salesforce Public Sector Solutions is the Operational Grant Management System:
  • Manages applicant interactions, solicitations, scoring, milestone tracking, compliance documentation, and authorization workflows.
  • It authorizes payments by transitioning a FundingDisbursement to Approved.
• State ERP / Financial System (e.g., SAP, Oracle Financials, CGI Advantage, Workday) is the Financial System of Record (SoR):
  • Manages the official chart of accounts, encumbrances, vendor bank routing details, federal treasury drawdowns, and 1099 tax reporting.
  • It executes the actual cash transfer via state treasury warrants or automated clearing house (ACH) batches.

Bidirectional Integration Pattern

1. Outbound Authorization: When a grant manager verifies milestones and marks a FundingDisbursement as Approved, a Salesforce Record-Triggered Flow triggers an OmniStudio Integration Procedure (or publishes a Platform Event to MuleSoft).
2. ERP Processing: The integration sends an outbound REST/SOAP payload to the ERP containing the Vendor ID, Accounting String, Award FAIN, and Authorized Dollar Amount. The ERP encumbers the budget and queues the payment batch.
3. Inbound Confirmation: Upon successful banking settlement, the ERP executes a secure callback to Salesforce. An inbound Integration Procedure updates the FundingDisbursement record with Status = Paid, stamps the PaymentReferenceNumber (e.g., State Warrant #948201), and logs the ActualDisbursementDate.

---

Post-Award Compliance & Progress Reporting

To ensure transparency and deliverable accountability, grantees must regularly report on operational progress and financial expenditures throughout the period of performance.

Deliverables & Milestone Tracking

Within the Experience Cloud portal, grantees manage an interactive compliance dashboard:

• Milestone Verification: Grantees submit quantifiable proof of milestone completion (e.g., Phase 1 Solar Array Installation Completed, 50 Certified Technicians Trained).
• Supporting Evidence Uploads: Grantees attach engineering inspection certificates, attendance rosters, and permits using Document Checklist Items.
• Agency Adjudication: Internal grant officers inspect submitted materials directly in their Grantmaking Console, approving the milestone or issuing a formal Request for Information (RFI) to clarify deficiencies.

Financial Expenditure Reporting (SF-425 Equivalents)

In addition to narrative progress, public grants require periodic financial accounting (typically quarterly), modeled after standard federal SF-425 Federal Financial Reports:

• Budget-to-Actual Tracking: Grantees report actual expenditures against each approved budget line item (Personnel, Fringe, Equipment, Supplies, Contractual, Indirect).
• Line-Item Variance Monitoring: Public sector grants enforce variance caps (e.g., the statutory 10% re-budgeting threshold). If a grantee overspends an individual line category by more than 10% without prior written approval, the system flags the report as a variance violation.
• Invoice Sample Auditing: Grantees attach general ledger transaction summaries, payroll registers, and subcontractor invoices for desk audits.

---

Grant Closeout & Fund De-Obligation

The final phase of the grantmaking lifecycle is formal Grant Closeout:

┌─────────────────────────────────────────────────────────────────────────┐
│                         Grant Closeout Lifecycle                        │
├─────────────────────────────────────────────────────────────────────────┤
│  1. Period of Performance Expires or Scope Completed                    │
│  2. Submission of Final Reports (Performance, Financial, Property)      │
│  3. Financial Reconciliation & Audit Clearance                          │
│     • Total Awarded: $500,000.00                                        │
│     • Total Audited Expenditures: $460,000.00                           │
│     • Unexpended Balance: $40,000.00                                    │
│  4. Formal Fund De-Obligation                                           │
│     • De-obligate $40,000 from FundingAward                             │
│     • Return $40,000 to Parent FundingOpportunity / Program Pool        │
│  5. Status Update: FundingAward.Status = "Closed"                        │
│  6. Archive Records per Statutory Document Retention Policy             │
└─────────────────────────────────────────────────────────────────────────┘

Closeout Prerequisites & Reconciliation

Before an award can transition to Closed, the agency verifies that all closeout obligations are met:

1. Final Performance Report: Comprehensive report detailing total program outcomes against original proposal objectives.
2. Final Financial Reconciliation: Reconciles total cash disbursed against verified, allowable project expenditures.
3. Property & Equipment Disposition: Grantees inventory all capital assets and equipment purchased with grant funds, executing state-mandated equipment disposition agreements.

Fund De-Obligation Mechanics

In public sector grants, recipients rarely spend exactly 100.00% of awarded funds. If an agency awards $500,000 to a non-profit for an environmental cleanup project, but the final reconciled and audited expenditures total only $460,000, $40,000 of taxpayer capital remains unspent.

Agencies cannot simply delete records or leave funds stranded:

• An automated or administrative De-obligation Workflow updates the FundingAward to adjust committed obligations down to the final actual expenditure ($460,000).
• The unspent balance ($40,000) is formally de-obligated and credited back to the parent FundingOpportunity or FundingProgram available budget pool.
• This restored capital becomes available for future competitive grant cycles or emergency reprogrammed allocations.
• The FundingAward record transitions to Status = Closed, and historical records are locked to satisfy public audit retention mandates (e.g., 3 to 7 years).

---

AP-222 Exam Strategy: Core Scenarios & Traps

• Scenario 1: Preventing Premature Tranche Disbursements: If an exam scenario describes a grantee receiving their second quarterly disbursement while their first-quarter performance report remains unsubmitted or rejected, configure an automated record-triggered flow or validation rule that checks child milestone/report statuses and holds the FundingDisbursement in On Hold status until compliance is restored.
• Scenario 2: State Accounting ERP vs. Salesforce Architecture: When asked how to integrate Salesforce Grantmaking with a state accounting backbone (e.g., SAP or Oracle Financials) for payments, always maintain Salesforce as the operational compliance authority and the ERP as the financial System of Record. Trigger outbound payment requests from Approved disbursements via Integration Procedures or MuleSoft, and handle payment confirmations asynchronously via ERP callbacks.
• Scenario 3: Final Award Closeout with Unexpended Funds: If an exam question asks how to handle an executed grant where the recipient completed all project deliverables but spent less than the full award amount, do not cancel or delete the award. Execute a formal De-obligation of the remaining unspent funds, credit the capital back to the parent funding opportunity pool, and transition the award status to Closed.