Your ERP keeps its authority.
The most common first question is whether another system is here to succeed the posting system. The answer is no, and it is not modesty but an architecture decision: FinanceOS defines finance processes on a finance model of its own and reads the systems where posting happens.
Does FinanceOS replace our posting system?
No
ERP, accounting, banks and operational systems keep their posting authority. FinanceOS does not post in their place.
What it takes on
The work between the systems: approvals, reconciliations, chasing, spreadsheets — and the connection between transaction, effect and decision.
Why that holds
A finance process is defined once on the finance model and applies to every connected entity — not once per source system.
Eight objects, six verbs.
The model is the reason a change of source changes the adapter and not your processes.
Canonical finance objectsOne implementation per process, not one per source system.
Each source is translated once, at the edge.
ERP and accounting
An adapter projects the posting system's objects onto the canonical model. NetSuite is the first and deepest path.
Bank channels
Account information comes from your existing channels. We claim no bank transmission of our own.
Document sources
Documents stay in their own store; FinanceOS reads them and attaches the finance context.
For any further posting system the route is the same: an adapter at the edge, not a second product. Which path runs how deep is something we say in a conversation, not on a logo wall.
What stays where.
Posting
Stays in the posting system
FinanceOS reads the canonical projection and writes no posting in its place.
Document
Stays in its own store
The transaction refers to the document rather than keeping a second copy.
Master data
Stays in its leading system
The model projects it; it claims no ownership.
Write-back
Defined per path and per system
We neither rule it out across the board nor promise it across the board. What is in scope is in scope.
What an ERP was not built for.
This is no complaint about the posting system. It is a statement about which question it answers.
A posting system
answers what was posted — completely, auditably, and in the period in which it was posted.
A planning tool
answers what is expected — on the data somebody entered into it.
A reporting layer
answers how the numbers look — it changes no transaction and carries no authority.
This layer
answers what a transaction turns into while it is still running — and who may carry the decision about it.
Three questions from the first conversation.
So do we need two systems for the same number?
The number arises once. The posting system holds the posted state, FinanceOS holds the obligation and the expected effect before it. Both refer to each other rather than duplicating each other.
What happens when we change ERP?
A change of source changes the adapter, not your finance processes. That is exactly what the canonical model is for — it is the answer to why we do not build one product per ERP.
And if our posting system cannot be connected at all?
Then we say so. A path we cannot evidence is not presented as present — that is what our transparency page is for.
What does “responsibility is not system ownership” mean?
That FinanceOS does not have to own a system in order to work across it. The posting, the bank item, the tax logic and the consolidation determination stay where they are owned. FinanceOS connects finance context, status, decision, control and evidence above them — and changes nothing in the source system.
How does FinanceOS know what a number means?
From the canonical model and the translation at the edge. Every metric carries its source, its business meaning, its period and its entity; the origin stays on the value rather than in a footnote. That is why a variance can be explained without anyone hunting for the source file.
Which classes of system can be a source?
ERP and accounting, banks, treasury, tax and planning systems, document sources, time and activity capture, and interfaces to authorities and providers. That is the map of classes, not a list of existing connections — which paths we can evidence today is set out under what we can evidence.
What happens when work is handed over between functions?
The context goes with it. When a record moves from one role to the next, the obligation, the deadline, the basis and the decisions so far move with it. A handover by word of mouth loses exactly that — and then the reconstruction starts.
Thirty minutes on your own system landscape.
Bring the posting systems, banks and entities that are in play at your end. We say where a common finance layer holds and where the adapter is the work.