Recurring gifts follow the same gift list process as one-time gifts — you create a list, validate, and sync. The difference is what happens after the initial sync, and it depends on your payment gateway.
This article covers how recurring gifts sync for both Stripe and BBMS, what to watch for, and how to confirm everything landed correctly in RE NXT.
Before You Start
Prerequisites
The same prerequisites that apply to one-time gift sync apply here:
The connected RE NXT account must have Solution Admin Rights
Every fund receiving recurring gifts must have a valid External Database ID matching RE NXT
Every recurring gift donor must be mapped to a constituent with a valid System Record ID
If any of these are missing, the sync will fail — just as it would for a one-time gift.
The two records that make up a recurring gift
Raiser's Edge tracks recurring donations using two linked records:
A Recurring Gift is the parent record — the donor's ongoing commitment (e.g., "$50/month"). It's created once and stays in place for the life of the commitment.
A Recurring Gift Payment is each individual charge under that commitment — the first $50, next month's $50, and so on. Every payment links back to its parent Recurring Gift.
Stripe: One Sync Cycle
For Stripe-powered recurring gifts, the process works like this:
Add recurring gifts to a gift list — You can include them on the same list as one-time gifts, or create a separate list. Recurring gifts are identifiable by their gift type in RE NXT.
Validate and sync — Run the sync just as you would for one-time gifts.
Commit the batch in RE NXT — Once committed, a recurring gift record is created on the constituent with the first payment attached.
Future payments — Subsequent payments are handled automatically by the payment gateway. They will land in RE NXT the same way — no additional action is needed from your side.
Tip: Create a gift segment with filters for recurring gifts and an open-ended date range. New payments will be added to the segment automatically, so you don't have to build a new list each month.
BBMS: Two Sync Cycles
For BBMS-powered recurring gifts, the initial setup requires two separate sync-and-commit cycles before future payments are handled automatically.
Sync #1: Create the recurring gift record
Add the recurring gift to a gift list and sync
Commit the batch in RE NXT
This creates the recurring gift record on the constituent — but no payment is attached yet
Sync #2: Attach the first payment
Go back to the same gift list in Almabase
Run the sync again
Commit the new batch in RE NXT
The first payment is now attached to the recurring gift record
After the two cycles
Once both syncs are committed, future payments are handled automatically — the payment gateway processes subsequent installments on its own without any action needed in Almabase.
Why two cycles? The recurring gift record and the first payment are separate objects in RE NXT. Putting each into its own batch gives you the chance to review the recurring gift record, make any edits to it, and catch any issues before the payment is attached. This two-stage process is currently available on BBMS only.
How to Confirm the Sync Worked
In Almabase:
Open the gift list and check the Sync Status column. After all required syncs are committed, the status should show as synced.
In RE NXT:
Go to Fundraising → Gift Management and look for the batch. Once committed, the recurring gift record should appear on the constituent's record with the first payment attached. For BBMS, you'll see two batches — one for the record, one for the payment.
FAQs
Q: Can I include recurring gifts and one-time gifts on the same list?
Yes. You can sync them together or keep them on separate lists — whichever works for your workflow.
Q: I've completed Sync #1 for a BBMS recurring gift. How do I trigger Sync #2?
Go back to the same gift list and run the sync workflow again. The system knows the first cycle is done and will push the first payment this time.
Q: What happens if a recurring gift donor isn't mapped before the next payment
The payment will fail to sync. Make sure all recurring gift donors are mapped to a constituent with a valid System Record ID before the next payment date. Almabase sends reminder emails for unmapped gifts to help you stay ahead of this.
Q: Do I need to do anything for subsequent monthly payments?
No. Once the initial setup is complete — one sync cycle for Stripe, two for BBMS — subsequent payments are handled automatically by the payment gateway and will land in RE NXT without any action from your side.
Q: What if the first sync (BBMS) fails — do I need to start over?
No. Fix the underlying issue (missing System Record ID, fund ID, etc.), then re-run the sync on the same list. The system tracks what's been synced and what hasn't, so only the failed items are retried.