These fundraising dashboard examples reconcile $120 promised, $40 receipt-evidenced, and $80 not yet evidenced for fictional pledge P01. The three installments explain the promise rather than increasing it. Duplicate and conflict views let you inspect whether a changed record really supports a changed total.
Keep one promise and three installments
The community-workshop example C01 uses USD and an October 13, 2026 review date. P01 promises $120. I01, I02, and I03 each schedule $40, due October 1, November 1, and December 1 respectively. Their sum is 40 + 40 + 40 = 120, matching P01.
Only I01 has receipt R01, for $40 dated October 1. I02 and I03 have no supplied receipts. Salesforce's fundraising guidance distinguishes a pledge from its related payment records. Apply that generic distinction without importing its software workflow or treating a promise as cash. These are original sample amounts and IDs, not actual donor records.
Read the scope of each amount
The promised total is $120, the installment plan is $120, and P01's supplied receipt-evidenced amount is $40. The remaining $80 describes scheduled amounts without receipt evidence. It does not predict collection, establish available budget, or make an accounting revenue determination.
Choose the unevidenced-installment filter to show I02 and I03. Its scheduled subtotal is $80 across two installment rows. Choose receipt-evidenced to isolate I01 and R01 for $40. Keep the pledge summary visible as a different counting unit, so filtered rows cannot appear to be extra gifts.
Check duplicates before changing the amount
The identical-duplicate example lists R01 twice with the same amount, date, and installment link. The receipt total stays $40 because the supplied identity is the same. The duplicate note retains both source references. This rule concerns the explicitly repeated R01; it is not permission to merge unrelated receipts that happen to share an amount.
The conflict example instead introduces R01 for $30 beside R01 for $40. The definitive receipt-evidenced amount and the not-yet-evidenced remainder become Unresolved. Choosing either row or summing them would conceal the contradiction. Restore baseline to recover the consistent $40/$80 worked example, without pretending the conflict was actually resolved.
Keep the unknown gift visible
Separate direct gift G02 has an unknown amount and sits outside P01's installment schedule. It belongs in the unknown-amount list and contributes no invented zero to a sum. P01's receipt amount is therefore a P01 result, not a complete campaign-received total including G02.
Use the source-question panel to identify the missing amount and evidence. The actual owner, response, and decision remain unsupplied. Ask for source confirmation before recomputing a definitive total. The reading controls send no donor messages, change no pledge, and connect to no bank. Maintain actual pledge, installment, and receipt records in the authorized workbook or system, including the references that explain any correction.
Copy this prompt to adapt the example
Design a fundraising ledger with separate commitment and receipt totals, installment filters, and a conspicuous source-conflict explanation. Return one self-contained HTML file with embedded styling and working interactions. Use readable type, strong contrast, clearly labeled keyboard controls, and a layout that flows on a narrow phone. Identify the supplied data as a fictional example.
Create a fictional community-workshop fundraising review C01 as of October 13, 2026, USD. P01 promises 120; I01/I02/I03 schedule 40 each for October 1, November 1, December 1. Only R01, 40 on October 1 linked to I01, has supplied receipt evidence. Show planned sum 120, P01 receipt-evidenced 40, and scheduled not-yet-evidenced 80. Never add pledge and payment as 160. G02 is a separate unknown-amount direct gift; show it outside sums and do not imply a complete campaign total.
Add All installments, Receipt-evidenced, Not yet evidenced, and Conflicting receipts filter buttons. Baseline Conflicting receipts has no rows; the amount-conflict scenario shows I01 there and removes I01 from Receipt-evidenced. Keep I02/I03 in Not yet evidenced. Update rows, matching count, and scheduled subtotal from the chosen filter. Include separate scenario buttons for Baseline, Identical R01 duplicate, and Conflicting R01 amount 30. Identical duplicates count once with both references retained. Conflict makes definitive receipt/remainder totals unresolved; never select a source arbitrarily. Show the source question that needs resolving. No collectability, revenue, available-budget, or tax conclusion. No donor data, messages, payment actions, live integration, or saved changes.
Ask the record owner to resolve the two R01 amounts before discussing a wider campaign total. For the conversation, NOS can render the sanitized pledge, installment, and receipt comparison together. Once the owner identifies the correct source, return to that installment and recompute: the dashboard should explain the answer, rather than become a second competing donation record.