ENVerified source
The Act governs management and control of public finances and separately defines the internal control system. Solution design starts from the organisation’s concrete duties, not merely the title of the Act.
Act No. 231/2025 ↗Workflows, documents and people
Internal control embedded in the workflow.
Rules, roles, limits, budget checks and four-eyes approval happen inside the process—not after the fact.
For organisations that want approval rules, limits and segregation of duties to operate in everyday work rather than only in policy documents.
See the process
From start to finish
An operation passes business, budget and accounting checks.
New operation
The requester describes the intended operation and the system selects the right route.
Complete evidence
Missing data or attachments go back for completion before approval starts.
Role-based control
Each control role sees exactly the evidence needed for its decision.
Independent approvals
Conflicting roles stay separate and controlled delegation covers absences.
Accounting evidence
Accounting receives approved evidence and auditors can trace the complete journey.
New rules from 2027
Internal control under Act No. 231/2025.
The Czech Act on the Management and Control of Public Finances takes effect on 1 January 2027. SIFYBOX can support controlled evidence, separated roles, approvals and a traceable audit trail. Installing software alone does not establish compliance; each organisation must configure processes, permissions and responsibilities for its remit.
Who is involved
Who is responsible for what.
Requester or case worker
Submits the operation with purpose, amount, counterparty and required evidence.
Operation approver
Confirms necessity and business correctness; returns, rejects or approves.
Budget controller
Checks funding and limits independently of the operation approver.
Chief accountant
Checks accounting conditions and ERP hand-off as configured by the organisation.
What happens when something goes wrong
Return, rejection and delegation
Missing evidence sends the case back to the exact step. Rejection requires a reason. During absence, only a specified role is delegated for a defined period—not the person’s whole account.
The result
Auditors receive a timeline of evidence, decisions, changes, approvals and hand-offs. The software supports demonstrable controls; it does not guarantee regulatory compliance by itself.
Product and integrations
The solution connects to the systems you already use.
Forms, roles and rules follow the way your team works. Every integration keeps the source of truth and error ownership clear.
Explore the product: Workflows, documents and people →Related solutions
What can connect to this workflow
Concise answers
Frequently asked questions
Who is this solution for?
For organisations that want approval rules, limits and segregation of duties to operate in everyday work rather than only in policy documents.
What happens when the input is incomplete or incorrect?
Return, rejection and delegation. Missing evidence sends the case back to the exact step. Rejection requires a reason. During absence, only a specified role is delegated for a defined period—not the person’s whole account.
What is the outcome of the workflow?
Auditors receive a timeline of evidence, decisions, changes, approvals and hand-offs. The software supports demonstrable controls; it does not guarantee regulatory compliance by itself.
Next step
Facing a similar situation?
Tell us how the work runs today and where it gets stuck. We will reply with a concrete next step, not a generic presentation.
Describe my situation