Media production companies — particularly those delivering visual effects (VFX), animation, and post-production services — operate in a uniquely complex commercial environment. A single project may involve fixed-price deliverables such as asset creation and onsite supervision, alongside usage-based services where billing is driven by the volume of shots completed at each complexity tier.

Traditional ERP systems struggle to accommodate this duality. Project managers are forced to reconcile billing models across disconnected tools, time recording is inconsistent, and external shot completion data from editing systems arrives with no structured integration path.

This blog demonstrates how SAP S/4HANA Cloud — specifically its Customer Project Management capabilities — addresses these challenges end-to-end. We walk through a real-world example: VFX Services for Neon / 50 Shots, a project serving Electronics, INC. (DE), covering everything from project planning through billing readiness.

Section 1

Structuring a VFX Project with Mixed Billing Models

Work packages map directly to billing elements, enabling simultaneous fixed-price and usage-based contract terms within a single project.

When project VFX4712 is created for a 50-shot engagement, the project manager defines six work packages — each corresponding to a distinct commercial commitment. SAP S/4HANA Cloud enforces a deliberate separation between how work is planned and tracked internally and how it is billed externally.

 

VFX Tier 1 – Simple (work package VFX4712.1.4) illustrates the usage-based model clearly: 20 planned pieces (=Shots) with a planned revenue of 56,000 EUR. Each shot approved by the editorial system increments the billable quantity — the project manager does not need to manually count or reconcile. Similarly, VFX Tier 3 – Complex carries the highest planned revenue at 138,000 EUR for 12 shots, reflecting the premium pricing for complex visual work.

In contrast, Asset Creation (VFX4712.1.1) carries a fixed planned revenue of 45,000 EUR regardless of how many hours are consumed internally. The separation ensures revenue recognition follows the correct accounting rules for each contract type

The Planning tab shows all six work packages with their cost vs. effort actuals, planned quantity (service-based), and planned revenue per billing element. Recognized revenue of 14,888 EUR against 7,404 EUR actual cost reflects a 50.27% margin at this stage of the project.

 

Section 02

Integrated Resource Management: Connecting People to Work

Resource requests are raised directly on work packages, giving project managers a real-time view of who is committed to which deliverable — and how much capacity remains unstaffed.

With the project structure in place, the next step is staffing. SAP S/4HANA Cloud's integrated resource management surfaces 17 resource requests across the project's work packages — each request specifying a role grade, time window, and required effort in hours.

For example, Asset Creation work package, three consultants are engaged across three grade levels. The staffing view confirms that requested and staffed efforts are fully aligned — a green signal for the project manager that no capacity gap exists on this work package.

• Role-grade costing: Each resource request carries a grade (T001–T003) which drives internal cost rates — enabling accurate margin simulation before work begins.

• Cross-package visibility: The same individual can be staffed across multiple work packages, and the system enforces utilization limits to prevent over-commitment.

• Billing relevance: On time-and-material billing elements, the staffed role grade determines the billing rate applied when time is recorded — creating a direct link from staffing to invoice.

Section 03

Ensuring Every Billable Hour is Captured Before Billing

The Time Recording view compares staffed effort against recorded effort per worker, surfacing gaps that must be resolved before billing can be initiated.

As the project progresses, VFX artists and designers record their hours against specific work packages. SAP S/4HANA Cloud continuously compares staffed effort (committed capacity) against recorded effort (actual time entries submitted), and calculates the delta as Missing Hours — visible to the project manager at any point.

In the current snapshot, the Asset Creation work package shows mixed compliance. 

Critically, VFX Supervision shows zero hours recorded ,despite a combined staffed commitment of 94h. With a billing due date approaching on 22.05.2026, the project manager must act immediately to send reminders and ensure time entries are submitted before the billing run is triggered.

Section 04

Commercial Billing Terms and Upcoming Due Dates

The Billing tab consolidates all six billing elements — their contract types, due dates, and amounts to bill — providing a single source of truth for commercial obligations.

Once project execution is underway, the Billing tab becomes the commercial control center. For project VFX4712, six billing elements have been configured — each derived from its corresponding work package and carrying its own contract type, billing due date, and amount.

The Asset Creation billing element (VFX4712.0.1) has a due date of 18.05.2026 with 15,000 EUR ready to bill — the first billing milestone approaching imminently. The VFX Tier 1 – Simple usage-based element also carries a due date of 18.05.2026, but currently shows 0.00 EUR to bill, reflecting that shot completions have not yet been confirmed by the external editing system.

The Billing Documents section below the elements shows no invoices have been generated yet. This is intentional — the project team is ensuring time recording completeness (Section 03) and shot confirmation updates are processed before initiating any billing documents.

• Billing due date monitoring: Due dates on billing elements drive automated reminders and billing run scheduling — the system ensures no milestone is missed.

• Contract type enforcement: Fixed Price elements bill on date or milestone trigger; Usage-Based elements accumulate quantities from shot confirmation events before billing can proceed.

• Profit center assignment: All six elements are assigned to Consulting Unit A (YB101), ensuring revenue recognition flows to the correct organizational unit automatically.

Coming Up in Part 2: Initiating the Billing Run – Part 2 

With the project structure defined, resources staffed, time recording reviewed, and billing terms confirmed, the project is ready for its first billing cycle. In Part 2, we will demonstrate how shot completion updates from external editing systems flow into SAP S/4HANA Cloud, how usage quantities are confirmed on usage-based billing elements, and how the billing run generates customer invoices for both Fixed Price and Usage-Based elements simultaneously — completing the revenue cycle.