Contract manufacturing pass-through costing sounds simple until the invoice hits finance. Many teams know the commercial model, but they struggle to explain which charges are reimbursed, which ones carry a markup, and where cost-variance risk sits. The confusion starts when teams use commercial labels too loosely.
Contract manufacturing pass-through costing sounds simple until the invoice hits finance. Many teams know the commercial model, but they struggle to explain which charges are reimbursed, which ones carry a markup, and where cost-variance risk sits. That confusion slows quote approval, creates audit friction, and drives invoice disputes at month-end.
Controllers need billing rules that define cost ownership, markup treatment, and invoice triggers before the first disputed line item hits month-end close.
Quick answer: Pass-through billing usually recovers a defined customer-specific cost at the agreed amount, often without a markup on that line. Cost-plus billing recovers an agreed cost base, such as materials, labor, and allowable overhead, then adds a documented fee or markup. T&M bills approved hours and materials at contract rates, while fixed-fee-per-unit prices production to a target and leaves the contract manufacturer responsible for ordinary variance inside that target.
The confusion starts when teams use commercial labels too loosely. Pass-through is often used as a catch-all term for any reimbursed material. That is too broad. A true pass-through line usually covers a customer-specific cost recovered at the agreed amount. Common examples include expedited freight, duties, specialty components, third-party testing, customer-directed tooling, or outside certification fees. If the manufacturer is also sourcing, coordinating, planning, or carrying risk on that cost, the agreement may need a markup, separate fee, or bundled unit price instead.
Cost-plus is different because it defines both the base and the return. The cost base may include materials, labor, outside processing, and allowable overhead. The return may be a percentage markup, a fixed fee, a burdened rate, or a tiered fee by cost class. That distinction changes customer transparency, gross-margin reporting, cash exposure, audit support, and how the ERP should classify each transaction.
Pass-through answers: which customer-specific costs get reimbursed at the agreed amount?
Cost-plus answers: which costs belong in the billable base, and what return is applied to them?
T&M answers: which hours, rates, and materials were approved and consumed?
Fixed-fee-per-unit answers: what price was agreed, and who absorbs ordinary variance inside that price?
Finance language matters here. A 20% markup on a $100 cost creates a $120 price and a 16.7% gross margin, not a 20% gross margin. Controllers and GMs need the contract and the ERP to say whether the commercial term is markup, margin, multiplier, burden, or fixed fee. If that definition stays fuzzy, the billing rule will drift later.
Under ASC 606, the label still does not settle presentation. Gross-versus-net treatment depends on whether the contract manufacturer controls the promised good or service before transfer. In other words, principal-versus-agent analysis, not the phrase pass-through, drives presentation.
Model | Customer transparency | CM margin protection | Cost-variance risk | ERP complexity | Common industries | Best-fit relationship |
|---|---|---|---|---|---|---|
Pass-through | High for qualifying reimbursable costs | None on the pass-through line itself | Customer usually bears qualifying cost changes | Moderate | Electronics EMS, medical, aerospace, food | Customer-specific purchases and documented exceptions |
Cost-plus | Very high, often open-book | Strong when the cost base and fee are well defined | Customer bears eligible cost changes | High | Medical contract manufacturing, aerospace, prototypes, NRE | Long-term, auditable programs |
T&M | High for labor and material detail | Protected through bill rates | Customer bears approved consumption | Moderate to high | Engineering, validation, repair, failure analysis | Uncertain or changing scope |
Fixed-fee-per-unit | Lower, because price matters more than cost detail | Strong only if target costs hold | CM bears ordinary variance inside the agreed boundary | Moderate | Food, stable EMS builds, mature repeat programs | Predictable volume, stable routings, repeatable specifications |
Pass-through works best when the cost is traceable, customer-specific, and outside the CM's profit model. Common examples include customer-requested air freight, import duties, third-party laboratory testing, special packaging, external certifications, or tooling acquired on the customer's behalf.
In electronics EMS, an OEM may nominate a scarce component supplier and require the contract manufacturer to purchase the part without markup. In medical contract manufacturing, an independent validation or biocompatibility test may be passed through when the customer requires the test and keeps approval rights. In food contract manufacturing, customer-specific ingredients or urgent freight may be handled the same way.
The invoice support has to be airtight. Each pass-through line should tie back to the contract clause, the vendor source document, the customer or program reference, and the authorization path. Pass-through does not mean every material line carries zero markup. It means the contract identifies a narrow cost category, ownership and risk are clear, and the contract manufacturer is not earning a return on that specific line.
Cost-plus recovers actual or agreed costs and then applies a defined return. The cost base may include direct materials, direct labor, outside processing, burdened labor, and allowable manufacturing overhead. It may exclude customer-owned inventory, taxes, nonbillable rework, manufacturer-caused scrap, or pass-through categories handled separately.
Medical contract manufacturers often prefer cost-plus for development, validation, and quality-heavy work because the customer wants visibility into engineering, QA, and change costs. Aerospace programs often lean the same way because documentation, ceilings, and audit support matter. This is where finance discipline matters most. The fee should be defined by cost class, not treated as one vague percentage.
Cost-plus only works if the ERP can prove what belongs in the fee base. If labor, overhead, freight, and pass-through exceptions are all pooled together, the model will create disputes instead of clarity.
T&M works when scope is moving. It is common for engineering NRE, prototype builds, failure analysis, installation, repairs, line transfers, process changes, and urgent customer-driven work where the contract manufacturer cannot lock a stable production economics model yet.
For T&M, labor is billed by role, rate card, or burdened-hour rate. Materials and outside services follow their own agreed rules. Some are billed at cost, some at markup, and some are included in a labor burden or shop rate. The ERP must capture approved time, effective dates, role mapping, customer and project linkage, and the category logic for billable materials.
T&M also needs active forecast discipline. Teams should watch EAC, estimate at completion, and ETC, estimate to complete, so approved funding is compared against forecasted consumption before the engagement goes underwater. For finance teams building that planning discipline, see NetSuite Planning and Budgeting (NSPB): Complete Guide to Financial Planning.
Fixed-fee-per-unit sets a customer price and shifts ordinary variance management to the contract manufacturer. This model is common for recurring food production, mature EMS assemblies, and other stable programs with predictable routings, repeatable yield, and a defined bill of materials.
The commercial simplicity can hide operational risk. A fixed unit price only works when the contract manufacturer can control standard-versus-actual variance, purchase-price variance, yield drift, scrap, and change orders. Commodity swings, BOM changes, MOQ shocks, customer-driven expedites, and quality events all need clear contract language. Without that, fixed-fee-per-unit turns into margin leakage. Teams building repeatable production controls can compare that discipline with this guide to production tracking, MRP, and shop floor control.
Electronics EMS most often uses pass-through or a blended commercial structure for purchased components, while engineering NRE and supply-chain recovery may sit under cost-plus or T&M. Assembly-focused manufacturers will recognize the same pattern when work orders, purchased components, and customer-specific pricing all sit inside one operational flow. Medical contract manufacturing frequently uses cost-plus for development, QA, and validation transparency, then shifts mature production to a unit price. Food contract manufacturing often uses pass-through for customer-specific ingredients or freight and fixed-fee-per-unit for stable high-volume runs, which shows up clearly in food processing operating models. Aerospace programs tend toward cost-plus or T&M where traceability, change management, and documentation demands are intense.
For industry context, finance and operations teams can review the electronics manufacturing resources from SEMI, medical device policy and operating context from MDMA, and broader manufacturing strategy research from Deloitte Insights.
The setup has to reflect the contract, not a generic billable checkbox. Each cost needs the right customer, program, and commercial rule at the transaction level. At Softype, this usually starts with a contract-to-transaction mapping exercise so finance, operations, and implementation teams use the same billing logic before configuration begins. If your team is mapping the wider production model around these rules, this manufacturing implementation guide gives the broader rollout context.
Create separate reimbursement categories or charge rules for freight, duties, customer-specific testing, tooling, and other defined pass-through classes.
Apply a 1.00 multiplier or zero-markup rule only to qualifying transactions, never to the full material pool.
Require customer, program, work order, and authorization references on each qualifying transaction.
Link vendor bills, receipts, and credits back to the same customer and program dimensions so later adjustments flow correctly.
Decide whether invoices show detailed source costs or a summarized support schedule.
Define the markup-eligible base by cost class: direct materials, direct labor, outside processing, allowable overhead, or burdened labor.
Use separate fee items, rate rules, or charge logic for each markup tier rather than one blanket percentage.
Exclude customer-owned inventory, pass-through categories, and nonbillable rework from the fee base.
Report actual cost, billed cost, cumulative fee, EAC, ETC, remaining funding, and contract ceiling status.
Build approval and exception controls so disputed costs never flow into billing by accident.
Set customer-specific labor rate cards with effective dates, role mappings, approval status, and overtime treatment.
Route time entries and materials to the right customer, project, work order, and contract line before billing is generated.
Define whether materials are billed at cost, cost plus markup, or bundled into a burdened labor rate.
Use cutoff controls and funding alerts so late, unapproved, or out-of-scope transactions do not quietly hit the invoice.
Use customer-specific item pricing and quantity-break schedules for the contracted assembly, lot, or service unit.
Maintain standard cost for quoting and operational comparison while separately tracking actual material, labor, and overhead variance.
Set change-order triggers for BOM revisions, commodity thresholds, yield excursions, MOQ changes, and expedite events.
Make variance reporting visible to finance and operations before the pricing issue becomes a renewal issue.
WIP invoicing breaks down when teams treat production timing and billing timing as the same event. They are not. Production can span periods, while billing may be triggered by material receipt, operation completion, a milestone, shipment, or customer acceptance. Your cost flow should preserve WIP and actual production cost. Billing should follow the commercial trigger in the contract. This gets much easier when planners and controllers work from the same MRP and work-order planning logic instead of disconnected spreadsheets.
For a cost-plus program, that may mean monthly as-incurred billing with cumulative cost and fee support. For a fixed-fee-per-unit program, billing may wait until completion or shipment. For pass-through tooling, the customer may be invoiced on vendor-bill receipt even while the production order stays in WIP. Finance should also assess revenue recognition separately from invoice generation and cash collection. The billing trigger and the revenue trigger are not automatically the same thing.
Hybrid agreements are normal in contract manufacturing. Many contract manufacturers do not run one billing model across the whole customer relationship. They run pass-through freight, cost-plus engineering, T&M recovery for urgent quality work, and fixed-price production on the mature build. That means customer-specific pricing overrides are not a convenience feature. They are the control surface that keeps one customer's contract from contaminating another's.
For finance teams, the rule should be simple. The ERP must separate contract lines, item pricing, rate cards, fee logic, and exception categories by customer and program. If every charge pulls from one shared pricing pool, hybrid agreements turn into manual workarounds. That is the same implementation discipline covered in NetSuite for Manufacturing: Complete Implementation Guide 2026.
Billing design fails when the customer cannot reconcile what it sees. A contract manufacturing customer portal should expose the right commercial evidence: order status, inventory ownership, WIP or milestone status, shipment details, invoice and credit status, certificates, and support schedules for pass-through or cost-plus charges. It should not expose every internal cost detail unless the contract requires that level of transparency.
Portal view: order status, inventory ownership, WIP or milestone status, shipment detail, invoice status, and support schedules.
EDI baseline: 850 purchase order, 855 acknowledgment, 856 advance ship notice, 810 invoice, and 846 inventory inquiry or advice.
High-control industries: automotive, aerospace, electronics, and regulated medical programs often require deeper release, label, and traceability detail.
For EDI contract manufacturing, the baseline usually includes the 850 purchase order, 855 acknowledgment, 856 advance ship notice, 810 invoice, and 846 inventory inquiry or advice. See How Automotive Tier-2 Suppliers Automate Big-3 EDI in Their ERP for a deeper look at release discipline, ASN controls, and connected billing evidence. These mappings must match the billing trigger and the level of detail the customer expects. If they do not, reconciliation breaks down fast.
Readers looking for adjacent manufacturing and traceability angles can also review NetSuite for Food Processing: A Sub-Vertical Architecture Guide for regulated production environments and How Automotive Tier-2 Suppliers Automate Big-3 EDI in Their ERP for release discipline, ASN controls, and connected billing evidence.
Cost ownership: which categories belong to the customer, which stay with the CM, and which trigger reimbursement.
Markup treatment: whether the return is a markup, margin, burdened rate, fixed fee, or separate service charge.
Billing trigger: vendor bill, milestone, operation completion, shipment, or customer acceptance.
Variance boundary: which cost moves require a change order, and which stay inside the agreed price.
Evidence standard: what portal data, support schedules, EDI detail, or source documents the customer expects to see.
The cleanest way to choose is to start with risk ownership, not invoice format.
Use pass-through when the cost is customer-specific, documented, and expected to be recovered at the agreed amount without a separate return on that line.
Use cost-plus when scope, quality, or input costs are uncertain and the customer wants an auditable cost base with a defined return.
Use T&M when the work is engineering-heavy, service-driven, or changing too quickly to estimate as a stable production price.
Use fixed-fee-per-unit when the build is stable enough that the contract manufacturer can manage variance to a target cost.
Use a hybrid model when the engagement contains different risk types, such as mature production, NRE, freight, tooling, and customer-directed exceptions.
In practice, the wrong model is usually the one that hides the risk allocation. The right model makes cost ownership, markup treatment, WIP trigger, change-order boundaries, and customer evidence obvious before the first invoice goes out.
Pass-through recovers a qualifying customer-specific cost at the agreed amount, usually without markup on that line. Cost-plus recovers an agreed cost base and adds a contractual fee, markup, or burden. The key difference is whether the contract manufacturer earns a return on the cost line.
EMS programs often use a blend. Components or customer-designated purchases may be handled as pass-through or built into a unit price, while engineering NRE, supply-chain recovery, and unusual customer-driven changes may be billed under cost-plus or T&M. The right structure depends on component volatility, customer ownership, and forecast stability.
NetSuite can preserve manufacturing cost in WIP while billing follows the commercial trigger, such as a milestone, vendor bill, shipment, or acceptance event. The important design rule is to keep production cost flow separate from billing logic so finance can manage WIP correctly and still invoice on the contracted event.
Yes. Many contract manufacturing agreements are hybrid. Separate contract lines, pricing rules, fee logic, and customer-specific overrides keep pass-through freight, cost-plus engineering, T&M support, and fixed-price production from being processed as one mixed billing pool.
Set pricing at the customer and item level using contracted prices, quantity breaks, effective dates, and customer-specific price logic. For cost-plus and T&M arrangements, pair those price controls with rate cards or charge rules so the billed value comes from the right cost or labor source.
The usual baseline is 850 purchase order, 855 acknowledgment, 856 ASN, 810 invoice, and 846 inventory inquiry or advice. Some industries add customer-specific releases, label rules, quality documents, or traceability requirements, especially in automotive, aerospace, and regulated medical environments.
Yes, if the contract allows it. If the customer expects those charges to be reimbursed as pass-through, configure them as separate zero-markup categories. Finance should never assume the material markup rule applies automatically to every landed-cost component.
The strongest contract manufacturing billing model is the one that makes the commercial rules impossible to misunderstand. When cost ownership, allowable cost, markup treatment, WIP trigger, variance responsibility, and customer evidence are represented clearly in the ERP at the transaction level, finance protects margin without damaging customer trust.
Softype helps contract manufacturers turn billing rules into governed NetSuite workflows that finance can defend and operations can execute. Whether you run electronics, medical, food, or aerospace programs, the next step is to make the billing rule visible before the next quote, work order, or invoice exception forces the issue.
The confusion starts when teams use commercial labels too loosely.
Pass-through works best when the cost is traceable, customer-specific, and outside the CM's profit model.
Cost-plus recovers actual or agreed costs and then applies a defined return.
Fixed-fee-per-unit sets a customer price and shifts ordinary variance management to the contract manufacturer.
Electronics EMS most often uses pass-through or a blended commercial structure for purchased components, while engineering NRE and supply-chain recovery may sit under cost-plus or T&M.
The setup has to reflect the contract, not a generic billable checkbox.
Helping businesses thrive with integrated ERP solutions.
NetSuite
Service
Company
Contact Us
Copyright © 2026
