SYNTHETIC PROOF WALKTHROUGH

Hold a freight invoice with an accessorial absent from policy

A synthetic freight preflight comparing supplied invoice charges with a customer-provided shipment and allowed-charge policy.

See the three stepsRead the product contract →
NO KEY · NO UPLOAD · NO CUSTOMER DATAThis demonstration runs entirely in your browser using the visible synthetic fixture below.

THREE STEPS

Put the control before the consequential action.

The invoice includes a 20.00 USD detention charge while the supplied policy contains no allowed detention accessorial.

  1. 01

    Supply shipment and charge evidence

    The caller provides linehaul, fuel, accessorial, delivery, duplicate, and customer-policy values.

  2. 02

    Compare each supplied charge

    The control checks quoted values, allowed accessorials, charge totals, and supplied delivery state.

  3. 03

    Route only the exception

    The unapproved code and amount are returned for carrier-review without contacting the carrier.

VISIBLE SYNTHETIC CONTRACT

Inspect exactly what the workflow sees.

The input and output are representative of the named product contract. Copy them into an architecture note, test fixture, or internal review—never treat this browser-only demonstration as a live control result.

Customer-authorized input
{
  "invoice": {
    "vendor_name": "Northstar Freight",
    "invoice_number": "FRT-2201",
    "currency": "USD",
    "total": "100.00"
  },
  "shipment_reference": "PRO-2201",
  "carrier_scac": "NSFT",
  "quoted_linehaul": "80.00",
  "invoiced_linehaul": "80.00",
  "quoted_fuel_surcharge": "0.00",
  "invoiced_fuel_surcharge": "0.00",
  "shipment_delivered": true,
  "allowed_accessorials": [],
  "invoiced_accessorials": [
    {
      "code": "DETENTION",
      "amount": "20.00"
    }
  ]
}
Agent-readable output
{
  "status": "COMPLETED",
  "decision": "REVIEW_REQUIRED",
  "exceptions": [
    {
      "code": "FREIGHT_ACCESSORIAL_NOT_ALLOWED",
      "severity": "HIGH",
      "message": "An invoiced accessorial is absent from the supplied allowed-charge policy.",
      "evidence": {
        "code": "DETENTION",
        "amount": "20.00"
      }
    }
  ],
  "evidence": {
    "shipment_reference": "PRO-2201",
    "carrier_scac": "NSFT",
    "accessorial_count": 1
  },
  "next_action": "Validate the charge against the carrier agreement before payment routing."
}

WHAT THIS PROVES

Evidence for a stop point—not permission to act.

Freight Invoice Control does not connect to a carrier or TMS, verify delivery, interpret a tariff, dispute a charge, or approve payment.

Decision
REVIEW_REQUIRED
Named exception
FREIGHT_ACCESSORIAL_NOT_ALLOWED
Evidence
codeDETENTIONamount20.00
Next action
Validate the charge against the carrier agreement before payment routing.

KEEP BUILDING

Move from the synthetic fixture to the exact API contract.

Review the product inputs, outputs, errors, and safety boundary before using authorized data. The related implementation guide explains the design decisions behind the control.

Product contract →Implementation guide →Security posture →

Try the control through the supported buyer path.

RapidAPI provides the subscription, key, quota, and capped marketplace plan for this synchronous control.

Get an API key on RapidAPIExplore every synthetic demo →