Match nonprofit pledge receipts without changing donor restrictions

A bank deposit rarely carries enough detail to prove which pledge it settled or whether a restriction follows it. A usable pledge receipts file shows what entered the schedule, what moved, and what still needs an answer. Record the entity, period, currency, source systems, preparer, reviewer, and cutoff at the top.

Export the full population before filtering or correcting it. Save report names, filters, timestamps, row counts, and amount totals. Compare the export with the prior open-item list and call out any missing channel or account. Keep the original file read-only so another reviewer can reproduce the scope.

For this workflow, collect pledge record, donor correspondence, deposit detail, campaign mapping, restriction record, and fund ledger. Give each item a stable reference. Capture its source, date, amount, currency, status, and owner. If a record is missing, label it missing and request it. An estimate or a screenshot from an unapproved message thread is not a substitute.

Begin with the last reviewed balance or status. Show additions, applications, releases, refunds, and corrections on separate lines, then tie the ending position to the current ledger or operating report. Gross movement matters here because netting can hide two different events.

Use plain categories such as missing record, timing difference, amount mismatch, duplicate, stale item, or judgment question. Add an owner, requested action, due date, age, and known financial effect. Keep an item open until the stated evidence or approval arrives.

The preparer can check arithmetic, compare observable fields, and draft a focused question. The preparer does not decide restriction interpretation and pledge adjustment. Route that question to the nonprofit finance owner, along with the evidence reference and the date a response is needed. Record the answer in the workpaper, not only in chat.

Use named accounts, approved storage, least-privilege access, and multifactor authentication where available. When someone changes a mapping, amount, owner, or conclusion, retain the prior value and log who changed it, when, and why. Sensitive records should stay inside the client's approved system.

Reperform large entries, manual adjustments, old exceptions, and items whose status changed. Trace some records from source to schedule and others from schedule back to source. If the same mismatch keeps returning, expand the sample and ask whether the written procedure matches the actual process.

Deliver the scope note, original exports, evidence index, movement bridge, exception list, approvals, and change log together. Carry forward only items that remain open. The reviewer should be able to understand the pledge receipts position without reconstructing the file from email or memory.