Mistakes happen — a check amount misread at entry, a gift logged twice. Edit and Void fix that from the gift's own row, on either the patron's Giving tab or the venue-wide Gifts ledger.
Before you start
Venue Admin or Super Admin. Editing and voiding gifts isn't gated by a separate capability today — any venue-admin or super-admin on the venue can do it.
Editing a gift
Go to AdminVenuesFundraisingGifts, or a patron's Giving tab, and click Edit on a gift row.

Update the fields you need to correct: Amount, Gift date, Goods/services value (FMV, $), Notes, or Anonymous.
Enter a Reason for change — this is required for every edit.
Click Save changes.
Amount is locked for card gifts. If a gift came in by card, Stripe is the source of truth for the amount — correct it with a refund instead of editing the dollar figure here.
Every edit appends a revision. If a gift has been edited before, a History button appears on its row — open it to see each change's timestamp, who made it, their reason, and the before/after values.
Voiding a gift
Click Void on the gift row.
Enter a Reason.
Click Void gift.
Voiding is not a refund — no money moves. It removes the gift from the patron's totals and from year-end statements, which is exactly right for a duplicate entry, but wrong for an actual gift the donor wants back. If money needs to move, process a refund instead.
Watch out
You can't edit or void a gift that isn't completed or pending — a refunded, disputed, or already-voided gift is locked.
Editing a gift's date across a tax-year boundary is blocked once a year-end statement has already been emailed for that patron and year. Void the gift and re-record it in the correct year instead.
If a gift was already posted to QuickBooks and you edit or void it, Noctern doesn't attempt to auto-correct QuickBooks — it flags the sync as needing a manual adjustment there.
- Open the demo venue's Gifts ledger and click Edit on a check or cash gift.
- Try leaving the Reason field blank and confirm the save is rejected.
- Open History on a gift that's already been edited once and read its revision.