Reconciling your donor CRM to the general ledger

The short answer

Your donor CRM is the system of record for who gave, which campaign and fund, and whether a gift is restricted. Your general ledger is the system of record for cash, income recognition, and the financial statements the board and auditors see. Reconciliation means proving that gifts recorded in the CRM equal deposits and income posted in the GL for the same period, after processing fees, refunds, and fund coding. Integrations reduce keying; they don't remove the need to match totals and clear exceptions.

The table below shows where each platform's path into the GL actually differs.

Quick reference

Bloomerang

Bloomerang's own help center confirms QuickBooks Online users connect directly to sync transactions, while Desktop users transfer transactions through an IIF export. Funds map to QuickBooks classes, and a nonprofit controls which QuickBooks accounts receive which gift types, down to custom mapping rules by fund, campaign, appeal, type, or method (Bloomerang). The CRM stays the place for donor and campaign detail; QuickBooks receives the financial impact.

Two details worth knowing before relying on the sync: Bloomerang's own documentation states plainly that "pledges do not sync because they cannot be represented as sales receipts in QuickBooks Online," and on the reverse direction, refunds and multi-line sales receipts don't sync back from QuickBooks to Bloomerang either (Bloomerang). Reconciliation still requires comparing Bloomerang gift totals, by fund and campaign and date, to QB income and to bank deposits. Online gifts often hit the bank net of processor fees, while the CRM shows gross.

DonorPerfect

DonorPerfect's own site confirms the integration in detail: gifts map to a QuickBooks bank account, income accounts, and classes, and a practice can post gifts as individual entries, a daily summary, or a monthly summary (DonorPerfect). Quick-access filters separate unposted gifts, ready to be posted, from posted gift history, which supports a controlled handoff from development to finance rather than an all-or-nothing sync.

Treat DonorPerfect as the gift source of truth and QuickBooks as the ledger. Month-end should prove three things agree: CRM gifts in the period, QB donation income adjusted for fees and refunds, and bank deposits attributed to fundraising.

Raiser's Edge NXT

Raiser's Edge NXT posts gift batches directly to Blackbaud Financial Edge NXT, confirmed directly from Blackbaud's own support documentation: posting creates journal references visible right in the Raiser's Edge NXT interface, with links back to Financial Edge NXT for every posting, and a defined journal reference and journal code open the journal entry (Blackbaud). Worth knowing before a close: gift batch details expire after 29 days if left unposted, and a returned gift or a posting error can be reversed directly in Raiser's Edge NXT. For non-Blackbaud ledgers, RE can produce a posting export that other systems import instead.

For organizations processing payments through Blackbaud's own merchant services, a feature called Deposit Connect, also described in Blackbaud's documentation as Automated Deposits, pulls gift amounts, fees, the record ID, and the disbursement report from the processor directly into Financial Edge NXT to build the deposit, specifically to cut down manual reconciliation (Blackbaud). Blackbaud's own warning is explicit: only gifts disbursed through Blackbaud Merchant Services are included in that automated workflow; anything processed elsewhere still needs manual reconciliation.

Even with native FE posting, finance still reconciles batch totals to bank activity and confirms fund restrictions match GL dimensions. Rejected, expired, or unposted batches are a common source of CRM-to-GL gaps.

Little Green Light

Little Green Light's own help docs describe the mechanics plainly: push gifts over to QuickBooks, where they create Sales Receipts, with the funds landing in the Undeposited Funds asset account, then "you'll then need to move those funds from Undeposited Funds to the bank account" through a separate deposit step (LGL). Gift category maps to QuickBooks product or service; campaign or fund maps to class.

That manual deposit step is the detail worth underlining: the sync creates the sales receipt automatically, but someone still has to batch and deposit those receipts in QuickBooks before cash actually moves out of the holding account. For QuickBooks Desktop or other ledgers, LGL documents lump-sum reports and disciplined double-entry or import workflows instead. Only certain transaction types, gifts and other income, flow through the QBO integration the same way; pledges and in-kind gifts need separate handling.

Worked example: the shared failure mode

A nonprofit records the following for one month, regardless of which of the four platforms it runs:

Add it up and three gaps appear. $890 in fees was never expensed, or never used to reduce income. $400 in refunds isn't reflected the same way in both systems. $410 is still unexplained, a timing gap, a miscoded deposit, or a gift sitting in the CRM that hasn't actually been deposited yet.

The bank reconciliation can still clear if other cash happens to fill the hole. The CRM total and the audited contribution total won't match until fees, refunds, and timing are all aligned, no matter how good the sync is.

A process that works on any of the four

1. Freeze a period in the CRM. Gift date or deposit date, pick one rule and stick to it consistently.

2. Export or report gifts by fund or campaign and payment method.

3. Pull GL donation income and related fee expense for the same period.

4. Pull bank deposits attributed to fundraising, along with any processor payout reports.

5. Match the chain: CRM gross, through fees and refunds, to net cash, to the GL.

6. Clear exceptions before close: unposted batches, the wrong fund, a deposit with no matching gift, or a gift with no matching deposit.

How Numetix works with donor CRMs

We sit alongside Bloomerang, DonorPerfect, Raiser's Edge, or Little Green Light, and whatever ledger a nonprofit already runs. AI helps match bank and processor activity to CRM gift batches and fund codes. A CPA-overseen team owns the monthly tie-out, so contribution revenue, restricted funds, and cash stay consistent for board and audit.

A practical first step: send us a period gift report from your CRM, broken out by fund, a processor payout or deposit report, and the GL donation activity for the same dates. We'll show you the matched totals and the open exceptions. Book 30 minutes with our team. More on how Numetix serves nonprofit organizations.

Frequently asked questions

Is the CRM or the GL the system of record for revenue? The CRM for donor, campaign, and restriction detail; the GL for financial statements. They have to reconcile; neither one replaces the other.

Do integrations eliminate monthly reconciliation? No. They reduce double entry. Someone still has to prove that CRM totals, fees, and bank deposits agree with the ledger.

How should processing fees be handled? Consistently, either netted against contribution income or booked as a fundraising expense, never left invisible so the CRM's gross figure and the bank's net figure silently drift apart.

What about pledges versus cash? Pledges can live in the CRM before cash ever hits the bank. GL recognition follows the organization's accounting policy, often cash or when verifiable. Reconcile cash gifts and pledge receipts separately from open pledge balances.

Which report should finance request every month? Gifts by fund, and by campaign if used, for a locked date range, with payment method and whatever "posted to GL" flag the CRM provides, plus processor deposit reports for online giving.

Can a native sync replace a bookkeeper for a nonprofit? No. A sync reduces keying. Someone still has to confirm fund coding, catch pledges and refunds that didn't sync, and prove the three-way match before the books close.