Generative AI Document Integration With Metadata-Guided Field Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing document integration systems require significant human expertise and effort for onboarding and transaction integration with trading partners, as they struggle to accurately and reliably transform documents of varying formats, languages, and electronic channels into structured database formats.

Innovation Solution

Utilizing generative artificial intelligence (AI) enriched with metadata about historical document characteristics to transform documents into fields and values, by detecting field locations and updating prompt templates, and integrating results into databases, while leveraging retrieval augmented generation (RAG) for continuous learning and improvement.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If traditional document integration systems are used to transform documents of varying formats and languages into structured database formats, then document transformation capability is maintained, but significant human expertise and effort are required for onboarding and transaction integration

Engineering Contradiction:
Improvedocument transformation automationVSAvoidsystem complexity
Core Design Contradiction:
Extent of automationVSDevice complexity

Solution Approach 1:

The system enables self-service document transformation by automatically detecting document types, extracting fields, and adapting to new document formats without requiring human expertise for onboarding. The system serves itself by learning from historical document characteristics and continuously improving its transformation capabilities through metadata enrichment and prompt template updates.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system changes parameters by dynamically adjusting prompt templates based on detected document types and historical metadata. It transforms documents by varying the extraction parameters and field definitions according to the specific document format, language, and structure, allowing automatic adaptation to different document types without manual reconfiguration.

Inventive Principle:
Principle #35Parameter changes

2Measurement precision

If traditional document integration systems transform documents with varying formats, languages, and electronic channels, then document compatibility is maintained, but accuracy and reliability of transformation deteriorate

Engineering Contradiction:
Improvefield detection accuracyVSAvoiddocument format adaptability
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary action by pre-processing documents through OCR and language detection before extraction, and by pre-defining prompt templates based on historical document characteristics. This preliminary preparation enhances the accuracy of field detection while maintaining adaptability to various document formats through pre-established transformation patterns.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses feedback by continuously learning from detected field locations and values, updating metadata and prompt templates based on historical document characteristics. This feedback mechanism improves detection accuracy over time while maintaining versatility across different document types through adaptive learning from diverse document formats.

Inventive Principle:
Principle #23Feedback

3Productivity

If manual onboarding and integration processes are used with trading partners, then human control and verification are maintained, but operational efficiency and productivity deteriorate

Engineering Contradiction:
Improvetransaction processing speedVSAvoidonboarding simplicity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system enables self-service onboarding by automatically detecting trading partner document formats, extracting necessary fields, and configuring transformation pipelines without manual intervention. This eliminates the need for human expertise in onboarding while maintaining ease of operation through automated adaptation to partner-specific document structures.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system achieves universality by handling multiple document formats, languages, and electronic channels through a single integrated platform. It maintains ease of operation by providing a unified interface that automatically adapts to different trading partners' requirements, eliminating the need for separate onboarding processes for each partner type.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Device complexity

If external transformation processes are used for document integration, then transformation capability is maintained, but the need for external systems and interfaces increases complexity

Engineering Contradiction:
Improvesystem architecture simplicityVSAvoiddocument transformation capability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The system merges document transformation capabilities directly into the database integration process, eliminating the need for separate external transformation systems. By combining OCR, language detection, field extraction, and database integration into a single unified system, it reduces architectural complexity while maintaining full transformation capability through integrated AI-powered processing.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS20260072992A1Adaptive document integration using generative artificial intelligence
Publication Date: 2026.03.12 ORACLE INT CORP
  • US20260072992A1 patent drawing
  • US20260072992A1 patent drawing
  • US20260072992A1 patent drawing

AI summary

Systems, methods, and computer-readable media are provided for using generative AI enriched with metadata about historical document characteristics to transform documents of various formats, including images, to the fields and values they represent. A prompt template may be selected in association with a type of document. The prompt template indicates field definition(s) of field(s) to be detected in the document and location(s) in which the field(s) have been detected in prior documents. A large language model is prompted with a prompt generated using the prompt template to generate a result that assigns value(s) to the field(s). Output from the language model is used for identifying the field to value mapping for the document, such that data detected from the document may be stored in appropriate database structures of a database. Metadata stored in association with the prompt template is updated based on location(s) in the document in which the field(s) were detected, and the value(s) of the field(s) are stored in a database. Outbound documents may be similarly translated to detect values of corresponding fields requested by third parties, even if those values are not stored in the database. In this scenario, values for fields may be detected in outbound documents using the prompt templates enriched with metadata as processed by the large language model before such information is prepared to be sent to a third party.