16 November 2026
Business Central’s Release and Reopen actions are simple to use: open a sales or purchase document via Search (Alt+Q) and click Release or Reopen on the action bar. Release changes the Status field to Released and makes orders available for downstream processing (for example, warehouse handling). Reopen returns the Status to Open and allows edits before releasing again.
This built‑in flow is useful operationally, but it has accounting and audit consequences that matter for Danish bookkeeping and SAF‑T reporting.
How Release and Reopen work (what the product does)
- To release a document: find the document (Sales Orders, Purchase Orders, Sales Invoices, etc.), open it and choose Release. The Status becomes Released. Approval workflows or prepayment rules can block Release — an order may show Pending Prepayment if a required prepayment isn’t settled and if Check Prepmt. when Posting is enabled.
- To reopen a released document: open the document and choose Reopen. The Status changes back to Open so you can edit and then release again.
- Reopening has constraints: it doesn’t remove existing warehouse reservations — you can’t change an item, location or unit of measure while related warehouse lines exist. These safeguards prevent some accidental changes but do not by themselves protect fiscal audit trails.
These are standard UI steps and system behaviours documented by Microsoft (Release / Reopen actions, Status field changes, constraints around warehouse lines and prepayment checks).
Why this matters for Danish bookkeeping and SAF‑T
Denmark’s bookkeeping expectations (as enforced by SKAT) require an auditable, unbroken record of posted accounting events and consistent VAT period treatment. Reopening posted sales or purchase documents after they influenced ledgers or VAT postings can:
- Alter which VAT period a transaction would be expected to belong to, creating discrepancies between posted VAT and SAF‑T exports.
- Obscure the audit trail if changes to posted documents are allowed without a clear, timestamped revision history.
Even if Business Central doesn’t automatically allow changes to posted ledger entries, reopening the source document and reposting can produce edits that are hard for auditors to reconcile unless the system or your processes capture who reopened or corrected a document, when, and why.
What this means for companies in Denmark
- Treat Release/Reopen operations as accounting controls, not convenience features. Uncontrolled reopening risks failing the SAF‑T review or creating questions from auditors about retroactive VAT changes.
- Assume that reopening a document that has had fiscal impact should be avoided. Prefer corrective accounting (credit notes/cancellation invoices) so VAT and posting periods remain intact and traceable.
- Ensure your SAF‑T export and audit evidence include revision history: auditors will want to see whether a posted invoice was later modified, who did it, and how the VAT period was affected.
How we would approach it at Invice
1. Lock posting windows at system level: set and enforce Allow Posting From / Allow Posting To (General Ledger Setup) so posting dates cannot be moved across VAT periods casually. Combine this with clear internal policies for period reopening.
2. Restrict Reopen rights: remove the Reopen/Release action from general user roles and grant it only to a small, named finance role using permission sets. Where needed, implement approval workflows for reopening.
3. Avoid reopening posted invoices: require corrective credit notes or cancellation invoices where an invoice has already had fiscal effect. Document this in your invoicing SOP and train sales/purchasing teams.
4. Enable and extend audit logging: turn on Business Central’s Change Log for relevant tables (sales/purchase header and lines) and capture user, timestamp and field changes. Ensure your SAF‑T extraction includes either the log entries or a linked report that shows reopen/correction events so auditors can reconcile changes.
5. Add proactive checks: create routine reports that flag reopened documents, posting date shifts and invoices with changed VAT postings so finance can resolve them before audit queries.
If you run Business Central in Denmark, these steps protect the integrity of your SAF‑T exports and align system behaviour with expectations under Danish bookkeeping rules. Invice can help implement the permission, posting‑date and audit‑log changes and update your SAF‑T export to surface revision history for auditors.
Source: Microsoft Learn

