Film and TV productions can reduce payment-fraud risk by verifying vendors and bank changes through an independent channel, separating invoice approval from payment release, and keeping a review trail from prep through wrap. The controls need to fit a production’s fast-changing departments, locations, crew lists, and vendor roster.

Where payment fraud enters a production

A production may engage hundreds of vendors and temporary workers while locations, departments, and payment deadlines change. That operating model creates several points where a fraudster can exploit urgency or incomplete handoffs:

  • Invoice manipulation: a legitimate invoice is copied or intercepted and returned with altered bank details.
  • Vendor impersonation: a fake company or lookalike contact submits an invoice for work never performed.
  • Duplicate or inflated billing: a supplier bills twice, exceeds an agreed rate, or charges for quantities not received.
  • Ghost crew or per-diem fraud: a nonexistent, duplicate, or unauthorized person is added to a crew or allowance list.
  • Urgent payment-change requests: a message claims that a vendor’s account, payee name, or remittance instructions must change immediately.

The last category overlaps with the broader impersonation and business-email-compromise pattern covered in AI impersonation and payment-change verification. This article keeps the production controls in view: who verifies the payee, which department owns the spend, and what evidence is retained before funds are released.

Why film and TV workflows need production-specific controls

Fast onboarding across departments and locations

A production may add a local equipment house, caterer, transport provider, location supplier, or post-production specialist with little lead time. Record the legal/payee name, tax details where applicable, agreed scope, approved contact, and payment destination before the first payment. A new vendor should not be treated as trusted solely because the request came from a familiar department.

Temporary teams and changing authority

Crew and production-office roles can change between prep, shoot, post, and wrap. Maintain a current approval matrix by department and amount, and remove access when a person leaves the production. A production accountant or finance lead should be able to explain who requested, approved, and released each payment.

Pressure to keep the shoot moving

A last-minute location move or equipment issue can make an urgent payment appear unavoidable. Use an exception path with a second approver and independent callback rather than allowing urgency to bypass controls. If a request cannot be verified, pause the payment and escalate it; a schedule concern is not independent evidence of a payee change.

Split responsibilities across production and finance

Department heads know whether goods or services were received; production finance knows the payment record; an authorized approver owns release. Keeping those responsibilities distinct makes it easier to challenge a plausible but false invoice.

A control sequence from prep through wrap

1. Establish the vendor record before payment

Collect the vendor’s legal/payee name, approved contact, service description, tax documentation required by the production, and bank or payment details through a controlled intake process. Compare the record with the contract, purchase order, deal memo, or department request. For a high-value or unfamiliar vendor, independently verify the business and contact details using a known source—not only the email or phone number on the invoice.

Do not assume that a tax-ID check, business-registration check, or micro-deposit proves that the person requesting payment is authorized. These are possible checks, not substitutes for ownership, scope, and contact verification.

2. Match the invoice to production evidence

The department receiving the service should confirm the work, dates, quantities, and rate. Finance can then compare the invoice against the approved vendor record and supporting documents. Useful evidence may include a purchase order, call sheet or delivery record, approved rate card, rental agreement, time record, or department sign-off. Mark exceptions explicitly instead of relying on memory during a busy shoot.

3. Treat every payment-detail change as a new risk event

A bank-account or remittance change should trigger a hold, a second-person review, and a callback to a previously known contact or another independently sourced number. Do not use the contact details supplied in the change request as the only verification channel. Record the old and new details, who confirmed them, when confirmation occurred, and who approved release.

4. Separate entry, approval, and release

Use different people or roles for invoice entry, business approval, and payment execution where staffing permits. Set an additional approval threshold for new vendors, changed bank details, unusual amounts, rush payments, and exceptions. A system workflow can document these handoffs, but it does not replace a person’s responsibility to validate the underlying transaction.

5. Reconcile crew, per-diem, and card activity

Before issuing a per-diem payment or card, compare the recipient with the authorized crew or contractor record and the relevant dates, location, and allowance policy. Reconcile issued amounts, returns, cancellations, and transactions to the production’s records. For controlled spending, EvedPay Card or another virtual-card program may provide limits and transaction visibility when configured for the production; card controls do not validate a fake vendor or prove that a charge was business-related.

6. Review exceptions during the shoot

Run a focused review of new vendors, payment-detail changes, duplicate invoice numbers, unusual rate or quantity changes, payments outside normal channels, and repeated rush requests. Anomaly flags should prompt human review, not automatic rejection or automatic approval. Keep an audit trail that identifies the decision and the evidence considered.

7. Close the loop at wrap

At wrap, reconcile open purchase orders, deposits, advances, card balances, per-diem lists, credits, and final invoices. Confirm that unused access and cards are closed or restricted, departing staff no longer approve or release payments, and unresolved vendor exceptions have an owner. A wrap review can surface a duplicate or unauthorized payment that was hard to see while production was moving.

Practical approval checklist

Before releasing a production payment, ask:

  1. Is the payee an approved vendor or authorized crew/contractor recipient?
  2. Does the invoice match the agreed scope, rate, dates, and evidence of delivery?
  3. Has any bank, payee, or remittance change been independently verified?
  4. Are the requester, approver, and payment releaser distinct enough for this transaction?
  5. Is this a rush, new-vendor, duplicate, unusual, or exception payment requiring escalation?
  6. Are the decision, evidence, and final payment destination recorded for later reconciliation?

Where the related fraud guides fit

For a production, start here: the controls above connect vendor onboarding, department evidence, payment-change verification, crew and per-diem reconciliation, and wrap. Practical event vendor fraud controls addresses event setup and on-site vendor pressure, so it is a useful comparison but not a substitute for film-production department and wrap controls. AI impersonation and payment-change verification focuses on impersonation, forged requests, and known-channel verification; it explains the attack pattern, while this guide applies verification to a production payment workflow.

For related payment workflow context, see EvedPay, Eved AP, Eved, and the entertainment industry overview. Product capabilities and configuration should be confirmed for the production’s current plan and workflow; no payment tool removes the need for independent verification and human review.

How to evaluate a payment-control platform

When assessing an AP or production-payments platform, ask whether it can support the controls that matter to your workflow: controlled vendor onboarding, configurable approval separation, payment-detail change review, role-based access, transaction-level records, exception reporting, and exportable reconciliation evidence. Eved describes payment and AP products that may support parts of this workflow, including Eved AP and EvedPay; verify current features, integrations, and operating responsibilities before relying on any specific control.

Key takeaways

  • Design around production stages: prep, shoot, post, and wrap have different vendors, approvers, and evidence.
  • Verify the payee independently: especially for new vendors and every payment-detail change.
  • Separate duties: invoice entry, business approval, and payment release should not depend on one person where practical.
  • Reconcile temporary populations: crew, per-diem recipients, cards, advances, and departing users need explicit closeout.
  • Use tools as control support: workflows, anomaly flags, audit trails, and card limits help, but human review and independent verification remain essential.
  • Keep the related guidance distinct: event controls are about event setup and on-site pressure; AI-fraud guidance is about impersonation and forged requests.

For product information, visit Eved or contact Eved.

Editorial reference

The original article also listed EvedPay, Eved AP, EvedPay Card, and Eved as related product context; those destinations are retained above rather than silently removed.