Making a financial correction during review
A financial correction re-tags a Beleg (receipt/expense document) with a corrected VAT rate, cost center, or GL mapping and recomputes its amounts. This article explains how corrections work, when they are allowed, and why they must be made during review — not after approval. The action requires the belege:correct-financial permission.
What a financial correction changes
A correction lets you set any combination of three financial tags on a Beleg:
- VAT rate (Umsatzsteuersatz) — the tax rate percentage.
- Cost center (Kostenstelle) — the internal charge code.
- GL mapping (Sachkonto) — the general-ledger account code.
The correction re-tags the whole Beleg: the corrected values are propagated to every line item, and for each line item the VAT amount and gross amount are recomputed from its net amount. The Beleg header totals are then recalculated so the document stays internally consistent.
When a correction is allowed
Corrections are a review-stage activity. They are permitted while the Beleg is in an editable state (Draft, Submitted, In Review, or Needs Clarification) and are blocked in immutable states — Approved, Paid, and Rejected. Attempting to correct an immutable Beleg is refused with a "cannot be modified in terminal state" error and the denial is audited.
Warning: There is no path back from Approved to In Review, and Approved is immutable. If you spot a financial mistake after approval you cannot correct it in place — so make corrections before you approve.
Applying a correction
- Open a Beleg that is still in an editable review state.
- Enter the corrected VAT rate, cost center, and/or GL mapping.
- Submit the correction. The platform validates the values, re-tags the line items, recomputes amounts, and saves.
Validation against active reference data
Corrected values are checked against your company's active financial reference data. If a VAT rate, cost center, or GL code is not on the active list, the correction is rejected as "financial reference is not active". VAT rates are rounded to two decimal places, and cost center and GL codes are matched case-insensitively. Keep your financial reference data current so valid corrections are accepted.
How corrections are audited
Every correction is recorded with a full before-and-after picture — the previous and new VAT rate, cost center, GL mapping, net total, and gross total. The data change and its audit record are committed together in a single transaction, so a financial change can never be saved without its audit entry. Denied attempts (unauthorized user or immutable state) are also recorded.
Related
- Approving a Beleg and how approval locks the record
- Reviewing Belege in the review queue
- Rule warnings, blockers, and override governance
- The compliance trail and retention
