Your Knowledge Base has moved to the new Help Center.  Check out the release notes for details. And don't forget to update your bookmarks and in-house documentation before May 28.

Shelby Project Codes

 
A church that uses the One-Click export from MinistryPlatform to Shelby v5 Financials has the added benefit that they can transmit a project code along with any debit or credit in the journal entries created in Shelby during this process.

Follow these steps to ensure your project codes are applied properly:
  1. Create a Project Code in Shelby v5 General Ledger and note the number assigned to this Project.
  2. Create a new Event in MinistryPlatform using the same name as the Project code created in Shelby v5. The number from step 1 should be entered into the Project Code field of the new Event.
  3. The Event is typically then set as On Donation Batch Tool = yes.
  4. The Event can be manually selected during donation entry in the Batch Manager Tool.
  5. The Event can be optionally added to the Program as a Default Target Event. If this is done, the system attempts to assign this Event to any Donation Distribution made to that Program when a Deposit is created.
  6. The One Click export to Shelby v5 Financials transfers the project code along with all other information in the Deposit(s) to the GL Journal Entry created in Shelby v5.

Note:  If an Event is associated with a Donation Distribution that does not have a project code value (from step 2 above), the system uses a Default Accounting Project value found in the Configuration Settings page when creating the Journal Entry in Shelby v5 General Ledger. A SPoC can edit this setting by going to Administration > Configuration Settings > DefaultAccountingProject. The system assigns the MinistryPlatform Project to registration entries sent to Shelby if a project code is not set on the related Event record. This is required to make the one-click integration work. After the data is in Shelby v5 General Ledger, you are welcome to remove the project code, if desired. See this related KB for more details.

See Also: Events and Project Codes