How to accept purchase orders for conference tickets

You can accept a purchase order for conference tickets if you've agreed how the buyer will pay, what you're reserving and when attendees can enter. The purchase order records the buyer's order and authorization. It doesn't mean money has reached you, and it shouldn't automatically turn an unpaid request into a paid registration.

So a university wants to send people to your conference. The department has the budget, the attendees are ready, and the coordinator asks you to accept a PO. You want the booking. You also need to pay for the venue and catering before the university's finance team finishes processing the paperwork.

The first thing you want to do is find out what that university means by "accept a purchase order." It might need an invoice bearing its PO number so it can pay before the event. It might expect you to admit attendees now and collect payment afterwards. Those are very different arrangements for your event business.

This guide explains how to make that decision, check the order and complete conference purchase order registration without confusing approval, payment and admission. We'll follow a fictional company booking through the process, including what happens when the order arrives late or the buyer needs to change it. The example quantities and dates illustrate a policy; they aren't industry benchmarks.

Decide what you're agreeing to before accepting the PO

A purchase order, often shortened to PO, comes from the buying organization. It usually identifies the seller, the purchase, the amount and an order reference. A department's internal request to raise a PO isn't necessarily an issued order. Ask for the document or authorized order information your agreed process requires.

Your invoice comes from you and requests payment for the agreed purchase. Payment confirmation follows your verification of the actual transaction. A reservation describes the places you're keeping available. Admission permission tells the registration desk who may enter. One booking can have all these records without all of them being complete at the same time.

The Organization of American Kodaly Educators makes the distinction explicit in its conference purchase order instructions. Schools can send an order to request an invoice, but OAKE says the PO itself isn't payment. Its process connects the invoice to the school's payment and the registration. That's a useful example of explaining the documents before the buyer starts.

Choose whether your conference requires payment before attendance or permits an approved organization to pay later. You can use different arrangements for different buyers if your terms and approval process support that. What you shouldn't do is leave the decision to whoever happens to answer the email.

Agreeing to later payment means your business is accepting that the money may arrive after you've delivered the conference. Consider whether you can fund those places and whether you trust the organization to complete payment. The legal effect of an order and conflicting terms depends on the agreement and applicable law. Get the appropriate review when the documents don't agree, rather than assuming a PO always settles the contract.

Ask the buyer how its payment process actually works

Start with a short conversation about the steps between approval and payment. Ask who raises the order, who approves your invoice, where the invoice must go and whether the organization can pay before the conference. The coordinator may know the event requirements perfectly while needing a colleague in procurement to answer the payment questions.

Don't guess from the buyer's size. A large institution can have several payment routes, and conference registration may have its own procedure. George Mason University's payment request guidance includes conference fees paid directly to the vendor and requires supplier registration before a request is submitted. Its rules show why "we're a university" doesn't tell you which documents this particular buyer needs.

Ask whether you're already registered as a supplier. If you aren't, find out what registration involves and who will confirm completion. A correct invoice can still wait while the organization establishes your business in its payment system. Sending more copies won't resolve a missing supplier record.

Then ask what starts the payment timetable. Is it receipt of an accepted invoice, approval by the department, the conference date, or confirmation that the service was delivered? "Our terms are thirty days" is incomplete if nobody explains when those days start or which step must happen first.

You also need to know the actual payment method. A bank transfer, a mailed check and a purchasing card create different practical requirements. Confirm the currency and any agreed treatment of payment charges. If the buyer can use an authorized card for this registration, ordinary ticket checkout may be easier for both teams.

End the conversation with a named contact for payment questions. Keep the attendee coordinator involved, but don't ask them to investigate every finance delay alone. With their agreement, include the colleague responsible for approving the invoice so the people who can complete the booking receive the same information.

Set a reservation policy you can afford

An unpaid company booking uses capacity you could sell to somebody else. That matters most when the conference is close to selling out or when a workshop has a smaller limit than general admission. Decide whether you will hold places while the buyer obtains its order, and specify which places the hold covers.

You can offer a quote without reserving anything. You can reserve places until a stated deadline. Or you can confirm a booking on agreed credit terms after approving the buyer. Each approach can work. Choose according to your available capacity, buyer relationship and ability to fund the booking before payment.

For most new buyers, I would start with a limited hold and payment before attendance. It gives the organization time to complete its process without committing your business to open-ended waiting. If that won't work for the buyer, discuss an approved exception before either team treats the registration as confirmed.

Use an exact expiry date, time and time zone. Tell the buyer what happens at expiry and whether an extension needs written agreement. A hold that quietly renews every time someone asks for an update can prevent you selling the places while still giving you no dependable payment date.

Also decide how the price works. Does issuing a complete PO before the early registration deadline secure that rate, or must payment arrive before it? You can choose either policy if it's lawful and properly agreed, but publish the rule that matches your actual process. Don't promise an early price in a quote and replace it because a separate checkout deadline passed.

Check the relevant ticket types before granting an extension. Keeping general admission available doesn't guarantee a seat in a sold-out session. If the company needs both, state whether you're holding both. Otherwise the coordinator may approve a package that your team can no longer deliver.

Check the issued order against the agreed booking

Treat the PO as something to review, rather than something to file and forget. Check the legal business buying the tickets and the legal business selling them. Conference names and trading names can help people recognize the transaction, but finance needs the correct organizations on the documents.

Compare the ticket quantities and types with your offer. Confirm the event dates, inclusions, currency and agreed total. If the PO includes a separate workshop or dinner, check that it matches the booking you agreed and that the relevant capacity remains available.

Check who has authorized the order under the buyer's process. A draft attachment, internal requisition or email saying "approved by my manager" may not be the issued document you need. Ask the buyer's procurement contact to clarify when you're uncertain. Don't change the buyer's PO yourself to make it fit.

Then read the payment and cancellation terms. A standard PO might refer to supplier conditions that don't match your conference terms. Flag the difference before acceptance. For example, your offer may require payment before attendance while the PO assumes payment only after the service. Those conditions need a decision, not a silent assumption.

Aston University explains in its No Purchase Order, No Pay policy that invoices must quote a valid PO number and that suppliers should obtain the order before proceeding. That's Aston's own policy, not a universal requirement. Use the buyer's published instructions to check what its finance team will accept.

If something is wrong, send one clear correction request identifying the mismatch and the agreed detail. Keep the current hold deadline visible while the buyer fixes it. An order that names the wrong seller or authorizes fewer tickets than requested shouldn't become a confirmed booking because everyone is tired of exchanging emails.

Follow one booking through approval and payment

Imagine Cedar Learning asks for six full conference passes for its staff. The conference takes place on 18 November. These are fictional details to show the process. You quote the agreed package and offer a hold until 22 October at the time specified in your terms, with payment required before attendance.

The coordinator confirms that Cedar needs an issued PO and your invoice before finance can transfer payment. Your supplier record is active in Cedar's payment system. You also verify Cedar's billing details in your records. You send the offer with the payment deadline, hold expiry and cancellation terms attached or clearly linked.

Cedar sends its PO on 20 October. Your team checks that it names the correct seller, covers six full passes and matches the agreed price and terms. The PO contains no workshop tickets, so you don't assume that a conversation about workshops has purchased them. You confirm acceptance of the checked order and issue the invoice through your normal accounting process.

At this point, Cedar has an accepted order and a valid invoice. Your record still shows payment outstanding. Its six passes are held under the agreement, and the coordinator receives the date by which payment must be verified. You haven't described the booking as paid or sent a message implying that every attendee can enter regardless of payment.

On 21 October, Cedar says the transfer has been sent. Your finance owner checks the transaction through the accepted payment method. If it hasn't appeared yet, you acknowledge the update and explain the current position. Whether you extend the hold while it arrives is an authorized decision under your policy, not a change made by the coordinator's screenshot.

Once payment is verified, you complete the supported ticket and registration process and confirm the paid booking. Attendee details may still need completion, but that doesn't make the payment outstanding again. Our guide to event confirmation emails explains how to tell buyers what is complete and which practical action comes next.

Send an invoice the finance team can process

The invoice should agree with the accepted order. Use the correct legal buyer, PO reference, booking reference and description of the tickets. State the currency, amount and payment terms you agreed. Include the tax details required for your transaction and jurisdiction through your accounting process.

Our event invoice template covers invoice fields and worked examples in more depth. For a PO booking, the main task is matching the documents. If the buyer authorized six full conference passes, your invoice shouldn't vaguely say "conference services" when finance needs to compare it with that order.

Ask where to submit the invoice and follow that route. The attendee coordinator's inbox may be useful for a copy, but the organization might require an accounts payable address or supplier portal. Confirm whether it wants one file per invoice, particular references or supporting booking information. Avoid resending the same invoice through several channels without checking whether that creates duplicates.

If the buyer requests a document to raise the PO before you can issue the final invoice, ask what it accepts and use the correct document type. A quote or appropriately prepared pro forma may serve that purpose. Don't invent an invoice number or tax treatment just to satisfy a form.

After submission, find out whether the invoice has been accepted for processing. "Sent" describes your action. It doesn't tell you whether the attachment arrived, the PO matched or the department completed approval. Resolve a rejection promptly and preserve the accounting record of the correction.

Give the buyer a clear payment reference, then use that reference to match incoming funds to the booking. If a combined payment covers several registrations, request the remittance information that identifies them. A total received into your bank without a booking match doesn't tell the registration team which attendees to confirm.

Make early registration deadlines workable for institutional buyers

An early registration offer can cause confusion when one date governs online payment and another governs PO acceptance. Buyers want to know whether starting their approval process qualifies them for the price. Your team needs to know how long it will reserve capacity and wait for payment.

Write the condition explicitly. You might require a complete issued order to reach you before the price deadline, followed by payment before the agreed due date. Or you might require completed payment before the lower price expires. Avoid the phrase "register by" unless the page explains what completed registration means for this route.

Allow for the buyer's real processing steps when discussing timing. Supplier registration, order approval and invoice checking are separate tasks. A company contacting you on the last afternoon of an offer may genuinely want to buy, but that doesn't mean your team can complete every step before the price changes.

Tell that buyer what you can actually approve. If you can extend the quote, name the new expiry and any conditions. If you can't reserve places, explain that the current offer remains subject to availability. Don't make an informal promise that the payment team will later contradict.

Keep the agreed price and the hold period distinct. You might preserve the quoted rate without reserving the tickets beyond the hold deadline. If that's your arrangement, say so plainly. The buyer otherwise has a reasonable chance of reading a price extension as a capacity extension too.

Publish the latest date for accepting new PO requests before the conference, based on the work you can complete. Provide a contact for buyers outside that timetable. A late request may still be possible through an authorized immediate payment route, but the person handling it needs to check rather than promise admission first.

Consider requests to pay after the conference separately

Some buyers cannot complete payment until the event has happened. SUNY Cortland's conference registration fee guidance says payment through its PO route cannot be processed until after the conference. It tells attendees to check whether the organizer will accept an order to secure registration. That is a specific institutional rule, and an example of the question you need to ask early.

If your policy requires payment first, an invoice reminder won't resolve that incompatibility. Ask whether the organization has another authorized way to pay, such as its permitted purchasing card process. Let the buyer confirm its own rules. Don't encourage an attendee to circumvent procurement or pay personally when their employer hasn't authorized that route.

If you decide to accept payment afterwards, approve the arrangement before issuing attendance permission. Confirm the purchasing organization, the accepted order, when payment becomes due and what evidence its finance team will require after the conference. Record who in your business approved the exception.

Consider the booking alongside your other unpaid commitments. A familiar organization may seem dependable, but several bookings on later payment terms can leave you funding a substantial part of the event. Your event cash flow forecast should reflect the expected collection date rather than treating every accepted PO as money available for supplier payments.

Agree who will provide any required delivery confirmation after the event. If finance needs the department to acknowledge the registration service, identify that owner while the coordinator is still engaged. You shouldn't discover that requirement when chasing an overdue invoice weeks later.

Explain cancellation and no-show terms before acceptance as well. Attendance records can help confirm what happened, but don't assume a person missing the conference automatically cancels the organization's liability or automatically proves it owes the full amount. Apply the accepted agreement and the rules relevant to your transaction.

Keep the buyer informed without mislabeling the booking

Use messages that describe the current facts. Acknowledging receipt of the PO should tell the buyer whether you're still checking it, have accepted it or need a correction. Include the booking reference and the next action. The word "confirmed" on its own leaves too much for the coordinator to infer.

Here's sample wording for a booking requiring payment first. Replace the bracketed details with the agreement you can deliver.

"We've accepted [organization]'s purchase order [PO reference] for [quantity and ticket type] at [conference]. Invoice [reference] has been submitted to [agreed billing route]. Payment is outstanding. We are holding the places until [date, time and time zone]. Please arrange payment by [agreed deadline]. Attendance requires verified payment under the terms accepted for this booking."

If you've approved later payment, the message should say that instead. "Your booking is confirmed on the agreed payment terms for [organization], and the authorized attendees may attend. Invoice [reference] is due on [agreed date]. Please complete [outstanding attendee information] by [registration deadline]." Only use this version after the person responsible in your business has approved that arrangement.

When payment arrives, confirm the verified amount and the booking it covers through your normal process. State any remaining task, such as supplying attendee names, separately. A company shouldn't receive another demand for payment because your registration owner is waiting for a dietary form.

Keep detailed payment correspondence with the people who need it. Individual attendees need their access instructions and relevant event information. They usually don't need a forwarded chain containing supplier onboarding documents or bank information. Ask the coordinator how tickets will reach each attendee, and verify that the delivery method actually works.

For buyers who can pay directly, Loopyah's ticket checkout sends a confirmation email linking to their QR tickets. That's a straightforward route when the organization permits checkout payment. It doesn't establish a purchase order acceptance, unpaid reservation or credit arrangement; confirm the supported process before promising those capabilities.

Handle changes without disconnecting the order from the tickets

A company may add attendees after you accept the order. Check availability, the price for the additions and whether procurement needs an amended or separate PO. An existing authorization for six passes doesn't necessarily cover a seventh, even when the same department will pay.

If the buyer reduces the booking, check the accepted cancellation terms before changing the invoice or registration. Tell finance whether the quantity is changing, whether a charge remains and which accounting document your process requires. Don't delete tickets and assume the buyer's payment system will discover the new amount.

A substitute attendee is a different request. The company may keep its purchased quantity while replacing one colleague. Apply the substitution rules agreed for the booking, verify who is authorized to request the change and update the supported ticket records. Check whether the substitute qualifies for any eligibility-based rate.

A mismatch between payment and invoice needs investigation too. The buyer may pay less because its order excluded an agreed extra or because a charge was disputed. Record what was received, identify the difference and agree the next step. Don't mark the whole order paid merely because a transfer arrived.

Prevent duplicate purchases when the coordinator changes routes. If the company pays through checkout after requesting an invoice, identify that transaction and close or correct the outstanding invoice through your accounting process. Keep enough information to show which purchase is valid. Issuing a second set of tickets would create an attendance problem as well as a finance problem.

For refunds, follow the agreed terms and verify the recipient and payment route. An email asking you to send money to a different account deserves a separate check. The FBI's business email compromise guidance recommends verifying payment requests and changes to account numbers or payment procedures directly with the person involved. Use independently established contact details rather than relying on a number supplied in the change request.

Give the booking one owner across your teams

Choose one person to own the purchase order booking through completion. That person doesn't need to do every task. Finance can check payment, registration can prepare tickets and your event manager can approve an exception. The owner makes sure somebody completes the next task and tells the buyer where the booking stands.

Keep a shared booking record in the systems your business already uses. It should identify the organization, coordinator, finance contact, accepted order reference, invoice reference and current quantity. Record the hold expiry, payment due date and attendance decision separately. Link the documents so a colleague can check what was agreed when the owner is unavailable.

Be careful with a single status called "approved." Approved by whom, and for what? The buyer's manager might have approved spending. Your finance team might have approved credit. Your registration team might have approved an attendee's eligibility for a discounted pass. Write the specific decision, who made it and when, because those approvals don't complete each other's work.

Agree which changes require a handoff. When finance verifies payment, it should tell the booking owner through your normal process. When the buyer changes the quantity, the owner should involve the people managing invoices and ticket capacity. When someone approves attendance before payment, registration needs that decision before issuing access or preparing the final list.

Use the same booking reference in messages between departments. The PO reference helps the buyer's finance team, but your internal booking reference connects the order to the event and attendees. A company can issue several POs across a year, while one payment can cover several invoices. Your records need to preserve those relationships without making staff guess from surnames.

Review outstanding bookings when a decision is due, such as a hold expiry or supplier commitment. Ask whether the invoice was accepted, whether payment is expected under the agreement and whether the current reservation still makes sense. Don't turn every review into another generic reminder. If the missing step is supplier registration, ask the person who can complete that task.

Before the owner takes leave or changes shifts, record the next action and the contact responsible. A colleague should be able to continue the booking without asking the buyer to resend everything. That handover also prevents an extension promised in one email from disappearing when another team member releases the places. Keep the current agreement accessible to everyone who needs to act on it, with personal and financial information limited to the appropriate staff.

Prepare the registration desk and close the payment record

Before the conference, give the registration owner the current admission position for every PO booking. Separate people cleared to attend from unresolved requests. Include the authorized decision contact so check-in staff know who can review a disputed booking without negotiating financial terms in the queue.

An attendee may arrive with a PO and sincerely believe it guarantees entry. Your team should be able to find the accepted booking and explain its terms. If payment was required first and remains outstanding, follow the agreed policy and escalate to the person who can approve an exception. Don't let a busy desk invent one.

Equally, a booking approved for later payment shouldn't be refused simply because the invoice remains unpaid. The admission record must reflect the agreement your business actually accepted. Test that distinction before doors open, especially when finance and registration use different systems.

Use the ticket system's supported permissions for the admission task. Loopyah lets organizers give door staff check-in access so they can scan QR tickets on their own phones. That permission helps staff admit valid ticket holders. Your commercial decision about an unpaid institutional booking still needs its own authorized owner and a clear record.

After the event, complete any agreed evidence of delivery and follow up outstanding invoices through the buyer's approved route. Check the payment record before every reminder. If the money has arrived under an unfamiliar reference, resolve the match instead of asking the company to pay again.

Review where the process needed intervention before your next conference. Perhaps supplier setup started too late, your price deadline was unclear, or the invoice went to the attendee instead of finance. Fix that specific problem in your published instructions. Accepting purchase orders is worthwhile when it helps suitable organizations buy and gives your team a booking it can deliver and collect under clear, affordable terms.