- Feature
- Reverse sustainability ledger entries
- Availability
- Generally available (October 2026)
- Industry focus
- Facilities management services
Facilities management companies are under growing pressure to report emissions, both their own and those linked to the services they deliver for clients. Energy, fuel, waste and travel data flow into sustainability ledgers every month. Mistakes happen: a wrong meter reading, a duplicated fuel entry, a misallocated site. Business Central 29.0 makes correcting them clean and auditable.
The industry challenge
A facilities management provider might record in Business Central's sustainability module:
- Electricity and gas use at client sites it manages
- Fuel for its vehicle fleet
- Waste volumes and disposal methods
- Business travel by managers and engineers
Much of this arrives through sustainability or general journals, often from spreadsheets or utility reports. When an entry is wrong, perhaps posted to the wrong site or entered twice, the business needs to correct it without distorting historical reports.
If corrections are made with manual offsetting entries in a different period, the reports for the original period stay wrong, and the audit trail becomes hard to follow.
What Microsoft delivered in Business Central 29.0
According to Microsoft, Business Central 29.0 helps keep sustainability data accurate by reversing sustainability ledger entries that contain mistakes.
When entries were posted from a sustainability journal or a general journal, users can use the Reverse Transaction action on the Sustainability Ledger Entries page. The reversal creates a new sustainability ledger entry with the document number and posting date of the original entry, and records the user who ran the reversal. Because it uses the original posting date, the values net to zero in the same period.
Where the value shows up
| Business area | Impact for a facilities management company |
|---|---|
| Data accuracy | Mistakes corrected without leaving a period overstated |
| Audit trail | Reversals linked to the original document and user |
| Client reporting | Site-level emissions reports stay correct historically |
| Assurance readiness | Clear evidence of how errors were found and fixed |
| Efficiency | One action instead of manual offsetting entries |
In sustainability reporting, credibility depends on traceability. External assurance providers and clients want to see not just the right numbers, but how wrong numbers were corrected.
A worked scenario
Consider a facilities management company running 60 client sites (an illustrative example). In the March close, an analyst imports electricity data for one client's office and accidentally posts it twice.
In May, the client's sustainability manager questions the March figure. The analyst finds the duplicate in the sustainability ledger and uses Reverse Transaction. Business Central creates a reversing entry dated in March with the original document number, recording the analyst as the user who reversed it. March now shows the correct consumption, and the client receives a corrected site report with a clear explanation.
Adoption considerations
- Know what can be reversed. The action applies to entries posted from sustainability or general journals.
- Agree who can reverse. Restrict reversal rights to trained users.
- Document the reason. Keep a note of why each reversal was made.
- Re-post correctly. After reversing, post the correct entry so the data is complete.
- Communicate with clients. Where client reports are affected, explain corrections transparently.
The bottom line
Facilities management companies increasingly sell sustainability performance as part of their service. Reversing sustainability ledger entries in Business Central 29.0 lets them correct mistakes in a way that keeps historic reports accurate and audit trails clear. It's a small feature that underpins trust in the numbers.
If you report emissions to clients or assurance providers, it's worth reviewing your sustainability data processes with an experienced Business Central adviser.
Source: Microsoft roadmap 573376