Business Central Sustainability APIs: Goals, Purchase Emissions and ESG Reporting Integration

With Microsoft Dynamics 365 Business Central, Microsoft has been steadily building out native Sustainability Management capabilities to bring greenhouse gas (GHG) tracking, water usage, and waste intensity directly into the operational core. Now, tracked under AI at Work roadmap ID 576874 and documented in the Dynamics 365 2026 release plan, Microsoft has launched four dedicated Sustainability APIs designed to automate data flows between Business Central and external software.

If you are an IT administrator, solution architect, or developer tasked with wiring Business Central into third-party ESG platforms, procurement portals, or business intelligence pipelines, this update changes what you can automate out of the box. However, not all four endpoints behave the same way. Understanding the strict boundary between what is writable and what is strictly read-only is essential before you start promising your compliance officers a fully automated nirvana.

Rollout Timeline and Roadmap Context​

According to Microsoft Learn's 2026 release wave 1 documentation and the AI at Work roadmap, the capability—officially titled Use new APIs in Sustainability for better integration—entered public preview on April 1, 2026, and reached general availability on June 5, 2026, for Worldwide Standard Multi-Tenant cloud environments. The feature is enabled automatically for end users, meaning administrators in Business Central online do not need to flip a special feature switch to make the endpoints appear.

Why is a June release showing up as a fresh October entry on the Microsoft 365 AI at Work roadmap? As noted in Microsoft Learn's release plan archives, Microsoft transitioned its tracking of Dynamics 365, Power Platform, and Dataverse capabilities over to the unified AI at Work roadmap starting in September and October 2026. The underlying functionality is live, launched, and ready for integration work.

Microsoft states that the business value of these additions is to reduce manual data handling, improve accuracy, synchronize sustainability goals, exchange emission details with procurement systems, and support regulatory compliance. While that is Microsoft's intended rationale, any veteran systems integrator knows that an API is only as good as the data model behind it. Let's look under the hood at the exact entities Microsoft has exposed.

Breaking Down the Four New Sustainability APIs​

Before this update, Microsoft Learn's Sustainability API reference already covered foundational entities such as sustainabilityAccountCategory, sustainabilityAccountSubcategory, sustainabilityAccount, sustainabilityJournalLine, and sustainabilityLedgerEntry. Those allowed connected apps to inspect the chart of sustainability accounts and work with journal lines or posted ledger entries.

The new release adds four specific API entities to the standard Business Central REST API framework. Crucially, two of them allow full read/write operations (GET, POST, PATCH), while the other two are strictly read-only (GET only).

1. Sustainability Goals (sustainabilityGoal)​

If your organization manages corporate climate targets in a specialized third-party planning tool or corporate scorecard platform, the sustainabilityGoal endpoint provides a two-way street. Because it supports GET, POST, and PATCH, external applications can read existing goals, insert new ones, or modify targets as corporate mandates evolve.

According to Microsoft Learn's Sustainability API reference, the entity exposes organizational metadata including the scorecard number, goal number, line number, name, owner, responsibility center, country/region code, unit of measure, and both active (startDate, endDate) and baseline date ranges (baselineStartDate, baselineEndDate), alongside a mainGoal flag.

More importantly, it breaks out discrete decimal fields across five environmental tracking pillars for baselines, current values, and target values:

• Carbon dioxide (CO2)
• Methane (CH4)
• Nitrous oxide (N2O)
• Waste intensity
• Water intensity

Keep in mind that while this endpoint lets you synchronize the target framework and current recorded values, the API itself is a data transport layer—it does not independently calculate organizational progress outside of Business Central's internal engine.

2. Purchase Lines with Sustainability Detail (sustainabilityPurchaseLine)​

For most supply-chain-heavy businesses, Scope 3 emissions—the indirect emissions buried in purchased goods, raw materials, and upstream logistics—are the hardest to wrangle. The sustainabilityPurchaseLine endpoint is arguably the most practical workhorse of the four additions because it supports GET, POST, and PATCH operations directly on purchase lines that carry environmental value-tracking information.

In addition to standard procurement fields like document numbers, item numbers, descriptions, quantities, unit costs, discounts, VAT, currency codes, and job numbers, Microsoft Learn documents several sustainability-specific properties on this entity:

• Account Mapping: sustAccountName and the associated sustainability account number.
• Energy Tracking: energySourceCode, energy consumption amounts, and a boolean renewableEnergy compliance flag.
• Emissions and Costing: Emissions data for CO2, CH4, and N2O, along with totalEmissionCost.
• Verification and Regulatory Flags: sourceOfEmissionData (string), emissionVerified (boolean), and cbamCompliance (boolean), which tracks whether the purchase line's Carbon Border Adjustment Mechanism status is verified.

Having POST and PATCH access here means an external procurement portal or supplier network can inject supplier-verified emissions data and CBAM compliance flags directly onto purchase lines as orders or invoices are created, rather than waiting for an accountant to key them in after the fact.

3. ESG Reporting Staging (postedESGReportLine)​

When it comes time to pull structured environmental disclosures into external business intelligence suites or statutory filing tools, the postedESGReportLine API provides read-only (GET) access to staged ESG reporting data.

Microsoft Learn shows that this endpoint exposes the structural anatomy of an ESG report line: the template name, esgReportingName, line number, grouping information, row number, description, reportingCode, conceptLink, and concept. It also surfaces technical lineage fields such as the underlying Business Central table number (tableNo), table field number (source), fieldCaption, valueSettings, accountFilter, reportingUnit, rowType, rowTotaling model, calculation instructions (calculateWith), display settings (show), and rounding rules.

Because this endpoint is strictly read-only, integrators cannot use it to push edits back into staged ESG reports or trigger statutory submissions directly through the API.

4. Emission Value Entry (sustainabilityValueEntry)​

The second read-only (GET) endpoint is sustainabilityValueEntry, which corresponds to the roadmap's "Emission Value Entry" item. In Business Central, value entries tie financial or quantitative adjustments to inventory items and capacity operations. This API exposes the carbon footprint equivalents calculated inside the ERP.

Per Microsoft Learn's schema documentation, developers can query the ledger entry number, document type and number, posting date, connected itemLedgerEntryType and itemLedgerEntryNo, itemNo, and capacityLedgerEntryNo. On the quantitative side, it provides valuedQuantity, itemLedgerEntryQuantity, invoicedQuantity, carbon footprint per unit (co2EPerUnit), actual carbon footprint (co2EAmountActual), and expected carbon footprint (co2EAmountExpected), alongside user IDs, source codes, sustainability account numbers/names, and project links (jobNo, jobTaskNo).

This is a treasure trove for data engineers building granular cost-and-carbon-per-SKU dashboards in Power BI or Microsoft Fabric, allowing them to see how actual versus expected $\text{CO}_2\text{e}$ tracks against inventory movement without recalculating the math outside the ERP.

Section Summary: The API Roster​

• Writable (GET, POST, PATCH): sustainabilityGoal and sustainabilityPurchaseLine allow external systems to push and update goal metrics and procurement-linked emissions data.
• Read-Only (GET): postedESGReportLine and sustainabilityValueEntry allow downstream analytics and reporting tools to extract staged report structures and calculated item/capacity carbon footprints.

Practical Caveats: How Business Central's Rules Affect Your API Calls​

Anyone who has ever built an integration against an ERP knows that REST endpoints do not exist in a vacuum. When you POST or PATCH a record into Business Central, your payload is still governed by the application's underlying business logic. Microsoft Learn's documentation on recording sustainability entries highlights several workflow constraints that developers need to account for when working with sustainabilityPurchaseLine.

First, while Business Central supports sustainability fields across purchase orders, invoices, credit memos, and return orders, there is a hard mutual exclusivity rule between manual emission amounts and formula-based calculations on a single purchase line. As documented by Microsoft Learn:

• You cannot combine manual emission amounts and formula values on the same line.
• If a line already contains manual values in Emission CO2, Emission CH4, or Emission N2O, those values must be cleared before formula values can be entered—and vice versa.
• Formula values can only be modified while the purchase document is open and the line has a valid Sustainability Account No. assigned.

Second, if your organization relies on Business Central to calculate purchase line emissions via built-in formulas rather than receiving pre-calculated emissions from a supplier via the API, an administrator must first enable Use Emissions in Purchase Documents and Use Formulas in Purchase Documents in the setup pages, and configure each sustainability account with a valid category (Emission Scope and Calculation Foundation) and subcategory (emission factors). Furthermore, while purchase documents support formula calculations for Scope 1, Scope 2, and Scope 3 categories, formulas for the Water/Waste scope are not supported on purchase documents. Attempting an unsupported combination triggers a calculation error in Business Central.

Finally, remember what happens at posting time: when a purchase document is posted, Business Central generates an independent Sustainability Ledger Entry for each purchase line that carries a Sustainability Account No.. The sustainabilityPurchaseLine API reference lists the entity's properties, but it does not guarantee that every single field is independently editable in every document state. Integrators should test field-level validation rules in a sandbox before deploying automated procurement syncs to production.

Enabling and Verifying the APIs: Online vs. On-Premises​

How you prepare your environment for these endpoints depends entirely on where your Business Central instance lives.

According to Microsoft Learn's API enablement documentation, APIs for Business Central online are enabled by default. Coupled with the release plan's confirmation that these four Sustainability APIs are enabled automatically for end users, cloud customers can immediately inspect and consume the endpoints using standard REST authentication and permissions.

However, if you are managing Business Central on-premises, APIs require explicit server-level activation. Microsoft Learn outlines the required procedure for on-premises administrators:

1. Open the Business Central Administration Shell.
2. Enable OData services by running:
   Set-NAVServerConfiguration <BC server instance name> -KeyName ODataServicesEnabled -KeyValue true
3. Enable API services by running:
   Set-NAVServerConfiguration <BC server instance name> -KeyName ApiServicesEnabled -KeyValue true
4. Verify that the PublicODataBaseUrl and ODataServicesPort parameters are properly configured (using Get-NAVServerConfiguration <BC server instance name>), and ensure that your Windows Firewall allows traffic on the OData port (which defaults to 7048).
5. Inside the Business Central client, search for and open API Setup, then select the Integrate APIs action to populate the integration tables (a process that can take several minutes).

If an integration developer comes to your desk complaining that their calls to a local Business Central server are bouncing back with an HTTP status code 405 (Method Not Allowed), check your server configuration first—Microsoft notes that a 405 error on-premises is the classic symptom that SOAP, OData, or API services have been turned off.

Regardless of whether you run in the cloud or on-premises, administrators and developers can verify which endpoints are published in their specific build by opening the API Overview page inside Business Central, which lists all active API pages, queries, and codeunits.

Final Thoughts for Architects and Admins​

Adding sustainabilityGoal, postedESGReportLine, sustainabilityValueEntry, and sustainabilityPurchaseLine to the Dynamics 365 Business Central REST catalog is a pragmatic step forward. Rather than forcing mid-market companies to buy monolithic, all-in-one environmental suites or rely on brittle CSV exports, Microsoft is opening the plumbing so Business Central can act as the system of record for financial and operational carbon accounting while playing nicely with specialized external tools.

Before you cut your integration code loose on production data, spin up a sandbox environment, open the API Overview page, and test your POST and PATCH payloads against sustainabilityPurchaseLine and sustainabilityGoal. Pay special attention to how your payloads interact with open versus posted documents and formula versus manual entry rules. Get those boundaries right in testing, and your compliance team might finally be able to recycle that shoebox.