JPS FinanceOS connects directly to your existing ERP — NetSuite today, Business Central next quarter — and delivers real-time cash visibility, automated 4-eyes payment approval, direct EBICS banking connectivity and a complete audit trail. No ERP replacement. Live in under 30 days.
Mid-market finance managers start every day the same way: NetSuite for open invoices, the bank portal for account balances, Excel for the cash forecast, Outlook for payment approvals, and a document folder for receipts. JPS FinanceOS is the missing connection layer.
| Without FinanceOS — today | With JPS FinanceOS |
|---|---|
| No real-time cash visibility — data scattered across banks, ERP and Excel | Live cash position across all accounts and currencies in one view |
| Payment approvals via email — no audit trail, no enforceable process | 4-eyes approval with configurable limits and immutable audit log |
| EBICS setup takes weeks and IT resources | 50 major German banks pre-configured — KONFIPAY setup in minutes, no certificate ceremony |
| Liquidity forecasting is a manual Excel exercise done too rarely | 13-week rolling forecast with Conservative / Realistic / Optimistic scenarios, updated daily |
| ERP and bank are disconnected — reconciliation is manual | Bidirectional NetSuite / D365 BC integration including payment status write-back |
| No clear audit trail — who approved what, when, from which IP? | Immutable append-only audit log on every action, sync and data transformation |
Every FinanceOS plan is built on the same four operational pillars. Each one replaces a manual, fragmented or unaudited process with a governed, real-time and ERP-connected alternative.
Live consolidated cash position across all bank accounts, currencies and entities. Cash Runway, Days Cash on Hand, Burn Rate and FX exposure — updated as transactions arrive. No more end-of-day reports, no more Excel aggregation.
Configurable 4-eyes principle — the originator cannot approve their own payment. Amount limits per role (e.g. up to €5k: Treasury Manager, above: Finance Director). Every decision logged immutably. EBICS submission fully automated after approval.
Three connection methods: JPS Native EBICS 2.5/3.0, KONFIPAY managed gateway (no certificate ceremony — fastest onboarding), and Open Banking / PSD2 for international accounts including Wise Business. 50 major German banks pre-configured.
NetSuite is live. Business Central follows Q3 2026. Payments flow from your ERP into FinanceOS for approval and EBICS execution — confirmation and payment status write back automatically. Cash-in-Transit cleared only after bank confirmation.
NetSuite creates Payment Run and books to Cash-in-Transit account
JPS FinanceOS retrieves the payment data via secure OAuth2 / TBA connector
Finance Director approves in FinanceOS — 4-eyes principle enforced, logged immutably
EBICS submission to bank — fully automated after approval
Bank confirms — JPS writes payment status and EBICS reference back to NetSuite
NetSuite clears Cash-in-Transit and posts to actual bank account — only after bank confirmation
We show you FinanceOS live — with a real NetSuite environment and real bank accounts. 30 minutes.
Book a live demoThe three modules below exist in the enterprise world — in platforms that cost EUR 500k–5M to implement and require 12–24 months of rollout time. JPS FinanceOS brings the same functional depth to companies from EUR 500k in revenue — with any number of entities. Live in weeks. No enterprise IT project. No dedicated treasury team required.
A Treasury Management System at enterprise depth — EBICS multi-bank connectivity, real-time intraday cash positioning, automated bank statement import, 13-week rolling liquidity forecast with three scenarios, FX rate management and Working Capital optimisation. This is not a cash dashboard. This is the complete TMS layer that large corporates pay EUR 1–3M to implement — now deployable in weeks, on a SaaS model, for the mid-market.
Most mid-market finance teams manage FX risk in Excel — if at all. JPS FinanceOS gives CFOs and Finance Directors a live view of FX exposure across all currencies, counterparty risk concentration, covenant compliance monitoring against banking thresholds, and payment default simulation showing cash impact if key customers pay late. Risk management that used to require a dedicated treasury team and a six-figure risk platform — now embedded in the standard Finance Operating System.
Finance platforms and HR/payroll systems are always separate — and the gap between them is where margin visibility gets lost. JPS FinanceOS closes that gap: contribution margin by customer, product line and entity, combined with payroll and personnel cost data, DSO and DPO by customer, and profitability by segment — all in the same governed, auditable Finance Operating System. No separate BI tool. No manual consolidation. No data left behind in payroll software.
Every incoming document — invoice, dunning letter, bank statement, contract, court notice — is automatically received, OCR-processed by Azure AI Document Intelligence, classified and routed to the right module without manual intervention. Invoices go to AP Automation. Bank statements go to Treasury. Court letters go to the Legal Queue. Contracts go to the GoBD-compliant archive. That archive lives in your own SharePoint — not in JPS servers, not in a third-party DMS silo. Your documents. Your Azure environment. JPS brings the intelligence layer on top. This is the fundamental difference to every classic DMS: no data migration, no separate system, no additional software to maintain.
| Capability | Enterprise TMS / Risk platform | Planning & consolidation tool | JPS FinanceOS |
|---|---|---|---|
| Full TMS with EBICS | 500k–3M EUR · 12–24 months | Not available | Included · 2–4 weeks |
| FX & counterparty risk | Add-on module · 100k+ EUR | Limited — no real-time | Built-in · Enterprise edition |
| Covenant monitoring | Custom development | Manual configuration | Standard feature |
| Contribution margin by customer | Separate BI project | Possible — complex setup | Native — ERP-connected |
| Payroll integrated into cash plan | Not available | Not available | FinanceOS Margin & HR |
| Incoming dunning & legal documents | Not available | Not available | AI-classified · Legal Queue built-in |
| Document archive (GoBD-compliant) | Separate DMS project | Not available | Your own SharePoint · GoBD 10 years |
| Minimum company size | 500M+ EUR revenue | 100M+ EUR revenue | From EUR 500k revenue |
| Go-live timeline | 12–24 months | 3–12 months | 2–4 weeks |
FinanceOS is modular by design. Professional and Enterprise editions bundle the most common module combinations — additional modules can be added to any edition at any time.
Authentication (Entra SSO), RBAC (7 roles), immutable audit log, Row-Level Security, function dependencies. The foundation — always included.
Live cash position, multi-currency, multi-entity, 4-eyes payment approval, IBAN masking, FX exposure and covenant monitoring.
Incoming invoices via email/scan/upload, OCR extraction, vendor matching, duplicate check, 3-way matching, ERP write-back, early payment discount recognition.
Dunning workflow stages 1–3, automated direct debit via EBICS, customer risk scoring, early warning system, DSO tracking and AR aging.
13-week rolling forecast, three scenarios (Conservative / Realistic / Optimistic), FX shock simulation, payment default simulation, CFO-ready dashboard.
CFO dashboards, Treasury KPIs (DSO, DPO, Cash Conversion Cycle), scheduled reports, GDPdU export for tax audit, multi-entity consolidation.
OCR via Azure AI Document Intelligence, automatic classification and routing — invoices to AP, bank statements to Treasury, contracts to DMS, court notices to Legal Queue.
GoBD-compliant archive in your own SharePoint (Microsoft Graph API). Documents stay in your Azure environment — no data silo in JPS. ERP write-back of SharePoint URL.
Critical documents — dunning stage 3, court letters, enforcement notices, tax assessments — automatically escalated to management, tax advisor or legal counsel.
Bidirectional integration: NetSuite (live, SuiteQL / OAuth2 / TBA) and D365 Business Central (Q3 2026). Payment Run Pull, write-back, GL / subsidiary / bank account sync.
JPS Native EBICS 2.5/3.0, KONFIPAY managed gateway (no certificate ceremony), Open Banking / PSD2. 50 German banks pre-configured. CAMT.052/053/054, MT940/942 import.
Payroll with DATEV export, project billing readiness and contribution margin / customer profitability analysis — on the roadmap as separate add-ons.
Professional covers liquidity, forecasting and reporting. Enterprise adds the full operational layer — Treasury, AP, Collections, Document Intelligence and Banking. Both editions include the complete security and audit foundation at no extra cost.
For finance teams that want to digitise liquidity planning, cash forecasting and CFO reporting — without a full platform project.
For organisations that want to centralise Treasury, AP, Collections, Documents and Banking in one auditable, ERP-connected platform.
The Banking Connector is the central bank gateway for all connected systems. Three connection methods so every organisation can start — regardless of their banking setup.
Not months. We handle environment setup, banking configuration, ERP connector and onboarding. Your team contributes one day of training. The rest is JPS-iQ.
Workspace provisioned, users invited, Microsoft 365 SSO configured and tested.
EBICS / KONFIPAY / Open Banking configured, bank accounts connected and statement import tested.
NetSuite or D365 BC connector configured, Payment Run tested, write-back verified end-to-end.
Bank accounts, vendors and customers imported. Data quality verified before go-live.
Finance Director, Treasury Manager and AP Manager trained by JPS-iQ. Role-specific walkthroughs.
First live payment submitted, bank statements flowing, liquidity report live. JPS-iQ present.
Every security measure in JPS FinanceOS is an architecture decision made before the first line of code. GDPR, GoBD and SOC 2 requirements are built in — not bolted on afterwards.
| Area | Measure | Standard |
|---|---|---|
| Data Encryption | IBANs and banking credentials: AES-256-GCM encrypted at rest. Plaintext fallback disabled. | GDPR Art. 32 |
| IBAN Display | Masked by default (xxxx 1234) — full IBAN only for authorised roles, every view logged. | Data minimisation |
| Access Control | RBAC with 7 roles from Platform Admin to Read Only. Permission gating at API level. | SOC 2 |
| Tenant Isolation | Row-Level Security on every database query. No cross-tenant data access is architecturally possible. | Multi-Tenant |
| Authentication | Microsoft Entra ID SSO — no passwords stored in JPS FinanceOS. JWT with 15-minute TTL. | Zero Trust |
| Audit Log | Immutable append-only log — user, timestamp, IP, action, data scope. Cannot be deleted or modified. | GoBD / GDPR |
| Hosting | Microsoft Azure West Europe — ISO 27001. Data Processing Agreement (DPA) signed May 2026. | GDPR |
| GDPR Rights | Art. 17 (right to deletion) and Art. 20 (data portability) implemented at API level. | GDPR Art. 17/20 |
| Compliance Docs | Processing register (Art. 30), Incident Response Plan (Art. 33), GoBD process documentation — all available on request. | GDPR / GoBD |
The FinanceOS Beta opens on 1 July 2026. JPS-iQ itself goes live as the first Beta customer — we run our own treasury operations on FinanceOS from day one. Beta participants receive: preferred pricing locked for 12 months, a dedicated onboarding by the JPS-iQ team, direct access to the product team and early access to every new module as it launches. Onboarding slots are limited.
NetSuite is an excellent ERP. JPS FinanceOS makes your NetSuite data actually usable for the finance team — real-time consolidation across bank accounts, neutral audit trail, automated payment approval with 4-eyes enforcement, and 13-week cash forecasting that runs without manual exports.
NetSuite is the system of record. FinanceOS is the operational layer above it.
FinanceOS eliminates the manual side — not the analytical side. Your Excel analysis gets better because the data underneath is clean, current and audited instead of manually assembled.
A standard implementation pays back within 4–6 months through time saved, errors eliminated and audit risk reduced.
Standard: 2–4 weeks. Not months. JPS-iQ handles environment setup, banking configuration, ERP connector and user training. Your IT team contributes less than 1 day. First live payment within the onboarding window.
No. Your ERP stays as the system of record. FinanceOS connects via secure, read-only API (with write-back for payment status only) and adds the operational control layer above. No migration, no data silo, no parallel system of record.
It is often the best time. FinanceOS is ERP-neutral — your financial operations remain consolidated and audited during the ERP migration. No lock-in to your current ERP. The FinanceOS connector switches when your ERP does.
All data is stored on Microsoft Azure, West Europe region. IBAN and banking credentials are AES-256-GCM encrypted at rest. Data Processing Agreement with Microsoft Azure signed May 2026.
GDPR Art. 17 (deletion) and Art. 20 (data portability) are implemented at API level. Processing register (Art. 30), Incident Response Plan (Art. 33) and GoBD process documentation are available on request.
We say this clearly: FinanceOS is not the right fit for companies looking for a full ERP replacement (we connect to your ERP — we do not replace it), or organisations that have no digital banking setup or IT contact at all for the initial configuration. If your only finance challenge is a single bank account with no ERP — there are simpler tools for that. For everyone else: we are built for you.
A 30-minute live demo — real NetSuite environment, real bank statements, your questions answered by the product team. Or send us a line for a Beta application, pricing or a technical architecture discussion.