A tooling charge audit should connect each quoted line to the product baseline, operation, required output, acceptance evidence, asset identity, custody, commercial terms, and change history. The IAS 16 page provides accounting context for tangible assets without deciding project ownership or quotation scope.
Audit a PCBA tooling charge by connecting the commercial line to a defined object or engineering task, the active product baseline, the approved scope, the acceptance result, the asset record and the applicable terms. A quotation, invoice or photograph can support one part of that chain. None of them proves the whole chain alone.
The audit should end with a usable state for every line: closed, closed with a bounded exception, correction required, or held pending named evidence. “Reviewed” is not a useful final state when the team cannot say which record controls, which object exists or who accepted the result.
This method does not set a fair market price, determine legal title or rate supplier performance. It checks whether the project’s own records explain what the buyer is being asked to approve and whether the physical or digital work remains controlled.
Give the Tooling Charge Audit One Object and Identifier
Create an audit row for each quoted tooling item or work package. Assign an audit ID and record the supplier response revision, quote-line reference, description, amount or commercial pattern, assembly and revision, process operation, requested output and current owner. Avoid placing several unrelated fixtures under one row called “NRE.”
Separate a physical asset from the engineering that produces or changes it. A functional-test fixture may involve mechanical fabrication, wiring, instruments, software, debug, golden-sample correlation, documentation and acceptance. Those objects may appear in one commercial line, but the audit still needs to show which deliverables the line covers.
Define the unit before collecting evidence. Otherwise, the reviewer may match an invoice to a photograph while overlooking excluded software, or match an acceptance report to a different fixture revision. The audit ID provides the join point for the rest of the record.
Record the same audit ID on every working extract so reviewers can trace a copied field to its controlling source without treating the extract itself as acceptance evidence.
Use neutral states for unknown fields. Do not label a missing asset ID as “not applicable” unless the responsible owner confirms that no controlled asset exists. Do not label a missing acceptance result as “passed” because production once ran.
Freeze the active source set
List the records that may control the review: current quotation or commercial response, purchase record, approved change, technical scope, drawing or configuration, acceptance result, asset register, custody or ownership terms, invoice and later amendments. Add the revision or date and the person who supplied each record.
Resolve supersession before comparing contents. A later email may clarify one field without replacing the full quotation. An engineering change can update the product baseline without changing the commercial terms. A purchase order can accept a line while leaving a technical deliverable open. Record each relationship instead of assuming that the newest timestamp wins every question.
The PCBA quotation assumptions register provides a way to keep response conditions attached to the applicable revision. For the audit, add the evidence source and the rule used to resolve conflicts.
Freeze the active response, product baseline and tooling record before matching evidence. Keep superseded records for traceability, but mark them inactive. An old response can explain why a fixture exists; it should not silently control a later invoice or reuse decision.
Reconcile Each Quote Line in the Tooling Charge Audit
Translate the commercial description into work that engineering, sourcing and quality can recognise. Identify hardware, design, build, wiring, programming, software, debug, validation, documentation, spares, maintenance, storage, repair and routine execution where they apply. Record which party supplies the inputs for each activity.
Read exclusions and prerequisites with the included work. A line may exclude golden samples, test limits, product interfaces, target hardware, firmware, instruments or buyer approval. Those exclusions can leave a technically necessary task outside the quoted amount. The audit should expose the gap rather than recalculate the supplier’s price.
Do not infer scope from the invoice description if the quotation has more detail. Conversely, do not use a broad quotation label to explain an invoice for a specific later change. Match the line, response revision and affected work.
Where the supplier uses a bundled line, request enough decomposition to identify deliverables and release evidence. The supplier does not need to reveal confidential internal cost calculations for the buyer to understand what the line buys.
Verify the product and process baseline
The tooling charge audit should show which product, revision, operation, quantity, and output the asset or service supports.
Record the assembly number, active revision, product variant, panel or unit form, quantity stage, manufacturing operation and test or programming output. Confirm that the technical records and commercial response use the same baseline.
A shared project name does not establish alignment. One document may reference the bare PCB revision, another the PCBA assembly revision, and another a product configuration. State the object type and effectivity. When several variants share a tool, list the variants and the evidence that supports common use.
Use the PCBA engineering change control guide to trace previous and current baselines. The audit should identify any change after quotation or acceptance and show whether the responsible functions reviewed its tooling impact.
Do not mark the line closed while a baseline conflict remains. A commercial approval tied to the wrong revision can be accurately signed and still fail to control the intended build.
Test technical acceptance against the intended output
Acceptance evidence should state what the item or work product must do, how the team checked it, the result, the configuration, the date and the approver. A delivery note proves receipt. A photograph supports existence or condition. Neither proves that a fixture produces the required output.
For a programming adapter, check target identity, connection, device, image revision, verification output and exception rule. With ICT or functional test, check access, instruments, loads, software or sequence, limit source, expected record, samples or correlation method and failure disposition. A carrier or assembly aid needs fit, support, orientation, identification and any dimensional or process acceptance criteria.
The PCBA test fixture development guide describes the input and output questions that affect fixture work. It does not prove that a particular project fixture passed. The audit needs the actual project result.
Acceptance evidence must identify the tool, configuration, method, result and authorised approver. When acceptance relies on a deviation or provisional sample, record the exception, protected scope, owner, expiry and next validation. Do not turn a bounded exception into a permanent acceptance state.
Match the Asset Register to Physical Custody
For physical items, record a unique asset ID or controlled configuration, description, associated assembly, revision, current location, custodian, condition, maintenance or calibration state where applicable, access limits and transfer record. For digital work products, record software or sequence identity, version, storage location, access owner and recovery path.
Compare the register with the item or controlled repository. Look for duplicate IDs, missing components, altered wiring, unavailable adapters, damaged surfaces, outdated software or records that point to a former location. Record the observation date; condition and location can change.
Custody does not establish ownership. Ownership does not establish current usability. Access does not establish permission to reuse the tool for another product. Keep those fields separate and read the applicable commercial record.
Where the asset cannot be found, do not close the line from historic records alone. Mark the physical readback incomplete and identify the next search, inspection or replacement decision.
Trace the charge’s commercial behaviour
Record whether the line is one-time, recurring, amortised, credited, refundable, conditional, separately approved or linked to a quantity or change trigger. Use the supplier’s actual terms. Avoid translating an unfamiliar term into a more favourable category without confirmation.
Identify the currency, tax or freight treatment only where they affect the audited line and the project record supplies the answer. This article does not interpret law or prescribe accounting treatment. Finance or the authorised commercial owner decides how the organisation books and approves the amount.
The first table shows the minimum evidence chain. A complete row still requires authorised reviewers; the table does not create a contractual term.
Audit link
Record to inspect
Required match
Failure state
Quote line to scope
Active response and work breakdown
Same line, revision and deliverables
Correction required
Scope to baseline
Assembly, revision, variant and operation
Same controlled product and output
Hold affected line
Baseline to acceptance
Method, configuration, result and approver
Intended output and current basis
Revalidate or hold
Acceptance to asset
Asset/configuration ID and location
Same item or released digital version
Reconcile asset
Asset to terms
Ownership, custody, access and transfer record
Same object and applicable agreement
Commercial review
Terms to payment
PO, invoice and approved response
Same condition and amount pattern
Finance/sourcing correction
If the line changed after the original approval, state the previous and new condition. A new amount may be valid while the description is stale, or the description may be accurate while the approving record refers to an older revision. The audit must reconcile both.
Trace Changes Through the Tooling Charge Audit
Build a short timeline: quotation, technical release, tool build or modification, acceptance, purchase approval, invoice, transfer, maintenance event and later change. Use actual dates and revision identifiers. The purpose is to find gaps in sequence, not to create a decorative chronology.
When a product, test, interface or quantity assumption changes, identify the affected audit rows. Then record whether the current tool needs no action, inspection, validation, modification or replacement, and whether the supplier issued a revised commercial response.
A change timeline links the previous baseline, delta decision, revised work and final readback. Preserve rejected proposals and superseded responses. They show why the team chose the active state and prevent the same unapproved assumption from returning in a later quote refresh.
Avoid retroactive closure. If the team used a tool before formal acceptance, record the actual event and the later decision separately. A later signature should not erase the period when evidence was incomplete.
Grade evidence by what it can prove
Grade every tooling charge audit record by the claim it can support: price, ownership, custody, acceptance, reuse, maintenance, or change.
Use the narrowest claim each evidence object supports. Also, the quotation supports the supplier’s commercial response at a point in time. Meanwhile, the purchase order supports buyer approval under its terms. A controlled drawing supports configuration. The inspection or validation record supports the stated method and result. Finally, the asset register supports recorded identity and location. Yet none of these objects automatically proves legal ownership, continued condition or current compatibility.
Label oral explanations and uncontrolled screenshots as leads until an authorised record confirms them. Screens can help locate an object or question, but they may omit revision, context and approver. Do not publish screen values or customer data.
The public quality assurance page describes general quality context. It cannot replace project-specific acceptance, asset or invoice evidence.
Where two strong records conflict, keep the conflict visible and route it to the owner of that decision. Evidence strength does not resolve a disagreement about scope or authority by itself.
Run a Cross-Functional Tooling Charge Audit Before Closure
Before closing the audit, bring engineering, test, sourcing, quality and the commercial approver to the same source set. First, engineering reads back the active assembly, revision and affected operation. Then, test identifies the required output, configuration and acceptance record. Meanwhile, sourcing points to the applicable response, purchase record and any changed commercial condition.
When these owners use different revisions, stop the affected row. If they agree on the baseline but not the work breakdown, request a corrected scope. Otherwise, continue to the asset and payment checks. Next, quality reads back the asset identity, condition and exception state. Specifically, the reviewer should name any maintenance, calibration or validation record that the decision needs.
Because an audit often spans several systems, do not rely on a copied spreadsheet alone. Although the spreadsheet can index the evidence, each owner should reopen the controlling source. Similarly, the final approver should compare the corrected field with the current quote line instead of an earlier export.
Finally, record who attended, which sources they reopened and which rows changed state. After the readback, preserve the prior state and correction date. Therefore, a later reviewer can distinguish a genuine source correction from a summary that someone edited without authority.
Close Each Row with an Owner and Readback
Use four closing states: closed, bounded exception, correction required, or hold. For each open state, record the missing or conflicting field, owner, requested evidence, due decision and protected scope. Do not use a percentage score to hide a missing critical object.
Closing state
Conditions
Required readback
Next action
Closed
Evidence chain matches current baseline and terms
Owner confirms object, result and commercial line
Release within approved scope
Bounded exception
Named gap does not affect protected work
Exception, expiry and owner confirmed
Track closure before expiry
Correction required
Record exists but line, revision or field is wrong
Corrected source and supersession confirmed
Re-run affected checks
Hold
Identity, baseline, acceptance, authority or terms cannot support approval
Missing evidence and hold boundary confirmed
Do not approve affected line
Require independent readback after correction. Reopen the source record, not a copied summary, and confirm the line, revision, asset, result, owner and state. Record the readback time and reviewer. This prevents a spreadsheet fix from being mistaken for a corrected quotation or asset record.
Audit closure requires the source record, corrected field, owner, final state and independent readback. The project owner should report the result without inflating it. “Six lines closed, one correction pending and one fixture-identity hold” is more useful than “audit passed.” The first statement tells purchasing what it may approve.
FAQ
Is an invoice enough to prove a PCBA tooling charge?
No. An invoice supports the billed line and amount. The audit still needs the applicable response or order, defined scope, product baseline, acceptance evidence and any asset or ownership records required for the decision.
Does a photograph prove that a test fixture was accepted?
A photograph can support identity, existence, location or visible condition when the context is controlled. It does not prove electrical operation, software, test coverage, limits, correlation, safety or authorised acceptance.
Should every tooling item have an asset ID?
Physical controlled items generally need a unique identity or configuration that the project can reconcile. The exact system depends on the organisation. Pure engineering work may use a deliverable or version identifier rather than a physical asset tag.
Can an audit close with missing ownership terms?
Close only the fields that current records support. If ownership, transfer or access affects approval, keep that part open or hold the affected line. A technical acceptance result does not decide commercial ownership.
Prepare the evidence package for review
Bring the active quotation revision, tooling schedule, assembly and revision, work breakdown, acceptance record, asset or configuration ID, custody and ownership terms, purchase or invoice reference, change history and open exceptions. Send that controlled package through the plain contact page for a project-specific review.
The expected output is a line-by-line record that tells engineering, sourcing, quality and finance what they may approve and why. Keep price reasonableness, legal title and supplier performance as separate decisions owned by the appropriate functions.
Source basis: The linked GNSEMS service pages provide general context. For a tooling decision, use the current quotation, asset register, configuration record, maintenance history, and written approval that apply to the named project. The presence of a document or asset does not, by itself, prove acceptance, ownership, enforceability or current use.
