Rock Solid Finances

Integrating financial tools with a people-centered focus to maximize donor management.

Current Version: McKinley 1.0
Note: A newer version of this book is available. Use the version dropdown to switch to the newest version.

Updates for McKinley 1.0

No updates made.

Updates for McKinley 2.0

No updates made.

Updates for McKinley 3.0

No updates made.

Updates for McKinley 4.0

Below is a summary of the updates for this version.

  • Added some notes about the transaction date used when scanning checks.
  • New recommendation on using the latest Ranger driver with Canon check readers.
  • Added a few updates to the check scanning software section.
  • Updated details on the batch blocks and the new batch audit log.
  • New chapter on the Giving Analytics block.
  • Updated the transaction screens with several small changed. Also noted that in Rock v4.0 all transactons must be in a batch.
  • New chapter on Benevolence.
  • Added description of the new Pledge Analytics page.
  • Documented the new Transaction Source option for the scanning application.
  • Added documentation for the new Saved Payment Accounts page.
  • Documented the new dataview filter on the statement generator.
  • The Pledge List block has a new Last Modified column and plenty of new block settings to make the block a powerful tool for your external website..
  • Added a new section on how to refund a transaction.
  • Added information on additions to the transaction list.

Updates for McKinley 5.0

Below is a summary of the updates for this version.

  • Added information on the new NMI gateway.

Updates for McKinley 6.0

Below is a summary of the updates for this version.

  • Documented the new features of the benevolence request system.
  • Added information on the new contribution statement list on the person profile page.
  • Added information about how to create new custom financial account attributes.
  • Added additional security actions to Security for Finance chapter.
  • Added Transactions Created Using Teller Import section to Batches chapter.
  • Removed PDS from Payment Gateway options in Payment Gateways chapter.
  • Added block names in Online Contribution Statements section of Contribution Statements chapter for clarification.
  • Corrected callouts on Account Detail screen in Accounts chapter.

Updates for McKinley 7.0

Below is a summary of the updates for this version.

  • Added details on how to handle transferring to new payment gateway.
  • Updated Account Detail screenshots and noted hierarchical navigation structure.
  • Updated Giving Analytics screenshots to show Advanced Options and updated callout information.
  • Added Payment Reversal Notification Workflow documentation to Payment Gateways and NMI Gateway sections.
  • Added Giving Envelopes chapter.
  • Added screenshot and callouts for Business Contributions Detail Page and added information about setting up scheduled transactions for businesses.
  • Updated Scheduled Transactions screenshot and callouts.
  • Updated Downloading Transactions configuration options in the Payment Gateways chapter.
  • Added Financial Batch Attributes information to the Batches chapter.
  • Added Advanced Transaction Entry Block Settings chapter.
  • Updated Statement Generator screenshots and documentation to include Save Settings in the Contribution Statements chapter.
  • Added additional security actions to Security for Finance chapter.
  • Added Transactions Created Using Teller Import section in Batches chapter.
  • Added Automated Batch documentation and screen shot to Batches chapter.
  • Updated Statement Generator steps and screenshots in Contribution Statements chapter.
  • Removed PDS from Payment Gateway options in Payment Gateways chapter.
  • Added block names in Online Contribution Statements section of Contribution Statements chapter for clarification.
  • Updated Statement Generator screenshots and information.

Updates for McKinley 8.0

Below is a summary of the updates for this version.

  • Updated Statement Generator screenshots and information.
  • Added Converting a Person to a Business section to Businesses chapter.

Updates for McKinley 9.0

Below is a summary of the updates for this version.

  • Added support for Image Safe Magtek check scanner
  • New check-scanner UI and added features

Updates for McKinley 10.0

Below is a summary of the updates for this version.

  • Added details to describe single-campus behavior.

Updates for McKinley 11.0

Below is a summary of the updates for this version.

  • The credit card expiration notice job can optionally delete expired cards
  • Businesses can now be merged in the same way as person records

Updates for McKinley 12.0

Below is a summary of the updates for this version.

  • The Rock Statement Generator has a new look and new features

Updates for McKinley 13.0

Below is a summary of the updates for this version.

  • The Business Detail page has been updated with a new look and new features
  • The new Giving Overview features provide detailed analysis of a person's giving and innovative alerts when an individual’s giving patterns change
  • Benevolence Requests have new features and options as well as a redesigned look
  • The Statement Generator software now allows you to save your configuration for future runs, provides additional run details, and lets you save the run information to a file

Updates for McKinley 14.0

Below is a summary of the updates for this version.

  • Text Giving allows people to donate from their phone by sending a simple text message

Updates for McKinley 15.0

Below is a summary of the updates for this version.

  • Businesses can now have Actions like the existing Actions on the Person Profile (e.g., launch Photo Request workflow)
  • The new Utility Payment Entry block is the Swiss Army Knife of transaction entry features

Updates for McKinley 16.0

Below is a summary of the updates for this version.

  • Businesses can optionally be stored in attributes of type Person
  • Text Giving has configurable responses for failed transactions

Welcome

Rock is developed on a clear set of objectives. These objectives cover the craftsmanship we want to bring to the product as well as the flexibility we want to achieve through open-source freedom. They also define what the product will do, which by default, defines what it won't do. Here’s what Rock is all about: we seek to improve relationships through quality software and processes. This means that if a tool or process makes a difference to your organization's guest, then we want to work hard to help you achieve success. However, this also means that, while there are a great many important back-office needs for your organization, they won't fit squarely into our charter, at least not at this time.

Sounds complicated, but here’s the bottom line: while a full back-office accounting system is important to every organization, it's not something that fits into our stated mission. Keep in mind that we’re a small team of developers pouring our time and effort into creating a crafted Relationship Management System. In the famous, albeit translated words of Michael Porter, "We can’t be all products to all people."

So, if you've been wondering, "Will Rock replace my accounting system?" the answer is no. That said, Rock does have some key features that organizational accounting teams will love. These features center around donor management since this is a major touch point with your guests. Let’s take a look at what's possible.

It Goes Beyond Gifts:

While we describe many of Rock's financial tools in terms of giving or donations keep in mind they are simply financial transactions. If your organization works around the concept of dues or payments, you can use these same tools. We've worked hard to make these tools be as reusable and multi-purpose as possible.

Financial Components

Before diving into the tools, let's look at the basic financial components of Rock. To do this, we'll step through the components, starting with the person. Again, it's important to note that while we use a scenario of donations, these transactions could just as easily be dues or other forms of payments.

Transactions

Like everything in Rock, it all starts with people. People make financial transactions with your organization through gifts, donations, subscriptions or dues. These transactions can be simple (like money given to a single purpose) or they can be more complex (perhaps a single transaction covers multiple purposes). To be able to handle multiple purposes, transactions have one or more detail records to hold the information for each purpose.

In our example below, Ted has given $110 dollars to Rock Solid Church. One hundred of these dollars are designated for the General Fund account with the remaining ten dollars going to the Building Fund account.

Transactions
Transactions

Batches

Transactions that occur in a similar date range are grouped together into batches. These batches help organize the transactions. They also play a key role in integrating to your General Ledger account system. Instead of re-entering every transaction into your General Ledger, you can enter the batch totals knowing that Rock will keep the historical details for you to reference later if you need them.

In our example below a batch has been created for the weekly gifts for the Rock Solid Church.

Batches
Batch

Accounts

Accounts determine what a transaction is for. In our examples above, both the General Fund and the Building Fund are accounts. These accounts usually tie into your accounting system.

Pledges

While most of Rock's financial tools are designed to be multi-purpose, the concept of pledges is closely tied to the nonprofit world of donations. Pledges allows your members and guests to commit to an amount that they will be giving over a stated period of time.

Batches

As we mentioned earlier, batches are a way of grouping financial transactions. Grouping transactions allows you to better integrate with your General Ledger software. You will only need to move over the batch totals instead of each financial transaction.

Characteristics of Batches

Before we dive into looking at the screens that make up batches let's first review the characteristics of batches.

Item Description
Name The name is used as a basic descriptor of the batch. You can come up with any naming convention you want.
Transaction Total The sum amount of all the transactions in the batch.
Control Amount When dealing with manually entered transactions, it's common to first do a manual count of the transaction totals by hand. This number is then entered into the Control Amount column to be used as a double-check since transactions are individually entered into the system. When you're done entering your transactions, the batch's Transaction Total should equal the Control Amount.
Status Batches can have one of three different statuses:
  • Open: This means that the batch is editable. The details of the batch can be changed and transactions can be modified.
  • Closed: The batch is done and should not be edited. Once you close the batch you should then move its total into your general ledger.
  • Pending: This is a special status used by the check-scanning software. When a batch is in a state of Pending, it means that transactions are still being scanned into the batch.
Start / End Dates These dates provide a date range for the transactions that they contain.
Account Code When you enter the batch total into your General Ledger there will more than likely be a transaction id generated by that system. This field allows you to enter that identifier.

Working With Batches

Batches can be viewed under Finance > Batches. Below is a figure showing the batch list screen with the various filters that are available.

Batches
1 Filters:
The following filters help narrow the batches that are displayed on the list.
2 Batches:
The filtered list of batches with relevant fields.
3 Warnings:
Warnings will be displayed when control amounts do not match transaction totals.
4 Actions:
Clicking the checkbox next to batches and then selecting an action allows you to quickly open or close several batches at once.
Batch Detail
1 Date Range:
The date range of the batch.
2 Amounts:
The transaction total, control amount and variance between the two.
3 Accounts:
This list shows account totals for the accounts that the transactions are tied to.
4 Match Transactions:
Batches that have been created by the transaction scanner need to have each transaction linked to an individual. This button takes you to the screen that assists with this process.
5 Transaction List:
A list of the transactions contained in the batch. Clicking on one of these transactions will take you to the details screen.
6 Add Transaction:
Assuming the batch is not closed, you can add new transactions to the batch.

Transactions

Transactions represent the actual exchange of currencies for activities like donations, event registrations, or other financial events. Each transaction is made up of one or more detail (or sub) transactions. This allows for giving to more than one account in a single transaction.

Where you view transactions in Rock will depend on what you're trying to do. If you're interested in transactions in the context of a specific batch, you can view them on the batch detail page.

Batch Details

Clicking on one of these transactions will then display the Transaction Detail page.

Transaction Detail
1 Person:
Link to the person who initiated and authorized the transaction.
2 Amount:
The total amount for the transaction.
3 Batch:
Link to the batch that the transaction belongs to.
4 Source:
Where the transaction originated.
5 Currency Type:
The form of payment that was used for the transaction.
6 Summary:
Any notes related to the transaction.
7 Updates:
Information about who last updated and processed the transaction.
8 Accounts:
This is the account split for the transaction that shows the details for each account that was included on the transaction.
9 Images:
Any images that are associated with the transaction (e.g. check images).

When you're searching for a specific transaction, it's often easier to use the transaction filtering capabilities found under Finance > Transactions. This screen allows you to provide a set of search options and list transactions that match.

Transactions

On-Site Collection

While the number of online transactions is skyrocketing, we shouldn't neglect to mention the tools that support the traditional on-site collection of cash, checks or even credit cards. Below we'll walk through how we process these transactions in the context of weekly giving.

Processing Cash Transactions

Cash transactions come in two formats: anonymous gifts and gifts given by a known person. Let's look at how we tackle each one.

Anonymous Gifts

Typically you'll enter an anonymous user into your database and link all anonymous gifts to this person. When you count up all of the anonymous cash for the weekend, you can add one transaction for this total amount and select the individual Anonymous.

Known Gifts

There are a couple of options when processing gifts from known individuals:

  1. Manually create transactions for these gifts entering in all the transaction details.
  2. If your organization uses a giving envelope, you could also use Rock's check scanner software to scan in the envelopes. Then, you'd then use the Match Transaction feature discussed below to process the remainder of the transaction information.

Credit Cards

You can add credit card transactions manually by going to the person's Person Profile page. The transaction can be entered using the button on the Transaction List block from the Transactions tab.

Checks

Checks can be scanned using Rock's check scanning software. More information about setting up and using this software can be found in the next chapter. Once the checks are all scanned, they must be matched to individuals and their amounts entered into the correct accounts. We'll discuss that next in the Matching Transactions section below.

Matching Transactions

When you've used the check scanning software to add checks or scanned images of envelopes to a batch you must match them to individuals before you can close the batch. To start this process, open the batch you want to work on under Finance > Batches and then click the Match Transactions button.

This will launch a screen to walk you through each check (or envelope) and allow you to tie them to an individual and enter the amounts into the proper accounts.

Transaction Matching
1 Progress Indicator
2 Add Family:
You may find that the transaction is for someone who is not currently in the system. Using this button will pop up a new window where you can add them.
3 Settings:
Allows you to select which accounts you are entering amounts for.
4 Check Images
5 Individual:
Rock can match a person to the account and routing number of their checking account. If a person already matches the check's account information, you can pick them from the list.
6 Assign To New:
Assigns a new individual to the check’s account number.
7 Person Details:
The screen will present the currently matched person's address and contact information. This is a great way to not only ensure that you have matched to the current individual but also that their contact information has not changed.
8 Account Split:
Accounts are shown to allow you split the checks total across multiple accounts based on notes in the memo field of the check or outside of the envelope.
9 Navigation Buttons:
Buttons at the bottom of the screen allow you to go to the next record or re-visit a previously completed record.

Saved Check Matching

Once a person is matched to a check via the check's MICR information their name will be displayed in the 'Individual' dropdown shown in item #5 above. You can remove someone from this list by removing the bank account from the Contributions tab of their Person Profile page.

Multiple People Matching At The Same Time

With large batches you might want multiple people to work on matching at the same time. Rock allows this by making sure that each person gets a different record to work on.

Scanning Checks

Rock provides special tools to help automate the scanning of large amounts of checks. Let's take a look at what's available.

Supported Scanners

Rock supports two types of scanners with its scanning tools.

Scanners that Support the Ranger Interface

Rock has integrated with the Ranger Interface API toolset from Silver Bullet Technologies. Technically any check scanner that works with the Ranger API should work with Rock. That said, in the process of developing Rock and testing, we have exclusively used the Canon CR-series of check scanners (specifically the CR-50). While other makes and models should also work, we haven't tested them. Ranger provides a list of supported scanners on their website: http://www.sbullet.com/products_ranger_types.html.

MagTek MICRImage

Because of the large numbers of these legacy scanners available, we have also integrated and tested with the MagTek MICRImage check scanners. To use the MagTek MICRImage, please install the drivers from https://www.magtek.com/support/micrimage. If you're in the market for new scanners, we highly recommend using the Canon CR-series though.

Rock Check Scanning Software

Rock's check scanning software allows you to quickly and easily add checks to transactions in Rock. Let's walk through the process of scanning checks using this software.

First start by launching the software and logging in. Users must be a member of one of the groups below to log in using this software:

  • Finance Administrator
  • Finance User
  • Rock Administrator

If this is your first time logging in, you'll also be asked for the web address of your Rock server. This is the address that the scanning software will upload checks to.

Login Screen

To scan checks, select a batch and click the Scan button.

Home Screen

The next screen lets you select which tender type you'll be scanning into Rock. In most cases you will be scanning checks, but you could also select Cash if you wanted to scan the envelopes that the cash transaction came in. When scanning checks, you can determine if you'd like to scan both sides of the check. You can also decide if you would like to enable duplicate document detection. With this enabled, the scanner will determine if two checks are stuck together by looking at the thickness of the paper.

Scanner Settings

Extra Features:

These double-sided scanning and duplicate detection are only available on scanners using the Ranger API (see the Supported Scanners section above for more info on scanners that support the Ranger API.)

Now the check scanner will start scanning checks. If there is a problem reading one of the checks, it will stop the scanning process and warn you of the error (upside down check, check facing backwards, etc.) From here you can delete the bad scan and attempt a rescan. Because of the speed at which the scanner operates, the problem check might be back a check or two. Use the navigation buttons to find the check in question.

Scanning Checks

Once the scanner finishes with the batch of checks in its hopper, you can add more and scan again. When you’re done scanning, press the Save button.

Showing a batch with a scanned check.

After pressing Save, the check images will be uploaded to your Rock server and you will be back on the batch screen. From here, you can add additional checks to the batch or create a new batch.

Installing The Rock Check Scanning Software

Installing the check scanning software is easy. It does require a Windows machine running Windows 7 or better to run. To install, follow the steps below:

  1. First install the drivers for the scanner you'll be using. If you're using the Canon CR-series that will be the Ranger software that came with your scanner. In either case, these are simple installs.
  2. Download the setup application under Admin Tools > Power Tools > External Applications > Rock Check Scanner.
  3. Run the setup. The check scanning setup is a breeze with just three quick screens.

Software Options

You can change the options used by the scanning software anytime. To do this, select Options > Tools from the menu. You will see a screen similar to the one below.

Scan Settings
1
The scanner that is currently configured.
2 Rock URL:
The Rock server address.
3Scanner Interface:
The type of interface currently set up (Ranger or MagTek).
4 Scan Image Color Type:
The color depth that should be used when scanning. Options will vary by scanner. The Ranger interface supports black/white, grayscale and color. Just understand that using an option other than black/white will significantly grow the size of your database.

Scheduled Transactions

Some transactions occur once and then they're done. Sometimes your guests will want to set up repeating payments that run on a selected schedule (weekly, monthly, etc.). Rock calls these Scheduled Transactions.

Administrating Scheduled Transactions

You can view all of the scheduled transactions in Rock under Finance > Scheduled Transactions.

Scheduled Transactions

From there you can choose a scheduled transaction to edit.

Adding A New Scheduled Transaction:

Scheduled transactions must be entered from the individual’s Person Profile page. They can also be added by your guests on your external website.

Scheduled Transaction Detail
1
Status of the schedule (active or inactive).
2
Scheduled transaction details.
3
History of changes and edits to the scheduled transaction.
4
Edit and delete buttons.
5
Listing of transactions that have been initiated by the schedule.

Personal Profile

Scheduled transactions can also be viewed on the individual's Person Profile page under the Contributions tab.

Scheduled Transaction Frequencies

The following options are available as frequency patterns for scheduled transactions. Each payment gateway will support only a subset of these options. Each gateway will also have some special rules for how they calculate the schedules. Notes on these rules can be found at the end of this document under the chapters for each gateway.

  • Weekly: Every 7 days starting on the start date.
  • Bi-Weekly: Every 7 days starting on the start date.
  • Twice A Month: Twice a month. Usually this is used with the start date of the first of the month. Payments will then come out on the 1st and 15th of the month.
  • Monthly: Once a month on that day of the month established by the start date.
  • Quarterly: Every three months on the same date as the first payment.
  • Twice A Year:Every six months on the same date as the first payment.
  • Yearly: Once a year on the same date as the first payment.

Online Giving

In this fast paced world, people are always looking for a way to save time. Online donations are a great way to provide flexible options to your attendees, while bringing consistency to your weekly giving. Let’s tour the online transaction options included in Rock.

These Tools Can Be Used For More Than Giving:

While the tools we'll discuss in this section were created mainly for online donations, they can be used for any type of online payment or transaction.

Types of Giving Transactions

As we’ve seen earlier there are two types of giving transactions:

  • One-Time Transactions: A single specific gift given on a single date.
  • Scheduled Transactions: A reoccurring transaction that follows a set schedule (weekly, monthly, etc.)

External Website Tools

Rock provides several pages for your website guests to use to set up and manage their online transactions. These pages can all be found under the Give Section.

Giving Homepage

Giving Homepage
1
Links to the various giving management pages.
2
If the guest is logged-in, a personalized view of their scheduled transactions will be shown with the option to give now.

Give Now Page

The give now page is a flexible page that walks a person through the process of giving in a wizard-like fashion.

Online Giving Flow
1 Entry Step:
The entry page is used to get the giving details from the guest. More information on this step and its settings can be found below.
2 Confirmation Step:
The next step in the process confirms what the guest has entered before saving and processing the transaction. The confirmation header and footer of this step can be customized from the block settings.
3 Final Step:
The final step provides the guest with the ability to save their account information (credit card or check account/routing number) for future use. It will also encourage the visitor to create a login to use for subsequent visits. Like the confirmation step, the header and footer can be updated from the block settings.

The entry step is by far the most complex. Let’s look at it in more detail.

Give Now Page
1 Accounts:
The guest will first be asked to select the dollar amount they would like to contribute to each account. The accounts that are listed are configured via a block setting.
2 Additional Accounts:
You can also configure less-frequently used accounts to be added from a list.
3 Frequency:
This setting determines if the gift will be one-time or be configured to process on a schedule of their choosing. See the section Scheduled Transitions for details on the scheduling patterns for each option. You can disable the creation of scheduled transactions using the block settings.
4 When:
This determines when the gift will come out of their bank. When used with a scheduled transaction this will be the start date for the schedule.
5 Personal Information:
This is the name and contact information of the guest. If they're logged in, it will be auto-filled with their current information. If they change it here, this information will also be updated in the database.
6 Payment Information:
This contains the credit card or checking account information needed to process the transaction. The block settings define a payment gateway for both credit card and ACH (checking accounts). If you would like to disable either of these payment types, simply leave the gateway blank for the one you would like to exclude.

The giving entry block has a few other settings that you should know about. These include:

  1. Batch Name Prefix: When the transactions are downloaded from the gateway, they're assigned to a batch. You can configure the names of these batches to all start with a certain prefix.
  2. Source: For reporting, it’s good to know where a transaction came from. For instance, you might use this block on your main website or a web-based kiosk in your lobby. Knowing the source for every transaction will help you determine the success of each platform. New source options can be set up under Admin Tools > General Settings > Defined Types > Transaction Source.
  3. Address Type: You'll want the address information the guest entered to be for their home address in most cases, but you can change this if you wish.
  4. Layout Style: This setting determines if the layout should be:
    • Vertical: Sections are stacked vertically (default)
    • Fluid: Sections flow in a horizontal layout as they fit.
  5. Display Option For Selecting Additional Accounts: Determines if the Additional Account option is shown.
  6. Impersonation: This setting allows staff with proper ecurity to enter in gifts for individuals in the database. This is helpful in cases where the block is used internally.
  7. Prompted For Phone: Determines if the guest should be asked to provide their phone number on the entry screen (default is no).
  8. Prompted For Email: Determines if the guest should be asked for their email address on the entry form (default is yes).
  9. Confirm Account Email Template: When a guest decides to create an account after confirming the gift, you can send them an email confirming this action. This setting allows you to select the email template to use for this email.

Transactions that occur from the Give Now page will be immediately processed through the payment gateway and added to a batch using the Batch Name Prefix block setting.

Giving History

This page shows all other previous transactions for the logged-in user.

Giving History
1 Date Range:
This allows the user to filter the transactions shown to a specific date range. The default range is the first day of the current year as the start date and the current day as the end date.
2 Accounts:
Used to filter transactions based on the account. The list of accounts shown is configured on the block settings.
3 Summary:
Shows transaction totals based on the filters provided.
4 Transaction List:
Shows all the transactions based on the filters.

Manage Giving Profiles

This page allows the guest to managing any scheduled transactions they have created.

Manage Giving Profiles
1 Profiles:
Listing of all configured scheduled transactions with the ability to edit or delete each one. This listing is created with a liquid template that allows you to modify the markup that's used to build the list.
2 Add Profile:
Button that allows the guest to create a new scheduled transaction.

Batches For Online Transactions

Unlike processing on-site transactions, which are manually entered, the creation of online transactions in Rock is an automated process. The steps differ a bit depending on whether the transaction is a one-time transaction or a scheduled reoccurring transaction.

One-Time Transactions

When a one-time transaction is created online, it's immediately sent to the payment gateway and processed. If the gateway accepts the payment, a transaction is immediately created in Rock. The transaction is added to an Online Transaction batch. The transaction will be placed in an existing batch if one is available with the following criteria:

  • Is open
  • Has a matching prefix to the one defined on the transaction entry block
  • The current date and time falls in between the batch’s start and end date

Otherwise, a new batch will be created for the transaction with a start and end date of the current day.

Future One-Time Gifts:

If a one-time gift is configured to process on a day other than the current day, it will be processed like a scheduled transaction.

Schedule Reoccurring Transactions

Scheduled transactions work a bit differently than one-time gifts. These transactions must be downloaded at a later date from the payment gateway. See the Downloading Transactions section of the Payment Gateway chapter for details on how to download these transactions.

Accounts

Accounts determine what a transaction is for. In our examples above, both the General Fund and the Building Fund are accounts. These accounts usually tie into your accounting system. Accounts are managed under Finance > Accounts.

Account List

This page shows a list of all the accounts defined in Rock.

Account List

Account Details

From the list above you can add or update an account using the account details screen.

Account Details
1 Name:
The name that will be used when selecting an account.
2 Description:
This is a great place to document what the account will be used for and any details you'd like to keep about when and how it should be used.
3 Active:
Since accounts cannot be deleted if they are used by any transactions, you'll need to mark them Inactive once they should no longer be used.
4 Parent Account:
Rock allows you to create account hierarchies to help manage situations when you need to configure numerous accounts.
5 GL Code:
The reference code used in the General Ledger software.
6 Account Type:
This setting allows you to categorize your accounts to help with reporting. The setting has no impact on how accounts are used in Rock. The list of account types can be set under Admin Tools > General Settings > Defined Types > Account Types. You might consider using this setting to designate accounts that are used for donations vs. those you use for event registrations.
7 Public Name:
You might want to describe your account differently when it's shown on the public website. This field allows you to configure a public-friendly name for your account.
8 Campus:
If the account is specific to a campus, you can select the campus here.
9 Date Range:
The date range you provide here will help determine when the account is displayed on various screens in Rock. If the account is no longer valid, based on the date range, then it will not be displayed when picking from accounts.
10 Is Tax Deductible:
Helps determine if the transactions assigned to this account are considered tax deductible. This is used in reporting.

Pledges

Pledges predict the level of donations you can expect in a given timeframe. Some organizations use them to plan for their yearly budgets. Others use them to track what has been committed to a specific building or capital campaign. Either way, Rock can help you easily track these commitments.

Managing Pledges

Pledges are frequently given via paper commitment cards. When this occurs, someone within the organization will need to hand-enter the pledges into the system. This can be done under Finance > Pledge List. From this screen you'll see a list of all pledges currently in the system. You can use the grid filters to help limit which pledges are shown.

Pledge List
1
Available pledge filters
2
Listing of pledges that match the filters provided

From this pledge list page you can update or add new pledges. The figure below shows this screen with the various options available.

Pledge Detail
1 Person:
This is the person who is making the pledge. For families you'll want to pick the head of house. As with many of Rock's financial tools, pledges can be viewed from a family perspective when linked to any adult in the family.
2 Account:
The account that the pledge is for. Often times this will be a unique account for a capital campaign or building fund.
3 Total Amount:
This is the dollar amount that will be given over the duration of the pledge.
4 Date Range:
This defines the duration of the pledge.
5 Payment Schedule:
This determines how often gifts (financial transactions) will be given to meet the pledge amount.

Self-Entry

When possible it's a great idea for members to enter their own pledges online. This not only allows you to reduce the amount of data entry, it also allows them to create a reoccurring giving profile to match their pledge. The sample external website that comes with Rock already has a pledge entry screen configured for you to use. You can find this page under Give > Pledge.

Pledge - Self Entry

This pledge block on the external site has several block settings to make it is very flexible for you to use. These settings include:

  • Enable Smart Names: This feature will attempt to find a matching person record in Rock to link the pledge to. This match will occur if a record exists with an exact match on first name, last name and email address. There’s also some logic built in to handle cases when someone types in Ted and Cindy or Ted & Cindy in the first name field. When this happens only the value Ted will be used in the search. If an exact match does not occur a new person record will be created with the record status of pending, for future review by an Admin.
  • Account: If you provide a specific account as a block setting, the guest won’t have to pick one, and their pledge will automatically be assigned to this account.
  • New Connection Status: In the case where a new person record must be created this will be the connection status that will be assigned to the record.
  • Pledge Date Range: This setting allows you to assign a date range for the pledge. If you provide both a start and end date these values will be used, no dates will display and the guest will not have to worry about entering them.
  • Show Pledge Frequency: Determines if the Pledge Frequency field should be displayed. You may not want your guest to have to provide this information.
  • Require Pledge Frequency: There may be times when you would like to show the pledge frequency but not require someone to enter one. In other cases, you might want to require this item. With this setting you can have it any way you'd like.
  • Save Button Text: This setting allows you to customize the text of the Save button.
  • Note Message: The block allows you to provide a note to your guests to help explain the pledge in more detail.
  • Receipt Text: This is the message that will be displayed to your guest upon saving. This is a great place to celebrate their commitment. It comes out of the box configured to link them to set up a reoccurring donation to match the frequency they selected. If one was not selected, it will allow them to pick one. This field supports liquid so you can personalize it.
  • Confirmation Email Template: You can also select to send a template confirmation email after the save. This email template can use the same liquid merge objects from the Receipt Text field.
  • Enable Debug: When you enable this setting, you'll see all of the available merge fields along with their values. This is helpful when you go to create your Confirmation Email and Receipt Text. These fields will only display after saving a pledge, so you'll need to save a sample one, and then delete it.

More On Block Settings:

Be sure to read Designing and Building Websites Using Rock for more information on changing block settings.

Once a person enters their pledge on-line you can still view and manage it using the same pages as described in the Internal Entry section above.

Pledge Frequencies

In several of the screens above, we mention picking pledge frequencies for determining how often someone will be giving towards their pledge. Rock comes pre-configured with several frequency values, but you can add to or edit them under Admin Tools > General Settings > Defined Types > Recurring Transaction Frequency.

Giving On The Person Profile

If you're interested in the giving information for a specific person, you can visit their Person Profile page. There is a tab that allows you to view their giving information. This tab is configured to only be accessible by people in the following groups:

  • Finance Administrators
  • Finance Users
  • Rock Administrators

Contributions - Person Detail Page
1 Scheduled Transactions:
Lists all of the reoccurring scheduled transactions.
2 Transaction List:
Filterable list of transactions for the current user.
3 Bank Account List:
Listing of bank accounts, from the matching transaction list, for the current user.

Family Giving

By default, giving transactions are summarized by family. This means that a husband and wife share the same giving total even if they split the duties of writing the checks.

Multiple Families

Since Rock allows people to be in multiple families, you can choose which family their giving applies to. This can be set from their Person Profile page by clicking the Edit Individual button. The Combine Giving With allows you to pick a specific family.

Individual Giving

There are situiations where even married couples will want their gifts split onto separate giving statements. If you leave the Combine Giving With field discussed above blank it will mark the individual as giving separate from the family.

Businesses

While Rock is all about managing people, there are some scenarios when financial transactions need to be managed for entities like businesses. Don't worry. Rock still has you covered. Businesses can be easily managed under Finance > Businesses.

Business List

From the business list you can add, update or delete businesses.

Business Details
1 Record Status:
Like individuals, businesses have a record status that allows you to mark them as inactive. Businesses can't be deleted from the database because there are historical financial transactions tied to them.
2 Name:
The name of the business.
3 Contact Information:
Businesses allow you to store an address, phone number and an email address.
4 Campus:
Like individuals, businesses can be assigned to a campus.

Business Contacts

While businesses will be the source of donations and gifts (financial transactions), there will most likely be an individual that links the business to your organization. Being able to manage these relationships is important.

Once a business is saved, you can add contacts to the business from the individuals stored within Rock. These relationships can be viewed on the Business Detail page and also on the Known Relationships section of the Person Profile page of the individual.

Business Details
Person Detail Page

Security For Finance

The finance features in Rock have been secured to only give access to those who need it. The following security roles have been created with the permissions below.

Finance Security Roles

Finance User: The finance user role is allowed to view and edit basic finance information like batches and transactions. They are not allowed to make modifications to the configuration of the finance features. For instance, they can't add a new account.

Finance Administration: The finance administrator role is allowed to view and edit all finance information including configuration information like accounts.

Areas That Are Secured

The following areas of Rock have been secured to limit access to financial information. Only those in the finance roles will have access to the following:

  • Finance Admin Pages: All the pages under Finance on the main navigation.
  • Person Details Contribution Tab: The Contributions tab on the Person Profile page.
  • Rock Check Scanner: Log-in to use this application.
  • Data View Filters: Write data views that report on financial information. (Once the data views are created however, anyone who has permission to view the data view can run them. Be sure to secure the data views you create.)
  • Reports: Creating reports. (Once the reports are created though, they can be run by anyone with view access to the report.)

Defined Types For Financial Features

There are several defined types used by the various financial features of Rock. Below we'll talk about each of them and tell you why they're important.

Account Type

This groups or categorizes Accounts by their usage. It’s provided for you specifically to help with reporting and is not used by Rock for any specific purpose.

Credit Card Type

This defined type determines which credit card types your organization will accept. Each card type also has several configuration options. These include:

  • Regular Expression Pattern: This pattern helps Rock determine if a given card number matches this type of credit card. The default values should not be altered.
  • Batch Name Suffix: Many times accounting teams want online transactions to be placed in batches specific to the credit card types when they are downloaded from the payment gateways. The suffix is what helps group the cards into batches. If all the cards have the same suffix, they will all share a batch (default setting). If you'd like all the Visa transactions to be in their own batch, then you'd change the suffix to something like Visa.

Recurring Transaction Frequency

This defined type determines which frequency types you want to offer your guests. These options must be supported by your payment gateway to work, so don't add new ones and wonder why they don't show up.

Refund Reasons

This defined value is not currently used. It will be used in the future for event registration purposes.

Tender Type

Determines the method (Cash, Check, Credit Card, etc.) a person used to make a financial transaction. Tender Type is used to help describe the payment source for a transaction and is also used in determining how batches are created.

Transaction Source

This value helps determine where the transaction took place. This is helpful in reporting. Many of the transaction entry blocks allow you to pick this value, so by all means add additional items that make sense to your organization. For instance, if you run multiple websites with their own giving pages, you may want to make a new source type for each site. This will help you determine which is most effective in generating donations.

Transaction Type

This defined type describes what a transaction is for (contribution, event registration, etc.)

Payment Gateways

When we start getting into the concepts of how financial transactions work in our modern economy things can get confusing pretty quickly. Don't worry though, we not only want you to understand how to use Rock, we also want to help you to understand the concepts of what's going on behind the scenes. Let’s help to demystify the concept of payment gateways.

We're all familiar with the concept of checking out at the store. The clerk rings up our purchases at the register and once a total amount has been determined, we swipe our card through the credit card terminal and we're done. Using this analogy Rock would play the role of the register and the payment gateway is the digital equivalent of the credit card terminal. Like the register, Rock helps determine what is being purchased/donated and comes up with a total amount. Rock then takes the guest’s account information (either their credit card or checking account information) and sends it through the terminal (aka payment gateway).

Gateway Analogy
Gateway

At that point the transaction has started its journey through the financial system. In many ways you're done with it, but let's track its journey and note some places that you'll need to initially configure.

Gateway Overview
1
Guest completes their transaction on your Rock website. Rock then sends their account information to the payment gateway that you have configured.
2
The payment gateway transmits the transaction to the guest's credit card company.
3
Once the transaction is approved the funds are transferred to your Internet merchant account. You'll need to work with your bank to establish this account. This is as easy as calling your bank and asking them for help creating an Internet Merchant Account that is compatible with the payment gateway you've selected with Rock.
4
The Internet merchant account then transfers the funds to your bank account via regularly scheduled transfers.

Available Payment Gateways

Currently Rock supports only a single payment gateway, PayPal's Payflow Pro. We expect several other gateways to be made available soon through community developers and possibly as a part of core. The PayFlow Pro gateway is a solid and reliable option that has been in use by numerous organizations for many years.

Configuring a Gateway

Payment gateways can be configured under Admin Tools > System Settings > Financial Gateways. There you will notice that there are actually two options: Payflow Pro and a Test Gateway. We created the Test Gateway as a way to allow Rock to come pre-configured in a way that allows an organization can sample Rock's tools without having to configure an actual payment gateway. Below is a screenshot of the various settings for the Payflow Pro gateway.

Payment Gateway Settings
1 Login Information:
The various login criteria needed to work with the gateway.
2 Mode:
Whether the gateway is in Live or Test mode.
3 Batch Process Time:
This time determines the cut-off for creating batches when downloading transactions from the gateway.

Other Configuration Steps

Once you're done setting up your gateway, you'll need to set it as the active gateway on the giving pages.

Downloading Transactions

There are two ways to configure this download. The first way is to setup a Get Scheduled Payments job to run every night. This can be done under Admin Tools > System Settings > Jobs Administration. This job will run each night (or when you decide you want it to run) and create batches and transactions for new payments.

Don't Forget To Setup The Download Job

It's important to remember to setup the Get Scheduled Payments job if you wish for the transactions to download automatically (highly recommended).

You can also choose to manually download the new payments from the payment processor. You can do this under Finance > Download Payments. This does the same thing as the Rock job but requires you to manually run the download.

Downloading transactions from the gateway is actually a bit trickier than you might think because of certain edge-cases and advanced features. We'll cover some of these next.

Recent Scheduled Transaction Changes

Consider this example. Ted has a scheduled transaction set that takes $120 out of his account every week and puts it to the General Fund account. Early in the morning the payment gateway creates a new transaction for this amount. Ted arrives to work and changes his giving to $100 per week. Finally later in the day, the church's Download Schedule Transaction job runs and pulls that day's transactions down from the gateway. The gateway's transaction says it's for $120 but Rock's information only has $100 allocated. When this happens (certainly a rare edge-case) Rock will apply any extra amount to a default account. This default account is the first active account that does not have a parent account and where current date falls between the account's start/end dates.

Naming Batches for Online Giving

The way that Rock calculates the Batch Name is by combining a batch prefix and a batch suffix. The prefix is usually set by a block or job setting (the default value used by the Transaction Entry block, Scheduled Payment Download block, Get Scheduled Payments job etc. is Online Giving). The suffix depends on the currency type (Tender Type Defined Type). If it is not a credit card transaction then the currency type value is used (e.g. ACH). If it is a credit card transaction, then the Credit Card type value is used (e.g. Visa, MasterCard, etc). However, the Credit Card defined value also has a Batch Name Suffix that can be used to override this value. For example, if you want to combine Visa, MasterCard and Discover transactions into the same batch, you can set all three of these defined values Batch Name Suffix to the same value (e.g. VMD) and then transactions of these types will be combined into the same batch.

Payflow Pro Gateway

Below are details about the Payflow Pro gateway with information on getting started and details that are unique to it.

Setup

You can set up a new account at the address:

https://www.paypal.com/webapps/mpp/payflow-payment-gateway

A couple of things to keep in mind:

  • Although the Payflow Pro service is run by PayPal, this is not a traditional PayPal account. Payflow Pro is a service that PayPal purchased from Verisign many years ago.
  • Be sure to sign-up for the Payflow Pro not the Payflow Link account.

At the time of writing this manual, the costs for a Payflow Pro account were:

  • Setup: $99
  • Monthly: $25
  • Gateway Fee: $.10 per transaction
  • Recurring Billing: $10 per month

Unique Scheduling Notes

While most of the schedules like weekly, monthly, etc. are pretty obvious, there are a couple of notes you should consider about Payflow Pro's scheduling.

Twice a Month

This basically states that you want two transactions a month. Many people will select this with a start date of the first of the month. When they do, the transactions will come out of the account on the 1st and 15th.

When the guest selects a starting date between the 1st and 15th, it's pretty simple to determine their payment schedule. It will always be the day of the month of their start date for the first payment and 15 days later for the second.

When the guest selects a starting date later than the 15th of the month, then the pattern changes a bit. One payment will come out on the numerical day of the starting date (e.g. the 25th of the month). The second payment date will be fifteen days after this date.

Once A Month

On a rare occasion, someone might say that they want their payment to be on the last day of the month. Since the number of days in the month varies this may seem impossible. With Payflow Pro however if you choose the start date as the 31st of the month, the payment will always occur on the last day of the month.

Generating Statements

When it's time to generate contribution statements, we've created some tools to make the process simpler. Since you may need to be able to both email and mail printed statements, the best file format will be a PDF, and we have just the tool for the job. Let's walk through the process of generating PDF statements with our statement generator software.

Installing the Statement Generator Software

Installing the statement generator software is easy. It does require a Windows machine running Windows 7 or better to run. To install, follow the steps below:

  1. Download the setup application under Admin Tools > Power Tools > External Applications > Rock Statement Generator.
  2. Run the setup. The statement generator setup is a breeze with just three quick screens.

Using the Statement Generator Software

Once you have it set up, it's pretty simple to operate the statement generator software.

Start by launching it and logging in. Users must be a member of one of the groups below to log in with this software:

  • Finance Administrator
  • Finance User
  • Rock Administrator

Please note that if this is your first time logging in, you'll also be asked for the web address of your Rock server.

Login Screen

To generate statements, click the Start button.

Home Screen

The next screen lets you select whether you want to generate statements for All individuals with transactions or for a specific individual. If you select Single individual, you'll be prompted with a search box where you can type in a person's name. If more than one person is listed in the grid, click on the person you want to generate the statement for. Press Next to go to the next step.

Who Needs a Statement

The Account Selection screen lets you select one or more accounts you want to include.

Account Selection

The Statement Date Range lets you specify the date range. By default, it will show the January 1 of the current year as the Start Date and today's date as the End Date.

Date Range

Select the layout you want to use for the statement output. Rock will ship with one default layout, but other custom layouts can be added by using the Dynamic PDF Designer, which can be downloaded from http://storage.rockrms.com/resources/DynamicPDFDesigner7.0.3.zip.

Quick Custom Layouts:

Open rock-standard.dplx, which can be found where you installed the statement generator (usually C:\Program Files (x86)\Spark Development Network\RockRMS Statement Generator). Just modify this layout and save it as a new custom layout. Make sure to set the MainReport Title to the new name of your layout, then save it as a new file (for example, my-custom-layout.dplx) into the same directory. Then, you can use the Import button in the statement generator to add your layout to the list.

Statement Layout

The statement generator will start to process the statements after you press Next on the Select Layout step. Once the Save As button appears, make sure you select a PDF output.

Progress Complete

Software Options

You can easily change the options used by the statement generator anytime. To do this, select Options > Tools from the menu on the home screen. This is where you can change the Rock URL if needed, but it is especially handy if you want a different logo. The logo you choose will be what is shown on the statements.

Options
Improve