Post arrives: a tax assessment, a dunning letter, a collection agency notice, a claim. Each of these documents creates an obligation, a deadline or a risk — and each of them gets filed first. Who picked it up, what has to be decided and when it becomes too late is in no system.
Post, portal, shared mailbox. The route to the right person is a shout across the room.
It is in the document. Whether it made it into a calendar becomes clear when it has passed.
Provision, payment, appeal: the decision gets made, the document stays in the folder, the reasoning stays in someone's head.
The data is usually there. It just takes effect in different systems at different times.
Four steps, and the same cross-functional capabilities across every one of them.
Every module is a standalone entry point. This chain shows what comes together once several of them run on the same finance data model.
Pilot / validation
Reads the document, recognises the type and the fields and files it with its finance context: entity, counterparty, amount, deadline, reference.
In active development
The document becomes a record with an owner, a date and a decision. Not a reminder, not a shout.
In active development
Where the letter belongs to an existing obligation, it hangs on it — not next to it.
In active development
Where a provision or accrual becomes necessary, it comes from the record and carries its basis.
Verified in product
Document, decision, effect and timestamp stay connected and can be read back later.
The deadline is carried and kept visible. Meeting it is the job of the person who picked up the record — FinanceOS does not decide in place of whoever is responsible.
Appeal, pay, provide or escalate — inside the authority that applies to this entity and this amount. The decision stays on the document, with its basis and its timestamp.
The filing stays where it is — mailbox, portal, DMS. FinanceOS reads the document and attaches the finance context.
The provision and the payment are posted there. FinanceOS runs the record and hands over the basis.
Proceedings and correspondence stay outside. FinanceOS carries what follows from them financially.
What is not marked, we do not claim. The full state per capability is on the module pages and under what we can evidence today.
No. A DMS files and retrieves. This chain starts after that: which obligation, which deadline and which decision follow from the document, who picks it up, and how you can later see that it was handled.
Classification and field extraction support the assignment; their maturity is stated below. The deadline is carried as a field on the record and kept visible. Meeting it is the job of the person who picked up the record.
It stays an open record with an owner instead of an unread PDF. An unclear case is a state you can see and escalate — that is the difference from a filing.
Bring this case as it looks in your organisation. We work through it on your example and say where a common finance layer holds and where it does not.