The tax position is created long before it is reported.
At period end tax delivers a figure that gets audited. It was caused months earlier: by a structure, a contract clause, a reclassification. FinanceOS carries the finance context of the tax position to where those decisions are taken.
Decided before, reported after.
Between the decision and its tax filing lie months and several systems in most organisations. The tax position is made in exactly that gap.
The decision
A restructuring, a contract clause, a transfer price, a change of location. At that moment the tax consequence is determined — and usually not calculated.
The context nobody carries
Which entity, which legal basis, which document, what effect on the group tax rate. Today a person holds that in their head, or a spreadsheet does.
The filing
The figure stands, it gets audited, and reconstructing the why costs the time of people who have other work to do.
FinanceOS moves nothing forward that belongs at the end. It holds the connection while it is being made: the tax context hangs off the transaction and the contract, not off a later analysis.
What this domain is responsible for.
The same contract clause determines revenue and tax.
That is why tax and revenue & billing sit next to each other in the product model: a change in one place moves the other three with it.
01 · Contract
Clause, term, consideration
02 · Price and terms
Discount, tier, indexation
03 · Delivery
Performed, accepted, documented
04 · Billing
Billing run and invoice
05 · Revenue recognition
By contract component
06 · Accrual
In the right period, with a reason
07 · Tax effect
Visible before it is reported
08 · Close and evidence
The evidence chain for the audit
Where this domain appears on the horizontal axis.
A domain on its own is a responsibility. It becomes visible where a business record runs through it.
The tax calculation stays in your tax engine.
FinanceOS calculates no tax and files no return. It connects the finance context so the tax consequence is visible before the decision is taken.
Your tax engine
Calculation, rates, rule set per jurisdiction.
Your adviser
The return and representation in proceedings.
Your ERP
Transaction, posting, tax code on the document.
FinanceOS
Connection, timing, owner, evidence.
The evidence chain an auditor asks for is one the product keeps for transactions anyway. For a tax audit the evidence is therefore a by-product of the work, not a separate effort.
What is verified in the product in this domain today
Tax context on the object
Verified in the product
The tax context hangs off transaction and contract and carries lineage and history.
Tax effect before the decision
Pilot or validation
The preview of the tax effect on the specific action.
Group tax rate and Pillar Two
In active development
The group view on the tax rate and Pillar Two relevant figures.
What is not marked, we do not claim.
Maturity per capability is stated on the product status page. What we can evidence today
Which tax question costs you the most time at close?
Bring one position whose derivation you reassemble every quarter. Thirty minutes, and afterwards you know which object the context would have to hang off.