Sovereign Enterprise Operational Intelligence

What SEOI means

SEOI is an intelligence layer on the enterprise backend systems you already run — ERP and accounting Systems of Record, audit software, and government tax authorities — where sovereignty and security are non-negotiable. Assist, not autopilot. The books stay where they are.

1. Sovereign

   Data, models, embeddings, and logs stay inside the customer boundary — on-prem, private cloud, or air-gap-capable. No public LLM API path for confidential invoices, customers, or prompts.

2. Enterprise

   Real books and systems of record already in place — Digiwin, CHI, and peers. Buyers include corporate finance/ops and accounting, audit, and CPA practices. VARs attach the overlay; we do not sell around you.

3. Operational

   Day-to-day document → match → verify → confirm → voucher workflows around the books. Exceptions are the work — partial bills, missing goods receipt, price variance — not MRP or strategy chat.

4. Intelligence

   An overlay that reads documents, discovers governing records, runs deterministic customer rules, and prepares cited evidence packets. Assist and verification only — never autopilot posting.

Core operational workflows

Same case desk for four production AP/AR workflows. SEOI books payable or receivable vouchers after two-person confirmation; it does not pay vendors or record customer cash.

• AP — Standard Purchase — Automates 3-way matching across purchase orders, goods receipts, and supplier (uniform) invoices — including partial billing and tolerance handling — then prepares the payable / purchase-tax packet for human confirmation.
• AP — Operational Expense — Handles non-PO vendor bills, recurring utilities, and operational service expenses: match to vendor master and terms, enforce mandatory expense/sub-account and cost-center classification, prepare Other Payables voucher packet.
• AP — Subcontract Processing — Governs outsourced manufacturing and multi-invoice processing lots: reconcile processing invoices to outsourced receipts, work orders, and quotations; one payable/voucher per invoice after approval.
• AR — Export & Domestic Sales — Reconciles export (and domestic sales) dossiers — including multi-document traversal, customs FX realization, and customer onboarding — then prepares receivable / revenue voucher packets for confirmation.

Demo may also show remittance matching / related intake; tax, audit assist, and liquidity modules are Phase 2 — not live equal offers.

How a case works

Same path for every workflow on the desk:

• Upload → My Docs (image vs fields) → Send to workflow (Suggested is only a guess)
• Case comparison: green agrees; red must fix; a close mismatch needs human accept; optional missing needs a reason. Verification states: Pass / Follow-up / Fail / Unable.
• Confirm → Wait for Approval → voucher PDF preview after Approve
• Two-person segregation of duties: the preparer cannot approve their own case. Nothing posts until a second person approves.
• These workflows book payable or receivable vouchers — they do not pay the vendor or record customer cash.

Governance

Assist, not autopilot. SEOI prepares cited packets; humans remain accountable. Two-person SoD before write-through. Compact six: determinism, provenance, auditability, sovereignty, security, and HITL. See Security & sovereignty for architecture intent.

Integration & pilot

• Start with export / snapshot data to prove value — no ERP write API required for the first pilot
• API connectors when available for controlled read/write later; read-only SQL only as a last-resort lookup fallback — never write via SQL
• Write-through waits for preparer confirm and a second-person approve. The ERP remains the system of record.

The ERP is the system of record the demo can write to, and only after that confirmation. Accounting software is the same kind of system of record when the books are kept there; that connection is intended, not live. Auditing software and a government tax-authority portal are other backend systems — intended, not live.

Channels operators already use — Web, email, and messaging apps such as LINE, WeChat, WhatsApp, or Telegram — with role-based access and audit logs.

For partners

Attach the intelligence layer to your Digiwin/CHI (or similar ERP) installed base. You own the customer relationship — we do not sell around you.

What we ask for a first design-partner motion:

• 3–5 named account candidates willing to explore a pilot
• A demo of the case desk across the four core AP/AR workflows; a first pilot may select 1–2 high-volume flows
• Agreed pilot path: Target scope → Snapshot proof → Governance setup → Connector activation
• A first pilot can start from an export or snapshot. Write-through waits for two-person confirmation.

Boundaries

• In: intelligence overlay on systems you already run; four core AP/AR workflows; HITL with two-person SoD
• Held out: rip-and-replace ERP; autonomous ledger posting without sign-off; autopilot payment or wire; public-cloud model APIs for confidential payloads; SQL write path; ISO certification sales
• Phase 2 labels (not live equal): tax reporting (TX-1), financial auditing / tax auditing (AU-1 / AU-2), liquidity / cash (FN-1 / FN-2)