Logistics

Freight invoice audit

Carrier charges must be compared with agreed rates, shipment records and approved extras before discrepancies are visible.

Business problem

Carrier charges must be compared with agreed rates, shipment records and approved extras before discrepancies are visible.

What teams see

  • Work waits between receive freight invoice and extract charges.
  • Owners reconstruct status from Gmail and Transport management system.

Why it happens

  • No shared state spans Gmail, Transport management system, Accounting platform.
  • Decision and exception rules are applied inconsistently.

Why it becomes expensive

  • Capacity is consumed by coordination and rework.
  • Late exceptions weaken visibility and service quality.

Business outcomes

  • Shorter approve or dispute charge cycle
  • Fewer handoff and missing-information exceptions
  • Clear ownership from receive freight invoice to approve or dispute charge
  • Inspectable decisions and recovery

Measurable KPIs

  • Turnaround time: Elapsed time from receive freight invoice to approve or dispute charge.
  • Manual intervention rate: Share of items needing a person outside defined review conditions.
  • Exception age: Time unresolved exceptions remain without a completed action.
  • Successful completion rate: Share of valid workflow items completing without terminal failure.

How the workflow works

  1. Receive freight invoice — Accept and identify the freight invoice audit trigger. Gmail
  2. Extract charges — Execute extract charges with validated sample data and an auditable result. Gmail
  3. Match shipment — Execute match shipment with validated sample data and an auditable result. Transport management system
  4. Fetch agreed rates — Execute fetch agreed rates with validated sample data and an auditable result. Accounting platform
  5. Reconcile line items — Execute reconcile line items with validated sample data and an auditable result. Gmail
  6. Flag discrepancy — Execute flag discrepancy with validated sample data and an auditable result. Transport management system
  7. Analyst review — Execute analyst review with validated sample data and an auditable result. SEIDO Review Queue
  8. Approve or dispute charge — Execute approve or dispute charge with validated sample data and an auditable result. Gmail
  9. Audit and KPI update — Persist the execution outcome, audit facts and workflow measurement events. SEIDO execution store

Integrations and ownership

  • Gmail: Provide workflow input
  • Transport management system: Lookup and update context
  • Accounting platform: Receive controlled outcome

Human responsibility: Logistics controller

Failure and recovery

Gmail is temporarily unavailable.

Retry with capped exponential backoff; preserve the run and move it to the inspectable failure queue after the limit.

Required data for extract charges is malformed or missing.

Stop downstream actions and show the missing fields, source evidence and correction action to the named reviewer.

The trigger or provider event is delivered more than once.

Return the existing execution identified by the idempotency key and do not repeat downstream business actions.

The human decision expires before completion.

Escalate to the configured substitute, retain the original request and record both expiry and reassignment.

When not to build this

  • Monthly volume is too low to justify integrating Gmail, Transport management system, Accounting platform.
  • An existing configured platform already handles freight invoice audit with adequate ownership and reporting.
  • Reliable source data or supported API access is unavailable.
  • No business owner has authority to define the decision and exception rules.

Related workflows