Home | Connectors | OpenText Active Documents Trading Grid | OpenText Active Documents Trading Grid - OpenText Core Case Integration and Automation
Data flow: OpenText Active Documents Trading Grid ? OpenText Core Case
When supplier invoices are received through Trading Grid, invoices that fail validation, mismatch purchase orders, or arrive with missing data can be automatically routed into a Core Case for review and resolution. Accounts payable teams can work the exception in a structured case that includes the original invoice, related purchase order, shipment documents, and internal comments. This reduces manual follow-up, shortens resolution time, and improves invoice processing accuracy.
Data flow: OpenText Active Documents Trading Grid ? OpenText Core Case
If a trading partner disputes a purchase order, quantity, price, or delivery term, the related order documents and correspondence from Trading Grid can be packaged into a Core Case. Procurement, sales, and operations teams can collaborate in one place to investigate the issue, track actions, and document the final decision. This creates a clear audit trail and helps prevent repeated disputes with the same partner.
Data flow: OpenText Active Documents Trading Grid ? OpenText Core Case
Shipping notices, advanced shipment notifications, and delivery confirmations exchanged through Trading Grid can trigger a Core Case when a shipment is delayed, partially delivered, or does not match the expected schedule. Logistics teams can use the case to coordinate with carriers, warehouses, and customer service, while maintaining visibility into the original transaction documents. This improves response time and helps protect customer commitments.
Data flow: OpenText Active Documents Trading Grid ? OpenText Core Case
In manufacturing, retail, or logistics, partner-submitted claims such as damaged goods, shortages, or incorrect shipments can arrive through Trading Grid and be converted into a Core Case for investigation. The case can include invoices, packing slips, proof of delivery, and photos or supporting evidence. Claims teams gain a controlled workflow for review, approval, reimbursement, or rejection, reducing cycle time and improving consistency.
Data flow: OpenText Active Documents Trading Grid ? OpenText Core Case
Transaction documents exchanged with suppliers or distributors can be monitored for compliance exceptions, such as missing mandatory fields, late submissions, or policy violations. When an exception is detected, a Core Case can be created for compliance officers to review the issue, request remediation, and record the outcome. This supports stronger governance and makes it easier to demonstrate compliance during audits.
Data flow: OpenText Active Documents Trading Grid ? OpenText Core Case
When customer service receives an order-related complaint, the original purchase order, invoice, and shipping documents from Trading Grid can be linked into a Core Case. Service agents, order management, and finance teams can then collaborate to resolve pricing errors, missing items, or fulfillment problems. This gives customer-facing teams faster access to transaction history and improves first-contact resolution.
Data flow: Bi-directional
During onboarding of new trading partners, Trading Grid can exchange required documents such as agreements, certifications, and setup forms, while Core Case manages any onboarding issues, approvals, or follow-up tasks. If a partner submits incomplete or incorrect documentation, a case can be created for internal review and resolution. Once the issue is resolved, status updates or approval outcomes can be sent back to Trading Grid to continue the onboarding process. This creates a controlled and traceable partner activation workflow.
Data flow: OpenText Core Case ? OpenText Active Documents Trading Grid
After a case is resolved in Core Case, the final decision, corrective action, or updated transaction document can be sent back through Trading Grid to the trading partner. Examples include corrected invoices, revised shipping instructions, claim outcomes, or approved exceptions. This ensures external partners receive timely, authoritative updates and helps close the loop between internal resolution and external document exchange.