How do you stop duplicate supplier payments at your event?

Your production manager has approved the sound company's invoice. Your bookkeeper has put it in the next payment run. Then the supplier calls you during load-in because the money hasn't arrived, and you pay it from your phone. Everyone was trying to keep the event moving. The supplier may now receive the money twice.

To prevent duplicate supplier payments, give each bill one shared record, separate approval from payment, and make one named person responsible for releasing it. That person checks existing payments and anything already scheduled before sending money, then records the bank result immediately. A reminder or forwarded copy goes back to the same record.

The interesting part is that two people can follow what they believe is the right process and still create the duplicate. Your production manager knows the work happened. Your bookkeeper knows the bill was approved. Neither necessarily knows that you paid it while standing outside the venue. Your event invoice approval workflow has to account for that moment.

This guide explains how to set up that workflow without turning every supplier bill into a meeting. We'll cover who checks what, deposits and corrected invoices, payments that appear stuck, and the handover when someone else takes over. There's a copyable record and a worked example for an event business running two paid shows.

Start with one bill and one payment record

The first thing you want to do is decide where a supplier invoice becomes an instruction your business can act on. It might arrive by email, through a supplier portal or as a document handed to the production manager. Those are ways of receiving the bill. They shouldn't become separate queues of people who can pay it.

Choose a standard submission route and tell your suppliers about it when booking. If they send invoices to your accounts address, ask event leads to forward anything received elsewhere to that address. The forward should include the event or booking reference and any useful delivery information. It doesn't need to say "please pay urgently" unless someone has actually checked the deadline.

Create one record for the invoice in your accounting system or payment register. Attach the original document, preserve the supplier's reference and give the record an internal reference your team can use in conversations. Every later copy, query and approval should refer to that same record. A supplier sending the PDF again hasn't necessarily supplied anything new.

The US Treasury's disbursement guidance for federal entities specifically highlights duplicate copies, submissions to multiple locations and adjusted invoices as situations needing attention. Its requirements apply to federal entities. For an event business, the useful warning is how easily several documents can refer to the same payment obligation.

Say your lighting supplier emails the producer on Monday and your accounts inbox on Tuesday. On Wednesday it sends you a statement listing the unpaid bill. Record the statement against the existing invoice and investigate its status. Don't approve the statement total as another bill while the invoice is already waiting for payment.

If your accounting system already collects invoices and routes approvals, use that process. A separate spreadsheet maintained by the event team can create another version of the payment status. The event team needs a way to provide delivery evidence and see the next action, with financial details restricted to the people who need them.

Give approval and payment different meanings

"Approved" is a surprisingly vague word. Your venue manager may mean the delivery was correct. Your event director may mean the cost fits the agreement. Your bookkeeper may interpret it as permission to send money now. Write down the question each person is answering so an enthusiastic reply doesn't become authority it was never meant to carry.

Start with the person who commissioned the work. They identify the accepted quote, contract or purchase order and any approved changes. Then the person responsible for delivery confirms the relevant work or payment trigger. For a deposit, that trigger may be a booking commitment before delivery. Don't ask someone to confirm receipt of equipment that hasn't arrived yet.

The financial approver checks the amount being authorised, the agreed terms and any unresolved issue. The person releasing payment checks the approved record, payee details, payment history and bank instructions. You may combine some administrative tasks in a small business, but make the approval decision and the act of moving money separately visible.

The Charity Commission's internal financial controls guidance, for charities in England and Wales, recommends written authority limits and checking invoices against orders and receipt of the goods or services. These are useful checks to adapt to a commercial event's circumstances, rather than a claim that charity rules apply to every promoter.

An example approval could say that the invoice matches the accepted production booking, the named production lead confirmed the agreed preparation stage, and the remaining amount is authorised for the scheduled payment date. That gives the payer something specific to check. A thumbs-up on a forwarded attachment doesn't explain which amount, document or stage was reviewed.

Use named backups as well. If your director is at another show, the team should know who can approve within the agreed authority and who can release payment. The backup receives responsibility through an explicit handover. They don't start paying bills simply because they have access and assume everyone else is busy.

Check for duplicates across the whole event business

An event code is useful for allocating costs, but it's a poor boundary for checking duplicates. The same supplier can work across several shows, and one invoice can cover more than one event. If each event manager only searches their own budget, both might approve the full document because it includes work for their event.

Search across the paying business's supplier records and payment history. Start with supplier identity and invoice number, then compare amount, currency, service dates, booking references and the work described. Include pending payments, scheduled bank instructions, card transactions and any authorised payments someone made outside the usual run. A search of completed bank transfers alone leaves a lot unexamined.

Preserve the invoice number exactly as supplied. If your software also supports a standard comparison format, use it to flag variations in spaces or punctuation for review. Don't alter the stored reference or add a character just to get past a duplicate warning. That makes the warning disappear without resolving the underlying question.

A matching amount isn't proof of duplication. A security company may legitimately charge the same agreed sum for two different shows. Equally, a different invoice number isn't proof of new work. A corrected bill might carry a new reference for the same equipment hire. Compare what the business owes, rather than relying on a single field.

Watch for duplicate supplier profiles too. The trading name on a quote may differ from the legal name on the invoice. Before creating another supplier, check the existing record and resolve the identity with reliable documents. Changes to identity or bank details need their own verification; familiarity with the brand doesn't settle either question.

For a bill covering several events, record the total payable once and allocate its cost between the events. The managers approve their relevant portions or delivery evidence within that record. They don't each create a full payment instruction. If separate legal businesses are paying different portions, confirm the invoicing and responsibility with your accountant and supplier before treating that as an ordinary internal allocation.

Make the current payment status useful

Your team should be able to tell whether money can still be sent without reading every email. Use statuses that describe what actually happened and what remains open. "In progress" won't help the person answering a supplier who says the payment hasn't arrived.

A practical sequence is received, awaiting information, approved for payment, scheduled, submitted to the bank, completed, and matched to the supplier's account. You can adapt the labels to your software. Keep a separate hold or exception reason where needed, and record the next owner and action. A disputed invoice shouldn't look ready simply because the payment date is near.

Define the difference between scheduled and submitted. A scheduled payment may still be waiting for a bank approver or future release date. A submitted payment has entered the bank's process, but its final result may remain unknown. Completed means the bank has confirmed the transaction completed under its terminology. Supplier allocation is a later check that the payment was credited to the intended invoice.

Never turn "unknown" into "unpaid" just to make the register tidy. If a bank screen times out after submission, hold the invoice against another release while the payer checks the transaction history or contacts the bank. The supplier's statement that nothing has arrived can be true while your transfer is still processing.

Before beginning a payment run, the named payer takes responsibility for the selected records and checks for existing instructions. Other authorised people must know those bills are being handled and avoid creating parallel payments. Record the bank batch or transaction reference as soon as available, with the amount, currency, time and result. Keep the status current before moving to the next task.

A shared sheet can show this responsibility, but it doesn't stop two people pressing the bank's payment button. Use your accounting and bank permissions, approval controls and payment history as well. If two people can independently release the same bill, agree who is acting now and require the other to verify that handover before taking over.

Keep deposits, balances and revisions connected

A deposit invoice and a final invoice may both be valid documents for one booking. The problem appears when your team treats each headline total as fresh money to send. Read what each document requests and match it to the contract, previous payments and any credits.

Suppose an invoice shows the total booking value and then deducts the advance already paid. The amount due is the remaining balance, subject to your checks. If the document instead asks for a separate instalment, confirm where that instalment belongs in the agreed schedule. Don't deduct a deposit twice or assume it was deducted when it wasn't.

Your supplier payment schedule should establish the purpose and trigger for each instalment before booking. The approval record then shows which instalment this invoice covers and what has already been paid. It should be possible to follow the booking from the initial advance through the final balance without reconstructing it from bank statements.

When the supplier corrects a bill, link the replacement to the original and explain what changed. Ask whether the original is cancelled, credited or otherwise replaced under the supplier's accounting process. Keep the original for the history and prevent it from remaining payable alongside the replacement. A new attachment should never silently inherit the old approval.

If the amount changes after approval, have the right person approve the revised amount and check any existing payment instruction before release. If money has already been sent, the question becomes how that payment applies to the corrected bill. Sending the replacement total before resolving the earlier transfer can create the duplicate you're trying to avoid.

Partial payments need the same care. Record each payment against the original obligation and show the remaining amount. A bill that is partly paid can't be reduced to a yes-or-no paid flag. If you agree to withhold a disputed portion, record the agreed treatment and obtain appropriate advice about your rights and payment duties. A workflow label doesn't change the contract.

Treat bank-detail changes as a separate decision

You can approve the right invoice and still pay the wrong account. A request to change bank details deserves a verification step before anyone updates the supplier record or releases funds. The request may be genuine, but the invoice approval doesn't prove it.

The FBI's business email compromise guidance recommends verifying changes to payment procedures and account numbers with the person making the request. It also warns against using a phone number supplied in a suspicious message. Contact the supplier through a trusted number you already hold or independently establish, rather than replying within the same email thread.

Record who verified the change, when, who they spoke to and where the verified details are held securely. Let the person checking the payment see that the verification happened. They don't need full account numbers copied into a widely shared event document or chat channel.

This is especially relevant when someone claims the supplier's usual account isn't working and asks you to pay somewhere else to keep the crew onsite. Urgency doesn't answer the identity question. Contact the supplier's authorised finance contact and your own payment approver, then decide what can be confirmed before money moves.

Ask your bank about available payee checks and approval arrangements and understand their limits. A successful name check can be useful information, but it doesn't establish that the invoice is new, that the work was authorised or that another payment isn't already pending. Each check deals with a different possible mistake.

If you suspect money has gone to a fraudulent account, contact your bank immediately and follow its instructions. The FBI also directs US victims to report through its Internet Crime Complaint Center. Use the appropriate reporting route where your business operates, preserve the evidence and don't promise your team that a recall will recover the money.

Copy this invoice approval record

Use the fields below within your existing accounting process. Some will already be stored on the supplier or purchase record, so link to those details rather than making people type them again. The purpose is to let another authorised person understand the bill, the decision and the payment status without guessing. If the supplier document itself is incomplete, our event invoice checklist explains the details to request before proceeding.

Identify the obligation

• Internal record reference and link to the original invoice.

• Paying business and verified supplier record.

• Supplier invoice number, invoice date, currency and due date.

• Booking or order reference, service dates and events covered.

• Invoice total, previous payments, credits and amount currently requested.

• Related deposit, replacement or disputed invoice references.

Record the checks and authority

• Named delivery checker and the evidence for the agreed payment trigger.

• Quote, contract and approved changes used for comparison.

• Duplicate search result across supplier records, payment history and scheduled instructions.

• Named financial approver, exact approved amount and approval date.

• Verified payee record and any separately approved bank-detail change.

• Hold reason, missing information and the person resolving it.

Record the payment and next action

• Current status, responsible payer and named backup.

• Intended payment date and any supplier receipt deadline.

• Bank batch or transaction reference, amount, currency and submission time.

• Final bank result, checked by whom and when.

• Supplier allocation confirmation or outstanding query.

• Next action, owner and follow-up time where the record remains open.

Australian Government guidance on what to include in an invoice recommends clear references, descriptions and payment details to make tracking easier. That page also covers Australian invoice requirements. Your approval record is an internal working record, so it complements the supplier document and your accountant's local requirements rather than replacing either.

Keep the approval history when someone corrects a field. The next person needs to know why an amount changed or a payment was held. If your system records revisions automatically, use that history. If it doesn't, leave a dated explanation with the supporting document and make clear which version is current.

Work through a corrected invoice for two paid shows

Let's use a fictional event business, Riverworks Live, which has booked Northline Production for two ticketed concerts. Every name, reference, amount and time in this example is invented to explain the process. All amounts are USD and include every supplier charge relevant to the example. They aren't supplier rates or a recommended payment schedule.

The accepted booking is $9,600 across the two shows. Riverworks has already paid a $2,400 deposit against invoice NL-401, recorded as AP-0194. The supplier later issues NL-488 showing the $9,600 booking total, the $2,400 deposit and a $7,200 balance due. The agreed balance becomes payable once the equipment schedule and crew plan are accepted, before onsite delivery. It is due on Wednesday 9 December 2026, before the shows that Friday and Saturday.

Maya, the production lead, checks the bill and spots a $600 charge for equipment the supplier agreed to remove. She attaches the approved change and asks for a corrected invoice. Lee, the bookkeeper, records NL-488 under AP-0267 and puts it on hold. It isn't added to a payment batch while the supplier resolves the amount.

Northline then issues NL-488R with a revised booking total of $9,000, less the same $2,400 deposit, leaving $6,600 due. It confirms that the replacement supersedes NL-488. Lee keeps both documents within AP-0267, records why the original cannot be paid, and checks the deposit against the actual completed transaction. The earlier $2,400 hasn't become payable again.

The two shows receive cost allocations of $5,400 and $3,600. Those amounts add to the revised $9,000 booking. For this example, Riverworks allocates $1,440 of the paid deposit to the first show and $960 to the second, leaving their final portions at $3,960 and $2,640. Together, those portions make the one $6,600 payment.

Maya accepts the revised equipment schedule and crew plan and records that the agreed payment trigger has been met. Sam, the financial approver, authorises $6,600 against the replacement invoice. Lee checks other supplier records, payments and scheduled bank instructions before preparing the transfer. The event managers can see their allocated costs, but neither receives an independent instruction to pay the complete invoice.

Follow the payment through the bank

On Tuesday 8 December, Lee takes responsibility for paying AP-0267 and records that the payment is being prepared. Sam checks the bank instruction under Riverworks' approval arrangement. The $6,600 transfer is submitted at 14:10. Lee records the transaction reference and marks the result as awaiting confirmation, so the invoice can't be treated as available for another release.

At 14:20, Northline calls Maya because its accounts team still sees an unpaid balance. Maya checks AP-0267 and sees the submitted transfer. She gives the supplier the relevant payment reference through the agreed contact route and asks Lee to investigate the status. She doesn't pay from her phone to settle the conversation.

At 14:30, Lee verifies that the bank reports the transfer completed and updates the record. At 15:05, Northline confirms that it has received and allocated the $6,600 to the replacement invoice. Lee records the confirmation. The bank result and the supplier's allocation are separate pieces of evidence, and both are now available to the team.

On Wednesday morning, an automated reminder for the original NL-488 reaches Sam. He finds its replacement link and completed payment record, then asks Northline to correct its outstanding list. He doesn't authorise $7,200 because that amount appeared on the earlier bill, and he doesn't send another $6,600 because the reminder arrived after approval.

The main prevention happened before the reminder. The original invoice was held, the replacement was linked, and everyone could see that Lee had already submitted the payment. Asking staff to be more careful would have left each person trying to remember what someone else might have done.

Separate the cost of the work from the cash movement

A duplicate payment creates a cash problem immediately, even while you work out how it should be treated in the accounts. It doesn't mean the supplier delivered twice as much production. Keep the booking cost, actual payments and any recovery claim separately understandable, then let your accountant determine the correct accounting entries.

In the Riverworks example, the revised supplier booking costs $9,000. The deposit and final payment together equal that amount. If the business had $11,800 available in its bank account immediately before the final transfer, paying $6,600 would leave $5,200. Sending the same amount again would take that isolated example balance to minus $1,400, before other transactions or bank restrictions.

Those figures explain exposure, not a guaranteed banking outcome. The bank might reject the extra payment or an overdraft might be available on particular terms. Either way, a recoverable overpayment can't fund tomorrow's venue charge while the supplier still holds it. Don't treat an expected refund as cash already returned.

Update the approved cost in your event budget and forecast when the supplier agrees a genuine price change. Update the cash record when money moves or a payment date changes. Keeping those questions separate helps you avoid overstating event costs while also overlooking a serious shortage in the bank.

Your event cash-flow forecast should use expected receipts and payments with their actual timing. With Loopyah ticketing, you can track ticket sales and receive payouts. Use your sales records and confirmed payout details to plan the income side, then check available funds in the bank before releasing supplier payments. A ticket sale or expected payout doesn't establish that the cash is available now.

Bring any recovery into that forecast cautiously. Record the supplier's commitment and expected return date, then update it when the bank confirms receipt. If other bills become difficult to meet, speak to the relevant suppliers before their deadlines. You need an agreed response to the shortage, rather than a forecast that assumes the missing money will reappear in time.

Deal with urgent payments before the venue gets busy

An event business needs a way to make a legitimate urgent payment. A replacement vehicle or approved production change may have to be paid before the next routine run. The answer is a shorter documented route with the same essential checks and a clearly available decision-maker.

Agree that route before build day. Name who can request the payment, who approves it, who releases it and who covers each role. State the authority limits and what happens when the usual approver can't be reached. Your event team briefing should tell onsite leads where to send the request and whom to call if the deadline is immediate.

The urgent request should identify the supplier, work, amount, reason for urgency and latest decision time. The payer still checks whether an invoice or payment instruction already exists. If the invoice hasn't arrived, determine what evidence and authorisation your business requires for that exceptional payment, then link the eventual invoice to the transaction. Its later arrival mustn't restart payment.

For a corporate card purchase, record which bill or purchase the card transaction settles. When the supplier later sends the invoice, match it to that transaction. The invoice may be needed for your records even though no further money is due. The same applies when an authorised staff member pays personally and requests reimbursement. Resolve who has been paid and who is now owed money.

Don't route an uncertain bank transfer through a card as a quick workaround. First establish whether the transfer failed, completed or remains unresolved. If the original cannot be stopped or verified in time, escalate the commercial decision to someone with authority to assess the exposure. Any exceptional decision needs its reason and follow-up recorded, including how a possible overpayment will be managed.

After the urgent payment, update the shared record before the next person starts the normal run. An instruction to "tell accounts later" is easy to lose during a show. If connectivity prevents access to the record, keep payment responsibility with one named person, contact the relevant team directly, and restore the record promptly. Don't let several people continue independently from disconnected lists.

Make the workflow work for a small team

If you're the founder, producer and person who usually pays the bills, an elaborate chain of approvals won't survive the week. Start with the mistake you're trying to prevent. A second person needs enough information to challenge the supplier, amount and payment history before money goes out, and your records need to show what happened afterwards.

That person might be a co-director, authorised colleague or external bookkeeper with an agreed review role. Be specific about what they can approve and what they can see. A bookkeeper preparing the figures isn't automatically responsible for confirming that the supplier delivered the agreed equipment. You still need the event lead's evidence for that decision.

The Australian Charities and Not-for-profits Commission's financial controls guidance recommends involving more than one person in authorising and completing transactions, with clear authority limits. It addresses charities. A small commercial event business can discuss a proportionate arrangement with its accountant and bank based on who is actually available.

If you're temporarily operating alone, acknowledge the limitation instead of inventing a second approval with your own initials. Use the checks your bank and accounting system support, restrict payment access and arrange an independent review as soon as practical. A later review can catch an error, but it doesn't provide the same protection as someone checking before payment.

Keep the routine predictable. Set payment review times that fit your agreed supplier terms and banking deadlines. Suppliers should know where to ask about a bill and when you'll respond. A reliable answer reduces the chance that they contact several event managers because nobody can tell them whether their invoice is being handled.

Before anyone takes leave, review open invoices together. Confirm which are awaiting information, approved, scheduled or already submitted, and identify unresolved bank results. The replacement payer accepts responsibility for named records and checks the bank before acting. Access to the account alone doesn't tell them which payments the previous person has already started.

Reconcile supplier statements without paying the total again

A supplier statement is useful because it shows what the supplier believes is still outstanding. Read it as a request to compare accounts. The balance may include invoices you haven't received, payments the supplier hasn't allocated, or documents that should have been replaced. Sending the statement total without checking those items can pay old charges again.

Work through it invoice by invoice. Match each line to your own record and confirm its status. For a completed payment still listed as unpaid, send the relevant remittance information through the verified contact route and ask the supplier to check its allocation. For an invoice you don't recognise, obtain the document and identify the booking before seeking approval.

Ask about credits as well. If a supplier agreed to reduce a charge, check that the adjustment appears in both businesses' records and that you understand which invoice it changes. Don't subtract an unexplained credit from a different bill just because the arithmetic produces a convenient total. Confirm the treatment with the supplier and whoever maintains your accounts.

If the statement combines several events, keep the individual invoice references visible in the reconciliation. You may make one authorised bank transfer covering several approved bills if your process allows it, but specify exactly how the amount should be allocated. The transfer total and its invoice breakdown need to agree, with no invoice left available for a separate release.

This check also catches bills that are genuinely overdue. A duplicate-payment process shouldn't become a reason to leave a supplier waiting while everyone points at someone else. If the work and amount are correct but approval is stuck, identify the missing decision and contact the authorised person. Tell the supplier when you'll respond and meet the agreed payment terms or discuss the problem promptly.

Hand over the payer's work, including unfinished transfers

A good handover includes what the outgoing person has started, not only a list of bills still marked unpaid. Before taking over, the replacement payer checks the approved records against bank instructions awaiting approval, future-dated payments and transactions with unresolved results. They need to know what could still move without another action from them.

The Riverworks example could go wrong earlier, too. Suppose Lee has prepared the transfer but Sam hasn't yet approved it in the bank. Another colleague sees the supplier reminder and an invoice that isn't marked completed. If they create a fresh transfer, the bank can now contain two instructions waiting for approval. The handover should identify the existing instruction and who is responsible for completing or cancelling it.

Record when responsibility changes and for which invoices. The outgoing payer stops acting on those records, and the replacement confirms that they've checked the bank and accepted the work. If responsibility returns later, repeat that exchange. Both people having access is convenient for cover, but it isn't a substitute for agreeing who will act.

Include supplier conversations that haven't produced a result. A promise to resend bank details, a request to stop a transfer and a disputed allocation all need an owner. Keep the next action attached to the existing invoice record. Otherwise the new payer may treat silence as permission to start again, even though the previous person was already investigating.

Choose software that supports the actual checks

The right system should make the normal route easier than paying from an email attachment. Start by showing your accountant or software provider the situations that cause trouble for your team. Ask how the system handles a resent invoice, a supplier with two profiles, a payment pending bank approval and a replacement document after a deposit.

Look for clear supplier records, duplicate warnings, approval history, controlled payment access and links between invoices, credits and transactions. Understand which information updates automatically and which depends on someone recording an action. If a bank payment appears in the accounting system only later, the team needs a way to see that it's already been submitted during the gap.

Ask what happens when two users act at once. Does the software stop both from creating payment instructions for the same balance, warn them, or simply allow both? Check the bank's role as well. A purchase approval inside the accounting system doesn't necessarily prevent someone with banking access from making another transfer separately.

Try ordinary cases before relying on the setup for a busy event week. Enter a copy of an existing invoice, a different invoice for another event at the same amount, and a corrected balance following a deposit. Check that a real duplicate receives attention and that a legitimate repeat booking can be approved with an explanation. Use a test environment or review process that won't release actual money.

Be careful with promises about automation. Reading a PDF and extracting its amount doesn't prove the charge was authorised or remains unpaid. Your system can help people find and compare records, while the business still has to define the approval evidence, exception decisions and payment authority. Ask the provider to demonstrate those decisions with your examples.

Once the process works, remove redundant lists and instructions. People will keep using an old payment sheet if it still appears to be the fastest way to get something done. Explain the new route, check that suppliers have the right address, and make sure the onsite team can find the payment owner without searching through an old group chat.

Recover a duplicate without hiding what happened

If you discover a possible duplicate, first establish the facts. Compare the invoices, bank transactions, amounts and supplier allocation. One entry may be a scheduled instruction that can still be cancelled, or two documents may describe a legitimate split payment. Pause further action on the affected bill while the authorised payer checks.

If two payments were completed for the same obligation, contact the supplier's verified finance contact with the references and request a return or an explicitly agreed treatment. Contact your bank promptly about any available action, especially where fraud is suspected. Don't assume a bank reversal is possible or that a supplier credit will solve an immediate cash shortage.

Record the amount to recover, the person following up and the agreed next date. A credit against future work is a different commercial outcome from money returned to the bank. Decide whether it fits your business, confirm it in writing and have the accounting treatment checked. Don't silently use the next event's budget to make the current event appear settled.

Keep the original payment history. Deleting the second transaction from a register may make the list look better, but it removes the information needed to recover the money and explain the cash position. Mark the recovery status and attach the evidence when the money returns or another treatment is agreed.

Then trace the duplicate back to the decision that allowed it. Did two event managers submit the same invoice? Did someone pay an urgent request without checking the scheduled batch? Did a corrected document remain payable beside its original? Fix that specific point and check other invoices exposed to the same problem. A general reminder to be careful won't tell staff what to do differently.

Before your next payment run, take one supplier with both an advance and an outstanding balance. Ask another authorised person to follow the record and explain what is approved, what has already moved and who is allowed to act next. If they have to call you to find out whether you paid it from your phone, correct that record and the handover before anyone sends more money.