•Payments are associated with a Contact.
•Payments are associated with a Source Code, which identifies the source of the money. They can optionally be associated with a Source 2.
•A source code is specified at Main Event level and each Sub Event will inherit that same source code.
•Each Sub Event, will have a different Source 2 specified that relates revenue to the Site or Venue.
Money generated by an Event can be in 2 forms:
Registration Fees
•Payments for Registration Fees will reference the Event/Sub-Event via a GST Applicable source code, e.g. RFL2015_REG
Donations/Proceeds e.g. Sponsorship revenue for a registered Participant, Donations given to a host at an event, etc.
•Donations/Proceeds relating to an Event will reference the Event/Sub-Event via a non-GST Applicable source code, e.g. RFL2015_DON
For Events that utilise Teams, there are 3 methods in which money can be deposited:
•From Captain via Deposit Slip (to Team which is an organisation record)
•From Supporter (to Team or Team Member)
•From Team Member (to Team or Self)
As revenue can only be associated with a Contact, each Team will be associated with a “Team” Contact.
Payments will be shown on the person making the payment (Hard) and this will be indicated on another team contact’s record (Soft) as per the table below:
Revenue |
Hard Payment |
Soft Credit |
From Team Captain via Deposit Slip |
On Team Captain |
On Team Contact |
From Supporter |
||
To Team |
On Supporter |
On Team Contact |
To Team Member |
On Supporter |
On Team Member |
From Team Member |
||
To Team |
On Team Member |
On Team Contact |
To Self |
On Team Member |
None |
From Committee Member via Deposit Slip |
On Committee Member |
On Team Contact |