Your Knowledge Base is moving on 3/25/24! Our new Help Center provides all the articles you know and love (plus so much more) in a one-stop shop. Ask your SPoC for details!

Donations

 

Basics

  • A Donation record in MinistryPlatform stores information about a financial gift. 
  • For online donations, credit and debit card numbers are not stored by the MinistryPlatform system even if they were accidentally returned to the MinistryPlatform system by the payment processor. The MinistryPlatform system only stores transaction ID/confirmation information.

How Terms & Concepts Relate to Each Other

Donation Distributions make Donations. Donations make Batches. Batches make Deposits.

Donation Record Fields

Asterisk (*) indicates required fields

  • Donor*: The Donor assigned credit for the Donation.
  • Donation Amount*: Total of the Donation (should match the sum of Distributions).
  • Donation Date*: Date of Donation (if from Batch Manager Tool, the original Setup Date).
  • Payment Type*: Type of payment (check, cash, credit card, stock, etc.).
  • Item Number: If from the Batch Manager Tool, the check number is read during scanning.
  • Batch: Batch that this Donation is a part of.
  • Notes: If entered from the Batch Manager Tool, the Memo. If from Online Giving, name and address information are captured during checkout. Or notes manually added by the User.
  • 3rd Party Memo: Notes from 3rd Party integrations such as PushPay, OGO, etc. This field could be leveraged by a church that doesn't use the MP portal for Online Giving to import "notes" information currently collected by a third party. Note: This field is populated by a 3rd Party integration.
  • Donor Account: The Donor Account record that matches the account and routing numbers with the Donor.
  • Anonymous: If True, Donor asked to remain anonymous. Set manually by User unless Donor requested as part of Mission Trip giving.

  • Transaction Code: ID of the transaction through the 3rd party integration.
  • Subscription Code: Populated if the donation is recurring. Pro tip: You can identify all recurring donations by creating a view on the Donations page and filtering by the Subscription Code field.
  • Gateway Response: Status of the donation from the gateway provider. A gateway provider allows your Church to accept credit card payments by connecting payment processors (the service charging the card) and merchant account providers (the service providing your payment systems).
  • Processed: Indicates whether the donation has been processed.
  • Currency: Currency of the Donation.
  • Receipted*: Indicates whether a receipt has been provided.
  • Invoice Number: Populated by the online giving provider.
  • Receipt Number: Number of the receipt, if the donation was an online donation.
  • Original MICR: If from the Batch Manager Tool, the MICR details are captured during scanning. Needed for matching the Donor to their Donor Account. Also needed for debugging if not parsed to populate the account, routing, and item number fields.
  • OCR Data: If from the Batch Manager Tool, the OCR details are captured during scanning. Needed for creating new Donor record if no Donor Account is matched.
  • Position: If from the Batch Manager Tool, the order the check was scanned in the Batch.
  • Third-Party Note: Notes added by the 3rd party giving provider.
  • Statement: Standard Statement associated with this donation.