Reference · built on requestOperator by FibricFinance & billing

Freight Audit

Carrier invoice lines checked against shipment records and contracted rates, with disputes proposed for overcharges and late deliveries.

Request accessPricing ↗

About

A carrier invoice is a list of charges the carrier believes it earned. This operator reads that list from the file the carrier drops on your SFTP server or the sheet you keep, then checks each line. It reads the shipment from ShipStation: shipmentCost at label time, weight, dimensions, carrierCode, and serviceCode. It requests the contracted rate for the same shipment through the UPS Rating API with negotiated rates or the FedEx Rates and Transit Times API with account rates. It reads the EasyPost tracker for the delivery time against the estimate.

Where the invoiced charge exceeds the contracted rate, a surcharge has no basis in the shipment, or a guaranteed service delivered late, it proposes a dispute with the evidence attached. A person approves each dispute before it goes to the carrier.

This is a reference listing. It documents what Fibric would read from Freight Audit and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Carrier invoice files on an SFTP folder you name, or rows in a Google Sheet, with tracking number, charge type, and amount per line
  • ShipStation shipments by trackingNumber, with shipmentCost, insuranceCost, weight, dimensions, carrierCode, and serviceCode
  • UPS Rating API responses requested with NegotiatedRatesIndicator set, giving the contracted charge for the same package
  • FedEx Rates and Transit Times API quotes, with LIST and ACCOUNT rate types, for the same service and route
  • EasyPost tracker status, est_delivery_date, and the delivered scan time, for service-guarantee checks
  • Vendor bills for the carrier in your ledger, so an invoice already paid is audited but not disputed twice
  • Disputes it proposed before, by invoice and tracking number

Proposed actions

  • Target capability: propose a dispute for an invoice line where the charge exceeds the contracted rate returned for the same shipment, with both amounts shown
  • Target capability: propose a dispute for a surcharge, such as a dimension or address correction, that the shipment record does not support
  • Target capability: propose a service refund request where the tracker shows delivery after the guaranteed time, with the scan attached
  • Target capability: propose a short-pay amount for the ledger bill equal to the disputed lines, for your payables team to apply
  • Target capability: propose a weekly summary per carrier: lines audited, lines disputed, and amounts, appended to the sheet you keep

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Catch the charge above the negotiated rate

    Each invoice line from the SFTP drop is paired with the ShipStation shipment by trackingNumber and re-rated through the UPS Rating API. Lines over the negotiated charge become dispute proposals.

    With SFTP, ShipStation, UPS

  • Question the surcharge the package does not deserve

    A dimension or residential surcharge on a FedEx line is compared with the weight, dimensions, and address on the shipment. Where the record does not support it, a dispute is proposed with the label data attached.

    With FedEx, ShipStation

  • Claim the guarantee the carrier missed

    EasyPost trackers for guaranteed services are checked for a delivered scan after est_delivery_date. Each late delivery is proposed as a refund request with the scan history.

    With EasyPost

  • Keep the audit in the sheet finance already reads

    Every audited line, its outcome, and the disputed amount are appended to a Google Sheet per carrier, and the short-pay total is proposed against the carrier's bill in the ledger.

    With Google Sheets, Sage Intacct

Requirements

  • A file connector where carrier invoices land: SFTP or Google Sheets
  • A shipping connector with the shipment record per tracking number: ShipStation
  • A carrier connector with rating access on your account: UPS, FedEx, or both, with negotiated or account rates enabled
  • A tracking source for delivery times: EasyPost trackers or the carrier's own tracking
  • Your contract terms in writing: the surcharges you accept, the guarantee terms per service, and the dispute window
Authentication
It has no carrier account login. It reads invoice files through the file connector you attach, and calls carrier rating APIs and ShipStation with the credentials you hold on those connectors.

Limits

  • FedEx states that rate quotes are estimates and may differ from the invoiced amount. A difference inside the tolerance you set is reported, not disputed.
  • It reads invoices as files. Invoice downloads are configured by a person in the carrier's billing portal; it does not log in to fetch them.
  • Late-delivery claims depend on the guarantee terms for the service and on exceptions the carrier declares. It proposes; the carrier decides the refund.
  • It files nothing with a carrier and short-pays nothing on its own. Each dispute waits for approval.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Freight Audit ↗

Questions and answers

What does approving a dispute do?
It releases the dispute you approved through the path you set: a message to the carrier's account contact with the evidence attached, or a prepared case for a person to enter on the carrier's portal. Either way, once, and nothing goes out before that.
What is kept for the carrier's response?
Per disputed line: the invoice, the tracking number, the invoiced and contracted amounts, the tracker scans, who approved, when, and the carrier's reply when it arrives. Lines within tolerance are kept as audited with no dispute.
Will it short-pay an invoice without me?
No. It proposes a short-pay amount for your payables team. The bill is paid by your usual run. It never changes a payment on its own.
Ask about Freight Audit

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy