Support

April 10, 2023 at 10:50 am

Hi there,

I’m not sure I understand your description, can you provide more detail or examples?

April 11, 2023 at 4:19 pm

Hi there,

So you have 6 registrations split across 3 events, 2 registrations in each event.

The EE Transaction for those 6 registrations is a single transaction linking all of the registrations together, the amount dude for that single transaction applies to all.

Within Event Espresso, we consider the ‘primary registrant’ to be the person handling all of the payments for the group which means the transaction record is linked to the primary registrant. We don’t split out the transaction amount across the events in the CSV like you are requesting currently and it gets tricky based on the use case to handle that for all setups.

We chose to apply the total transaction amount and total amount paid only on the primary registrant within the CSV as its the most reliable method to keep track of the total payments.

I’m curious about this:

I need to show the amount in each event download.

How are you expecting the amounts to show in the CSV?

So in your example, you have 6 regs, each at $1 across 3 events

So when you export a single event, what do you expect the Transaction Amount Due to be for each of the 2 rows for that specific event?

Same with Amount Paid?

April 11, 2023 at 4:53 pm

I would expect the transaction and paid amounts for each line to be $1 which is the cost of that registrant for that event.

But that’s not valid because each event does not have a transaction, the total transaction amount for that group registration is $6 as there is a single transaction.

We ‘could’ change the CSV to output the transaction amount owed on each individual row, which would mean each of those rows show a Transaction Amount Due value of $6… problem is that could be then be interpreted as $12 per event, or $36 in total ($6 across 6 regs). This is part of what I was referring to about this getting tricky to suit all use cases.

The reason is that we tally up the income by event, which is not possible the way it works.

The registration CSV is filtered, which means ALL of the values used within it can be changed, you can add, remove, edit fields within CSV on the fly using a code snippet. So changing the CSV to output the details you need is likely possible but will require some PHP.

It also is not as easy to skim the CSV and see who has not paid yet. (All of our payments need to be manual so they come in after the registration).

There’s a registration an transaction status which are intended to show you who has been approved and show’s transaction is complete. Do ou often split up transaction amounts on a per-registration basis from within a group?

Because we also have late fee in some cases, that makes it even harder to figure out the income by event.

Again this shows how it’s really tricky to cover all use cases for payments within the CSV itself without complicating it for use cases. The info to include (and how to include it) for a distributed report is tricky.

Since the amount allocated shows on the registration record, I figured it would be available in the CSV download.

Payment related to each individual registration can be pulled into the CSV and displayed if that’s what you are looking to do?