How to control event purchases before supplier invoices arrive

Your production lead has booked an extra technician. The venue has arranged another access day. Someone has told the printer to go ahead with the larger order. None of the invoices has arrived, so the budget still looks comfortable. Then you approve something else against money you've effectively promised to spend already.

An event purchase approval process should make those promises visible before anyone makes the next one. Record the full purchase, check who can authorise it, and give the supplier a clear instruction only after approval. Keep changes connected to the original order so a series of small additions can't quietly become a much bigger booking.

That sounds fairly straightforward. The difficult part is making it work when several people are buying different things, a supplier wants an answer today, and the person who usually approves spending is at another event. Your process needs to cope with those situations while there's still a decision to make.

We'll work through a fictional paid conference, then build a purchase record you can adapt. Whenever someone asks to buy something, you should be able to see the full amount you're agreeing to pay and whether it leaves enough for the rest of the event.

Put the approval before the supplier starts

The first thing you want to do is agree what counts as permission to buy. An event budget gives you an overall spending plan. It doesn't necessarily give every person who can see it permission to sign a contract, order equipment or accept an extra charge. Write down who can make those decisions.

A purchase request is the team's internal proposal. A purchase order is an instruction issued to a supplier for specified goods or services. Some businesses use signed contracts or accepted quotes instead. Whatever documents your operation uses, distinguish asking for approval from communicating an authorised purchase. Calling both things "approved" leaves too much room for interpretation.

Santa Clara University's requisition and purchase order guidance makes that sequence explicit in its own purchasing system. An internal requisition goes through approval before a purchase order gives the supplier permission to begin. The university's requirements are its own, but the distinction is useful for an event team of any size.

Choose the document that fits your existing purchasing and accounting arrangements. You don't need to invent a second order system if your finance software already records requests and approvals. You do need the event lead to know when a request is still waiting, when somebody has approved it internally, and when the authorised instruction has actually reached the supplier.

Be careful with informal conversations during sourcing. Asking whether a crew is available is different from telling the crew to reserve paid dates and start preparing. If you're only seeking a quote, say so. Clarify whether a proposed hold is free, expires at a stated time, or creates any obligation before accepting it.

Don't assume an absent purchase order means you owe nothing. The Australian Government's guide to types of contracts explains that contracts can be verbal as well as written. The effect of a particular conversation depends on the agreement and applicable law. Your internal approval policy is a way to control decisions, not a guarantee that an unauthorised promise has no external consequences.

Find the commitments you already have

Before introducing new approvals, establish what your team has already agreed. Otherwise, you can follow every approval step and still use an incomplete total. Ask each person who books suppliers to identify accepted quotes, signed contracts, card purchases, email instructions and later changes for the event.

Include work that has happened without an invoice. A supplier who completed the agreed site survey hasn't become free because its accounts team is slow. Include future work you've ordered too. The sound system arriving next month still affects what you can afford to buy today.

For this guide, the commitment total means the full value of purchases already agreed, including amounts paid against them. Keep the unpaid portion alongside it. This is a management record for purchasing decisions, not a substitute for your accountant's rules about when expenses or liabilities belong in the accounts.

Separate an agreed commitment from an estimate for work you haven't ordered. You may need security, transport and cleaning even while the suppliers remain undecided. Those estimates belong in the final cost forecast. Leaving them out would make uncommitted money look available for optional spending when it's already needed to deliver the event.

Your event budget review should bring agreed work and expected remaining costs together. The purchase process then controls which proposed costs become new commitments. Keeping both records connected helps the approver see whether today's request confirms an existing estimate, replaces it at a different price, or adds something the plan never included.

Check who is actually buying as well. A venue, agency and organiser may each be able to order services, but that doesn't mean they are all buying on the same business's behalf. Identify the paying business and any charge that will be passed back to you. Don't let two parties assume the other has included a service, or both order it independently.

Work out what is available before approving an extra

Let's use Eastbank Events, a fictional organiser planning a paid conference. Every name, amount and reference in this example is invented. All money is USD, and the figures include all charges assumed for the stated purchases, with no assumed tax recovery. They explain the method, rather than suggesting supplier rates or a suitable budget for your event.

Eastbank has approved a $50,000 spending ceiling for this example's event costs. It has already agreed purchases totalling $34,000. Of that total, $8,000 has been paid and $26,000 remains unpaid. The paid amount and unpaid amount are two parts of the same commitments. They aren't extra costs to add to $34,000.

The team also expects $9,500 of necessary purchases it hasn't placed yet. That includes a $5,000 production estimate and $4,500 for other required work. Its current expected cost is therefore $43,500, made up of $34,000 agreed and $9,500 still estimated. This example concentrates on spending control, so it doesn't calculate ticket revenue or event profit.

The director wants to retain $3,000 of the ceiling for unresolved risks. That reserve is separate from the $43,500 expected cost, rather than another estimate for the same work. After allowing for both, $3,500 remains available for discretionary decisions. The team shouldn't describe the entire $16,000 between agreed purchases and the ceiling as spare money.

Now the production quote arrives. Equipment is $4,800, delivery is $400 and the required crew is $600. The complete purchase is $5,800. The approver needs to review that total, the work included and the payment terms. Looking only at the equipment line would hide $1,000 of the decision.

Approving the complete quote replaces the earlier $5,000 estimate. Agreed purchases become $39,800, while necessary unplaced work falls to $4,500. Expected cost becomes $44,300. With the same $3,000 reserve, discretionary room falls to $2,700. The change against the previous forecast is $800, not another $5,800 on top of it.

This is why the purchase request should name the estimate it replaces. Without that link, one person may leave both amounts in the forecast while another deletes the estimate without adding the order. Both errors can survive until the invoice arrives, even though the team believes it approved the right purchase.

Approve the whole purchase, not just the deposit

Eastbank's supplier requests a $1,740 deposit, with $4,060 due later under the agreed schedule. Together they make the $5,800 purchase. An approver reviewing only the deposit would miss most of what the business is agreeing to pay. Show the full order value and the payment schedule in the same request.

After the deposit is paid, Eastbank's paid amounts across all agreed purchases rise from $8,000 to $9,740. Its unpaid commitments become $30,060. Those amounts still add to $39,800. Paying the deposit changes the cash position and outstanding balance. It doesn't reduce the full value of the production booking.

Use the same approach for staged payments, subscriptions and minimum guarantees. Identify the period or work covered, the minimum commitment, any usage charges and the conditions for cancellation. A low initial charge may be one instalment of a larger purchase. A recurring arrangement may continue beyond this event unless someone acts before a renewal date.

Uncertain quantities need a clear limit or a clear escalation point. For crew paid by the hour, record the approved hours and rates, what happens if the schedule overruns, and who can approve additional time. Don't enter an apparently fixed total while leaving the supplier authorised to keep adding hours without review.

For catering, distinguish the current estimate from the guaranteed minimum and final ordering deadline. If the team approves a minimum now and can increase later, record both the commitment and the expected final quantity. The final forecast should reflect the event you expect to deliver, while the purchasing record shows what has actually been authorised.

Ask your accountant how tax, foreign currency and deposits should appear in the systems you use. The practical requirement is a consistent comparison. Someone reviewing an inclusive spending limit needs the complete charge on that basis, rather than an attractive quote subtotal that omits tax, delivery or another unavoidable fee.

Give people authority they can use

A workable approval policy names people, amounts and circumstances. "Check with management" is too vague when the supplier is on the phone. State who can approve an ordinary purchase, who can approve a higher amount, and which decisions need additional review regardless of price.

Eastbank could, for example, allow its event manager to approve purchases up to $1,000 within an agreed category allowance. Purchases above that go to the director. These are invented limits for this example. Your business should choose its own limits based on the size of commitments, available oversight and the consequences of getting a decision wrong.

Make the limits cumulative for related work. Two $700 purchases for one planned print package make a $1,400 decision. Splitting the order across two dates, two cards or two suppliers shouldn't turn it into two unrelated approvals. Ask what the team is trying to buy and assess that connected requirement.

Also distinguish permission to approve from permission to place the order. Your producer may check whether equipment is suitable, your director may approve the commitment, and your coordinator may issue the authorised order. Tell the supplier who can change the instruction later. A helpful onsite colleague shouldn't accidentally become an unrestricted buyer.

The Australian Charities and Not-for-profits Commission's fraud prevention guidance recommends separating financial duties where possible, keeping decision records and setting authority limits. It addresses charities. A commercial event business can adapt those principles to its own team, with professional advice where needed, rather than copying charity requirements as if they were universal rules.

Keep a named backup for each approval role and define when they take over. The backup needs access to current commitments, not just a message saying the usual approver is busy. Record the handover so two people don't independently approve spending against the same remaining allowance.

Make small purchases quick and important purchases visible

If every cable, parking charge and print correction needs a director's meeting, staff will look for ways around the process. Give ordinary purchases a short route with enough information to check the need, complete price and remaining allowance. Save the longer discussion for decisions with larger or less reversible consequences.

You can preauthorise a defined class of routine purchases within an overall cap. Specify the category, permitted items, period, responsible buyer and evidence required. The buyer still records each purchase against the shared total. A card limit on its own doesn't tell them whether the event budget can support another charge.

For example, a production coordinator might have authority for consumables within a capped allowance for one build. If the supplier offers a different item outside that category, the same card doesn't create permission to buy it. If several buyers share the allowance, somebody needs to maintain the remaining total as purchases occur.

Price isn't the only reason to escalate. A modest purchase can involve customer data, a new cancellation commitment, an exclusive arrangement or a promise to a sponsor. Put these exceptions in ordinary language and give staff a contact. They shouldn't have to interpret a long policy while trying to decide whether a supplier's new terms matter.

Keep the decision proportional to the consequence. Buying replacement stationery from an established supplier is different from accepting an unfamiliar contractor's terms to install equipment. The event lead checks whether the proposed work is suitable and whether specialist review is needed. Financial approval doesn't establish technical suitability, safety or permission to use the venue in a particular way.

Tell people how quickly ordinary requests will be reviewed and what information prevents delay. A request submitted before the supplier's deadline gives the approver a real choice. One submitted after work starts asks them to handle a problem that has already happened, regardless of how quickly they respond.

Copy this purchase request record

Use these fields in your existing purchasing system where possible. Link to information already held on the supplier record, rather than asking staff to retype it into several places. The record should let someone who wasn't in the sourcing conversation understand exactly what you want to buy and why a decision is needed.

Identify the purchase

• Request reference, event, paying business and person requesting it.

• Supplier identity and link to the supplier record.

• Goods or services, quantities, delivery dates and location.

• Quote or proposed agreement, with its date and version.

• What is included, excluded and still awaiting confirmation.

Explain the money and the decision

• Full proposed commitment, currency and consistent treatment of tax and fees.

• Deposit, later payments, due dates and payment conditions.

• Budget category and the estimate or existing order this request replaces.

• Current event forecast, retained reserve and position after approval.

• Reason for the purchase and the consequence of delaying or declining it.

• Last useful decision time, quote expiry and any cancellation or renewal commitment.

Record approval and the supplier instruction

• Named reviewer for delivery suitability and any required specialist review.

• Named financial approver, authority used, decision and timestamp.

• Conditions still required before the order can be placed.

• Person authorised to order, current order reference and supplier confirmation.

• Owner responsible for receipt, changes and eventual closure.

Keep rejected, withdrawn and expired requests understandable too. Otherwise, a colleague may find an old quote and assume somebody forgot to place an approved order. Mark what happened and preserve the decision without leaving the request available for someone else to issue.

If the approver asks for a lower price or different scope, record that condition clearly. "Approved if delivery is included within $5,800" doesn't authorise a $5,800 subtotal plus delivery. When the revised quote arrives, check it against the actual condition before issuing the order.

The record doesn't have to be long. A straightforward repeat purchase may use a short form with linked evidence. A complex booking may need a fuller review. The test is whether another authorised person can identify the complete commitment, the decision and the supplier instruction without asking you to reconstruct a conversation.

Stop simultaneous requests spending the same allowance

Two sensible requests can become an unaffordable pair if each approver looks at the same old balance. One person approves a print order while another approves transport, and both assume the available money is still untouched. A shared document helps only if the decision and its effect become visible before the next approval.

Give one person responsibility for updating commitments and reserved approvals, or use a system that updates them as approvals occur. The approver checks the current totals before deciding. Record approved requests waiting to be issued as well as orders already sent, so another buyer can't use their allowance in the gap.

Be precise about the difference. An internally approved request may reserve money for a planned order without yet being a supplier commitment. Show the reservation separately and avoid counting it again after the order is issued. If the request replaces an estimate, the forecast shouldn't contain the estimate, the reservation and the final order as three costs.

Set an expiry or follow-up date for those reservations. A supplier may decline the booking or let the quote expire while the team leaves the money reserved indefinitely. The owner should confirm whether the request will proceed, needs repricing or can be withdrawn. Releasing its reserved amount doesn't remove any separate obligation already made to the supplier.

When choosing software, ask the provider to show this exact situation. Have two authorised users review competing requests against one allowance in a demonstration that can't place orders. Check whether the second user sees the first decision immediately, receives a warning, or can still proceed from stale information. Know where your team's own coordination remains necessary.

Restrict who can change approval limits and supplier instructions. A system that records a director's approval but lets another user increase the order afterwards leaves the main question unresolved. Your team needs to see which version was approved and whether the instruction now being issued still matches it.

Define what an agency can buy on your behalf

If you use an event agency, agree its purchasing authority before suppliers start receiving instructions. Establish which business contracts with each supplier, who owes the payment and whether the agency is buying for itself or acting for you. Have the agreement reviewed where necessary. A shared event name doesn't settle those responsibilities.

For purchases requiring your approval, ask for the full amount your business will bear, including the agency's agreed charges and relevant third-party costs. Confirm what the agency may approve independently and what comes back to you. Budget access, operational responsibility and authority to commit your money are separate permissions, even when one account manager handles the conversation.

Require the same clarity for changes. If a venue offers additional access directly to your producer, the agency needs to know whether that instruction changes its booking. If the agency adds crew under its own supplier agreement, you need to know what charge reaches your event and whether your approval is required first.

Keep one current account of the commitment and its allocation, supported by the underlying agreements. Don't add both the agency's inclusive package and its included supplier costs to the forecast. Equally, don't assume an excluded service is covered because the agency arranged it. Ask who pays for it before treating the package total as complete.

Keep the supplier's agreement aligned with the approval

Once the internal decision is complete, send the authorised supplier instruction through your agreed route. Identify the buying business, event, accepted scope, complete price, payment terms and relevant quote version. Where your process uses a purchase order, include its reference and make clear how it relates to any signed contract.

Ask the supplier to confirm the same arrangement. If its order acknowledgement adds charges or different terms, resolve the difference before treating the booking as settled. An internal approval for one scope doesn't make a supplier's different scope correct. Keep the agreed version where the event team and finance can find it.

Explain how later requests will work. Name the person authorised to request a change, who confirms the price and who gives the final instruction. This helps the supplier respond when somebody onsite asks for more equipment without knowing whether the request has financial approval.

Consider the messages you send while waiting. "We're happy with this, just waiting for the director" can sound more definite than you intend. Say whether you are requesting information, seeking a temporary hold under stated terms, or placing an order. Don't use uncertain internal approval as a reason to give the supplier an unclear commercial instruction.

Record any condition that remains open, such as the final meal quantity or confirmed access schedule. Give it an owner and deadline. A booking can have settled terms while a quantity still needs final confirmation, but the team must know what it has authorised in the meantime and what could change the total.

When several versions exist, label the current instruction and keep earlier ones as history. Don't delete a previous quote simply to make the folder look tidy. The old version may explain the deposit, a removed service or a later dispute. The person checking the invoice should be able to follow the sequence without guessing which attachment was accepted.

Reapprove changes against the full order

After Eastbank approves the $5,800 production purchase, its programme changes. The supplier quotes another $1,200 for the required additional work. The revised order would total $7,000. That full value belongs in the change request, alongside the $1,200 increase, so the approver can see both the decision now and the booking it creates.

Under Eastbank's example authority rules, the director reviews this request. The event manager can't approve it as a fresh small order, and the original director approval doesn't automatically cover any later addition. The request explains the new work, why it's needed, the effect of declining it and any consequences for other suppliers.

If the director approves and the supplier accepts the revised instruction, Eastbank's agreed purchases become $41,000. Remaining necessary unplaced work stays at $4,500, so expected costs become $45,500. Keeping the separate $3,000 reserve leaves $1,500 available below the $50,000 ceiling. The team updates the order and the event forecast together.

Columbia University's change request policy illustrates how a purchasing system distinguishes modifications to an issued order from work requiring a new order. Its specific rules belong to the university. For your event, define which changes need renewed approval and preserve the relationship to the original booking, rather than treating every addition as unrelated spending.

Check the complete effect of the change. Extending the programme may also extend venue access, cleaning and crew meals. Show those consequences before approval, or state what remains uncertain and how further authority will be obtained. Approval of the performance extension alone shouldn't quietly authorise everything that follows.

Our guide to resolving supplier scope changes develops the supplier negotiation itself. Here, you need to establish who can approve the revised commitment and make the updated total visible to the other buyers. If everyone waits for the invoice, they may keep approving purchases against money you've already agreed to spend.

Check cash before accepting the payment terms

A purchase can fit the event's spending ceiling and still create a payment problem. Before accepting it, check when each payment becomes due and whether the business expects usable cash at that time. A final cost allowance doesn't prove the deposit can leave the bank this afternoon.

For a separate cash illustration, suppose Eastbank has $9,000 available immediately before a deposit deadline. Other confirmed payments due first total $8,000. That leaves $1,000 for the $1,740 production deposit, producing a $740 shortage on these isolated assumptions. This is an alternative timing example, not a change to the purchase totals above. The purchase may fit the cost forecast while its proposed timing doesn't fit the cash available.

The director needs a confirmed response before accepting those terms. That might be an agreed payment change or another legitimate source of funds. An expected ticket payout should use its confirmed timing and conditions. Don't quietly assume a supplier will accept late payment after you have already promised the original date.

Keep this check connected to your event cash-flow forecast. Include the whole business's relevant commitments if several events share the same funds. A deposit that looks manageable inside one event can compete with the venue balance for another event happening that week.

In Loopyah's event CRM, ticket, door and sponsor sales, refunds, fees, promoter payments and AI Ads Manager spend feed into the finance view. You can add event costs or copy them from a previous event to review projected profit and break even ticket sales. Cash is shown separately from profit.

Use those connected inputs for the financial review, then have the responsible person confirm the new supplier scope and approved total. A cost copied from the last event won't establish what this supplier has agreed today. Keep the purchase approval evidence in the records your business uses, and update the cost when the agreement changes.

Create an urgent route before build day

Something will occasionally need a fast answer. A failed item may need replacing, a supplier may be unable to deliver, or an unexpected venue requirement may appear during setup. The useful response is a shorter route with a reachable decision-maker and clear limits, agreed before the event gets busy.

Name the onsite person who can request an urgent purchase, the approver and the backup. State the circumstances covered and the maximum commitment they can authorise. The limit should cover the whole purchase, including delivery and other necessary charges, rather than the smallest amount needed to start the conversation.

An urgent request still needs the supplier, proposed work, complete amount, reason, available alternative and latest decision time. The approver needs the current committed total and forecast. If access to the system fails, agree how the decision will be recorded and communicated, then restore the shared record as soon as practical.

For Eastbank, imagine a necessary replacement service costs $600. The original $4,500 of unplaced work included a $450 estimate for that service. The appropriate approver confirms the replacement and the order is issued. Commitments rise from $41,000 to $41,600, while remaining unplaced work falls to $4,050. Expected costs become $45,650, an increase of $150.

With the $3,000 reserve retained, Eastbank now has $1,350 below its spending ceiling. Recording the $600 purchase without removing the $450 estimate would overstate expected costs. Removing the estimate without recording the order would understate them. The short urgent route still needs that connection.

Financial approval doesn't decide whether equipment is safe, whether a venue can open or whether an activity should continue. Use the event's established incident and operational decision procedures for those questions, with qualified people where required. The purchase record captures the financial decision made within that response.

Don't make bank verification disappear because the request is urgent. The FBI's Internet Crime Complaint Center advises verifying account changes through another channel. Keep that verification separate from approving the purchase, use an independently established contact route, and store sensitive payment information in the appropriate restricted records. A genuine need for replacement equipment doesn't authenticate a new bank account.

Deal with purchases made before approval honestly

If someone has already told a supplier to proceed, record the facts immediately. Identify what was said, by whom, when, and what the supplier has done in response. Preserve the quote, messages and evidence of work. Don't backdate an approval to make it appear that the normal process happened.

Give the issue to the person authorised to resolve it. They need to understand the possible commitment, whether further work can be paused, and the commercial or legal options available. Your internal lack of approval doesn't by itself establish that the supplier has no right to payment. Get specific advice when the obligation is disputed.

Keep the likely cost visible in the forecast while it is investigated. Mark it as awaiting a decision so recording the amount doesn't look like routine approval. If the team intends to continue with the work, resolve who can authorise that next step and send the supplier one clear instruction. Silence leaves both sides making assumptions.

Also distinguish approval from reimbursement. A staff member paying personally doesn't make the purchase cheaper or automatically authorised. Establish what was bought, for which business, under what instruction, and whether reimbursement is due under your arrangements. Link the receipt and any reimbursement to the original purchase so the cost isn't recorded twice.

After resolving the immediate issue, ask why the route was bypassed. Was the decision-maker unreachable? Did the requester think budget access gave them buying authority? Did a supplier interpret an availability check as an order? Fix the specific misunderstanding and tell the people involved what changes next time.

Repeated exceptions deserve a different response from a one-off mistake. If the same department regularly starts work before approval, review its access, authority and planning deadlines. A policy that records every breach afterwards without changing the behaviour isn't controlling commitments before they happen.

Keep commitments current through delivery and closure

The record needs an owner after the order is placed. They track the delivery, approved changes, invoices and remaining work, and they ask the supplier about anything unclear. An approved purchase left untouched for months can become as misleading as an unrecorded one when quantities or dates change.

When invoices arrive, compare them with the current agreement and evidence for the payment condition. Don't add the invoice total to the full order total as though it were another purchase. Show how much has been invoiced and paid against the existing commitment, and investigate differences before deciding what happens next.

The invoice approval workflow handles that later stage, including duplicate checks and payment responsibility. Your purchase record gives it the earlier evidence: what the business authorised, which supplier instruction was current and what changed. The invoice shouldn't be the first reliable account of the booking.

Close unused amounts carefully. If the final service costs less, confirm the supplier's final position and any outstanding charges before releasing the difference. An internal order balance isn't automatically a saving. There may still be an uninvoiced delivery charge, a disputed change or a contractual minimum to resolve.

Keep cancelled purchases as history with the agreed cancellation terms and final amount. If a deposit is awaiting return, record the expected recovery separately from money actually received. Cancelling future work may reduce expected costs while a refund remains uncertain or arrives much later. The cash forecast needs to reflect that distinction.

For a recurring event series, link shared orders to the events they serve. The total commitment should appear once for the paying business, with allocations that add up to it. Event managers need their relevant costs, but each manager shouldn't treat the complete shared order as a separate booking they can change independently.

Start with the orders people are about to place

You don't need to reconstruct every historic purchase before improving the next decision. Start with current commitments and the requests most likely to become orders this week. Ask the relevant buyers to confirm the accepted scope, full amount, payments already made and work still expected. Resolve missing information before approving optional additions.

Then walk one ordinary request and one urgent request through the process without placing a test order. Can the requester identify the complete purchase? Can the approver see the position after saying yes? Does the supplier instruction match the decision? Can the backup find the same information when the usual owner is unavailable?

Use what those walkthroughs reveal to simplify the route. Remove duplicate data entry, give staff the access they need and make the approval contact easy to find. If people must ask three colleagues where to submit a request, the process will struggle when setup is running late.

At Eastbank, the next optional proposal is a $1,800 addition. After the approved production change and urgent replacement, only $1,350 remains below the spending ceiling while retaining the separate $3,000 reserve. The director can see immediately that the proposal needs a confirmed offsetting reduction, an explicit change to the reserve or ceiling, or a decision to decline it. The current purchase authority alone doesn't make the money available.

That decision belongs before the supplier is told to begin. Take your next real purchase request and ask the approver to identify the complete commitment and the event's remaining spending room from the record. If either answer depends on an invoice nobody has received, add the missing agreement now, while you can still choose what happens next.