Go to Installed Plugins, select Subsplash, and click on your API client. Find the Batch Method dropdown option.

Subsplash organizes donations and non-charitable payments into separate batches in Rock. New donations enter a temporary batch named Subsplash Pending Transfer. Rock renames this batch to Subsplash Transfer, followed by the transfer ID once the payout completes. Non-charitable payments enter separate batches labeled Subsplash Event Transfer, followed by the transfer ID.

To reconcile your records after the batches post in Rock:

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 fees into their own account, you can adjust the plugin setting in your API Client Finance settings and designate a default Rock account for them.

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.

The sync job failed or matched the gift to a different contact. Check if your batch numbers match. If the numbers do not match, the transaction is missing from Rock. Verify if the Subsplash profile is missing a first name, last name, or email. If your batches do match, the transaction exists in Rock. Verify if the donor used a different email address or has a duplicate contact profile in Rock.

You can issue refunds from Rock or Subsplash. Learn more about this process in our Rock & Subsplash: Full & Partial Refunds article.