Gifts are now automatically synced between the church giving platform and the Church Community Builder (CCB) church management system (ChMS)!!!

That’s right, no more double entry, .csv exporting and importing, or managing two separate systems. Happy days for all.

Here’s how it works:

A gift/donation is made to your church via the mobile app, text-to-give, or online giving from your church’s website.That gift/donation is processed in the giving platform and automatically sent over to CCB.Once the gift/donation is in CCB it will be auto matched to existing members or, if not auto matched, you can match it to a person in the system. When matching is complete you can create your batch and be done.

Below is an example of where you’ll see giving transactions show up in CCB prior to them going through the transaction creation process.

Financials > Online Gifts is where you’ll find the below screen. Unmatched people will show up on the Step 1 tab while those who match an existing CCB people record (eg. your members) will be matched based on email and show up on the Step 2 tab where you can create the CCB transaction.

After you’ve successfully matched everyone and created all your transactions this list will be empty.

Gifts made via showing up in the CCB “create transactions” dashboard.

Once gifts have been matched and transactions have been created the transactions will show up on peoples CCB records like you see below.

To see this information, when on an individuals record, go to the Financial tab and you’ll see a list of transactions. created transactions will show up as coming from an “online” source. Date, fund/designation, source and gift amount will all show up right where you’re used to seeing it.

Gifts made via showing up on a church members CCB record.

There you have it. + CCB = Yiippeeee for all you churches that use our systems to enhance the great work you’re doing.

Connecting CCB and is Simple.

Create a new API user in CCB. That can be done by clicking on the gear in the top right corner of CCB when logged in and then going to the API button.

Once you’re in the API area, click on the “add new API user” button and fill out all the appropriate information.

After filling out the information be sure to click on the “Services” tab in the blue menu then select the “online_giving_insert_gift” and “transaction_detail_type_list” checkboxes.

Be sure to write down the username and password. You’ll need it when you head back over to to complete the setup. Click the “Save button to save the new API user.

Once you’ve saved the new API user, be sure to take note of your CCB API URL. This can be found on the summary screen of the API section in CCB.

After you’ve created the new API user you’ll head over to the ChMS sync section of

Once there, select “Church Community Builder” from the drop down and fill in the appropriate information.

This includes the CCB API URL, your new CCB API username and password, and an optional campus ID if you have multiple campuses.

Remember, your CCB API URL can be found on the summary screen of the API section in CCB. The URL will look something like what you see in the screen shot to the left.

After you’ve filled in the appropriate information, click save and voila, you’re done.

We hope this systems integration helps your church be more efficient and effective! And by all means, please send us your questions, feedback, and of course any encouraging comments you feel inclined to share :)

*We recommend that you audit integrations on a bi-weekly basis to ensure that everything is working accordingly and no donations are incorrectly syncing

Note: If you need to add or change a giving type in this MUST be done in CCB first. You go to the chart of accounts in CCB, update or add the giving type, and then head to the Integrations tab in and enter your CCB API Username and CCB API Password and click Save. This will automatically sync the giving types. If you edit giving type in without following the above process the gifts will not match. 

Note: Transactions from will come over immediately at time of transaction 

Did this answer your question?