Reconcile NDT Report Quantities Before Invoicing

Read the actual agreement and identify what each billing line measures. It may concern a component, an examination event, a length, a visit, time or another defined service unit. A result table uses a structure chosen for technical reporting and may not match that commercial unit. One component can produce many readings, while one report can cover several visits. Start with the agreed unit and map the evidence to it. Do not assume that the easiest spreadsheet count is the quantity the parties agreed to use.

Keep this reconciliation separate from estimating a market price. The worksheet does not supply rates or determine what a customer owes. The quotation cost-driver guide explains planning inputs before a quote. This workflow begins after work has been performed and asks whether the proposed quantity is supported by the actual agreement and records. An unresolved interpretation of the commercial unit belongs with the responsible contracting participants, not with an improvised rule created by the report compiler.

Record the purchase order, service instruction or other actual agreement reference for the billing line. Include relevant authorized changes when they affect the quantity or unit. A broad project name may be insufficient when several work packages use different terms. Preserve the link between the original scope and any additions, removals or repeat visits. This makes the quantity explainable without requiring the invoice reviewer to reconstruct the entire job from unrelated emails and report filenames.

As a specific public example, FAR32.905 lists quantity and unit of measure among invoice information for its federal procurement context. That is not a universal rule for every private NDT invoice. The practical lesson is to make the actual unit and agreement reference explicit. Use the requirements that apply to your customer and contract, and avoid importing government payment deadlines, tax rules or other conditions into an unrelated service arrangement merely because the example is publicly available.

Count unique physical components separately from the events performed on them. A weld examined before and after repair is one physical weld with more than one examination event. Whether both events contribute to a billing quantity depends on the actual terms. Preserve the event identities so that question can be answered accurately. Do not collapse the history to make the technical report match a component-based invoice, and do not inflate the number of components because the report contains several legitimate events for the same item.

Keep methods and stages distinguishable when they affect the agreed service description. A surface examination and a volumetric examination on one component may be separate scope items or part of a combined service. The records should show what occurred without deciding the commercial treatment by assumption. A reconciliation table can include both the technical event count and the proposed billing quantity, with an explanation of their relationship. This is more useful than forcing every record into one count that means different things to different readers.

If the agreement uses a physical quantity such as length or area, identify the source of that quantity and its units. A drawing dimension, a field measurement and an approximate planning estimate are not automatically interchangeable. Record which basis the parties actually agreed to use and whether the performed scope differs from it. Do not estimate a precise billable length from the number of report rows or a schematic image that was not intended to provide dimensional evidence.

Where a conversion is needed, retain the original quantity and the checked calculation reference. Avoid mixing units in one total or rounding each row in a way that creates an unexplained difference from the agreed method. The technical record should preserve its actual measurement meaning even if the commercial presentation uses another unit. If the conversion or rounding convention is unclear, resolve it through the responsible process before presenting the resulting total as an agreed quantity.

A second visit may involve new examination scope, a repair follow-up, completion of previously inaccessible work or a return caused by another circumstance. Record the actual purpose and the performed events. Similar component names across visits do not prove that the work was duplicated. At the same time, a copied summary row should not create another visit or examination event. Use the underlying field and report references to distinguish legitimate repeat activity from duplicate presentation of the same evidence.

Keep the reason for the visit separate from the decision about whether it is chargeable. That decision depends on the real agreement and authorized clarification. A technical report should not change its description of the event to support a preferred commercial position. If responsibility for the return visit is disputed, preserve the factual chronology and route the commercial question appropriately. The reconciliation record can identify the unresolved issue without declaring fault or inventing a contract term.

Time-based work cannot always be reconstructed from the final report quantity. Preparation, setup, access delays, review and travel may or may not be included under the actual terms. Use the relevant time and activity records rather than inferring hours from the number of completed components. A low output count does not by itself prove little time was spent, and a large report does not prove a particular number of chargeable hours. Preserve the activity evidence and the agreement’s definitions.

Where several people worked simultaneously, distinguish elapsed site time from personnel time. A crew on site for a period does not automatically mean one person-hour total or a crew-day charge. Use the actual unit and supporting attendance records. Do not add universal overtime, minimum callout or travel rules to the worksheet. Those are agreement-specific questions. The contract comparison tool can help organize entered time and reimbursement terms, but it does not determine contractual entitlement.

A requested item may remain unexamined because of access, preparation or another recorded limitation. Preserve that state in the technical record. Whether associated mobilization, standby or other services are billable is a separate question under the actual terms. Do not mark the item examined merely because a charge may be appropriate for some other activity. Similarly, do not erase performed preparation or attendance evidence simply because no technical result was obtained.

If scope was canceled or removed, retain the actual instruction reference and its relationship to the work already performed. The commercial consequences may differ depending on timing and terms, but the worksheet should not invent them. Identify the facts needed for the responsible decision: what was requested, what changed, when the change applied and what activity occurred. A clear factual record supports a fair reconciliation more effectively than a technical report altered to make the proposed invoice total look inevitable.

In a fictional assignment, ten components receive an original examination. Two of those components later receive authorized follow-up examinations after repair, producing twelve examination events across the same ten physical identities. The report correctly preserves all twelve events. The billing reviewer checks the actual agreement to determine how original and follow-up work should be represented. The proposed invoice does not call the job twelve components, because that would misstate the physical quantity even if twelve events are relevant to the commercial calculation.

A separate return visit also includes documented access waiting time. The team records that activity independently and applies only the terms actually agreed. This example provides no rates or entitlement decision. Its purpose is to show how one assignment can legitimately contain several different counts. A reconciliation matrix connects ten components, twelve examination events, the actual visit records and the proposed billing units without changing any technical result or treating every count as interchangeable.

A daily report, a summary and a final consolidated package may all describe the same examination event. Identify that shared event so it is counted once for the relevant quantity. Do not delete the source records merely because they repeat information. The reconciliation matrix can point to the controlling evidence while retaining the delivery history. Conversely, two rows with the same component number may represent different events and should not be merged without checking their date, method, stage and source relationship.

If you use spreadsheet counting functions, understand what the formula actually counts. Microsoft’s COUNTIFS documentation describes counting entries that meet specified conditions across ranges. That operation does not decide whether a row is a unique examination or a billable event. Define and review the event keys first, then check the formula against known examples. A correct formula applied to a misunderstood unit can produce a precise but commercially meaningless total.

A principal provider may receive subcontractor records using units different from the customer’s agreement. Preserve both bases and document the mapping. A supplier invoice for personnel time is not automatically evidence of the number of components examined, while a report table may not capture every activity included in the supplier’s terms. Keep source organization, event and commercial references clear. Do not present the subcontractor’s billing quantity as a technical count unless the underlying records establish that relationship.

Check overlapping work packages for the same event before combining totals. Two providers may contribute to one examination process or cover separate methods on the same component. The actual service structure determines how the work is represented commercially. The reconciliation should make the facts visible without implying that the report compiler performed all work or has authority to settle every supplier term. Preserve unresolved differences for the responsible commercial and technical participants instead of forcing the figures to match through unexplained adjustments.

When the proposed billing quantity differs from the raw report count, record why. The difference may be a unit conversion, removal of a duplicate presentation, an authorized scope change or treatment of a repeat event under the actual agreement. Keep the adjustment specific enough that another reviewer can reproduce it. A balancing entry labelled correction is not sufficient if nobody can identify which events it affects or what evidence supports the change.

Preserve the original quantity alongside the adjusted commercial representation where useful. Do not alter technical measurements, examination outcomes or performed-scope statements to make the invoice reconcile. If a source report itself contains an error, address that through the actual report correction process and identify the resulting version. The commercial worksheet should reference the corrected evidence rather than silently editing its own copy and leaving the customer’s technical record inconsistent with the quantity used for billing.

Some differences cannot be resolved by arithmetic because the agreement or evidence is unclear. Identify the exact question and the responsible next action. A proposed quantity can remain under review without implying that the underlying examination did not occur. Conversely, a completed technical report does not settle every commercial term. Use precise states such as evidence mapped, commercial interpretation pending or quantity confirmed through the actual process, rather than one generic approved label that hides which decision has been made.

The inspection quote comparison tool can help locate the actual scope and exclusions recorded during procurement. It is a planning aid, not a legal or invoicing engine. If the parties need a clarification, preserve the resulting instruction and apply it consistently to the affected line items. Do not use a market average or an invented customary practice to fill a gap in the agreement. This worksheet supports evidence-based discussion without claiming to determine payment rights.

The free digital reporting workspace prepares examination reports and PDF records. It is not an invoicing or payment application. Use it to preserve the actual technical results and scope references, then connect the relevant report information to your organization’s commercial process. Do not imply that exporting a PDF automatically produces an invoice, calculates charges or sends a payment request. Keep sensitive payment details out of the technical report unless a real project requirement makes them necessary.

Check which supporting records the customer actually requests with the invoice. A concise quantity reconciliation may be more useful than sending every raw data file. At the same time, a summary without retrievable evidence may leave the reviewer unable to confirm the quantity. Use the actual delivery requirements and permissions. The report buyer-review guide can help confirm the technical package’s completeness, while the commercial reviewer checks the separate billing requirements.

Before submission, choose each proposed line item and trace its unit, quantity and supporting events back to the agreement and performed records. Confirm that repeat events are handled consistently, canceled scope is explained and no examination is counted twice through summary copies. Check any formulas or conversions independently through the organization’s normal process. The reporting importer does not execute spreadsheet formulas, so a calculated source total should not be assumed to have been recalculated or verified during import.

Use the worksheet below to preserve the mapping and unresolved questions. Replace fictional examples with actual references, and keep technical quantities distinct from commercial quantities when their meanings differ. A successful reconciliation produces an explainable invoice basis while leaving the examination history intact. It does not require every number in every document to be identical. It requires each number to have a clear unit, a supported source and a transparent relationship to the work and terms it is intended to represent.