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-neutral Finance Operations Platform 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 finance data model
Accounts, entities, documents, receivables, payables, transactions and delivery objects in a system-independent model.
- 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 an enabler — not part of the product.
In a Microsoft landscape FinanceOS touches two layers, and it matters that both are named correctly: identity and operations. Anything beyond that would be a claim we do not make here.
- 01
Microsoft Entra
Identity and access. People sign in with the identity that already applies in your organisation — no second user directory.
- 02
Microsoft Azure
The operating layer. FinanceOS runs on Azure. For the specific hosting region and the associated contractual detail we deliberately point to the platform page and the conversation rather than paraphrasing them 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 Microsoft-native finance app and not “FinanceOS for Business Central”.
- Not a NetSuite-only product, even though NetSuite is today the deepest path.
Why the boundary matters
This boundary is not modesty but architecture: a product tied to one platform could not solve the problem it is built for — finance organisations rarely run on exactly one system.
What the platform does
Seven pillars — the scope in one line each.
The full module and functional scope belongs on the FinanceOS platform page, not here. What you get here is the structure — so you can judge whether the layer addresses your problem.
- 01
Connect
Bring finance data from ERP, banking and adjacent systems onto one shared model.
- 02
Control
Run controls, reconciliations and evidence where they stay traceable.
- 03
Plan
Forecast and scenarios on the same data on which posting and control also happen.
- 04
Operate
Run day-to-day finance operations: cases, ownership, deadlines, exceptions.
- 05
Automate
Execute recurring routines by rule rather than by reminder.
- 06
Analyze
Analysis on the canonical model — not on a reconstructed copy.
- 07
Intelligence
Patterns, deviations and signals out of live operations.
Maturity & roadmap
Where FinanceOS stands today — and where Business Central stands.
We keep the maturity visible here on purpose, because a product in Early Access has to be judged differently from an established standard product.
- 01
Early Access
FinanceOS is in Early Access: the first 100 finance organisations, onboarding through the end of 2026. That is a programme with expectations on both sides, not a pre-sale.
- 02
NetSuite
Today the first and deepest ERP path.
- 03
Business Central
The next strategic path on the same contract and on the roadmap: not available — and we do not present it as a feature you can buy today.
- 04
Further source systems
Provided for through provider adapters. Scope and timing belong in a conversation, not on an overview page.
If you run Business Central today and find FinanceOS interesting, that is a sensible conversation — but it is a conversation about a roadmap path, not about an order. We tell you at first contact what works today and what does not.
Early Access
How an Early Access conversation runs.
Early Access means: you get early access and influence over prioritisation — and we get a finance organisation the product has to prove itself against. The two belong together.
- 01
Read the situation
Where does your finance organisation run beside the ERP today — and which of those places costs the most time or certainty?
- 02
Fit
Which source systems are in play, and does today's adapter coverage reach them? If it does not, we say so.
- 03
Scope
Which pillars are actually relevant to your starting position — and which are visibly not?
- 04
Decision
Early Access or not. A no at this point is a good outcome if the starting position does not fit.
Good fit
Who this layer is relevant for.
Good fit
- Your ERP is implemented and sound at its core — the problem visibly sits above it.
- You run several entities and several currencies and feel it at the close.
- Controls, approvals and exceptions today run through Excel, email and bank portals.
- You want a layer that stays ERP-neutral, because your system landscape will keep changing.
- You can work with an Early Access product and want influence over prioritisation.
Weaker fit
- You are looking for a reporting or dashboard tool — FinanceOS is explicitly not that.
- You expect a productive Business Central connection today — that is on the roadmap and is not available.
- Your real problem sits in the ERP itself — then ERP optimisation is the more honest first step.
- You need a finished standard product with a long reference list — Early Access is something else.
- You are looking for operational bookkeeping capacity rather than a platform — BPO by JPS-iQ exists for that.
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 an enabler — Entra for identity and access, Azure as the operating layer. FinanceOS is neither part of the Microsoft product family nor a Business Central extension.
Is there a Business Central connection today?
No. Business Central is the next strategic path on the same contract and is on the roadmap — not available, and we do not present it as a feature you can buy today. If you run Business Central a conversation still makes sense, but it is a conversation about a roadmap path.
Is this not just Power BI under a different name?
No, and the difference is fundamental. An analytics tool shows what happened. FinanceOS is an operating layer: controls, approvals, cases and actions run there — with ownership, a deadline and evidence. Analysis is one of the seven pillars, not the product.
Do we need FinanceOS if we implement Business Central?
No. Business Central is a complete ERP and works without FinanceOS. Conversely, Business Central is not a precondition for FinanceOS. The two solve different problems: Business Central posts the transaction, FinanceOS runs the finance organisation.
How mature is FinanceOS today, honestly?
FinanceOS is in Early Access — the first 100 finance organisations, onboarding through the end of 2026. It is not a finished standard product with a long reference list, and we do not present it as one. What carries today, and at what depth, we settle in the first conversation against your specific source systems.
Where do I find the full product information?
On the FinanceOS platform page. This page is deliberately a bridge: it explains the layer and the Microsoft perspective, and points to suite.jps-iq.com for modules, detailed architecture, editions, security architecture and Early Access terms.
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 whether Early Access makes sense for you at all. If it does not, we say so.