On 3 November, Microsoft announced that it is “welcoming Microsoft Sustainability Manager into the Dynamics 365 ERP portfolio”, under a new name: Microsoft Dynamics 365 Sustainability. The post promises “greater interoperability with Dynamics 365 Finance, including a green ledger view”.
Most coverage will focus on the rename. The more interesting part is the direction. Emissions data is moving out of a side system and into the ERP, next to the transactions that cause it. In Business Central, that has already happened: since October 2024, emissions can be recorded on purchase invoices and posted to a sustainability ledger alongside the financial entries.
That changes how emissions data fails. A spreadsheet error is visible to whoever opens the spreadsheet. A posting error isn’t. It looks exactly like a correct entry, it rolls up into reports, and nobody notices until someone checks it against the source. Finance teams learned that lesson with money a long time ago. Business Central sustainability testing is about learning it again for carbon.
Once emissions post like money, they fail like money: silently, plausibly, and only visible when someone reconciles.
This piece covers what Microsoft did and didn’t announce, how emissions actually post in Business Central, five ways the numbers go wrong without an error, and what to test before an auditor asks.
What Microsoft Announced, and What It Didn’t
It’s worth being precise, because the announcement is lighter on detail than the headline suggests.
| The announcement says | The announcement doesn’t say |
| Sustainability Manager joins the Dynamics 365 ERP portfolio as Dynamics 365 Sustainability | When anything changes for existing customers, or whether there’s any migration |
| Greater interoperability with Dynamics 365 Finance, including a green ledger view | How the green ledger works or when it ships. There’s no Microsoft Learn documentation for it yet |
| Scope 1, 2 and 3 emissions, water and waste, calculated from activity data and emission factors | Licensing or pricing |
| Support for frameworks including CSRD, GRI, IFRS Sustainability Disclosure Standards and SASB | Business Central or Supply Chain Management integration |
| Agents can work with sustainability data through the Dataverse MCP server in Copilot Studio | Any released AI feature for emissions data. Its Scope 3 example starts with “Imagine” |
So for Dynamics 365 Finance, this is a direction to plan for rather than a feature to test this quarter. For Business Central, the sustainability ledger is documented, generally available and testable now. The rest of this piece uses it as the worked example; the same questions will apply to Finance’s green ledger when it arrives.
How Emissions Post in Business Central
Business Central’s sustainability features are set up like a second chart of accounts. Microsoft’s sustainability management overview describes the pieces; here’s how they fit together:
| Piece | What it holds | Why it matters for testing |
| Chart of sustainability accounts | Accounts with the same structure as a chart of accounts, including totals | Every emission lands on an account, and reports read from these accounts |
| Account category | The emission scope (1, 2, 3, out of scope, or water/waste), which gases are tracked, and the calculation foundation (fuel/electricity, distance, installations, custom) | The category, not the person posting, decides which scope an emission counts toward |
| Account subcategory | The emission factors for CO2, CH4 and N2O, or water and waste intensity factors | The multiplier behind every calculated number |
| Emission fees | Carbon equivalent factors and internal carbon fees by gas, with optional date ranges, country and responsibility centre | How CH4 and N2O are converted to CO2e |
| Sustainability journals | Manual entries or formula-based entries, with standard and recurring templates and approval workflows | The main manual path into the ledger |
| Purchase documents | A Sustainability Account No. and emission or formula fields on purchase lines | Emissions post when the invoice posts |
| General journals | Total CO2, CH4 and N2O amounts on invoice and credit memo lines | A second path, with totals only and no formulas |
| Sustainability ledger | Posted entries, which can’t be edited or deleted | What every sustainability report is built from |
The design mirrors the general ledger closely, and that’s the point. It also means every lesson from testing financial postings applies, including the uncomfortable one: a successful posting proves the entry was valid, not that it was right.
Five Ways Emissions Go Wrong Without an Error
None of these raises an error in Business Central. Each produces a ledger that looks complete and a report that adds up.
1. The right number in the wrong scope
Scope comes from the account category. Map a purchased-electricity account to a Scope 3 category instead of Scope 2 and every kilowatt-hour posts correctly, to the wrong line of the disclosure. The total is unchanged, so a total-level check passes. Only a check of each account’s scope against your classification policy catches it.
2. Factors that changed after the numbers were entered
Emission factors live on the subcategory. Microsoft notes that if factors change after journal lines are filled in, you must run Recalculate to get the right amounts. Skip it and the journal posts the old figures. Business Central also has a setting, Block Calculation Foundation Change If Ledger Entries Exist, that stops a formula changing once it has been used. If it’s off, last year’s entries and this year’s can be calculated two different ways under the same account.
3. CO2e conversion set up the wrong way round
The Carbon Equivalent Factor on the Emission Fees page converts other gases into CO2 equivalent. Microsoft’s own example is easy to get backwards: if 1 kg of N2O equals 298 kg of CO2, you divide 1 by 298 and enter 0.00336. Someone who enters the global warming potential itself has set up the conversion the wrong way round, and every N2O figure posts with a confident, wrong CO2e value. Entries posted before CO2e was set up also need the Update Carbon Fees action, or they keep the old values.
4. Corrections that fix the money but not the carbon
This is the one finance teams will trip over. Microsoft is explicit that reversing a G/L transaction “doesn’t automatically reverse its sustainability ledger entries”, and that reversing a sustainability entry doesn’t touch the related G/L entry or document. Entries posted from a purchase document can’t be reversed directly at all: you correct them with Cancel, Correct or a corrective credit memo, which copies the values from the posted invoice. A correction made only on the financial side leaves the emissions standing.
Partial postings need care too. When you invoice part of a line, Business Central posts a proportional share of the formula-based emissions, so a three-part invoice should add up to the full line. That’s an easy assertion to make, and an easy one to skip.
5. Emissions calculated from the general ledger
A custom category can Calculate from General Ledger: Business Central sums G/L entries that match a G/L account filter and date range, and you run Collect Amount from G/L Entries before posting. Two things to know. It sums the absolute value of the matching amounts, so a credit adds to the total rather than reducing it. And the filter only covers the accounts it names, so a new G/L account added for the same spend quietly falls outside it.
What to Test Before an Auditor Asks
Treat sustainability postings the way you already treat financial ones: known inputs, a known expected result, and an assertion on what landed in the ledger.
| Test | Set up | Assert |
| Scope mapping | List every sustainability account with its category | Each account’s scope matches your classification policy; nothing posts to “out of scope” by accident |
| Formula calculation | One purchase line per calculation foundation in use, with known quantities and factors | CO2, CH4 and N2O on the ledger entry match a hand calculation |
| CO2e conversion | A line for each gas, using Microsoft’s 298 → 0.00336 example as the pattern | CO2e equals the expected value for each gas |
| Factor change | Fill a journal, change a factor, then post with and without Recalculate | You know which value posts; the block-calculation-change setting matches your policy |
| Partial invoicing | Invoice one purchase line in three parts | The three ledger entries add up to the full line’s emissions |
| Corrections | Cancel or correct a posted invoice; separately reverse a G/L transaction | Emissions reverse with the document; a G/L-only reversal leaves emissions, so your process catches it |
| G/L-derived totals | Post a credit and a new G/L account inside the period | The collected amount behaves the way you expect for credits and new accounts |
| Reports | Run the sustainability reports for the period | Report totals reconcile to the sustainability ledger by scope and account |
Run the set when you first configure sustainability, again after any change to accounts, categories or factors, and after Business Central updates. The update side of that is covered in our guide to Business Central update testing; sustainability scenarios belong in that regression set.
If purchase invoices already change your numbers after posting through cost adjustment, the same invoices now carry emissions too. Our piece on Business Central inventory costing covers the financial side of that ripple.
Why Assurance Raises the Stakes
Emissions numbers used to live in reports that few people checked line by line. That’s changing. Under the EU’s Corporate Sustainability Reporting Directive (CSRD), sustainability information has to be externally assured, and Microsoft lists CSRD among the frameworks Dynamics 365 Sustainability supports. Assurance means someone will sample entries and trace them back to source, the way financial auditors do.
That makes the evidence matter as much as the number: which factor was applied, when it changed, who posted the entry and how corrections were made. A tested configuration, with test results kept, is the easiest evidence to hand over. Our SOX testing checklist for AI agents in ERP covers how to keep that kind of evidence for financial controls, and most of it carries straight across.
Where Agents Come In
Microsoft’s announcement points agents at sustainability data through the Dataverse MCP server in Copilot Studio, and invoice capture is already being automated: Business Central’s Payables Agent drafts purchase invoices from emailed PDFs, which a person then reviews and posts. As more of the path from supplier document to ledger entry gets automated, the emission values on those lines need the same scrutiny as the amounts. Our BC Payables Agent testing piece covers the invoice side.
Where Sofy Fits
Sofy’s Dynamics 365 test agents cover Business Central: the product page says they validate financials, purchasing, inventory, sales orders and postings. Sustainability entries travel the same roads, posted from purchase documents and journals, so the scenarios above sit naturally beside your existing purchasing and posting tests rather than in a separate project.
The page also says the agents adapt automatically to Microsoft’s updates without re-recording, and run from Azure DevOps pipeline triggers, so sustainability scenarios can run on every update instead of once a year before the report is due.
SEE IT ON YOUR BUSINESS CENTRAL POSTINGS
Watch Sofy’s agents run purchasing and posting scenarios end to end in your own Business Central environment.
What Still Needs a Human
Testing proves the system calculates what you configured. It can’t tell you whether the configuration is right: which emission factor source to use, how to classify a borderline purchase between scopes, or whether an estimate is good enough to report. Those are decisions for your sustainability lead and, increasingly, your auditor.
And factors change in the real world. When a supplier publishes a new emission factor or a grid’s electricity mix shifts, someone has to decide when the new value applies. Business Central’s date-effective emission fees can hold the answer; a person still has to supply it.
Frequently Asked Questions
What is Dynamics 365 Sustainability?
It’s the new name for Microsoft Sustainability Manager, which Microsoft announced on 3 November 2026 is joining the Dynamics 365 ERP portfolio. Microsoft says it helps organisations record environmental impact, report progress and reduce their footprint, with closer interoperability with Dynamics 365 Finance, including a green ledger view.
Does Business Central track emissions?
Yes. Business Central has a chart of sustainability accounts, sustainability journals and a sustainability ledger. Emissions can be recorded on purchase documents and general journals, calculated from emission factors, converted to CO2 equivalent and reported by scope.
Can you edit a posted sustainability ledger entry?
No. Posted entries can’t be edited or deleted. Entries from journals can be reversed; entries from purchase documents are corrected with Cancel, Correct or a corrective credit memo. Reversing a G/L transaction doesn’t reverse its sustainability entries.
How do you test emissions data in an ERP?
The same way you test financial postings: post known transactions with known factors, then assert what landed in the ledger, including the scope, each gas, the CO2e value and the posting date. Add tests for corrections, partial invoices and factor changes, and reconcile reports to the ledger.
Why does sustainability data need the same rigour as financial data?
Because it’s posted and reported the same way, and increasingly audited the same way. Under CSRD, sustainability information needs external assurance, so auditors will trace entries back to source, just as they do with financial postings.
The Bottom Line
Microsoft’s announcement is a signal more than a release: sustainability is becoming part of the ERP, and Finance’s green ledger is on the way. In Business Central it’s already here, and it behaves like any other ledger. It posts what you configured, it can’t be edited, and it doesn’t tell you when the configuration is wrong.
Test it the way finance teams test money. Know the expected number before you post, check the scope as well as the total, follow every correction through to the emissions, and keep the results. When the assurance request arrives, that evidence is what you’ll want to hand over.