Skip to content

Corporate course bookings: separate the organiser, attendees and invoice

When a company books and employees attend, Austrian course providers need clear contacts, invoices and payment records. Follow this practical booking workflow.

BD
  • Bahram Davoodi
on Saturday, 10 October 2026
Share:LinkedInXWhatsAppEmail
Corporate course bookings: separate the organiser, attendees and invoice

For a corporate booking, the person ordering, the attendees, the invoice recipient and the paying department are often different. Austrian course providers should record these roles separately at registration and connect them with one booking reference. Venue information then reaches the attendees, while the invoice goes to the agreed company address. An additional attendee list alone does not solve the problem.

One booking, four responsibilities

The following allocation describes an operational process, not a special tax rule for seminars:

Role

Information needed

Appropriate message

Ordering contact

Company, contact, places booked

Confirmation and changes

Attendee

Name, date, required course details

Directions and course materials

Invoice recipient

Verified company and billing details

Invoice and correction

Paying department

Payment reference and agreed due date

Reconciliation and queries

The ordering contact may perform all four roles. Your process should allow this without assuming it for every order. Collect only the information needed for each purpose. For example, a full attendee list does not automatically belong in every payment reminder.

Example: six places and one replacement

A fictional Vienna company books six seminar places at €180 each, totalling €1,080. Human resources places the order, six employees attend and accounts pays. Two days before the course, one attendee is replaced by a colleague.

If the price and service remain unchanged and the agreement permits substitution, first update the attendee allocation. This does not automatically create a new order, refund or additional invoice. Record who requested the change, when it was accepted and who should receive the course information.

If only five people ultimately arrive, the attendance list must still be accurate. Whether all six places remain chargeable or a correction is needed depends on the agreement and circumstances. Attendance, contractual scope and payment status are three different facts. Treating them as identical creates unnecessary queries.

Confirm five points before accepting the booking

  1. Which company is ordering, and who can approve changes?
  2. Are names required immediately, or can they follow by an agreed deadline?
  3. What service, quantity and price basis have been agreed?
  4. What is the legally correct invoice address, and where should it be delivered?
  5. Which substitution, cancellation, transfer and payment rules apply?

A customer's purchase order number or cost centre can help internal allocation. It does not replace mandatory invoice information. The Austrian business portal on invoice requirements explains the recipient, description and date of supply. The VAT treatment of the particular seminar needs separate assessment.

Send changes to the right people

Use attendee contacts for room changes and the agreed commercial contact for invoice corrections. Check the actual recipients before sending a group message. Booking-system documentation on email settings illustrates why communication rules require deliberate configuration; it does not establish a particular automation in Lonio.

Keep changes connected to the original booking. Never silently overwrite an issued invoice. Determine whether only contact details or an invoice requirement is affected, and make any necessary correction traceable. A payment arriving from another company bank account should first be matched, rather than creating a duplicate booking.

Prepare the workflow in Lonio

Lonio connects reservations, customer records and digital invoices. These areas provide the foundation for a joined-up process. Verify which separate contacts, attendee fields and delivery rules your configuration actually supports before use. This is not a promise of automatic attendance certificates or a dedicated corporate portal.

Test a sample booking with six places, a separate invoice recipient, one attendee replacement, an outstanding payment and subsequent matching of the receipt. Staff should be able to identify what was booked, who is registered and what has been paid.

Frequently asked questions

Does every attendee need a separate invoice?

Not simply because they attend. The agreed recipient of the service and the correct billing of that transaction determine the answer.

Should the company accounts team receive every course message?

Define responsibilities. Payment queries and course arrangements often need different contacts; share personal details only as necessary.

Is changing an attendee automatically a cancellation?

No. Check the booking conditions and any actual change in service. A name replacement can be handled operationally if the agreement permits it.

Ready to modernise your POS?

See how Lonio fits your business in a free, no-obligation call.