Controls run in Excel
Reconciliations, checklists and control evidence are produced beside the system — and are therefore neither versioned nor audit-proof.
Your ERP posts the transaction. FinanceOS runs the finance organisation.
JPS FinanceOS is our own product: an ERP- and ledger-neutral Finance Operating System that sits as a control and action layer above ERP, banking, documents and finance processes. This page explains how FinanceOS relates to a Microsoft landscape — and where the limits of that statement run.
The core sentence
“System of record → system of control → system of action. The ERP is the first stage. FinanceOS is the second and third.”
JPS FinanceOS · JPS-iQ Solutions Group
The missing layer
The ERP is implemented correctly. Finance still runs beside it.
It is one of the most common findings after a clean ERP implementation — and one of the least often named: the system posts correctly, the configuration is sound, and the finance organisation still works largely outside it.
Approvals run by email
Who approved what and when sits in mailboxes rather than in a traceable case.
Payments run through bank portals
The payment leaves the system and comes back as a posting — in between sits a gap with no four-eyes evidence.
Exceptions have no home
Every deviation is resolved individually, usually verbally, and leaves no trace for the next case.
Reporting is reconstructed alongside
Numbers are assembled from several sources instead of coming from one consistent model.
Knowledge sits with people
The process works because certain people carry it in their heads — not because it is modelled.
This is not an ERP defect and cannot be solved with more ERP configuration. A layer is missing: a place where finance data from several systems comes together, controls run, approvals happen, exceptions are worked and actions are triggered — traceably and repeatably.
Architecture
One core, one canonical model, provider adapters.
FinanceOS is not built as one product per ERP but as one core with a canonical finance data model. What a source system delivers is projected onto that model; everything above that boundary works on the canonical model. That is why FinanceOS can stay ERP-neutral and does not have to be rebuilt with every new source system.
NetSuite is today the first and deepest ERP path. The order follows the group's product history, not an assessment of the platforms.
- 01
One core
One platform, not a product variant per ERP. What is solved in an adapter does not have to be solved in the core.
- 02
Canonical minimum
Not a mega-schema but a small, stable core of 108 business objects with typed relationships, lineage per value and history per version — kept small so it holds across system boundaries.
- 03
Provider adapters
One projection onto the canonical model per source system — with clearly named limits rather than an implied assumption of completeness.
- 04
ERP neutrality as architecture
Not as a marketing statement: the neutrality follows from the model, not from a declaration of intent.
Microsoft's role
Microsoft technology is a facilitator — not part of the product.
In a Microsoft landscape FinanceOS touches five places. One is a strong integration, three are optional, and one is a source system. That makes Microsoft 365 a noticeable facilitator and not a prerequisite for running FinanceOS.
- 01
Microsoft Entra ID
Identity and access, and the strongest of the five integrations. People sign in with the identity that already applies in your organisation. No second user directory, and the role and amount limits in FinanceOS hang off that identity.
- 02
Microsoft Azure
The operating layer. FinanceOS runs on Azure, with data storage and processing under European data protection requirements. For the specific region and the contractual details we point to the platform page and the conversation rather than paraphrasing them here.
- 03
SharePoint
Optional document and evidence integration. Where SharePoint is in use it stays the store and the full-text search; FinanceOS carries the document's finance context — what it belongs to, what it evidences, which decision it justifies. Optional means FinanceOS works without it.
- 04
Microsoft Teams
Optional collaboration surface. Approvals and clarifications can happen where your organisation already works. The case, the authority and the evidence stay in FinanceOS — an approval in a chat without an audit trail would not be an approval.
- 05
Business Central and Dynamics 365
A possible system of record. Both keep the transaction and the posting authority. Which paths we can evidence today is set out under product status; we make no statement about dates here.
What FinanceOS explicitly is not
- Not a Microsoft product and not part of the Microsoft product family.
- Not a Business Central add-on and not an extension in the Business Central sense.
- Not a Power BI front end and not a dashboard layer — FinanceOS is an operating layer, not an analysis layer.
- Not a platform-bound finance app and not “FinanceOS for Business Central”.
- Not a NetSuite-only product, even though NetSuite is the deepest path today.
Microsoft 365 is a facilitator, not a prerequisite
This boundary is not modesty, it is the architecture: a product bound to one platform could not solve the problem it is built for. Finance organisations rarely run on exactly one system, and after acquisitions two or three run in parallel. Where Microsoft 365 is present it makes a noticeable difference to sign-in, document archive and clarification — but it does not decide whether FinanceOS runs.
Product architecture
Twenty-two domains in four layers.
The complete domain and function scope belongs on the FinanceOS platform, not here. What you get here is the structure — so you can judge whether the layer meets your problem.
- 01
A · Sixteen business finance domains
Steering and result, finance operations, case and contract, further business domains. They are delivered modularly: the entry point is a domain, not a programme.
- 02
B · Two domains effective inside every other one
Risk, Controls & Compliance and Finance AI & Agentic Automation. Control is a construction principle, not an add-on.
- 03
C · Four domains as the shared foundation
Finance Data Fabric, Identity & Access Governance, Data Lifecycle & Records, Platform & Administration. Part of every entry point, because without them no chain could be evidenced.
- 04
D · Systems of record keep their authority
ERP and general ledger, banks, DMS and CLM, project and payroll systems, tax and consolidation systems. FinanceOS connects context, control, decision and evidence across them.
The vertical axis says who is responsible for what. The horizontal one says how the work runs: 93 modelled end-to-end chains in 23 families, with 121 named handoffs between domains. In most organisations that stretch is done by people, by email.
Product status
What we can evidence today — and what we cannot.
We keep maturity visible here, because a statement about a capability is worthless without its mark. The rule is short: what is not marked, we do not claim.
- 01
Maturity per capability, not per product
Four states, written out: verified in the product, pilot or validation, in active development, defined capability. The mark sits on the capability, never on the product as a whole.
- 02
NetSuite
The first and deepest ERP path today. The order follows the group's product history, not an assessment of the platforms.
- 03
Business Central and Dynamics 365
A possible system of record. Which paths we can evidence today is marked per capability on the product status page. We make no statement about dates.
- 04
Further source systems
Provided for through provider adapters. Scope and depth belong in the conversation, because they depend on your specific systems.
If you run Business Central or Dynamics 365 today and find FinanceOS interesting, that is a sensible conversation. In it we tell you what we can evidence today and what we cannot — and if the starting position does not fit, we say that too.
Getting started
How it starts.
No six-month selection process and no preliminary study nobody reads. Four steps, and the first two cost nothing but time. A no after step two is a good result if the starting position does not fit.
- 01
Conversation, 30 minutes
Legal entities, banks, systems, volume and the question that takes longest to answer in your organisation. No presentation.
- 02
An assessment on one page
Which chains make the biggest difference for you, which entry point fits them, in what order, and what it does not solve.
- 03
A demo on your own constellation
Your banking structure, your legal entities, your documents. Not our demo environment with prepared data.
- 04
The first stage in production
One entry point, implemented with support, with a defined acceptance criterion and a named owner through into operation.
Good fit
Who this layer is relevant for.
Good fit
- Your ERP is implemented and sound at its core — the problem clearly sits above it.
- You run several legal entities and several currencies and feel it at close.
- Controls, approvals and exceptions run through spreadsheets, email and bank portals today.
- External audit, internal audit or group requirements demand evidenced processes.
- You work with Microsoft 365, Entra ID, SharePoint and Teams — not a requirement, but a noticeable difference.
Less good fit
- You are looking for a reporting or dashboard tool — FinanceOS is explicitly not that.
- One legal entity, low volume, a cleanly running system — then FinanceOS is the wrong answer, and we say so in the first conversation.
- Your real problem is inside the ERP itself — then optimising the ERP is the more honest first step.
- You expect a platform you configure yourself — every implementation here runs with support and a named owner.
- You need operational accounting capacity rather than a platform — that is what BPO by JPS-iQ is for.
Common questions
What usually gets asked at this point.
Is FinanceOS a Microsoft product?
No. FinanceOS is product IP of the JPS-iQ Solutions Group and built ERP-neutral. Microsoft technology is a facilitator: Entra ID for identity and access, Azure as the operating layer, SharePoint and Teams optional. FinanceOS is neither part of the Microsoft product family nor a Business Central extension.
Do we need Microsoft 365 to run FinanceOS?
No. Microsoft 365 is a facilitator, not a prerequisite. Where Entra ID, SharePoint and Teams are present they make a noticeable difference to sign-in, document archive and clarification. Without them FinanceOS runs just the same, using other sources for the same tasks.
How does FinanceOS relate to Business Central?
Business Central is a complete ERP and a possible system of record: it keeps the transaction and the posting authority. FinanceOS solves a different problem — the stretch from an operational event through the financial effect and the owned decision to the verified effect. Which paths we can evidence today is marked on the product status page; we make no statement about dates.
Isn't this just Power BI under another name?
No, and the difference is fundamental. A classic reporting layer typically focuses on data, context and signal. FinanceOS additionally connects control, case, decision, approval, action, outcome, verification, evidence and learning in the same product model — with ownership, a deadline and an audit trail.
How mature is FinanceOS today, honestly?
Maturity here sits on the individual capability, not on the product as a whole: verified in the product, pilot or validation, in active development, defined capability. What is not marked, we do not claim. What holds today and in what depth is stated on the product status page and clarified in the first conversation against your specific source systems.
Where do I find the complete product information?
On suite.jps-iq.com. This page is deliberately a bridge: it explains the layer and the Microsoft perspective and points to the product pages for the 22 domains, the chains, the entry points, the security architecture and the product status.
Contact · JPS FinanceOS
Does your finance organisation run beside the ERP?
If the description above matches your situation, the next step is an orientation conversation: which places cost you the most, which source systems are in play, and which entry point we would begin with. If none of them fits, we say so.