🚀 JPS FinanceOS Beta — available 1 July 2026  ·  Apply for early access →
JPS-iQ Group FinanceOS Suite Documents
Module 8 · 9 · 10 · Document Intake · DMS · Legal Queue

Every incoming document — classified, routed and archived. Automatically.

JPS FinanceOS Document Intelligence receives every inbound document — from email, scan, upload or SharePoint — processes it with Azure AI OCR, classifies it and routes it to the right destination: AP Inbox, Treasury, Document Archive, or Legal Queue. Your archive stays in your own SharePoint. No data silo.

OCRAzure AI Document Intelligence
ArchiveYour own SharePoint · GoBD 10 years
LegalAutomated escalation routing
The document operations gap

Invoices in email. Contracts in a shared drive. Court letters in someone's inbox.

Document operations in most mid-market finance teams are an unsolved problem — not because a solution doesn't exist, but because the existing solutions require a full DMS implementation, significant IT effort and ongoing maintenance. JPS FinanceOS solves this differently: your documents stay in your SharePoint. We bring the intelligence layer.

NOW
Typical document operations today

Manual. Error-prone. No audit trail.

Invoices arrive as email attachments. Someone downloads, renames and files them manually. Approvals happen via email reply. The "archive" is a shared drive with inconsistent folder structures that nobody searches. Legal documents — court notices, enforcement orders — sit in an email inbox until someone happens to open them. Response deadlines are missed. GoBD compliance is aspirational.

Before
  • Invoices manually filed from email
  • No OCR — documents not searchable
  • Legal letters sitting unread for days
  • Archive in shared drive — inconsistent structure
  • GoBD retention not enforced
  • No link between document and ERP record
With JPS FinanceOS
  • All inbound documents received and processed automatically
  • Azure AI OCR — every document fully indexed and searchable
  • Legal letters escalated immediately to the right person
  • Archive in your own SharePoint — GoBD-compliant, 10-year retention
  • Retention policy enforced automatically per document type
  • SharePoint URL written back to ERP record after archiving
Module 8 · Document Intake & Intelligence

The intelligent front door for every inbound document.

Module 8 is not a document archive — it is the intelligent intake channel that receives, reads, classifies and routes every incoming document. The archive (Module 9) and the legal escalation queue (Module 10) are separate, downstream destinations.

Module 8 — Document Intake & Intelligence

Receive → OCR → Classify → Route — without human intervention

Every inbound document — regardless of channel — passes through the same processing pipeline. Azure AI Document Intelligence performs OCR on every document, extracting structured data (amounts, IBANs, dates, party names, invoice numbers). The classification engine then identifies the document type and routes it to the correct downstream module.

EMAIL Email attachment Dedicated inboxes (rechnungen@, vertraege@) — Power Automate triggers on attachment receipt
SCAN Document scan Physical mail scanned and uploaded via web interface or MFP integration
UPLOAD Direct upload Drag-and-drop upload in FinanceOS — single documents or batch import
SP SharePoint drop folder Documents placed in a configured SharePoint folder are automatically picked up and processed

Routing — every document type goes to the right place

After classification, FinanceOS routes each document to its designated destination module. Routing is deterministic — based on document type, not on user action. No manual sorting required.

Document type Examples Destination
INVOICE Vendor invoices, credit notes AP Inbox (Module 4)
PAYMENT_REMINDER First and second dunning notices from vendors AP Inbox (Module 4)
BANK_STATEMENT CAMT.053 / CAMT.054 bank statements and confirmations Treasury (Module 2)
CONTRACT Supplier contracts, service agreements, NDAs DMS / SharePoint Archive (Module 9)
GENERAL_DOC Correspondence, confirmations, general attachments DMS / SharePoint Archive (Module 9)
DUNNING_3 Third dunning notices, final demand letters Legal Queue (Module 10)
COURT_NOTICE Payment orders (Mahnbescheide), court summons Legal Queue (Module 10)
ENFORCEMENT Enforcement orders (Vollstreckungsbescheide) Legal Queue (Module 10)
TAX_NOTICE Tax assessments, notices from Finanzamt Legal Queue (Module 10)
Module 9 · Document Archive & DMS

Your documents. Your SharePoint. Our intelligence.

The most important decision in the DMS module: where does the archive live? JPS FinanceOS stores all documents in the customer's own SharePoint via Microsoft Graph API — not in a JPS-hosted storage system. Your data sovereignty is structural, not a policy.

Architecture decision — not a configuration option

The archive lives in your SharePoint — not in a JPS data silo

Many DMS systems require you to migrate your documents into their proprietary storage. JPS FinanceOS takes the opposite approach: the archive is your own SharePoint site, accessed via Microsoft Graph API. JPS provides the intelligence layer (OCR, classification, routing, full-text search, retention enforcement) — the documents themselves never leave your Azure environment.

Module 9 — GoBD-Compliant Archive

Compliant document management — without a separate DMS product

  • Primary storage: customer's own SharePoint via Microsoft Graph API
  • Fallback storage: Azure Blob (JPS-hosted) if SharePoint not configured
  • GoBD-compliant retention: 10 years for invoices, configurable per document type
  • Retention enforced automatically — documents cannot be deleted before retention period expires
  • Read-only archive: archived documents are immutable — modification creates a new version
  • Full-text search across all archived documents via OCR-extracted content
  • SharePoint URL written back to ERP after archiving — ERP shows the link, document stays in SharePoint
  • Approval workflow engine: configurable approval chains per document type and amount threshold

ERP write-back — the link between document and ERP record

After a document is archived, its SharePoint URL is written back to the corresponding ERP record via the bidirectional connector. In NetSuite: the linked file URL is attached to the Vendor Bill, Customer Invoice or Contract record. The ERP record shows the link — clicking it opens the document directly in SharePoint. No duplicate storage.

Beta · 1 July 2026

See intelligent document intake live — in your SharePoint environment.

30-minute live demo. We configure a test inbox, run documents through the OCR and classification pipeline, and show how the Legal Queue escalation works.

Explore other modules