This report includes three integrated views to support different financial analysis needs.

Find the transaction report in the Platform Reports:

Transaction Overview Report

This overview report includes:

• Detailed view of all completed transactions with customisable filters
• Complete transaction history with payment details
• Real-time status tracking and updates

View the transaction details via the links on the right, or export the transaction information you need.

Note: This report includes the name of the purchaser, NOT the learner/participant (unless the purchaser has purchased on behalf of themselves). Use the Transaction Line Item report to get the name of the learner/participant, as well as the purchaser.

Exportable fields include:

Transaction information:

• Transaction UUID - this is a unique Academy identifier for the transaction
• Academy invoice number - available when using Academy's invoices
• Total seats purchased in the transaction
• Client invoice number - available when you are attaching invoices from an external / third party invoicing system
• Purchase order number - if entered by the customer or by a sales representative
• Invoice type code - indicates which invoice type is being used for the transaction. The different types include stripe_generated, academy_generated, and client_generated. 
• Invoice status code - indicates the status of the transaction. The different status codes include draft, pending, approved, paid, voided, and deleted. 
• Collection method - Collection methods are:
  • charge_automatically - the customer has paid immediately by credit card, or other instant payment option eg. GooglePay, ApplePay.
  • send_invoice - the customer has requested to pay later via invoice.

Dates:

• Purchase date - the date of purchase, or the date the invoice was requested
• Invoice sent date - the date the invoice was sent. If using Academy's invoice, this will be the same as the date of purchase. If using external / third party invoices, this is the date the external invoice has been attached to the Academy invoice record and sent.
• Invoice due date - calculated as per your platform settings
• Paid date - the date the invoice was paid.

Financial Details:

• Subtotal - this is the total amount for the transaction BEFORE tax has been applied
• Discount - If a discount code was applied at the time of the program purchase, this is the dollar amount of the discount (ie. the amount that has been discounted from the "normal" price). If multiple seats were purchased, the discount amount on the parent transaction will reflect the total discount for all seats.
• Discount percentage - If a discount code was applied at the time of the program purchase, this is the percentage amount of the discount (ie. the amount that has been discounted from the "normal" price). If multiple seats were purchased, the percentage amount on the parent transaction will reflect the total percentage for all seats.
• After discount - this is the total amount for the transaction BEFORE tax has been applied, but AFTER a discount has been applied
• Tax % - If a tax (eg. GST) percent adjustment was applied at the time of the program purchase, this is the percentage amount used for adjusting the price (i.e., the percentage that has been applied to the "normal" price).
• Tax - If a tax (eg. GST) amount adjustment was applied at the time of the program purchase, this is the dollar amount of the adjustment (i.e., the amount that has been adjusted from the "normal" price). If multiple seats were purchased, the tax amount on the parent transaction will reflect the total adjustment for all seats.
• Total amount paid - This is the amount that has been paid for the transaction. If the user has not paid yet, this will be 0. If the user has paid, this amount will match the invoiced_amount.
• Stripe fee amount - This field stores the amount representing the fee charged by Stripe for the transaction.
• Stripe fee currency - This field stores the currency of the fee charged by Stripe for the transaction.
• Stripe fee tax amount - This field stores the tax amount charged for the fee that Stripe assessed during the transaction.
• Stripe fee tax currency - This field stores the currency of the tax charged for the fee that Stripe assessed during the transaction.

Payment Details:

• Payment method - The payment method the user has used to purchase their program eg. credit card. “External” means the user has paid using a method Academy does not know about eg. a direct bank transfer. In this case, the transaction would have been manually marked as paid, or automatically marked as paid via the Update Transaction API.
• Invoice paid status - can be 1 (paid) or 0 (not paid)

Coupon Information:

• Coupon used - can be 1 (a discount code was used with this transaction) or 0 (a discount coupon was not used)
• Coupon code - if a discount coupon was used for the transaction, this is the code that was used

Other Fields:

• Purchaser & participant information - name and contact details of the person who purchased the program/s and the person/s who will be participating in the program. If the participant purchased for themselves, these will be the same. If the purchaser purchased on behalf of someone else, these will be different.
• Sponsor Information - name and contact details of the participant's program sponsor. These fields will only be populated if the sponsor information is enabled. The sponsor is not the same as the purchaser.
• Billing details - the billing information for the purchaser.

Transaction Items Report

The transaction items report includes a line-item breakdown of all enrolments attached to a transaction.

If multiple seats were purchased in one transaction, then this report will show the learners in separate line items.

Exportable fields include:

Transaction Item Information:

• Transaction UUID - this is a unique Academy identifier for the transaction
• Item amount - this is the cost associated with each transaction item eg. one seat
• Payment status - can be 1 (paid) or 0 (not paid)
• Access granted - indicates whether an individual has been granted access to a program before payment has been received.

Dates:

• Paid date - the date the invoice attached to this transaction was paid.

Financial Details:

• Subtotal - this is the total amount for the transaction BEFORE tax has been applied
• Discount - If a discount code was applied at the time of the program purchase, this is the dollar amount of the discount (ie. the amount that has been discounted from the "normal" price). If multiple seats were purchased, the discount amount on the parent transaction will reflect the total discount for all seats.
• Discount percentage - If a discount code was applied at the time of the program purchase, this is the percentage amount of the discount (ie. the amount that has been discounted from the "normal" price). If multiple seats were purchased, the percentage amount on the parent transaction will reflect the total percentage for all seats.
• After discount - this is the total amount for the transaction BEFORE tax has been applied, but AFTER a discount has been applied
• Tax % - If a tax (eg. GST) percent adjustment was applied at the time of the program purchase, this is the percentage amount used for adjusting the price (i.e., the percentage that has been applied to the "normal" price).
• Tax - If a tax (eg. GST) amount adjustment was applied at the time of the program purchase, this is the dollar amount of the adjustment (i.e., the amount that has been adjusted from the "normal" price). If multiple seats were purchased, the tax amount on the parent transaction will reflect the total adjustment for all seats.
• Total amount paid - This is the amount that has been paid for the transaction. If the user has not paid yet, this will be 0. If the user has paid, this amount will match the invoiced_amount.
• Stripe fee amount - This field stores the amount representing the fee charged by Stripe for the transaction.
• Stripe fee currency - This field stores the currency of the fee charged by Stripe for the transaction.
• Stripe fee tax amount - This field stores the tax amount charged for the fee that Stripe assessed during the transaction.
• Stripe fee tax currency - This field stores the currency of the tax charged for the fee that Stripe assessed during the transaction.

User Profile Attributes (Learner):

These are the user details of the person participating in the program including name, email address, and any other fields enabled in the user profile on your Academy platform.

Transaction information:

• Transaction UUID - this is a unique Academy identifier for the transaction
• Academy invoice number - available when using Academy's invoices
• Purchase order number - if entered by the customer or by a sales representative
• Invoice type code - indicates which invoice type is being used for the transaction. The different types include stripe_generated, academy_generated, and client_generated. 
• Invoice status code - indicates the status of the transaction. The different status codes include draft, pending, approved, paid, voided, and deleted. 
• Collection method - Collection methods are:
  • charge_automatically - the customer has paid immediately by credit card, or other instant payment option eg. GooglePay, ApplePay.
  • send_invoice - the customer has requested to pay later via invoice.

Program Details:

These are the details of the program/s that was purchased in the transaction and that the learner is participating in.

Sponsor Information

Name and contact details of the participant's program sponsor. These fields will only be populated if the sponsor information is enabled. The sponsor is not the same as the purchaser.

Abandoned Transactions Report

This report monitors incomplete enrolments. That is, potential purchasers who have partially completed an enrolment/purchase, but have not progressed to the purchase confirmation screen.

There is a two-hour tracking window for abandonment. That is, a purchase is considered “abandoned” if the purchaser hasn't progressed to the purchase confirmation screen within two hours of starting their purchase.

In addition to the fields explained above the Abandoned Transaction Report includes the point at which the potential purchaser abandoned the transaction. This can be:

1. the Profile screen - that is, the potential purchaser created their account, but did not submit their user profile
2. the “Enrolment for other users” screen - the screen where the potential purchaser enter the participant names. NOTE: this applies only to “multi-seat purchases” and “purchase on behalf of someone else” workflows.
3. Payment - the screen where the potential purchaser enters their payment details.