Integrations

Reviewed imports may carry style, color, size, season and assortment identifiers from the customer’s design or merchandising source. A source label does not approve a BOM, substitute a SKU or establish a live PLM/commerce connection.

• Bank statements. Map statement entries to the correct company account, currency and bank reference. Detect repeated imports and reconcile entries to receipts, payments and charges before treating them as cleared.
• Payment instructions. Keep authorization, file creation, transmission, bank acceptance and settlement as separate events. An upload acknowledgement does not prove payment. Preserve the payment reservation while an outcome is uncertain, and investigate before sending another instruction.
• Payroll payments. Generate instructions only from eligible approved payroll under the agreed release controls. Parallel payroll produces comparison evidence without creating bank instructions. Reconcile the actual settled amount and any rejection to the approved run.

• EDI and order channels. Map external purchase orders, acknowledgements, invoices and shipment notices to the correct customer, entity and source document. Repeated messages reuse their external identity; exceptions stay available for review.
• Storefronts and portals. Agree which products, prices and stock availability may be published. Incoming orders still follow credit and approval rules. Portal access, customer acceptance and supplier uploads require their own tested identity and document boundaries.
• E-signature. Tie the signature result and signed artifact to the exact offer or agreement revision sent. A changed price or term requires renewed acceptance rather than reusing an earlier signature.

• Tax calculations and filings. Confirm the jurisdictions, tax treatments and filing formats the chosen service supports. Retain the calculation inputs, service response and filing confirmation. A configured tax code alone does not establish compliance coverage.
• Payroll providers. Define responsibility for statutory calculations, remittances and year-end documents by country. Match employee elections and effective dates before importing calculated components; reconcile results to the reviewed payroll and ledger.

• Carriers. Test rates, labels, tracking and delivery evidence against the selected shipping service. Shipment status and the carrier’s delivery response retain separate histories.
• Scanners and time devices. Validate employee or warehouse identity, units and duplicate-event handling. A repeated scan or clock event must not receive goods, ship stock or pay time twice.
• CAD and product systems. Review imported products, bills of material and routings before release. Existing work orders retain their approved production revisions and cost assumptions.

• Identity providers. Map company access and role assignments explicitly, including leavers and delegated authority. Removing a login does not erase the employee’s historical transactions.
• Benefits and time services. Import proposed elections, deductions or time into the applicable effective period. Approved time and leave need reconciliation before payroll consumes them.
• Reporting platforms. Export agreed posted and operational datasets with entity, period and currency context. Apply the same payroll privacy and commercial cost restrictions to exports as to the application.

Each connection needs a named owner, restricted service identity, credential policy and observable failure queue. Agree its source identifiers, replay behavior, approval boundaries and reconciliation totals before activation. Store sensitive payloads under the relevant access rules. A provider response can support a business decision; it cannot replace the human approval required by that process.