Congress registration and payment: from registration types to badges

Congress registration and payment covers a sequence of steps: the attendee creates an account, chooses a registration type and add-ons, applies a discount, enters invoice details, pays, and finally receives a badge and documents. When these steps run on a single record, the secretariat can see on one screen who paid what, what they are entitled to and which documents they will get. Below we explain which rules to settle in advance at each step.

What steps make up congress registration?

Registration starts with an attendee account. When authors who submit papers and people attending only as listeners use the same account structure, papers, registration and documents all come together under one identity. Information collected through separate forms has to be matched by hand later, and the same person can end up appearing as two different records.

After creating an account, the attendee chooses a registration type, adds extras such as a gala dinner or a workshop, applies any discount and sees the total. They then enter invoice details and choose a payment method. Once payment is confirmed, the registration is final, and the badge, invitation letter and, after the event, the attendance certificate are tied to that confirmed record.

Each step carries a rule: who may choose which type, what proof each discount needs, when an unpaid registration lapses, and when each document becomes available. Writing these rules down before registration opens is the only way to answer the growing number of exception requests consistently as the event approaches.

When registration, payment and documents are three states of the same record, who is entitled to what stops being a matter of debate.

How should registration types and fees be defined?

Registration types define in what capacity someone attends and what they get access to. Too many types confuse attendees; too few squeeze different needs into the same price. A good structure separates a handful of main types from optional items that can be added to them.

• Main types such as presenting author, listener and student should each have their own fee.
• If in-person and online attendance give different entitlements, they should be set up as separate types.
• Items such as a gala dinner, workshops and courses should be optional add-ons to the main registration.
• For workshops with limited places, remaining capacity should be visible during registration and the option should close when full.
• If accompanying persons can register, state clearly which events they may attend.
• The scope of each type, meaning which sessions, materials and documents it includes, should be shown on the registration page.

Calculating fees from registration type and add-ons means the secretariat never has to work out totals by hand. The amount on the payment screen should be built automatically from the chosen type, add-ons and discounts, and the same calculation should flow into the finance report.

When registration and add-on sales open and close is part of the fee structure too. Closing only the gala option when it is full, closing the whole form when the registration period ends and reopening an item when needed should be settings the secretariat can manage without a technical team. Last-minute changes can then be applied without showing anyone a wrong price.

How should early-bird rates and discount codes work?

Early registration encourages attendees to decide sooner and gives organisers early data for planning. The early period and its exact end time should be announced with the call, including the hour at which the last day closes. It should also be decided in advance how long an unpaid early registration can still be paid at the old rate after the period ends.

Discounts come in two kinds: those tied to who the person is and those granted by code. Discounts based on student status, academic title or association membership may require the attendee to upload proof and the secretariat to approve it. Code-based discounts are issued to sponsors, invited speakers or institutional group registrations.

Every discount code needs a usage limit, an expiry date and a list of registration types it applies to. An unlimited, open-ended code can undo the entire pricing structure the moment it is shared online. Whether discounts can be combined should also be a written rule; otherwise one attendee might stack the early rate, a membership discount and a code on top of each other.

Institutional group registrations need their own arrangement. When an organisation wants to pay for several staff members in one payment, each attendee should still register with their own account, and the organisation's payment should be matched to those registrations. Issuing a group-specific discount code keeps both the price and the list of people who used it traceable.

How should payments and collections be tracked?

Congresses usually offer two payment routes side by side: online card payment through a virtual POS and bank transfer. For card payments, the result should arrive from the payment infrastructure as a signed callback, and the registration should be confirmed on the basis of that verified message. A success message in the attendee's browser should never count on its own as proof of payment.

For bank transfers, the attendee uploads the receipt and the secretariat checks the bank movement and approves it. Asking attendees to put their registration number in the transfer description makes matching easier. Listing transfers awaiting approval separately ensures nobody falls through the cracks.

Email and SMS reminders for unpaid registrations make collection noticeably easier before the deadline. After the congress, a finance spreadsheet with separate sheets for registrations, payments, discounts and add-ons speeds up reconciliation with the accounting team.

How should invoice details and refunds be handled?

The invoice for a congress fee is often issued not to the attendee but to their institution. Registration should therefore offer individual and institutional invoice options, with the institution's name, tax office, tax number and address collected as separate fields. Collecting this before payment cuts down on correction requests after the event.

Whether the invoice is issued as an e-Fatura or an e-Arşiv invoice depends on the status of the issuer and the recipient. Check current thresholds, obligations and dates with the official sources of GİB, the Turkish Revenue Administration, and with your accountant; this article is not tax or legal advice.

Refund rules should be clearly visible on the registration page before payment: until when a full refund applies, until when a partial one, whether add-ons are refundable and whether a registration can be transferred to someone else. A refunded registration should lose its badge and document access, and the refund should appear as a separate entry in the financial records.

How are badges and congress documents prepared?

The badge is the on-site face of the registration data. Name, institution and registration type should come straight from the record, and the layout should be designed once and produced in bulk for every attendee. Marking the registration type with a colour or label makes checks at the gala and workshop doors easier.

• The name and institution on the badge should match exactly how the attendee entered them at registration.
• The registration type should be shown with a colour or label that staff can recognise at a distance.
• Add-ons such as the gala and workshops should be marked on the badge or printed as a separate entry card.
• No badge should be produced for unpaid registrations; those attendees should be directed to the registration desk.

Invitation letters needed for visas or institutional leave should be downloadable from the attendee's own panel once registration is confirmed. The attendance certificate should open after the congress, and only for fully paid registrations. Tying document access to payment status means the secretariat no longer has to check each request individually.

On congress day, the registration desk is the last on-site checkpoint for the data in the system. If desk staff can look attendees up by name and instantly see their payment status, registration type and add-ons, queues get shorter and any corrections made on the spot are saved to the same record. A name corrected at the desk then appears correctly on the certificate produced after the event.

Frequently asked questions

How large should the early-bird discount be?

There is no single correct rate; the discount should be large enough to prompt an early decision and modest enough not to strain the budget. Looking at when people registered in previous years is the most reliable guide for deciding when the early period should end.

Should bank transfer still be offered?

Yes, transfers are still widely used, especially when an institution pays on the attendee's behalf. What matters is that each transfer is tracked on the same record through receipt upload and admin approval, and appears in the same finance report as card payments.

Can a registration be transferred to someone else?

That is the organiser's decision, and it should be announced in advance alongside the refund rules. If transfers are allowed, the new attendee should complete the details through their own account, and the badge and documents should be produced in the new name; cases that create a price difference should also be covered by the rule.

How should attendees' consents be stored?

For consents collected at registration under KVKK, Turkey's data protection law, record which text was accepted, when and from which device. Check which consents you need with the current guidance of the Personal Data Protection Authority and with your legal adviser.

Should on-site registration be accepted?

On-site registration can help people who decide at the last minute, but it complicates planning for badges, catering numbers and room capacity. If you accept it, announce its fee, payment method and included add-ons in advance, and record these registrations in the same system as all the others.

Before registration opens

Before registration opens, put registration types, fees, discount rules, payment routes, invoice options and refund terms into a single document, and have the scientific committee and the financial lead approve it together. That document becomes the shared source for the registration page, the system settings and the secretariat's answers to questions.

Once the rules are clear, registration, payment and documents feed each other naturally, and the pressure of congress week does not land on the registration desk. At Bir Web Ajans we build this flow with Nova CongressPort, bringing registration types, discounts, virtual-POS and bank-transfer collection, reminders and badges together on the same record.