Cimpleit/DataIQ Platform
ERP integration & data operations platform

DataIQ

The integration layer connecting LicenseIQ to Oracle Cloud ERP and EDI trading partners — exposing clean, validated data operations through a structured API so enterprise data moves reliably, every time.

Sign in to DataIQ → Talk to our team
OracleCloud ERP native integration
EDITrading partner connectivity
MCPAI-accessible tool interface
100%Idempotent write-back operations
The problem

ERP data doesn't move
cleanly on its own.

Every Oracle ERP transaction — invoice, receipt, journal entry — requires data to be fetched, validated, transformed, and submitted with the right identifiers, in the right format, at the right time. Doing this directly from LicenseIQ means tightly coupling business logic to Oracle API details that change without notice.

DataIQ sits in between — translating clean, named operations into the exact Oracle API calls required — so LicenseIQ stays focused on business logic and DataIQ owns the integration complexity.

DecoupledOracle API complexity isolated from LicenseIQ business logic — changes in one don't cascade to the other
IdempotentEvery write-back tool uses posting_log to ensure at-most-once submission — safe to retry without duplicate Oracle transactions
AuditableEvery sync, every write, every rule evaluation logged — with client-scoped context for full traceability
Platform modules

Three layers for the
full integration lifecycle.

DataIQ covers data from source to destination — syncing it reliably, transforming it accurately, and routing it safely into Oracle.

🔄
Transaction Sync
Scheduled, per-client synchronisation of Oracle AR invoices, receipts, and credit memos into DataIQ's store for LicenseIQ to consume

DataIQ pulls Oracle Receivables data on configurable schedules — per client, per transaction type. Each sync run is tracked with a freshness threshold, so LicenseIQ always knows how current its data is. Syncs are idempotent: re-running doesn't duplicate records. The Admin UI gives full visibility into sync history, last-run status, and per-client configuration — without touching Oracle directly.

Per-client sync configuration
Each client has independent sync schedules, Oracle path overrides, query parameters, and freshness thresholds — configurable through the Admin UI without code changes.
AR invoices, receipts, credit memos
Supports receivablesInvoices (INV, CM, DM, CB) and standardReceipts — with correct Oracle ID field mapping and expand parameter handling per resource type.
Freshness tracking
Every sync run records its timestamp. LicenseIQ tools surface data age alongside results — so stale data is visible, not silently consumed.
Idempotent upserts
Sync runs upsert on Oracle's natural ID — re-running a sync updates existing records rather than creating duplicates, making retries safe.
Admin UI monitoring
Sync history, last-run timestamps, error counts, and per-client config all visible in the Admin UI — with manual trigger and schedule override controls.
Bootstrap sync
One-time historical data load for new clients — pulls all available Oracle history into DataIQ before the regular scheduled sync takes over.
⚙️
Write-Back Tools
Idempotent MCP tools for posting journals, applying receipts, and submitting Oracle transactions — safe to call from LicenseIQ AI agents

LicenseIQ AI agents call DataIQ write-back tools to post data into Oracle. Every tool is wrapped with posting_log idempotency — the first call submits to Oracle and caches the response; subsequent calls with the same idempotency key return the cached result without re-submitting. COA segments are derived dynamically from a rules engine before each submission, with optional live Oracle validation.

Journal import batches
Posts journal import batches to Oracle GL — with COA derivation, segment validation, and posting_log idempotency to prevent duplicate journal entries.
Receipt application
Applies Oracle standard receipts to open invoices — with correct lockbox and receipt method handling per client Oracle instance configuration.
COA rules engine
Derives Oracle Chart of Account segments from a configurable rules engine — client-specific rules evaluated in priority order, with optional live Oracle FSCM validation.
posting_log idempotency
Composite unique key (client_id, tool, idempotency_key) prevents false deduplication across clients. Cached responses returned for retries — Oracle never sees duplicate submissions.
UDF translation
Client-specific UDF definitions and value mappings translate LicenseIQ field values into Oracle-expected codes — with translation_gaps surfaced when mappings are missing.
MCP tool interface
All write-back operations exposed as named MCP tools — LicenseIQ agents call them by name with structured inputs, never making direct Oracle API calls.
🔗
EDI Integration
EDI trading partner connectivity for 850 POs, 810 invoices, 856 ASNs, and 997 acknowledgements — managed through the Admin UI

DataIQ provides the framework for EDI integration with trading partners — Walmart, Target, Costco, and others. EDI documents are exchanged via AS2 (Mendelson) and SFTP, with per-partner transaction sets managed through the Admin UI. Inbound documents are parsed and stored; outbound documents are generated from DataIQ data and transmitted on schedule.

AS2 & SFTP transport
Mendelson AS2 handles partners requiring encrypted, signed document exchange. SFTP handles partners using file-drop delivery — both managed through the Admin UI partner configuration.
850 / 810 / 856 / 997
Purchase orders (850), invoices (810), advance ship notices (856), and functional acknowledgements (997) — per-partner transaction sets configured independently.
Per-partner configuration
Each trading partner has its own ISA/GS qualifiers, transport settings, transaction set enablement, and schedule — all configurable in the Admin UI without code changes.
Document tracking
Every inbound and outbound EDI document is logged with interchange control numbers, partner ID, transaction type, and processing status for audit and troubleshooting.
997 acknowledgement handling
Functional acknowledgements are tracked per interchange — accepted, rejected, and pending 997s visible in the Admin UI for each trading partner.
LicenseIQ MCP exposure
EDI data surfaces to LicenseIQ through named MCP tools — partner lists, document status, and transaction queries available without direct EDI system access.
How it works

From Oracle data to
LicenseIQ AI agent.

Step 01
Schedule & sync
DataIQ pulls Oracle Receivables data on per-client schedules — invoices, receipts, credit memos — and stores them locally with freshness timestamps. Syncs are idempotent and retryable.
Step 02
Expose via MCP
LicenseIQ AI agents call named MCP tools to query synced data, look up client configurations, and trigger write-back operations — never making direct Oracle API calls.
Step 03
Derive & validate
For write-back, COA segments are derived from the rules engine, UDF values are translated using client-specific mappings, and inputs are validated against Zod schemas before Oracle submission.
Step 04
Post & log
Validated payloads are posted to Oracle with posting_log idempotency. Responses are cached per idempotency key. Retries return cached results — Oracle never sees duplicates.
Who it's for

Built for teams running
Oracle ERP operations.

LicenseIQ Operators
Use DataIQ's Admin UI to configure and monitor per-client sync schedules, COA rules, and write-back settings — without touching Oracle or LicenseIQ code.
Per-client sync configuration in the UI
Sync history and freshness monitoring
COA rules and UDF mappings management
Oracle ERP Teams
DataIQ handles the Oracle API complexity — correct ID fields, expand parameters, OU scoping, and SCIM query constraints — so ERP teams don't have to coach every consumer.
Oracle API quirks isolated in one place
Idempotent write-back prevents duplicate postings
Posting log for full audit trail
EDI Trading Partner Managers
Configure and monitor EDI trading partners — transport settings, transaction sets, and document status — through the DataIQ Admin UI.
Per-partner transport and transaction configuration
Document tracking and 997 acknowledgement status
AS2 and SFTP partner management in one place
LicenseIQ AI Agents
Consume DataIQ via MCP tools — named, structured operations that abstract Oracle API calls, return validated data, and handle idempotency automatically.
Named MCP tools, never raw Oracle API calls
Structured inputs validated by Zod schemas
Translation gaps surfaced, not silently dropped
Implementation Engineers
Onboard new clients by configuring Oracle connection settings, sync schedules, COA rule sets, and UDF mappings — all through the Admin API and UI.
Client configuration without code changes
Bootstrap sync for historical data load
Per-client oracle_path_override and query_params
Finance Operations
Trust that Oracle data surfaced by LicenseIQ is current, complete, and traceable — with DataIQ freshness timestamps and posting logs providing the audit trail.
Data freshness visible on every LicenseIQ response
Posting log for every Oracle write-back operation
No silent failures — gaps and errors surfaced explicitly
📋
LicenseIQ Platform
The AI-powered contract and billing intelligence layer that consumes DataIQ's MCP tools to surface Oracle data and drive financial operations.
Explore LicenseIQ →
🛠️
OpsIQ Platform
Agentic Oracle managed services — from environment assessment and benchmarking to autonomous issue resolution with human-in-the-loop controls.
Explore OpsIQ →

Ready to connect LicenseIQ
to Oracle?

DataIQ is the integration layer your Oracle ERP operations need — reliable syncs, idempotent write-backs, and a clean MCP interface for LicenseIQ AI agents.

Sign in to DataIQ → Talk to our team