Event invoicing and tax

Create event-order invoices with the tax detail your market needs

Collect buyer billing details, apply your approved GST, VAT, or custom tax lines, and deliver a numbered PDF invoice connected to the original event order.

Organizer-defined invoice identity Buyer billing and tax fields Order-linked PDF delivery
EventHex portal showing Tax and Discounts settings with tax configuration and discount controls
EventHex portal showing Invoice and Billing settings with invoice generation and delivery controls
Order-linked PDF delivery
Invoice workflow

Keep every invoice attached to the transaction that created it

The invoice starts from the paid registration or ticket order, not from a disconnected spreadsheet or document template.

Set the invoice rules

Choose identity, numbering, buyer fields, and tax configuration.

Buyer requests an invoice

Show the invoice option in the supported registration or checkout journey.

Complete payment and order

Retain ticket, amount, currency, buyer, and tax context.

Generate and deliver

Create the PDF and send it through the configured order workflow.

Your invoice identity

Make the document match the organizer and the transaction

Set the fields your finance team has approved before opening ticket sales.

01

Document title

Use Invoice, Tax Invoice, Receipt, or another approved title.

EventHex Global Ticket Settings showing Invoice and Billing controls
Document title Invoice · Tax Invoice · Receipt Document title
02

Bill-to label

Adapt the buyer section label to the document type.

Bill-to label Bill-to label Bill-to label
03

Organizer details

Show the configured billing company, address, and logo.

Organizer details Billing company · Address · Logo Organizer details
04

Invoice number label

Name the reference field the way your workflow requires.

Invoice number label Invoice number label Invoice number label
Invoice numbering

Start with the prefix and sequence your event uses

Configure the invoice prefix and starting number so generated documents carry a consistent order-linked reference.

01

Prefix

Add the approved event or document prefix.

02

Starting number

Choose where the generated sequence begins.

03

Invoice label

Control how the number is named on the document.

04

Order connection

Keep the invoice reference with the source transaction.

Buyer billing details

Collect the information the invoice needs during registration

When the buyer requests an invoice, surface the configured fields in the same journey instead of chasing them after payment.

Company name

Collect the legal or trading name supplied by the buyer.

Tax ID

Use GSTIN, VAT number, TRN, or another configured label.

Billing address

Capture the address needed for the organizer's document.

Required fields

Choose which supported B2B fields must be completed.

Invoice preview

Show the configured buyer details in the available preview flow.

Order record

Retain invoice-request context with the registration or order.

Configurable tax detail

Use named tax lines with inclusive or exclusive ticket pricing

Your team supplies the tax names and percentage rates; EventHex applies that configuration to the supported checkout and invoice breakdown.

01

Tax-exclusive price

Show the base ticket price and add the configured tax lines to the order total.

Best when tax is added at checkout
02

Tax-inclusive price

Treat the displayed ticket price as inclusive and show the configured tax portion in the breakdown.

Best when the advertised price already includes tax

EventHex applies organizer-defined rules; it does not select the legally correct rate or jurisdiction for you.

Global by configuration

Use the tax language your market and finance team approve

The product mechanism stays the same; the labels, IDs, and rates change with the organizer's approved setup.

  1. 01

    India

    Use GST and GSTIN labels when they are required for the event's approved invoice setup.

    • GST label
    • GSTIN label
    • Approved event setup
  2. 02

    UAE and GCC

    Use VAT, TRN, or another locally approved label and configured rate.

    • VAT label
    • TRN label
    • Locally approved rate
  3. 03

    United Kingdom

    Use VAT and the billing fields approved for the organizer's UK invoice workflow.

    • VAT label
    • Approved billing fields
    • Organizer's UK workflow
  4. 04

    United States

    Use the applicable organizer-defined sales-tax label or no tax line where advised.

    • Organizer-defined sales-tax label
    • Applicable event setup
    • No tax line where advised
  5. 05

    Cross-border events

    Keep the event currency and buyer details visible without implying tax determination.

    • Event currency
    • Buyer details
    • No implied tax determination
  6. 06

    Custom terminology

    Adapt supported labels to the document and market your team has validated.

    • Supported labels
    • Approved document wording
    • Validated market terminology
PDF delivery

Give the buyer a clear document they can keep with the order

Generate the available invoice PDF from the order data and send it through the configured invoice-delivery path.

Order-linked PDF delivery

Branded PDF

Use the configured organizer identity and invoice labels.

Ticket and order lines

Show the source purchase and amount context.

Tax breakdown

List the configured tax names, rates, and calculated values.

Email delivery

Send the generated document to the buyer through the supported order workflow.

Finance-ready configuration

Keep tax decisions with the team responsible for them

EventHex gives organizers the fields and document workflow; the organizer remains responsible for choosing valid labels, rates, numbering, and required information.

01

EventHex configures

Invoice identity, supported buyer fields, tax lines, price mode, numbering, PDF, and delivery.

02

Organizer approves

Business identity, tax names, rates, required fields, and event setup.

03

Adviser validates

Jurisdiction, tax treatment, statutory wording, and filing obligations.

04

Payment provider handles

The selected gateway's payment, settlement, and account requirements.

Connected event commerce

Continue into the workflow that owns the next job

Invoice data starts in registration and follows the payment and order path.

Designed for paid event orders

Use the invoice workflow across the events your team runs

Apply one approved setup per event and market.

Conferences

Give delegates and corporate buyers an order-linked invoice.

Exhibitions

Support exhibitor or attendee ticket purchases with billing detail.

Association events

Handle member and company registrations with invoice requests.

Corporate events

Keep internal or customer-event documents consistent.

Tech conferences

Connect paid ticket orders to buyer finance requirements.

Multi-market teams

Reuse the workflow while configuring the correct regional labels.

Event invoice questions

What teams ask before enabling invoices

Can buyers request an invoice during registration?

Yes. In the supported flow, organizers can enable invoice requests and collect the configured company, tax-ID, and billing-address details.

Can we use GST, VAT, or a custom tax label?

Yes. Your team configures the supported tax names and percentage rates. GST and VAT are examples; EventHex does not decide which tax applies.

Can we customize the invoice number?

You can configure the supported invoice prefix, starting number, document title, and invoice-number label.

Does EventHex calculate the legally correct tax automatically?

No universal tax-determination engine was verified. Your finance or tax adviser should approve the labels, rates, treatment, and required fields.

Can EventHex send a PDF invoice?

The supported invoice workflow generates an order-linked PDF and can send it through the configured delivery path. Confirm the exact trigger and template in the demo.

Does this page include credit notes and reconciliation?

Those invoice-document capabilities were not verified end to end. Payment refunds and event finance reporting belong to the Payment Processing workflow and should not be presented as proof of credit-note automation.