Skip to content
Oxford Abstracts

Buyers, ticket holders and who receives what

For event organisersLast reviewed 1 August 2026

When one person books tickets for colleagues, the buyer and the ticket holder are different people — and that explains most registration puzzles.

Submitting, reviewing or attending? This guide is for event organisers. Find help for your role.

A departmental administrator books five tickets for five colleagues. Registration keeps track of two different roles here, and once you know which screens show which, several confusing things stop being confusing.

  • The buyer placed and paid for the order.
  • The ticket holder is the person attending, named on each ticket.

They are often the same person. When they are not, this is what follows.

Who receives the confirmation email#

The buyer receives it. The ticket holders do not.

At the end of an order the screen confirms the order and names the address the email went to — the buyer's. The people who now hold tickets have had nothing at that point.

This is the single most common surprise. If delegates tell you they never received anything, check whether someone else booked for them before assuming the email failed.

Tip

Your delegates still need to complete their own registration details. See Completing registration when someone bought your ticket.

Which name you see, and where#

The same order shows a different name depending on which screen you are looking at. This catches people out when reconciling lists.

Screen Shows
Registrations table → Attendees the ticket holder
Registrations table → Transactions (Order owner) the buyer
Attendee details panel ("Order created by") the buyer
The invoice, if you include Buyer email the buyer

So a list of your attendees and a list of your payments will not line up name for name where people booked for each other. Neither list is wrong; they are answering different questions. Use the order reference, which is on both, to match them up.

Addresses and details on the invoice#

Details you collect on the registration form belong to the ticket holder. So if you ask for a billing address and someone books on behalf of a colleague, you capture the colleague's address, not the address of whoever is actually paying.

Where the buyer's details are what you need on the invoice — which is usual for institutional purchases — collect them through custom questions for delayed payments instead, which are put to the buyer at checkout. See Letting attendees pay by invoice or bank transfer.

You can also include the buyer's email on the invoice directly, at Registration → Finance → Payment providers → Configure invoice and receipts, under the customer details options.

Sending an attendee their receipt or invoice#

You do not need to talk anyone through finding it themselves. Go to Event dashboard → Registration → Registrations table, click the attendee's row, and use Email to send them the receipt or the invoice, or Order downloads to save a copy yourself.

See Downloading invoices and receipts.

Buying on behalf of someone yourself#

As an administrator you can place an order for someone else. When you do, you are the buyer, so the confirmation comes to you and the order is recorded in your name. See Registering on the behalf of someone else.

Note

This is also true when you are testing. An order you place while checking your own setup is a real order, recorded against you, and it will appear in your attendee list.

Was this article helpful?

Still stuck? Send us a ticket

Tell us what you're trying to do and one of our support team experts will come back to you promptly with the solution.

Create ticket
Browse all guides