Statement Generation
Admin Guide

Statement Generation

Steward
Access:Super AdminFinance Admin

Two different documents come out of Statements. Official receipts (CRA tax receipts, each with its own serial number) are produced only when finance staff create a statement run from Steward → Statements. Monthly giving statements are produced on a schedule, only for a church that has turned them on, and are never receipts.

Schedule

FieldTypeDescription
On-Demand GenerationWhen a run is createdProcesses statement runs created by finance staff from Steward → Statements.
ZIP PackagingOn demandPackages generated statement PDFs into downloadable ZIP archives. Runs with concurrency of 3 for parallel processing.
zip-cleanupEvery 30 minutesRemoves expired ZIP files from storage. Runs for every church at once, so it has no Run Now button.
monthly-statementsMonthly on the 1st at 6:00 AMYour church’s time. Acts only when Auto-generate monthly statements is on; otherwise recorded as Skipped. No Run Now button. See below.

Monthly Giving Statements

At 6:00 AM on the 1st of each month, in your church's timezone, the monthly-statements job looks at your church's Statement Settings:

  • Auto-generate monthly statements off (the default): nothing is made. The job log shows the run as Skipped, “Monthly statements are off for this church”.
  • On, Auto-email off: a giving statement is prepared for every donor who gave last month. Nothing is emailed. The statements are listed under Monthly giving statements on Steward → Statements, where you can download each donor's PDF.
  • On, Auto-email on: the same, and each donor with an email address on file is emailed their statement as a PDF, once.

The month is your church's previous calendar month. A giving statement lists the donor's gifts in that month from posted sessions and online giving, less any refunds, with the total. A donor whose statement preference is None doesn't get one, and neither does a donor whose gifts for the month were all refunded.

Each month is prepared once per church. If the job runs again for the same month, it does nothing and the log says the month is already prepared. The emails are sent from a queue that survives a server restart, and a donor who has already been sent that month's statement isn't sent it again.

On-Demand Processing

When a finance user creates a statement run from the Steward module, the request is added to the statements BullMQ queue. The Statement Generation Processor picks up the job and calls processRun, which generates individual statement records and PDFs for each eligible donor.

ZIP Generation

After statements are generated, a Super Admin or Finance Admin can request a bulk download as a ZIP file (Download All in the run's drawer). This is handled by a separate zip-generation BullMQ queue with a concurrency of 3, allowing multiple ZIP jobs to process in parallel. The finished ZIP is kept in the file storage and downloaded through a link that is renewed while the ZIP is kept.

If a ZIP job fails, the job status is updated to FAILED with the error message recorded for troubleshooting.

Related Pages