Guide
Connecting your donor database to your accounting, so donations reconcile
By Mavrin Labs. Published . Last updated . Reviewed by Mavrin Labs on . How this guide was researched and checked.

Your donor database, often called a CRM, is the program that records who gave, what each gift was for and who gets the thank-you, while your accounting system records the money. Connecting the two means each gift is entered once and both systems agree on it, so the board, the auditor and the donor all see the same gift.
The guide is written for the finance or operations lead of a nonprofit with paid staff, a board and an outside accountant or auditor. It covers why the two systems disagree, what to map, whether to integrate or reconcile, what a sync should do and what a person still checks. It is not tax, audit or legal advice.
Sources last checked Monday, November 16, 2026, or, where a citation says so, a later date. Mavrin Labs reviews this guide every quarter, and each source's own page always wins over it.
What is a donor database integration?
A donor database integration is a software link that posts each gift from the donor database into the accounting system by written mapping rules, so a gift is entered once and both systems agree on it. It replaces the retyping, not the monthly check.
It is one kind of link between a CRM and another system, which the page on what a CRM integration is defines in general.
Most links post one summary for each deposit batch rather than every single gift, and they stop at any code they do not recognize. Whether you need a link at all is a later question in this guide, because the monthly reconciliation comes first either way.
Why it matters: more gifts to match each month
Most charitable money in the U.S. comes from individuals, and a donor database is where those gifts are recorded.
Giving USA 2026 puts giving by individuals at $394.2 billion of the $617.20 billion given in 2025 (the Giving USA announcement, checked Monday, November 16, 2026). Each gift has to reach the books once, with the right fund, date and restriction.
Matching gifts by hand is clerical work, and the hours it takes are paid hours. A clean map and a monthly sheet save those hours for the questions that need a person.
Why do the donor database and the accounting system disagree?
The donor database and the accounting system disagree because they record different events for different jobs. The database records a gift when a donor makes it, and it credits the people connected to that gift. The books record money when it moves, and they follow accounting rules on promises and restrictions. Both can be right and still show different totals.
Six causes explain most of the gap: timing, pledges, fees, soft credits, returned gifts and restricted gifts (gifts a donor has limited to a purpose or a period). Each one below says what each system records and what to agree before anyone builds a link.
What should you map between the two systems?
Map each code the donor database uses to exactly one place in the accounting system, and write the map down before anyone builds a sync. Three codes matter most. A fund says what a gift is for, and a campaign says why it came in, such as a spring appeal or a dinner.
A class is the tag the books use to report by program.
Each fund maps to one revenue account, one restriction status and one class. Campaigns usually stay in the database, because the books need only the kind of revenue. A gift with no mapping should wait for a person, never land in a catch-all account.
| Database code | What it says | Where it lands in the books | Who signs off |
|---|---|---|---|
| Fund | What the gift is for | A revenue account, a restriction status and a class | Finance lead |
| Campaign or appeal | Why the gift came in | The kind of revenue, such as gifts or event income | Development lead and finance lead |
| Gift type | Cash, stock, goods or services | A separate account for gifts that are not cash | Finance lead, with the auditor on values |
| Batch number | Which deposit the gift belongs to | The memo on the journal entry for that deposit | Whoever posts the deposit |
Event gifts need one more split. When a donor pays for a dinner ticket, part of the payment buys the meal and only the rest is a gift.
Above an amount the IRS sets, the charity must give the donor a written statement with a good-faith estimate of what the donor received. Record the two parts separately, and map each part to its own account.
Should you integrate the two systems or reconcile them each month?
Reconcile the two systems every month, whether or not software connects them. Reconciling means comparing the totals, explaining every difference and fixing the record that is wrong. Integration is a separate decision: an integration moves gifts into the books by software instead of by hand, and it earns its place only once the map has stopped changing.
Integration removes the typing, not the checking, because a sync can only repeat the rules it was given.
Reconciling by hand is enough while:
- gifts are few, and most arrive by check;
- fund and campaign codes still change often;
- one person enters the gifts and can explain each one.
Integration earns its place once:
- online gifts arrive in payout batches every week;
- staff type the same gift into both systems;
- the map has stayed the same through several month-ends;
- your finance lead can write down every rule the sync must follow.
How do you reconcile donations with the books each month?
You reconcile donations with the books each month in five steps, from closing the month's gift batches to signing the sheet. One person prepares it and a second person reviews it, so nobody checks their own work. The steps stay the same every month, so the one-page sheet further down can be reused each time.
- Close the batches. Finish entering the month's gifts and close each deposit batch in the database.
- Total both sides. Total the database by fund and by batch, and the books by account and class, for the same dates.
- Match the deposits. Tie each batch to a bank deposit and to the journal entry that recorded it.
- Explain each gap. List every difference with its cause: timing, a pledge, a fee, a soft credit, a returned gift or a restriction.
- Fix at the source. Correct the wrong record in the system where it was first entered, then sign and date the sheet.
What should a sync do, and what should it never do?
A sync should move agreed totals from the database into the books, by the rules your finance lead wrote, and stop at anything it does not recognize. A sync is the software link that copies records from one system to another on a schedule.
Give the sync its own sign-in, with only the access its job needs. NIST calls this least privilege: each user or process gets the smallest set of permissions its task requires (the NIST glossary entry). A sync that signs in as a staff member can do anything that person can.
A sync should:
- post one summary entry for each deposit batch, split by fund, account and class;
- carry the batch number into both systems, so anyone can trace a deposit to its gifts;
- hold any gift with an unmapped code in a queue for a person;
- keep a log of what moved, what waited and who released it.
A sync should never:
- create accounts, funds or classes in the books on its own;
- post into a month your finance lead has closed;
- change or delete a gift in the database to match the bank;
- copy donor names and notes into the books when a summary will do;
- send a thank-you or any other message before a person approves it.
What does a person still check?
A person still checks every difference the sync cannot explain, and every decision that needs judgment. Software can total, match and flag, but it cannot tell whether a gift was restricted or a pledge had a condition, so a person reads those cases before the month is closed.
Thank-you letters need the same care, because the letters come from the database and their amounts have to match the books.
A donor needs a written acknowledgment for any single gift of $250 or more, and the charity's statement gives the amount and says whether the donor received anything in return (IRS Publication 1771, checked Wednesday, November 18, 2026).
A payment of more than seventy-five dollars that is partly a gift, such as a dinner ticket, needs a written statement with a good-faith estimate of what the donor received (the same IRS publication).
Each month, the person checks:
- that the unexplained line on the sheet reads zero;
- any new fund or campaign code, before its first gift;
- restricted gifts received, and releases when a restriction is met;
- pledges and grants with conditions, against their payment schedule;
- at year-end, contributor totals for Schedule B, taken from real gifts and not soft credits.
What does a one-page reconciliation sheet look like?
A one-page reconciliation sheet starts from the database total and ends at the bank deposits, with one line for each cause of difference. Copy the table below into your own spreadsheet, keep one sheet for each month, and file it with that month's bank statement.
If the same line appears month after month, fix its cause rather than explaining it again.
| Line on the sheet | What it shows |
|---|---|
| Gifts in the database | The month's gifts by fund, from the database's own report |
| Soft credits | Recognition that is not money, taken out of the total |
| Timing items | Gifts made this month but deposited next month, and the reverse |
| Processing fees | What the processor kept from each payout |
| Returned or reversed gifts | Each one, with the date of the original gift |
| Event benefits | The part of each ticket that bought something, recorded outside the gift |
| Deposits in the bank | The month's deposits, which the lines above should reach |
| Pledges and restricted gifts | New promises, payments, restrictions and releases, set beside the books |
| Unexplained difference | What is left over, which should read zero |
| Sign-off | Who prepared the sheet, who reviewed it and the dates |
How can Mavrin Labs help connect the two systems?
Mavrin Labs helps by building the link between a donor database and an accounting system, as part of its CRM and systems integration service. A sync it builds follows the map your finance lead approves, holds any gift it cannot place and, by default, sends nothing to a donor until a person approves it.
Every engagement starts with a workflow assessment, and a build includes a written design plan and acceptance tests, so your finance lead can check the map before any link goes live.
A care plan covers monitoring, fixes and updates when a provider changes something. Mavrin Labs never uses client data to train AI models, and your organization owns all of its data.
Mavrin Labs gives no tax, audit or legal advice. The page on how a Mavrin Labs build treats your data sets out each data term in full.
Key takeaways
- The two systems disagree for ordinary reasons: timing, pledges, fees, soft credits, returned gifts and restrictions.
- Map every fund, campaign and class to one place in the books, and write the map down.
- Reconcile every month, whether or not a sync connects the systems.
- Let a sync move agreed totals, and leave every accounting decision to a person.
- Keep one signed sheet a month, with the unexplained difference at zero.
Sources behind this guide
Every source in this guide was last checked on one of the two dates at the top of the page, and the guide is reviewed quarterly. The table below pairs each outside fact with its publisher.
| Fact | Source |
|---|---|
| The date of a gift, what a thank-you letter states, and the statement for a payment that is partly a gift | IRS publication on charitable contributions |
| When a promise counts as revenue, and gifts with or without donor restrictions | FASB update on contributions received |
| Which contributors the annual return lists, and how their gifts are totaled | IRS instructions for Schedule B |
| Each user or process gets only the access its task needs | NIST glossary entry on least privilege |
| Giving in 2025, and the share from individuals | Giving USA announcement |
| The two classes of net assets | FASB update on nonprofit financial statements |
| What a written acknowledgment must hold | IRS page on written acknowledgments |
A processor's own payout schedule is the place to confirm when its batches reach the bank. This guide names no processor, so read your processor's help pages for the timing that applies to you.
Corrections and changes, newest first:
- Wednesday, November 18, 2026: the IRS publication on charitable contributions was read again and its dated citations now give that date. A passage on why the contribution rules changed, a diagram of one gift's path, and two primary sources (the FASB update on net assets and the IRS page on written acknowledgments) were added.
- Tuesday, November 17, 2026: the title and main heading changed to name reconciling donations, the paragraph pointing to the donor follow-up demo was removed with the demos, and the written-acknowledgment rule was added to the section on returned gifts.
- Monday, November 16, 2026: the definition section and the section on why it matters were added with the Giving USA figures, and the paragraph on the IRS publication was split.
Where to go next
The page for nonprofits shows the workflows Mavrin Labs looks at first for nonprofits with paid staff. Systems integration explains how a link is mapped, tested and watched.
If the books are not the first fix, the six-question project finder asks where your team's hours go and points to the project to start with.
For duplicate records and failed messages, work through the integration checklist. If the same gift data feeds board and funder reports, data and reporting covers how those reports come together, and the guide to nonprofit grant reporting straight from the books shows how restricted gifts reach each funder's report.
If a link between the two systems is worth building, the guide to the technology grants for nonprofits Florida foundations offer locally sets out who might pay for part of it. To talk through one workflow, start a conversation.
Frequently asked questions
Should donor names go into the accounting system?
Donor names rarely need to go into the accounting system, because the books report money by fund, account and class rather than by person. One summary entry for each deposit keeps donor details in the database. Your finance lead and your auditor decide whether any gift needs a name in the books, such as a large grant with conditions.
Which system is right when the totals differ?
Neither system is right by default when the totals differ, because each one answers a different question. The bank statement settles how much money arrived. The database settles who gave and what each gift was for. The books settle what the organization reports. The monthly sheet explains the gap, and a person fixes the record that is wrong.
Do we need special software to reconcile each month?
You do not need special software to reconcile each month. A gift report from the database, the bank statement and the revenue report from the books are enough, set side by side on the one-page sheet in this guide. Software helps once matching gets slow, but the sign-off stays with a person.
Is this guide tax or audit advice?
Nothing in this guide is tax, audit or legal advice, and Mavrin Labs gives none. The guide explains in plain words what a few public sources say, and it links each one so you can read the source yourself. Your finance lead, your auditor and your counsel decide how your organization records and reports its gifts.
