Contents |
Associations and Clubs using online registration and payments will most likely need to report on registration, transaction and payment information. The financial reports in the Sportzware Online Membership system allow these organisations to find detailed financial information with ease. This page explains how to access and run the reports and what types of information each report generates.
Below is an explanation of the three reports and what each field within the report describes.
These are an “all purpose” suite of reports – most likely to be used to track down a particular transaction or for SportingPulse reporting requirements across different levels of a Realm. Clients can use these but they’re less useful than the other two from a client point of view and have a particular objective.
Below are the fields available in the report and what they describe:
Transaction ID: SportingPulse unique transaction identifier
Product: Product name
Payment For: Name of member the payment is for
Amount Due: Amount due to be paid
Quantity: Quantity purchased
Manual Receipt Reference: Manual receipt reference if recorded manually by organisation
Payment Type: Method of payment
Bank Reference Number: PayPal transaction ID and correlation ID
Payment Log ID: SportingPulse Payment log identifier (a payment log may be composed of many transactions)
Payment amount (may cover many txns): Total amount of the payment of which this transaction was a part
Transaction Date: Transaction date and time
Payment Date: Payment date and time
Transaction Status: Unpaid/Paid
Transaction Notes: Any notes if they were recorded
Export Bank File ID: The identifying number of the MassPay run that distributed the funds to the associations/clubs
Club Payment for: The club the payment was made for
Specifically used by an organisation to track the funds they have received to their PayPal account. This can be filtered by date, and shows the various transactions from which they received funds (including those transactions that were generated by a different organisation, but received by the organisation running the report. For example, if a club was selling a product and a $10 portion of each sale went to the association, then the association will see that $10 in this report as it is funds they have received, regardless of who sold the product).
Below are the fields available in the report and what they describe:
Transaction ID:SportingPulse unique transaction identifier
Product: Product name
Payment For: Name of member the payment is for
Payment From: The club or association that generated the payment
Transaction Amount: The total amount of the original transaction
Money Received (after fees): Funds actually received to the PayPal account
Bank Reference Number: PayPal transaction ID and correlation ID
Payment Log ID: SportingPulse Payment log identifier (a payment log may be composed of many transactions)
Payment Date: Payment date and time
Export Split Bank File ID: The identifying number of the MassPay run that distributed the funds to the associations/clubs
Date Funds Received: Date and time the funds were deposited to the organisation's PayPal account
Different to the Funds Received reports, this report shows the sales that were actually made by the organisation running the report. This shows sales, not income. For income and reconciling their PayPal account, they should use the Funds Received reports.
Below are the fields available in the report and what they describe:
Payment Log ID: SportingPulse Payment log identifier (a payment log may be composed of many transactions)
Payment Type: Method of payment
Bank Reference Number: PayPal transaction ID and correlation ID
Total Amount Paid: Total amount that was paid when the transaction was completed
Settlement Date: Date the transaction was completed
Payment For: Member for whom the payment was made
Split Level: Identifies the organisation who was sent the Split Amount as part of the payment split ("Fees" refers to SportingPulse)
Split Amount: The portion of the total that was split to each organisation
