SIFYBOX · Workflows, documents and approvals

Controlled workflows, documents and signatures.

A deployable platform for forms, workflow, document generation, budget checks, delegation, signatures and trusted storage.

How SIFYBOX connects people, data and systems

Internal control

Financial control as part of the everyday workflow.

SIFYBOX connects responsible roles, control order, funding, delegation and the audit trail in one managed workflow. The organisation defines its rules and responsibilities; the system helps enforce and evidence them.

The Czech Act on the Management and Control of Public Finances takes effect on 1 January 2027. These functions support a managed workflow and audit trail; they do not by themselves guarantee that a deployment complies with the law. The responsible organisation must confirm its rules.

Czech Act No. 231/2025

How internal control works
The completed document is stored with the process history

An outcome that stays the same

The workflow ends with a document. We put it in the digital filing cabinet.

Just as a completed paper file used to go into a cabinet, SIFYBOX stores the final document in CUL or hands it to records management. Its inputs, decisions, signatures and audit relationship remain traceable.

The outcome does not need to be reconstructed later by the current application version. What was actually approved and issued remains preserved even if rules, print layouts or rounding have changed.

CUL is the operational document layer. Where formal records management applies, the connected certified e-records system remains authoritative.

For whom

Who the solution is for

Medium and large organisations
Universities and research organisations
Public-sector bodies
Organisations connecting several systems and approval roles

What changes

Documents stop moving manually between email, spreadsheets and ERP.

Defined roles, limits, sequence and four-eyes approval are enforced in the workflow.

Operations teams see queues and exceptions; management receives a traceable outcome.

Reusable process building blocks reduce one-off development.

From input to outcome

What happens after the input arrives.

01

Input in one place

A form, PDF, email or API payload becomes one controlled case.

02

Verified data

The system prepares the data and a person resolves only uncertain or invalid values.

03

Controlled decision

The workflow applies funding, delegation and independent approvals under organisational rules.

04

Outcome where it belongs

The document is signed and stored, then handed to accounting, finance or records management.

User perspectives

Each person sees their work and responsibility.

Operations specialist

Reviews intake, resolves exceptions and knows where each case is.

Approver

Sees supporting data, budgets and prior decisions; can approve, return or reject.

Accountant

Receives controlled data and documents ready for the finance system without rekeying.

Executive and assurance

Gets evidence of decisions, segregation of duties and exceptions.

Integrations

Connect what you already use.

  • ERP and finance platforms through versioned interfaces
  • Identity through Keycloak, OIDC, SAML or the customer provider
  • Electronic records-management integration
  • HR, research, registry and specialist APIs

Deployment and delivery

Aligned with sensitivity and ownership.

  • On premises — sensitive data remains inside the organisation
  • Cloud — managed operation based on the agreed architecture
  • Hybrid — local data combined with selected cloud services
  • Delivered by DERS or an implementation partner

Next step

Let’s discuss your specific use case.

Bring one real case. We will separate standard product scope, integrations and decisions your organisation needs to make.

Discuss a specific caseGo to documentation