OpenText Active Documents Trading Grid - OpenText Active Community - Trading Grid Integration and Automation

Common Integration Use Cases Between OpenText Active Documents Trading Grid and OpenText Active Community - Trading Grid

• 1. Exception handling for failed B2B document transactions

  Data flow: OpenText Active Documents Trading Grid ? OpenText Active Community - Trading Grid

  When an invoice, purchase order, or shipping notice fails validation or delivery in Trading Grid, the transaction details and error context are posted into Active Community for partner and internal operations teams to review. This allows buyers, suppliers, and support teams to resolve issues in a shared workspace instead of relying on email chains or manual follow-up.

  Business value: Faster resolution of document errors, fewer delayed shipments or payments, and improved partner responsiveness.

• 2. Collaborative dispute resolution for invoice and order mismatches

  Data flow: Bi-directional

  Trading Grid sends the original transaction documents and status updates to Active Community, while users in the community add comments, request clarifications, and attach supporting evidence such as corrected invoices or packing slips. Once the issue is resolved, the updated outcome is reflected back in Trading Grid to maintain a complete audit trail.

  Business value: Reduces time spent reconciling mismatched documents and improves accuracy in financial and supply chain processes.

• 3. Partner onboarding and trading setup coordination

  Data flow: OpenText Active Community - Trading Grid ? OpenText Active Documents Trading Grid

  During onboarding of a new supplier, carrier, or retailer, Active Community is used to coordinate testing, share implementation instructions, and track readiness tasks. Once the partner is approved, Trading Grid is configured with the required document flows, routing rules, and transaction profiles based on the onboarding outcome.

  Business value: Shortens partner activation cycles and reduces setup errors across trading relationships.

• 4. Shipment exception collaboration and corrective action tracking

  Data flow: OpenText Active Documents Trading Grid ? OpenText Active Community - Trading Grid

  When shipping notices, delivery confirmations, or transport-related documents indicate a delay, shortage, or mismatch, the exception is automatically published to Active Community. Logistics, customer service, and partner teams can coordinate corrective actions such as rerouting, rescheduling, or issuing revised documents.

  Business value: Improves supply chain visibility and helps prevent downstream service disruptions.

• 5. Shared document review for compliance and audit requests

  Data flow: Bi-directional

  Trading Grid stores and transmits the official transaction documents, while Active Community provides a controlled collaboration space for compliance teams, auditors, and trading partners to review supporting evidence, discuss exceptions, and confirm remediation steps. Relevant documents and responses can be linked back to the original transaction record.

  Business value: Strengthens audit readiness, supports regulatory compliance, and reduces the effort required to gather evidence.

• 6. Partner communication for recurring transaction failures

  Data flow: OpenText Active Documents Trading Grid ? OpenText Active Community - Trading Grid

  If a trading partner repeatedly sends documents with the same formatting or mapping issue, Trading Grid can trigger a community discussion thread or case for that partner. Operations teams can share examples, correction guidance, and agreed remediation steps in one place, while monitoring whether the issue is resolved over time.

  Business value: Reduces repeat defects, lowers support workload, and improves partner document quality.

• 7. Cross-functional coordination for high-priority transaction escalations

  Data flow: Bi-directional

  High-value or time-sensitive transactions in Trading Grid, such as critical purchase orders or urgent shipping notices, can be escalated into Active Community when they require immediate attention from procurement, logistics, finance, and the partner account team. Status updates, decisions, and attachments are shared in the community and synchronized back to the transaction record.

  Business value: Speeds decision-making for critical transactions and reduces the risk of revenue loss or service failure.