Please feel free to submit feedback here if you need any assistance.
How will this export work?
A new Event reconciliation report will be present below the current Event Reconciliation Report grid that will display a new table and option for the setup wizard. The wizard will allow for additional configurations including: filtering by date or community, scheduling, notification emails and SFTP file retrieval if this option is enabled on your site.
How will adjustments tie back to their parent transactions?
Adjustments will contain their parent's transaction ID in the transaction ID column.
Will this allow custom fields to be added?
We will be allowing Profile and Re-usable Instance fields to be added to the report configuration but similar to the Giving Transaction Export we will be including this at the grid level. This means that all reports of this type will contain the same columns based on the configuration when the report is run.
Will Adjustments and Offline Transactions be a configurable option for this report?
No, these transactions types will be always included in the report but they can be easily filtered out of the CSV after the report has been generated.
Can transactions be filtered to include or exclude certain sub-communities?
Yes, if the report is being created at GID 1 then an option to filter data by sub-communities will be available. However, if the report is being created at the sub-community level (not GID 1) then the report will only include transactions from that sub-community.
Are purged event submissions included in the Event Reconciliation with Adjustments?
Yes, even though an event submission has been purged from the form all resulting transactions will still be available on the event reconciliation with adjustments report. These transactions are not currently denoted in any special way.
What columns will be included in the report?
- Commerce Identifiers (unique per client)
- Community Name
- Community ID
- Form ID
- Form Name
- Constituent ID
- Member ID
- First Name
- Last Name
- Registered By (Populated for guests with main registrants LastName, FirstName)
- Re-useable and additional Profile Fields (Defined by admin - unique per GID)
- Order Total (Negative for adjustments)
- Transaction ID (For adjustments this would be the parent transaction ID)
- Purchase Date
- Authorization Code
- Customer Trans Number
- Retrieval Code
- Appeal Code
- Billing Name
- Credit Card Type
- Billing Email
- Billing Phone
- Billing Street 1
- Billing Street 2
- Billing City
- Billing State
- Billing Zip
- Billing Country
- Adjustment ID
- Campaign Name
- Donation Amount