Integrations

• Accounts and contacts. Keep stable source identifiers and define which team may change billing, ownership and credit details. Resolve contact and account references before using them on live documents.
• Opportunities and products. Bring the proposal context and source product lines into quoting. Unmapped SKUs stay in a review queue until a valid catalog match is made.
• Commercial updates. Return the primary quote’s agreed amount and outcome with its revision context. A delayed event from an older proposal must not overwrite a newer accepted result.

• Documents out. Send the approved revision with its parties, selected options, commercial values and operative terms. Preserve the original document and the executed copy separately.
• Evidence in. Retain provider event identity, timestamps and payload context. Validate the envelope and revision before applying a signature, decline or void; repeated and stale callbacks cannot accept a different offer.
• Provider setup. Assess the selected signature provider, signer routing and document requirements during implementation. Naming a provider in the model is not a verified connector commitment.

• Released orders. Carry accepted line values, products, configured options, bundle references, addresses, purchase order and service dates into the receiving system. Retain the destination’s reference with the delivery outcome.
• Delivery evidence. Record shipment or provisioning quantities separately from customer acceptance. A billing milestone uses the specific event and extent of completion agreed for it.

• Invoices and credits. Preserve source line, product, revenue category, service period and tax provenance. Keep local preparation separate from confirmed external posting and retain the accounting reference.
• Cash and corrections. Import payments with stable source references, and exchange applications, returns, refunds and credit effects without applying the same money twice. Finance owns matching exceptions and reconciliation.
• Tax ownership. Agree whether configured supported cases are calculated locally or accounting supplies the final tax. Missing tax is unresolved, and accounting-owned totals must return before an invoice is sent or settled.

• Email. Use the company’s configured sending identity for quote links, invoices, reminders and notices. Preserve delivery status and suppress historical messages during migration.

Give each connection a scoped identity, an owner and an explicit set of actions. Retain event keys, payload digests and per-destination delivery outcomes. Repeated delivery should reuse the prior result; conflicting content or an uncertain remote outcome needs reconciliation before a retry could create another signature request, order or financial posting. Pausing a connection must leave its unfinished work visible.