OpenText Active Documents Trading Grid - OpenText Core Content - Metadata Integration and Automation

Common Integration Use Cases Between OpenText Active Documents Trading Grid and OpenText Core Content - Metadata

1. Auto-classify incoming trading documents with governed metadata

Direction: OpenText Active Documents Trading Grid ? OpenText Core Content - Metadata

When purchase orders, invoices, shipping notices, or order acknowledgements arrive through Trading Grid, the documents can be routed into Core Content and assigned standardized metadata such as document type, supplier ID, plant, region, order number, and transaction date. This improves search, retention, and downstream automation.

Business value: Faster retrieval, consistent classification, and reduced manual indexing effort for AP, procurement, and logistics teams.

2. Enforce metadata rules for outbound partner documents

Direction: OpenText Core Content - Metadata ? OpenText Active Documents Trading Grid

Before documents are sent to trading partners, Core Content can validate required metadata fields such as customer account, shipment reference, contract ID, or compliance category. Only documents that meet the approved metadata rules are released through Trading Grid.

Business value: Fewer rejected transactions, better partner data quality, and stronger control over what is shared externally.

3. Link B2B transaction records to governed content archives

Direction: Bi-directional

Trading Grid can deliver the operational transaction, while Core Content stores the supporting document set with metadata that ties each file to the business event. For example, an invoice, packing slip, and proof of delivery can all be associated with the same order and supplier record for audit and dispute resolution.

Business value: End-to-end traceability, easier audits, and faster resolution of billing or shipment disputes.

4. Improve partner document search and reporting

Direction: OpenText Active Documents Trading Grid ? OpenText Core Content - Metadata

Documents exchanged with suppliers, carriers, or retailers can be stored in Core Content with metadata that supports reporting by partner, document status, transaction type, and business unit. This enables operations teams to analyze document volumes, late submissions, and exception trends across the supply chain.

Business value: Better visibility into partner performance and document processing bottlenecks.

5. Support exception handling for incomplete or non-compliant documents

Direction: OpenText Active Documents Trading Grid ? OpenText Core Content - Metadata

If a received document fails validation or is missing required business data, Trading Grid can still pass it to Core Content with exception metadata such as error code, partner name, and resolution owner. This allows compliance, AP, or customer service teams to track and remediate issues in a controlled workflow.

Business value: Faster exception resolution, fewer lost documents, and clearer ownership of corrective actions.

6. Govern retention and lifecycle policies for exchanged documents

Direction: OpenText Core Content - Metadata ? OpenText Active Documents Trading Grid

Core Content metadata can determine retention class, legal hold status, or regulatory category for documents that will be exchanged through Trading Grid. This ensures that outbound and inbound business documents are handled according to corporate policy and industry requirements.

Business value: Stronger compliance, reduced legal risk, and consistent records management across partner transactions.

7. Create a single source of truth for supplier and customer document packages

Direction: Bi-directional

Trading Grid manages the secure exchange of business documents, while Core Content maintains the structured metadata needed to assemble complete document packages for suppliers, customers, or auditors. For example, a vendor onboarding package can include contracts, tax forms, certificates, and correspondence, all indexed under a common metadata model.

Business value: Better cross-team collaboration, fewer duplicate records, and a complete business context for each partner relationship.