When gifts are synced from Almabase, they land in Raiser's Edge NXT as an uncommitted batch — a holding area where your team can review everything before it becomes part of the permanent record. This gives you a chance to catch any issues with amounts, constituent assignments, fund allocations, or campaign codes before the gifts are finalized.
Until the batch is committed, the gifts won't appear on constituent records, in fundraising reports, or in any queries. This article covers how to find your batch, what to check, and how to confirm everything landed correctly.
Step 1: Find the Batch
Log in to RE NXT
Go to Gifts → Overview
Look for the batch from your Almabase sync
If you noted the batch number during sync (visible in Almabase under the gift's Sync Details), you can search for it directly.
Step 2: Review the Batch
Open the batch and review the gift details. Check for:
Amounts — do they match what you expect?
Constituents — are gifts assigned to the correct donors?
Funds — are gifts allocated to the right funds?
Campaign, Appeal, and Package codes — are the metadata codes correct?
Gift Type — one-time vs. recurring, cash vs. check, etc.
If you configured gift attributes at sync time in Almabase (or at the giving page level), those values should already be applied. This review is your opportunity to catch anything that looks off before it becomes permanent.
Tip: If you need to make changes to individual gifts within the batch, you can edit them directly in RE NXT before committing. Once the batch is committed, changes must be made on the individual gift records.
Step 3: Commit/Approve the Batch
Once you've reviewed the batch and everything looks correct, approve/commit it.
After committing:
Gifts appear on constituent records in RE NXT
Gifts are included in fundraising reports and queries
In Almabase, the sync status for those gifts updates from "Added to a batch" to "Synced"
Step 4: Spot-Check Constituent Records
After committing, it's good practice to spot-check a few constituent records to make sure the gifts landed correctly.
Open a constituent who received a gift in the batch
Check their Giving History — the gift should appear with the correct amount, date, fund, and campaign/appeal/package codes
Repeat for two or three other constituents to confirm the batch processed cleanly
FAQs
Q: Can I add more gifts to a batch after it's been created?
Yes — as long as the batch hasn't been committed yet. When you run another sync from Almabase and select an existing batch, the new gifts are added to it. Once a batch is committed, you can no longer add gifts to it.
Q: What if I find an error in the batch before committing?
You can edit individual gifts within the batch directly in RE NXT before committing.
Q: The sync status in Almabase still shows "Added to a batch" even though I committed. Why?
It can take a short time for the status to update. If it persists, reach out to Almabase Support for help.
Q: Does Almabase create one batch per gift list/segment?
Not necessarily. A gift list/segment in Almabase is a way to group gifts for sync — it doesn't map one-to-one to a batch in RE NXT. You choose the batch at sync time, so gifts from different lists/segments can go to the same batch, and gifts within a single list/segment can be added to different batches across separate sync runs. You can create a new batch for each sync or reuse an existing uncommitted one — whichever fits your workflow.