Head to System Settings > Financial Gateways and add a new Gateway. Select Subsplash Gateway and have it use your Subsplash API client:

Activate the Gateway and click Save.

Start by going to Admin > Installed Plugins > Subsplash > Funds and Sync Funds to bring over your Subsplash Funds into Rock.

You will see a row for each Fund and Sub-fund you have in Subsplash, and if you use Campuses, there will be additional rows with the same Fund name but different campus names:

When first synced, there will be no Rock Account selected, and you can start mapping Funds to Accounts. A Fund can be mapped to many Accounts as needed.

After mapping funds to accounts, select Sync Transactions and set your date to your first gift in Subsplash. This will backfill Rock with your Giving data.

You can return to this page at any time if you need to sync gifts manually on specific days or time frames.

So you do not have to sync each day manually, we recommend setting up our job!

In Admin > System Settings > Job Administration, click + to add a new Job. Look for "Sync Subsplash Donations (Plugin)" and select your Subsplash Financial Gateway:

Your Cron Expression will be how often this job runs; we recommend at least nightly. Your number of days back to sync will be set to 14 days by default to cover ACH processing times.

At this point, your existing donations should have been synced over from the initial Sync Transactions step above, and they will continue to sync thanks to the job.

The plugin will return various information during its donation sync, but most importantly, it will let you know if any gifts, recurring gifts, or payments could not be sent over to Rock. There are two intentional exceptions that need attention.

If a gift, recurring gift, or payment is associated with a profile in Subsplash that does not have a first/last name and or email, then we cannot map it to a Contact in Rock.

To fix this, we will provide the id in the exception, and you can search in Subsplash for it and find the profile that's associated. Then fill in missing details as needed.

If a fund, sub fund, or campus in Subsplash is not mapped to a Rock account, but we try to sync it over to Rock, it will result in this exception. To fix this, you go to Admin > Installed Plugins > Subsplash > Giving > "Pull funds" and make sure all rows have a Rock account selected.

Since donations are processed through Subsplash, your Transfer will always come from Subsplash and show on the Transfers page, but you do have control over batches in Rock.

In your Installed Plugins > Subsplash > Settings, click on your API client. The Batch Method dropdown option will have:

When Subsplash transfers are synced, donations and non-charitable payments are organized into separate batches in Rock. As donations come in, they are initially placed into a batch called Subsplash Pending Transfer until the payout is processed. Once the transfer completes, that batch is renamed to Subsplash Transfer followed by the transfer ID.

Non-charitable payments follow a similar flow but are placed into their own distinctly named batches labeled Subsplash Event Transfer, followed by the transfer ID.

Once the batches post in Rock, navigate to Giving > Transfers in Subsplash, open the corresponding transfer based on the ID, and export the transfer folder. The exported folder will have a donations file and a payments file, making it easy to quickly reconcile with each Rock batch.

Refunds cannot currently be initiated through Rock. You will receive an intentional error that lets you know to initiate a refund in Subsplash to return the money to your donor.

When a refund occurs in Subsplash, the automatic sync job or manual sync will update the status of the original transaction in Rock and create a new transaction to balance out the funds, subtracting the amount.

Donor covered fees (DCF) will be included in the same transaction as the donation. By default, the fees will be associated with the same account as the original gift. If you would like to move them into their own account, you can adjust the plugin settings.

This feature simplifies pledge tracking by automatically splitting a gift into two transactions: the intended gift and the covered fee. By sweeping fees into a separate Rock account, only the net gift amount applies toward a donor’s pledge, which prevents their progress from being inflated.
​

It also ensures tax statements match donor expectations by reflecting the exact intended gift per fund while categorizing fees separately. Because the plugin also handles refunds and disputes automatically, admins can maintain clean, accurate reporting in Rock without the need for manual adjustments or complex reconciliation.

Either the job failed to sync the transaction into Rock, or it was synced over to a different person than the one you are looking at. If your batch numbers are not matching correctly, then it's safe to say the transaction is missing from Rock altogether, and you should determine why the job is failing and/or why that specific gift is failing to sync. Some common reasons would be missing the first name, last name, and/or email for the person in Subsplash. If your batches match, then the transaction is somewhere in Rock, but you may be wondering why it's not associated with the right person. Make sure they did not give under a different email address in Subsplash or that they have a duplicate contact in Rock.

At the moment, payments are not synced to Rock, and refunds only support donations. Payment refunds will need to be initiated in Subsplash but manually created in Rock for the time being.