Integrations
Connect external inputs and provider outcomes without losing their source history.
The specification defines integration responsibilities for implementation. It does not establish a live dealer portal, warehouse device, carrier, bank or tax connection. Agree each source’s identity, field ownership, permitted data and acceptance evidence before enabling the handoff.
- Dealer and supplier channels
- Dealer ordersin and out
- Supplier communicationin and out
- Warehouse, delivery and production evidence
- Operational capturein
- Delivery outcomesin
- Production inputsin and out
- Financial services and reporting
- Banking evidencein
- Tax and rate evidencein and out
- Approved reportingin and out
- Agents
- Your agentWorks within the permissions you assign
Dealer and supplier channels
- Dealer orders. A configured channel may supply a draft request, party reference or agreed commercial information. The local acceptance and revision rules still apply. Receiving another copy of the same external order must not create a second commitment or fulfill already consumed quantities.
- Supplier communication. Preserve the approved purchase revision and original line identity through sending, confirmation and arrival. A supplier message is distinct from actual receiving evidence and accepted supply. Bill inputs retain their match and exception history rather than bypassing the local payables controls.
Warehouse, delivery and production evidence
- Operational capture. Scanners or external tools must identify the actual person, action, source and quantities within their permitted scope. A scan or imported status cannot independently approve a cost change, release held goods or create duplicate stock.
- Delivery outcomes. Route and carrier handoffs retain their shipment, stop and attempt identity. Requested, acknowledged, uncertain and actually completed outcomes remain different. The reviewed title terms determine whether stock remains owned in transit until accepted delivery.
- Production inputs. External capture may provide permitted operation or material evidence. Accepted terminal output and work-order cost rules determine the resulting stock and financial effect. An intermediate operation count cannot become another finished completion.
Financial services and reporting
- Banking evidence. Import or retrieve the defined statement and payment outcomes under restricted authority. A submitted instruction or provider acknowledgment is not final settlement. Preserve uncertain action identity until reconciliation instead of issuing another economic instruction.
- Tax and rate evidence. Retain the reviewed source, effective basis, currency and rounding used for the document. Missing required evidence must be resolved before an affected release; an unavailable result is not a verified zero amount.
- Approved reporting. Share permitted entity reports and references with their population and cutoff. Exporting local journals to another destination does not authorize creating a second local posting for the same transaction. Consolidation or elimination work needs its separately agreed scope.
How connections are governed
service accounts, audit, pausingUse authenticated source namespaces, stable action and destination identities, and an exact content revision. Repeated same-content delivery reconciles to the recorded result; changed content requires an explicit correction or revision. Provider uncertainty retains the original action until its outcome is resolved. Test retries, delayed messages, revoked access and partial outcomes before rollout. Historical cutover records must not send new orders, issue goods, settle cash or replay messages simply because their imported state is complete.
The API is one more client of the same interface. AI assistants and API →