1. NGOs ERP
  2. Features
  3. Funding review
Feature · Funding review

Funding review

Review submitted funding cases and retain decisions with operation evidence.

OverviewReview Decision History
NGOs ERP · Funding review

Review Decision History

Review decisions

New
Funding caseDecisionDecided atReason
FC-2889Approve06 OctApprove rd-648
FC-4751Return13 OctReject rd-107
FC-5549Approve10 OctReturn rd-232
FC-2705Return26 OctApprove rd-852
FC-2560Approve20 OctReject rd-337
6 of 6 records
Approve rd-648Review decisions · RD-21881
Approve
Funding caseFC-2889
Decided at06 Oct
Example screen with sample data

What you can do

Put the decision on the case

Funding Review Queue brings submitted cases to Funding Reviewer with the project, donor, requested amount and restriction visible. The reviewer decides the case through Funding Case Review Decision. That workflow records a review decision, updates the funding case status and writes an operation receipt. The decision record carries the outcome, date, reason and case reference.

The available decision outcomes are approve, reject and return. The case itself has draft, submitted, approved, rejected and closed statuses. Keep the decision outcome and case status distinct when reading history: the workflow changes the case, while the decision record retains what the reviewer chose and why. A later case status should not erase the earlier reason.

How the work is organized

  • Submission. Funding Officer checks the donor, project, amount and restriction before the case enters review.
  • Decision. Funding Reviewer acts on a submitted case and records the reason with the outcome.
  • Receipt. The workflow writes an operation receipt so Finance Lead can follow what happened during processing.

The approval is a person’s decision. A submitted status requests review; it does not grant approval by itself. Program Lead may need the result to plan project work, but Funding Reviewer owns the review choice. Finance Lead reads the associated receipt when a processing result needs investigation.

What to agree during setup

Agree who is eligible to review funding cases and whether the creator of a case may also decide it. Establish what the reviewer should check before approval, including the project, donor, requested amount and restriction. Decide what explanation is expected for a rejection or return. The reason field is the place to retain that explanation with the decision.

Set a policy for repeat submissions after a return. The case status and review decision record serve different purposes, so agree the status path for a returned request before using it. Avoid interpreting a receipt marked completed as a second approval. It reports the operation result, while the decision record states the review outcome.

Check the handoff on an actual case

Funding Officer prepares a draft request for a known donor and project. Submit it and check that it appears in Funding Review Queue with the requested amount and restriction. Funding Reviewer opens the case and records an approval with the decision workflow. Check the case status, Review Decision History and Operation Receipt History together.

Repeat the rehearsal with a different submitted case that should be rejected or returned. Confirm that the reviewer can give a reason and that the outcome is visible in the decision history. If an operation receipt needs review, Finance Lead follows it in Operations Needing Review without treating the failed processing state as the business decision itself.

What your team sees

  • Funding Review Queue — Submitted cases waiting for a reviewer’s decision.
  • Review Decision History — Dated approve, reject and return outcomes with reasons.
  • Operations Needing Review — Failed or needs-review processing results tied to cases.

Follow the work through

Use the funding review process for the decision handoff. The funding case process covers preparation and submission.

What it keeps track of

Data model
Funding cases
A record here is a request for funding tied to a project and donor, used to track approval and status.
Review decisions
A record here is the outcome of reviewing a funding case, used to track who decided what and why.
Operation receipts
A record here logs one attempt to disburse or process funds, so the team can see what happened and when.
Donors
A record here is a person or group who gives funds, used to keep track of contacts and giving activity.
Projects
A record here is a funded initiative with a location and timeline, used to track progress and budget.

Who uses it

Permissions
Funding Reviewer
Makes the case decision.
Funding Officer
Prepares and submits the request.
Finance Lead
Investigates receipt exceptions.
Program Lead
Follows the approved funding context for project delivery.

Set up NGOs ERP your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started