Skip to content
Freight invoice audit

Freight invoice audit

Agent: the finance agent (finance in ExecuteLoop), with the rate-confirmation and SLA evidence documents.

What it does

It checks what carriers bill against what you agreed, and drafts the short-pay or credit request for finance to approve. Its jobs:

  • Invoice against rate confirmation. Finds accessorial lines that the rate confirmation doesn’t authorise, units billed inside free time, and rates above the one agreed.
  • SLA credits. Works out the service credits owed under an SLA clause for late pickups or missed delivery windows.
  • Order, invoice and bill of lading. Finds where the three disagree on quantity, and by how much.
  • Spend oversight. Sorts transactions into categories with a stated confidence, flags spend that departs from its baseline, and compares options by cost-benefit, total cost of ownership and cost to serve.

What it reads

Carrier invoices, signed rate confirmations, master service agreements and their SLA clauses, purchase orders, goods-received records, invoice lines, the general-ledger chart you use, and the rules Rules Recon found in your data. It can run read-only queries against the connection a run was started with.

What it produces

  • Evidence documents RATE_CON_ACCESSORIAL_AUDIT (accessorials billed above the rate confirmation) and MSA_SLA_COMPLIANCE_AUDIT (service credits owed). Their headline amounts count as money only as described on Action cards & money.
  • Action cards proposing a short-pay, a dispute or a credit request, on Actionable Twins under the claims play.
  • For spend oversight: categorised transactions with a confidence, anomalies with the observed and expected values side by side, and recommended actions.

Human oversight

  • An accounts-payable or finance lead approves every short-pay, dispute and credit request. The agent never pays, withholds or credits money itself.
  • Budget reallocations and procurement changes it suggests are recommendations only.

Model

The deployment’s general reasoning tier.

The audit documents’ amounts are fixed arithmetic over your invoice and rate confirmation. No model computes them.

Where it runs and data handling

On the deployment’s own model plane: Runink’s shared machines on a Trial, your own cloud on Cloud and your own servers on On-premises. No outside AI service is called on any plan. See Facts shared by every card.

Guardrails

  • Compares your invoice with your own rate confirmation, line by line. A rate the confirmation doesn’t state is reported as not stated, not disputed on a guess.
  • Refuses to falsify cost-benefit, total-cost-of-ownership or cost-to-serve results.
  • Refuses to fabricate or hide procurement spend to favour a vendor, and refuses to invent market-rate benchmarks.
  • Stays on finance: claims disputes, dispatch, maintenance schedules and compliance audits belong to other agents.

How to read its results

  • Its reference is your contract: every figure is measured against your own rate confirmation.
  • Identified money is not recovered money. Only what a carrier credits or pays back is recovered.
  • A transaction category comes with the agent’s confidence. It is a suggestion for your chart of accounts, not a posting.
  • When the contract, the invoice line or the SLA clause is missing, the figure is reported as missing and no amount is given.