Design-partner program · Core donor operations in active build

See the roadmap
Skip to content
Beneora

Reconciliation

The nonprofit month-end close playbook

A sequenced close for organizations taking online, offline and recurring gifts across multiple funds.

12 min readBeneora product team

Takeaway

Close in a fixed order — money in, money explained, money mapped, period locked — and record why every exception was accepted.

This playbook assumes one finance lead, several giving streams and an accounting package that is not your gift ledger. It is written to be run in a day.

Stage 1 — Money in

  • Confirm every payout for the period has a matching bank deposit line.
  • List deposits with no payout: they are offline gifts, grants or transfers, and each needs an owner.
  • Freeze offline gift entry for the period before you begin matching.

Stage 2 — Money explained

  • For each unmatched difference, name a cause: fee adjustment, refund, dispute, timing or data-entry error.
  • Record the cause on the exception rather than in a private note.
  • Escalate anything you cannot explain rather than plugging it — an unexplained plug becomes permanent.

Stage 3 — Money mapped

  • Confirm each fund maps to the correct account, including new funds created during the period.
  • Check restricted allocations against their restrictions before posting.
  • Produce the summary your accounting system needs — not a gift-level dump.

Stage 4 — Period locked

  • Record unresolved exceptions on the close batch instead of leaving them open indefinitely.
  • Capture who signed off and when.
  • Note anything that should be fixed upstream so next month is shorter.

A close that takes three days is usually a data model problem wearing a process costume.

Beneora product principle

Keep reading

Related to this

ArticleReconciliation

Why your bank deposits never match your gift totals

Five structural reasons the two numbers differ, and which of them are supposed to.

7 min
GuideDonor data

Migrating donor data without inheriting its errors

A dry-run-first approach to imports, duplicates, households and recognition preferences.

10 min
GuideOperating model

Operating a recurring giving programme with two staff

Owners, cadences and escalation rules for a monthly programme that does not depend on heroics.

9 min

Design-partner program

We write these from partner sessions

If this matches your week, a working session is the fastest way to make the product fit it. Partners see the honest status of every module and are never charged for a prototype.