Film and TV production AP needs a workflow that connects the budget to each invoice, routes spend to the right department approver, and leaves a usable record at wrap. This guide explains how to set up production and cost structures, code invoices, handle exceptions, approve spend, hand off payments, and close the books without losing project context.
A production may start quickly, use a temporary vendor network, spend across departments and locations, and close on a fixed schedule. The AP process therefore has to support production pace while preserving budget control, payment security, and an audit trail. If you are comparing platforms at an executive level, see our separate guide to what event and production CFOs should demand from a payment platform.
For a broader introduction to automation across entertainment and events, start with the general AP automation guide for events and entertainment. This article stays narrower: the production invoice workflow from budget setup through wrap.
What a film and TV AP workflow must keep connected
Production AP is more than scanning an invoice. Each transaction needs enough context for a production accountant and department owner to answer four questions:
- Which production and department owns the spend?
- Which budget line, cost code, purchase order, or commitment should it use?
- Who confirms receipt and who approves the financial impact?
- What happened after approval, and can the team find it at wrap?
The vendor population also changes by project. Locations, equipment houses, transportation providers, caterers, fabricators, and post-production suppliers may work on one production and return months later. A repeatable workflow can reuse an existing vendor record while still applying the current production’s terms, coding, and approval rules.
Step 1: Set up the production budget and departments
Before the first invoice arrives, define the production entity or project, budget structure, departments, cost codes, approval thresholds, and accounting handoff. Typical department examples include locations, camera and lighting, art, transportation, wardrobe, post-production, and office operations. The exact structure should follow the production’s accounting design rather than a generic corporate chart of accounts.
This setup turns the budget into routing logic. A location invoice can go to the location owner; an equipment invoice can go to the department responsible for the commitment; and production finance can review coding and budget impact. Document who may approve, what evidence is required, and when a transaction needs escalation.
Step 2: Onboard vendors for the current production
Production teams should collect business, tax, and banking information through a protected intake process instead of asking vendors to send sensitive details through ordinary email. Keep the record tied to the vendor and the production so finance can distinguish a verified repeat vendor from a new or changed payee.
Onboarding is not the same as approving an invoice. The vendor record supports payment readiness; the invoice still needs a production, department, cost code, supporting documentation, and the appropriate approvals. For vendor onboarding, payee verification, and final disbursement controls, see the separate production vendor payment-readiness guide.
Step 3: Capture and triage invoices
Invoices arrive in different formats and may reference a purchase order, estimate, commitment, or production contact. Bring them into a controlled queue that can identify the vendor and production, extract key fields, and flag missing information before approval.
At intake, check for:
- Vendor identity and production assignment.
- Invoice number, date, currency, amount, and payment terms.
- Department, cost code, budget line, purchase order, or commitment where applicable.
- Receipt confirmation, contract, estimate, timesheet, or other supporting record.
- Duplicate invoice numbers or repeated amounts.
A centralized queue makes incomplete work visible. It also gives production finance a place to resolve exceptions instead of relying on individual inboxes and disconnected spreadsheets.
Step 4: Code each invoice to the production context
Coding should capture both the accounting treatment and the operational context. At minimum, review the production, department, category, cost code, and purchase order or budget line when one exists. If the invoice spans departments or scenes, split it according to the production’s accounting rules and keep the supporting explanation with the record.
A practical coding review asks:
- Does the vendor and invoice belong to this production?
- Does the department owner recognize the goods or services?
- Does the cost code match the budget line and approved commitment?
- Is the amount within the available budget or does it require an exception?
- Are the required documents attached?
Automation can suggest fields or route clean invoices, but a person should review uncertain coding and exceptions. Faster entry is not a substitute for a reliable budget decision.
Step 5: Route approvals by department and threshold
A production approval matrix should reflect how work is actually managed. The department owner can confirm receipt and business purpose; production finance can validate coding and budget impact; and a production executive or other designated approver can review transactions above the agreed threshold.
Approval paths may vary by production, invoice type, department, and dollar threshold. Record the approver, decision, date, comments, and any changed coding. Clear routing reduces email chasing and creates evidence for a later production review or audit request.
If an invoice exceeds a commitment, lacks a purchase order, has a changed vendor detail, or has conflicting coding, route it as an exception rather than silently pushing it forward. For a production-specific view of payment fraud controls, see payment fraud prevention for film and TV productions.
Step 6: Hand approved invoices to the right payment method
After approval, select the payment method that fits the vendor, timing, documentation, and production policy. Depending on the situation, that may be ACH, wire, check, virtual card, or a cross-border payment in the vendor’s local currency. Keep the approved invoice, payment status, remittance detail, and any required documentation connected in the same workflow.
The payment handoff should make ownership clear: what is approved, what is scheduled, what has been released, and what is still waiting on information. Payment capabilities and country or currency availability depend on the configured service and production requirements; do not treat a payment option as proof that every vendor or jurisdiction is eligible. See EvedPay for the payment product context.
Step 7: Reconcile during production and prepare for wrap
Reconciliation should happen while the production is active, not only in the final days. Compare approved invoices and payments with commitments, budget-to-actual activity, outstanding exceptions, and open vendor balances. Return consistently coded invoice and payment results to the production accounting record and retain the approval history and supporting documents.
At wrap, use a close checklist to identify:
- Approved but unpaid invoices and scheduled payments.
- Open purchase orders, commitments, deposits, and credits.
- Missing receipts, contracts, invoices, or approval evidence.
- Vendor records or banking changes that need review.
- Costs awaiting allocation across departments or productions.
- Payment and accounting statuses that have not synchronized.
The goal is a defensible invoice-to-payment trail, not merely a screen that says “paid.” A structured wrap process helps the team resolve exceptions before the project record is archived.
How the workflow connects to production accounting
The AP and payment workflow should complement production accounting, not replace the financial book of record. Define which system owns the production, vendor, purchase-order, cost-code, tax, and banking data; how approved invoices and payment results return to accounting; how corrections synchronize; and which documents remain available after close.
Eved can be evaluated as an operational layer for vendor onboarding, invoice intake, coding, approvals, payment status, and accounting handoff, including integrations used in entertainment finance such as Cast & Crew. Confirm the required fields, permissions, integration behavior, and payment coverage for the specific production before selecting a workflow. For invoice and approval automation, see EvedAP; to map requirements to a production environment, schedule a walkthrough.
A production AP checklist
Use these questions when selecting or redesigning a film and TV AP process:
- Can every invoice be assigned to a production, department, and budget category?
- Can coding be reviewed against a purchase order, commitment, or budget line when one exists?
- Can department and finance approvals vary by production, invoice type, and threshold?
- Are duplicate invoices, missing documents, and unusual vendor changes routed for review?
- Does payment status remain connected to the approved invoice and remittance record?
- Can finance review budget-to-actual activity and open commitments before wrap?
- Can approval, coding, payment, and supporting-document history return to production accounting?
- Can the workflow distinguish production AP from the separate process for vendor onboarding and final disbursement?
FAQs
What is a film and TV production AP workflow?
It is the operating process that connects production budget setup, vendor and invoice intake, department and cost-code assignment, approvals, payment handoff, reconciliation, and wrap documentation. It preserves the project context needed to manage each transaction.
How is production AP different from corporate AP?
Productions use changing vendor networks, project-specific budgets, department-based decisions, fixed schedules, and often multiple locations or currencies. The workflow must retain production context instead of treating every invoice as an ordinary corporate expense.
What should be coded on a production invoice?
Review the production, department, category, cost code, amount, and purchase order or commitment when one exists. Also retain the invoice number, vendor, supporting documents, approval history, and final payment result so the transaction can be reconciled at wrap.
Should AP automation replace production accounting software?
No. Production accounting should remain the financial book of record. An AP and payment workflow can manage operational intake, coding, approvals, and payment status, then return complete and consistently coded information to accounting.
How should teams handle an invoice that fails a production AP check?
Route it as an exception to the appropriate owner. Resolve missing documentation, unclear coding, duplicate indicators, budget variance, or vendor-detail changes before payment, and record the decision rather than bypassing the control.
Can this workflow support global vendor payments?
It can keep payment method, currency, status, remittance, and documentation associated with an approved invoice when the configured payment service supports the vendor and jurisdiction. Availability and requirements should be confirmed for each production; global disbursement readiness is a separate vendor-payment concern.