Contribution statements are often time consuming and difficult to run due to the sheer number of statements that must be gathered. For this reason, Fellowship One includes a statement request and queuing tool. When a statement request is submitted, it is immediately added to a queue where Fellowship One runs and generates the statement files while you continue working.
Contribution information for the statement generator is housed in a different location than your Fellowship One contributions information. The reason it is separated are for those times when you are running hundreds, if not thousands of statements. If you were to do this within Fellowship One, it would take all of the bandwidth resources from your database and prevent other users from working. To mitigate this problem, ACTIVE Network Faith created the Data Warehouse.
Rest assured that it is an exact copy of your contributions data. In fact, data from Fellowship One is replicated into the Data Warehouse nightly.
Note: Because replication only happens during the night, any changes you make to data in Fellowship One will not appear in statements created from the statement generator until the following day. If you need a statement immediately, use the Report Library to generate single statements.
You can use reports from the Report Library if you would like. All of the styles available in the statement generator are also available from the reports in the Report Library. The main caveat is that you cannot run hundreds of statements at a time. However, these reports are perfect for when you need to run single contribution statements, especially in the event that you need to run a statement the same day you have made a change to an individual’s contribution data.
The contribution statement reports are located by clicking Reports. When the Report Library opens, click FT Reports and then click the Statement tag. Any statement report aside from those marked (Data Mart) will result in a current contribution statement.
As statements begin to process, PDF files are created in the statement queue. Each file contains 1000 statements. These statements can be either multi-page or single-page statements so the file may actually be more than 1000 pages. Depending upon how the statement request was configured, the file names will either be by last name/organization name or by zip code.
Example: A church runs a statement request limiting the statement output to all statements within the 70000 zip code block for the year 2009. 3000 statements match the criteria. Since each file only holds 1000 statements, three files are generated. The files will be named Postal Codes (1st statement zip code - 1000th statement zip code), Postal Codes (1001st statement zip code - 2000th statement zip code), and Postal Codes (2001st statement zip code - 3000th statement zip code).
Example 2: A church runs a statement request with no limits on the statement output and the output is sorted by last name. 5500 statements are generated. Since each file only contains 1000 statements, 6 files are generated. The files are sorted by last name (or organization name) as requested and will be named Last Name (1st statement last name/organization - 1000th statement last name/organization). The remaining 5 files are named in succession according to the 1st statement's last name and the 1000th statement's last name.
Two additional files may be created with the statement files. The Report Summary generates any time statement requests are created for any set of statements other than individual statement requests. Individual requests only contain one statement, which does not require a summary page.
The Postal Code Report is generated if this options is selected on the statement request. This report is comparable to the existing G1000z - Contribution Counts by Zip Code report found in the Report Library.