Outbound Accounting

The four flows in this section all share a direction: Tai is the source of truth, and the third party is responsible for getting the record into the target accounting system. Whether that's a customer invoice a Tai user just printed, a carrier bill the ops team just approved, or a check batch the AR clerk just posted, Tai holds the canonical record — the integrator's job is to make sure the other system agrees.

Why this direction exists

Most of the day-to-day accounting activity in a brokerage happens inside Tai — the shipment is created there, the pricing is there, the operator approves the bill there, the invoice goes out from there. But the general ledger, aging reports, cash-flow forecasts, bank reconciliations, and vendor payment runs all live in the accounting system. Without a live sync, the two drift within hours: Tai says "invoiced," SAP says "not yet"; the customer calls the AR clerk who's looking at a stale dashboard; a carrier gets paid twice or not at all.

The outbound flow is the fix. Every record Tai creates gets pushed — live via webhook where available, on a batch schedule as backup — until the target system acknowledges it via a sync status update. Anything that fails to reach the target lands in Tai's Accounting Sync History page for a user to correct and retry.

What's in this section

Six record types, each with its own doc. Bills, Invoices, Customers, and Carriers carry a HOOK webhook for live delivery; Payments are batch-only.

AR side (money in)

• AR Records: Tai → Third Party — customer invoices generated in Tai.
• AR Payment Records: Tai → Third Party — customer payments applied to invoices in Tai.

AP side (money out)

• AP Records: Tai → Third Party — carrier and vendor bills approved in Tai.
• AP Payment Records: Tai → Third Party — check and ACH runs paid out from Tai.

Master data (referenced by every transaction)

• Customer Records: Tai → Third Party — customer master creates and updates. Feeds AR.
• Carrier / Vendor Records: Tai → Third Party — carrier master creates and updates. Feeds AP.

Master-data flows are simpler than transactional flows — no sync-status close-the-loop step, no per-shipment activity log. Just webhook and (where available) batch lookup.

Two channels, one contract

Every outbound doc describes two ways to receive a record — a live webhook (HOOK on create) and a batch GET filtered by ?SyncStatus=None. You can register the webhook alone, use the batch alone, or run both together. The recommended pattern is both: webhook for immediacy, batch for guaranteed delivery. See Choose your delivery cadence on the parent doc for the trade-offs.

Regardless of channel, the closing step is the same: Sync Status Updates tells Tai the record has been handled so it stops re-serving on the next batch.