Calibration and Safety Compliance Controls in Plex

Executive Summary

Plex Manufacturing Cloud enforces two things well on calibration and safety compliance spend: it keeps a due-date schedule for gauges and equipment inside Quality Management, and it enforces a three-way match between purchase order, receipt, and invoice inside procurement. Both are real, documented Plex behaviors, and both matter.

Neither checks contract pricing. Plex's three-way match confirms an invoice agrees with its own purchase order, not that the purchase order price agrees with a rate schedule, a per-instrument fee cap, or a travel and trip charge clause buried in a service agreement. Plex's calibration schedule confirms a gauge was due for service, not what the vendor was contractually allowed to bill for performing it.

The result is a control that stops the invoice that contradicts itself and passes the invoice that quietly contradicts its contract. A calibration vendor who raises a per-gauge rate, adds a trip charge, or bills a certificate fee the contract does not authorize clears Plex cleanly, because the purchase order was cut at the new number and the invoice matches the purchase order. The diagnostic exists to catch what the match was never designed to test.

1. What does Plex's Quality module actually track for calibration?

Plex's Quality Management System maintains a calibration schedule for gauges, fixtures, and measurement equipment tied to each asset record. It flags equipment as due, overdue, or out of calibration and can hold a device from use in production until service is logged. This confirms the work was due and was performed.

It records nothing about what the vendor was contractually entitled to charge for performing it.

The calibration schedule sits inside Plex's Quality module, attached to the equipment master record rather than to accounts payable. Each gauge or instrument carries an interval, a last-serviced date, and a next-due date, and Plex can prevent a device from being used in a production process once it passes due.

When a calibration event is logged, the record shows that a technician or outside vendor serviced the equipment and passed or failed it. That is a quality control, built to keep uncalibrated equipment out of production, not a cost control.

The schedule has no field for a contracted per-gauge rate, no field for a travel or trip minimum, and no link back to the service agreement governing the vendor performing the work. A vendor can service every gauge on schedule, exactly as required, and still bill above the rate the contract sets. Plex's Quality module has no way to see that, because pricing was never part of what it was built to track.

2. Does Plex's three-way match catch a rate that violates the contract?

Plex enforces a three-way match: the invoice must agree with its purchase order and the corresponding receipt in quantity and unit price. This blocks an invoice that bills differently from its own purchase order. It does not test whether the purchase order's price itself complies with the calibration or safety compliance service agreement, because the contract is not a field the match checks against.

Three-way matching is standard Plex procurement behavior. Accounts payable will hold or reject an invoice that does not tie to an open purchase order and a posted receipt within tolerance. That stops a common error: an invoice quantity or price that disagrees with what was ordered and received.

It does not stop a different error: a purchase order that was itself cut at a rate the underlying contract does not permit. If a calibration vendor's agreement sets a fixed per-instrument fee and someone issues a purchase order at a higher number, whether by a pricing update, an admin error, or a vendor quote that quietly moved, the invoice matches that purchase order exactly. Nothing in the three-way match compares the purchase order price to the contract's rate schedule, because the contract itself is not data Plex procurement holds in a structured, checkable form.

The control does its job. It just answers a narrower question than the one that determines whether the company is paying the right amount.

3. Where do certificate fees and trip charges slip through?

Calibration and safety compliance invoices commonly carry line items beyond the base service fee: certificate issuance, travel or trip charges, expedite fees, and re-calibration after a failed reading. Plex has no structured field distinguishing a contracted line item from an added one, so these charges post as ordinary invoice lines and clear the match as long as they were also present on the purchase order.

A calibration service agreement typically separates the base per-gauge or per-visit fee from ancillary charges: a certificate of calibration, a trip or travel charge for on-site work, an expedite fee for rush turnaround, and a re-calibration charge when an instrument fails and needs a second pass. Some contracts cap or waive specific ones of these; others leave them open.

Plex records the purchase order and the invoice as line items. It has no concept of which line items a specific vendor's contract authorizes and which it does not. If a trip charge appears on the purchase order, whether because someone approved it or because it was copied forward from a prior order, the invoice matching it clears without exception.

This is not a defect in the match. It is a boundary. The system was built to confirm internal consistency between three documents it holds, not to hold the fourth document, the contract, as a structured source of truth.

4. Can Plex flag a calibration vendor who bills above their agreed rate card?

No. Plex has no rate card object for service vendors comparable to a purchased-part price list. Component and material pricing lives in Plex's item and supplier price records, but calibration and safety compliance services are typically entered as generic service lines on the purchase order, priced manually at the time of entry rather than checked against a stored contracted rate.

Plex's strength is on the shop floor: bills of material, routings, and purchased-part pricing are tightly structured, and a price variance on a stocked part is visible because the system holds an expected cost to compare against.

Service spend does not get the same structure. A calibration visit is usually entered as a non-stock or service line on the purchase order, with the price typed in at that moment rather than pulled from a maintained rate card. If the person creating the purchase order enters the vendor's current invoice rate instead of the contracted rate, Plex has no reference value to compare it to and no reason to flag the difference.

This is a structural gap, not a configuration mistake. Extending Plex's item pricing model to cover contracted service rates would require building and maintaining that rate card as its own object, then keeping it current every time a service agreement is renewed or amended.

5. Does Plex's supplier record capture the calibration contract itself?

Plex's supplier master holds identification, payment terms, and performance history for a vendor, not the calibration or safety compliance service agreement's rate schedule, interval commitments, or fee caps. The contract itself typically lives outside Plex entirely, as a PDF or signed document, which means nothing in Plex can test an invoice against it automatically.

The supplier record in Plex tracks who the vendor is, standard payment terms, and quality performance metrics like on-time delivery or defect rate where applicable. That is useful for deciding who to source from.

It is not where a calibration contract's substance lives. The per-instrument rate, the annual visit count, any volume discount, and the terms governing certificate and trip fees sit in a signed agreement that predates the Plex record and is rarely re-entered into it in structured form.

Because the contract exists outside the system as an unstructured document, no Plex process reads it and no Plex control can compare an incoming invoice against it. Whatever a person remembers about the agreement, or does not, becomes the actual control. That gap is exactly what a contract compliance audit is built to close: reading the agreement once and turning its terms into a checkable rule set.

6. What should an AP team check by hand until that rule set exists?

Until calibration contract terms are captured outside the vendor's own invoice, an AP team can pull the signed agreement for each calibration and safety compliance vendor and check three things on every invoice batch: the per-instrument or per-visit rate, whether trip and certificate fees were contractually authorized, and whether the visit count for the period matches what the contract commits to.

Three checks catch most of the drift a purchase order match will not. First, compare the invoiced per-gauge or per-visit rate to the number in the signed agreement, not to last quarter's invoice, since an invoice that only ever gets compared to itself will drift upward indefinitely without ever looking wrong.

Second, list every ancillary fee on the invoice: certificate, travel, expedite, re-calibration. Check each against the contract's fee schedule rather than assuming a charge is legitimate because it appeared before.

Third, if the contract sets an annual or quarterly visit commitment, either a minimum or a cap, track actual visits against it. A vendor billing for more visits than the equipment schedule required is a different problem than an inflated rate, and Plex's calibration due-date tracking will not surface it because it was never designed to reconcile against a contracted visit count.

7. Does a diagnostic or a software add-on fix this gap faster?

A diagnostic reads the existing calibration and safety compliance contracts against 12 to 18 months of invoices already posted in Plex and quantifies what has already leaked. Software configured before those contracts are read can only enforce whichever rules someone guesses at setup. The two are sequential, not competing: read the contracts first, then decide what a forward control should check.

A retrospective review works with what already exists: the signed calibration agreements and the invoice history sitting in Plex's accounts payable module. It reads the contract terms once, applies them against the purchase orders and invoices already posted, and quantifies the gap without requiring any change to how Plex is configured.

A forward control, whether built inside Plex or bolted on beside it, only enforces the rules it is given at setup. If those rules are guessed rather than read from the actual agreements, the control enforces the wrong thing confidently, which is worse than enforcing nothing, because it creates false assurance that calibration invoices are being checked.

The practical order is to read the contracts and quantify the existing gap first, then use what that review finds to decide exactly which rate caps, fee limits, and visit counts a forward control needs to check going forward.

For the wider pattern this sits inside, start with the margin drift guide. See also diagnostic or software: what to buy first and build vs. buy: can you do contract-to-invoice matching in excel?.

8. Frequently Asked Questions (People Also Ask)

Does Plex track calibration due dates for safety equipment as well as gauges?

Plex's Quality module can track calibration and inspection intervals for any equipment record entered into it, including safety-related instruments, not only production gauges. The scope depends on which equipment a company has set up as tracked assets, not a system limitation.

Will Plex block payment if a calibration certificate is missing?

Plex's calibration schedule can hold equipment from production use if service is overdue, but that hold operates in the Quality module. Accounts payable in Plex does not check for a certificate before releasing payment on a calibration invoice unless a manual approval step is added outside standard matching.

Can Plex's three-way match be configured to include a contract rate check?

Not as a native field. The match compares invoice, purchase order, and receipt for quantity and price agreement with each other. Adding a contract rate comparison would require building a separate rate reference and a custom validation step outside standard Plex matching behavior.

Is this gap specific to Plex, or does it show up in other ERPs too?

The same seam exists wherever a quality or maintenance module tracks calibration schedules separately from an accounts payable module that matches purchase orders to invoices. Plex is a real, verifiable example of the pattern, not an exception to it.

Where do rebate or volume discount clauses in a calibration contract get checked in Plex?

Nowhere automatically. If a calibration vendor's agreement includes a volume discount once a certain number of gauges are serviced in a year, Plex has no mechanism to track cumulative volume against that threshold or apply the discount, since the threshold is not data the system holds.

What is the fastest way to find out if we are overpaying a calibration vendor right now?

Pull the signed contract and the last 12 to 18 months of that vendor's invoices from Plex, then compare the invoiced rate and fees, line by line, against what the contract actually authorizes. A margin drift diagnostic does this systematically across every service vendor at once.

Does Plex distinguish between a calibration failure re-test and a routine scheduled visit on the invoice?

Not automatically. Both typically post as service lines on a purchase order and invoice. Whether a re-test charge is contractually billable depends on the agreement, and Plex has no field marking an invoice line as a re-test versus a scheduled visit.

Should a safety compliance disclosure be added if we discuss regulatory calibration requirements?

Yes. Any discussion of calibration intervals tied to regulatory or safety compliance obligations is general information, not legal advice, and a company should confirm its specific regulatory calibration requirements with qualified counsel or its compliance function.