Skip to content
TixFin

Workshops & training

From booking to certificate, without the admin

Places per date, participant details collected at booking, a certificate issued the moment someone checks in, and an invoice their employer can reimburse.

Start Your ProjectContact Sales

In short

How does TixFin work for courses and workshops?

A training provider spends more time on paperwork than on selling seats. TixFin removes most of it. Each course date is an event with its own capacity and sales window, and buyer questions per ticket type collect the participant details you need — name, employer, dietary requirements, prior qualification — validated at purchase instead of chased by email afterwards. Attendance certificates are a certificate mode in the ticket designer: a layout per ticket type, generated automatically after check-in or sent manually, rendered server-side to PDF and downloadable by the participant. Every booking produces a ZUGFeRD invoice with a DATEV-oriented CSV export.

  • Participant details collected at booking
  • Attendance certificates issued on check-in
  • ZUGFeRD invoices for employer reimbursement

Capabilities

What you get for a training provider

  • 01

    A date is an event

    Every course date carries its own capacity, sales window and public page, and recurring dates are planned as a series rather than copied one by one.

  • 02

    Participant questions

    Configure text, textarea, select, checkbox and file fields per ticket type; required answers are validated server-side at purchase and stored per individual place.

  • 03

    Automatic certificates

    A certificate layout per ticket type, generated after check-in or sent manually, rendered server-side to PDF and downloadable by the participant under My Tickets.

  • 04

    Reimbursable invoices

    ZUGFeRD 2.x XML per invoice with customer VAT ID and address, plus a DATEV-oriented CSV export from the billing dashboard.

  • 05

    Modules as add-ons

    Sell an extra module, materials or catering alongside the course place, or bundle a course and its add-ons at one price.

  • 06

    Reminders and recovery

    In-app notifications and email campaigns for the run-up, plus up to three recovery reminders for a booking that was started and never finished.

Key facts

Key facts for training

Course dates
One event per date, each with its own capacity and sales window
Participant data
Buyer questions as TEXT, TEXTAREA, SELECT, CHECKBOX, FILE
Certificates
Per ticket type, triggered on check-in or sent manually, rendered to PDF
Certificate tokens
Title, participant, event name, event date, organiser, check-in date
Invoicing
ZUGFeRD 2.x with customer VAT ID and address, plus DATEV CSV export

Certificates

The certificate writes itself at check-in

Certificates use the same canvas editor as the ticket, with dynamic tokens for title, participant name, event name, event date, organiser name and check-in date. Activation, automatic email dispatch and the certificate title are configured per ticket type — so the only manual step left is the one you choose to keep.

The TixFin project dashboard showing course bookings and certificate settings
The TixFin project dashboard showing course bookings and certificate settings

Workflow

Running a course

  1. 01

    Publish the dates

    Create each course date as an event with the number of places it actually has.

  2. 02

    Ask at booking

    Add the participant questions the course needs, and mark the ones the trainer should see in the scanner.

  3. 03

    Design the certificate

    Lay out the certificate in the designer and switch on automatic dispatch after check-in.

  4. 04

    Check in and invoice

    Check participants in on the day; certificates go out and invoices export as ZUGFeRD or DATEV CSV.

Challenges

Where training admin goes wrong

  • The certificate is a manual job

    Someone opens a template, types a name, exports a PDF and emails it — once per participant, after every course.

  • The details arrive by email

    Employer, invoice address and dietary requirements chased individually after booking, then copied into a list by hand.

  • Bookings are paid by someone else

    The participant attends, the employer pays, and the invoice has to carry a VAT ID and address before anyone can expense it.

Features

The features behind it

FAQ

Questions from training providers

  • Yes. After a successful check-in, a certificate can be generated automatically per ticket type. It renders server-side to PDF, can be emailed as an attachment, and participants download it themselves under My Tickets. Admins can also trigger dispatch manually.

  • Yes. Buyer questions are configured per ticket type as text, textarea, select, checkbox or file fields. Required answers are validated at purchase, stored per individual ticket and exported as dedicated CSV columns.

  • Buyer questions marked as scanner-visible are shown with the scan result, and each check-in list can define its own extra fields that the scanner asks for right after a successful scan.

  • Each invoice produces ZUGFeRD 2.x compliant XML with seller and buyer data, line items and tax indicators. Customer VAT ID, address, postal code, city and country are first-class fields, and a DATEV-oriented CSV export is available from the billing dashboard.

Open your next course

Publish the dates, ask what you need at booking and let the certificates send themselves.