Budget requests

Budget increases in Contrixt run as requests with an approval workflow — traceable, rule-based and without email ping-pong.

Submitting a request

Under Requests you create a request with:

• Cost center and category (the budget cell to be increased)
• Amount and reason (at least 10 characters)

If no budget exists yet for the chosen cost center and category, the form points this out: approving the request creates the budget for that combination.

After Submit the request receives the status pending; the responsible budget owner is notified — in-app and by email.

Deciding

Administrators and controllers decide on pending requests — Approve (the plan value of the budget cell is increased automatically) or Reject, each with an optional note. Requesters are notified about the decision.

Withdrawing a request

As long as a request has not been fully approved (status open or rejected), the requester can delete it themselves — via the Delete button in the request list, with a confirmation prompt. Any stage approvals already granted are discarded. Fully approved requests remain immutable because their amount has already been applied to the budget.

Multi-stage approval

If your administrator has configured approval stages, a request passes through every stage whose amount threshold it reaches — e.g. controlling first, plus administration from €10,000:

• The request list shows the progress (stage x/y) and who is currently up.
• Each stage is decided by the configured party — a role, the budget owner of the budget cell, or a specific user; they are notified automatically.
• Only the final stage makes the request approved and increases the plan value. A rejection at any stage rejects the request as a whole.
• Every stage decision appears with name and date directly on the request.

Rules (configurable)

Under Administration → Settings administrators define:

Rule	Effect
Auto-approval up to an amount	Requests up to this amount are approved automatically (0 = off)
Four-eyes principle	Requesters may not approve their own requests — with approval stages, nobody may decide two stages of the same request either

The four-eyes principle is on by default. If only one user currently works in your organization, that user can't approve their own requests — the Requests page automatically shows a hint to invite a second approver or adjust the setting.

Administrators configure approval stages and approval requirements for purchase orders/investments under Approval workflow.

History

Every request keeps its full history: who requested, who decided each stage, when, with which note. Every decision also lands in the audit log.