Are you a new Houdini motion designer staring at a blank invoice template and wondering what details really matter? You might be unsure which line items to include, how to describe your tasks or what pricing terms to use. This confusion can lead to late payments or awkward back-and-forth with clients.
Without clear guidance, it’s easy to overlook critical elements like project scope, licensing rights or payment schedules. Missing information can frustrate both you and your clients, slowing down your cash flow and damaging your professional reputation.
This article will walk you through exactly what to put on a motion designer‘s invoice, from essential headings to optional extras that clarify your work. You’ll learn how to label your services, break down costs and include the legal language that protects you.
By the end, you’ll have a clear template tailored for Houdini projects—complete with descriptions for modeling, simulation or rendering tasks. You’ll know how to set payment terms, add invoicing dates and include contact details so there’s no confusion.
With this guidance, you can present a professional invoice that speeds up approval, secures timely payment and strengthens your client relationships. Let’s dive into the must-have elements to make your next invoice both accurate and effective.
What client and project identification details are required on an invoice?
Accurate identification prevents miscommunication and speeds up payment. As a Houdini motion designer, you must reference the exact project scope defined by your client. This includes both business information and pipeline-specific codes.
- Client legal name and billing address: Matches the entity on the purchase order (PO).
- Client contact and email: The accounts-payable or project manager responsible for approvals.
- Project title or code: Use the client’s internal code (e.g., “PROJECT-XYZ-2024”) and your own shorthand (e.g., “HIP_Sim_Rev02”).
- Purchase Order (PO) number: Ensures invoice ties directly to the approved work order.
- Invoice number and date: A unique incremental identifier combined with the issuance date.
- Houdini scene reference: Optionally note the HIP file or shot/asset name (e.g., “Shot_012_FLIPSim_v3.hip”) for clarity on billed tasks.
Why include a scene reference? In larger VFX houses, multiple simulation revisions can exist. Referencing the exact HIP file or shot name helps the client cross-check the rendered frames, verify the WIP versus final output, and avoid disputes over which version you billed. Always confirm naming conventions with the client’s pipeline lead before delivering the invoice.
Which line items should a Houdini motion designer list and how should they be described?
When invoicing as a Houdini motion designer, each charge should map to a concrete production task. Clients often see “FX” or “rendering” as vague. Break down work into procedural categories—simulations, rigs, shading, lighting and final renders—to illustrate both creative and technical effort. Clear descriptions build trust and simplify approvals.
Sample line item descriptions for Houdini work (e.g., simulations, rigs, fx, lighting, renders)
Below are real-world examples. Adapt names and units (hours, days, or flat fees) to your workflow:
- Pyro Simulation Setup (8h): Construct pyro solver network, define fuel/source fields, set collision geometry, configure voxel size and cache for production-quality smoke.
- Flip Fluid Solver (6h): Create flip tank, adjust particle separation, enable velocity resampling, export particle cache to SOPs for meshing and surface smoothing.
- Character Rigging (10h): Build CHOP-driven FK/IK rig, automate joint blending, implement Python callbacks for custom pose libraries and control parameters in the channel editor.
- Procedural Crowd Setup (12h): Design agent network, set random seed attributes, integrate L-system growth patterns, optimize for GPU instancing during render.
- Shader & Lighting Pass (5h): Author VEX material templates in SHOPs/VOPs, apply layered textures, configure Mantra LPE outputs and sample counts per light.
- Mantra Render & Compositing (4h): Schedule deep EXR export, multiplex AOVs, assemble in Nuke for passes, adjust cryptomatte IDs and motion vectors.
How to separate creative, technical, and revision time for clear billing
Organize hours under three columns: Creative (concept and artistic direction), Technical (node-building, scripting, optimization), and Revision (client feedback iterations). This prevents scope creep and clarifies where time is invested.
| Category | Activities | Billing Unit |
|---|---|---|
| Creative | Concept art, style tests, look-dev approval | Hours or Fixed Fee |
| Technical | Simulation caching, rig implementation, tool scripting | Hours |
| Revision | Client notes, scene adjustments, re-renders | Hours |
By listing each category separately, you give transparency to both artistic decisions and technical complexity. Clients appreciate seeing where resources are allocated, making negotiations smoother.
How do I show pricing: hourly vs flat-rate vs milestone billing for Houdini projects?
When drafting an invoice for a Houdini project, selecting the right pricing model ensures transparency and aligns expectations. An hourly rate works well for small tweaks or unpredictable simulations, a flat-rate suits clearly scoped tasks, and milestone billing helps you manage larger procedural pipelines.
- Hourly rate: Ideal for debugging VEX snippets, adjusting node parameters, or running short smoke and particle sims. Track time in your project management tool alongside HIP file versions to justify hours.
- Flat-rate: Best for fixed deliverables like a completed Pyro shelf tool, a procedural crowd setup or a cached flip simulation. Define input geometry, output caches, render settings, and revision limits in the quote.
- Milestone billing: Suited to complex, multi-stage builds such as full procedural city generators or multi-pass destruction setups. Break the pipeline into nodes—and checkpoints—like SOP modeling, DOP simulation, Mantra renders, and final compositing.
By aligning billing with Houdini’s procedural workflow, you demonstrate clear value: clients see exactly when you build the SOP network, cache sims, write Python callbacks, or hand off ROP outputs. That clarity reduces scope creep and builds trust.
What payment terms, delivery milestones, and licensing/usage rights should be included?
Establish clear payment terms to protect both parties. Commonly, Houdini motion designers request a 30% deposit before starting procedural setups in the OBJ and SOP contexts. A second 40% is due when simulation caches (e.g., .bgeo.sc files) and initial lighting renders are approved. The final 30% is tied to delivery of HD or 4K composited passes. Specify accepted methods (wire transfer, PayPal, cryptocurrency) and late-payment penalties (e.g., 1.5% monthly fee).
Define precise delivery milestones to track progress. Break the workflow into discrete stages: initial blockout in the Geometry node tree, RBD or FLIP sims, shader and POP network tweaks, Mantra or Karma render tests, and final export of Hip and Hipnc files. For each stage, include deliverables (scene files, texture sequences, EXR passes) and sign-off requirements. This clarity prevents scope creep when iterating Houdini Digital Assets (HDAs) or tweaking VEX snippets.
Outline licensing/usage rights so clients know their permissions. Specify whether the Houdini assets and caches are licensed exclusively or non-exclusively, and define territory (global or regional), duration (perpetual or time-limited), and media (broadcast, online, Sizzle reels). If you’re handing over HDAs with editable parameters, clarify whether they can resell or modify those procedural setups. A well-scoped license protects your procedural know-how while giving clients the flexibility they need.
How should taxes, reimbursements, invoice numbering and other legal/administrative items be formatted?
Properly structuring the administrative section of your Houdini motion design invoice ensures clarity for both you and your client. Start by giving each invoice a unique, sequential number—using a prefix like “HD-2024-015” helps you track projects over time. Include your company’s tax ID or VAT number, your client’s tax registration if required, and clear payment terms (e.g., “Net 30 days”).
Taxes should be shown in a separate line directly under the subtotal. List each tax type—such as VAT or sales tax—with its rate and the computed amount. For example:
| Description | Rate | Amount |
|---|---|---|
| Subtotal | $2,500.00 | |
| VAT | 20% | $500.00 |
| Total Due | $3,000.00 |
When billing reimbursements—for example, cloud GPU render time, specialized Houdini plugins, or on-set expenses—itemize each cost with date, vendor, and receipt reference. This transparency helps clients verify charges and accelerates payment.
- Date of expense
- Expense category (e.g., “Render Farm – AWS EC2 Spot”)
- Invoice or receipt number
- Amount in the invoice currency
Finally, include your banking details or payment link, your legal address, and a brief note on late fees or early-pay discounts. By combining clear numbering, precise tax calculations, and transparent reimbursement lines, you’ll present a professional, audit-friendly invoice that builds trust with your clients.