Low-latency sync for Link to Fabric shortens the time between a posting in D365 Finance and Operations and the same row in Microsoft Fabric. Microsoft’s Fabric blog says most observed syncs now finish in under 15 minutes, while Microsoft Learn still documents up to an hour. For month-end close, that changes what finance can check during the close day: unposted journals, subledger tie-outs, intercompany balances, and movements against last month can be reviewed while there is still time to fix them. It does not make the close jobs run faster, and it does not lock a period. Because numbers now move in front of more people until the period is put on hold, frozen as-of snapshots matter more, not less. For how the sync works and what you still build on it, see Link to Fabric for D365 F&O.
What changes, and what does not
| Changes with fresher data | Does not change |
|---|---|
| Posted entries reach reports within the close day | How long settlement, revaluation, inventory close, and consolidation take to run |
| Each batch step’s result can be reviewed soon after it finishes | The order of the close: some steps still wait for others |
| Late postings, cutoff breaks, and intercompany mismatches are visible the same day | Period locking: the ledger calendar stops postings, and inventory close blocks inventory postings dated before its closing date |
| Flux reviews against last month and budget can run as entries land | Entries that are wrong at the source: a late or misposted entry still needs a correcting entry in F&O |
| Controllers can check tasks marked complete against ledger data the same day | The need to freeze an as-of version for sign-off |
Where low-latency sync stands in November 2026
- Status. Microsoft announced low-latency sync as generally available on June 9, 2026, with a station-by-station rollout it planned to finish by the end of July 2026 and called approximate. There is no opt-in: new links in an enabled station use it automatically. To check a link, open Link data, then Fabric Links, and look for the Low-latency mode flag.
- Existing links. A link created before your station was enabled keeps the previous engine until you unlink and relink it. Microsoft Learn lists minimum builds for F&O 10.0.47, 10.0.48, and 10.0.49; an environment below the minimum for its version must apply the latest quality update first. The build numbers are also in the Export to Data Lake guide.
- Speed. Microsoft Learn says incremental updates typically take up to an hour and gives only throughput for low-latency sync: up to 1 million or more records per hour per table, with actual sync times depending on initial load, data churn, table sizes, and number of columns. Microsoft’s Fabric blog says sync times are under 15 minutes for most observed cases, down from up to two hours. Measure yours at month-end volumes before you plan around either number.
- Measuring it. Microsoft warns that latency reports built on the difference between SinkModifiedOn and ModifiedOn can mislead, because a long-running F&O transaction can be synced several times and SinkModifiedOn shows only the last.
- What stays slow. F&O kernel tables, including DATAAREA, USERINFO, and the security tables, still run a full sync once a day. A new column on a linked table takes up to an hour to reach Fabric, and delta syncs can fail intermittently until it does, so freeze schema changes in close week.
Do not relink in close week. Unlinking deletes the Fabric lakehouse and fails while semantic models, pipelines, or other items still reference it. Relinking triggers a full initial sync of every table, and with long-term retention the shortcuts show only live data until Microsoft migrates the retained history. Microsoft recommends off-peak hours or weekends: plan it for the quiet days after the close.
How fresh each F&O reporting route is on close day
| Route | How fresh | Close-day caveat |
|---|---|---|
| Trial balance in F&O, with the dimension set balance feature | 0 to 5 minutes; since 10.0.47 an Update balances button runs it on demand | Inside F&O only |
| Financial reporting | General ledger transactions copied to its data mart every minute; exchange rates every 17 minutes | With thousands of accounts on historical rate translation, Microsoft says report data can lag up to an hour; a data mart reset takes 15 minutes to four hours, with reports unavailable |
| Embedded Power BI on the Entity store | Every hour at most with automated refresh, or on demand | Each aggregate measurement is refreshed separately |
| Account reconciliation workspace | Every six hours by default; the schedule can be changed | Shows when its data was last updated |
| Business performance analytics | Twice a day, at 12:00 AM and 12:00 PM UTC | The full pipeline can take four to five hours or more; see Fabric or Business performance analytics |
| Link to Fabric, as documented | Up to an hour for incremental updates, per Microsoft Learn, which gives no separate minutes figure for low-latency sync | Plus your model’s refresh |
| Link to Fabric, low-latency sync, as observed | Under 15 minutes for most observed cases, per Microsoft’s Fabric blog, which says the previous engine could take up to two hours | Plus your model’s refresh |
| Power BI on Fabric | Import: up to 48 scheduled refreshes a day; Direct Lake: framing reads only Delta metadata and can take a few seconds, and with automatic updates on, the model picks up new data without a schedule | Models that read through the SQL analytics endpoint wait for its metadata sync; a report is only as fresh as the slowest step between the posting and the visual |
Business Central does not use Link to Fabric; its routes into Fabric are compared in Business Central to Microsoft Fabric: what changes for BC reporting.
The close calendar in D365 F&O, and which steps stay batch jobs
The Financial period close workspace tracks closing tasks across companies, areas, and people for a closing schedule built from a template. Each task has a due date relative to the period end and can depend on other tasks; a padlock marks a task that is blocked by an unfinished dependency. The workspace tracks tasks that people mark complete. Marking a task complete does not check the ledger, so confirm each completed task against same-day ledger reports before the next one starts.
Posting is controlled separately, in the ledger calendar. Update period status sets a period to Open, On hold, or Permanently closed, and Update module access limits posting by module to all users, none, or a user group, across several legal entities at once. Microsoft recommends On hold at month-end and warns against Permanently closed, which cannot be reopened.
Microsoft’s close process map lists these subprocesses: finalize and post transactions, reconcile the ledger and subledgers, revalue currency, perform ledger settlements, consolidate and eliminate, prepare statements, and close the periods. Its Ledger settlements page puts two of them the other way around: run general ledger revaluation after ledger settlement, so unrealized gains and losses from earlier runs are not marked for settlement. Most of these steps are jobs, and none runs faster because data syncs faster:
- Subledger transfer. Batches move to the general ledger asynchronously or on a schedule.
- Ledger settlement, then revaluation. Microsoft says to revalue foreign currency in the general ledger after ledger settlement.
- Inventory close. A required month-end step for every inventory model except moving average; Microsoft recommends running it off-peak, and only the last closed inventory period can be reopened.
- Revenue recognition and deferrals. Recognition journals created by periodic processes, which can run in batch.
- Cash flow forecasts and consolidation. Calculations you run, covered below.
What fresher data changes is the wait after each step. Check reports after each step finishes, once the next refresh has picked up its postings, and review the result before the next step starts.
Checks you can run during the close day
- Unposted journals and pending transfers. Journals that are still open, and subledger batches not yet transferred to the general ledger, if those F&O tables are in your Link to Fabric selection.
- Cutoff. Entries dated in the closing period that were posted after the cutoff time.
- Subledger to ledger. The three exception types the Account reconciliation workspace uses (in subledger but not in ledger, in ledger but not in subledger, and amount mismatch), between its six-hour runs.
- Intercompany. Due to and due from balances by trading partner. Microsoft recommends unique main accounts for each company to simplify intercompany reconciliation and elimination.
- Inventory to the general ledger. Inventory value against the ledger after inventory close; in practice, differences usually trace back to misconfigured posting types or other posting setup.
- Flux review. Movement against last month and against budget by account and dimension, as entries land.
Running these checks during the day puts many people on the same reports at once, and that close-day peak is what a Fabric capacity has to be sized for; see Fabric capacity sizing for Dynamics 365 analytics.
Revenue, cash flow, and budgets on close day
Revenue recognition. Microsoft deprecated the sales-order Revenue recognition feature in January 2024 and points new users to subscription billing. In the older feature, Create journal on the Recognize revenue page recognizes lines up to an as-of date, and the journal is not posted automatically, so it can be reviewed first; lines are marked as processed when they are transferred, whether or not the journal is posted. In subscription billing, the recognition journal takes a cutoff date and includes only lines that end on or before it, and Microsoft notes that you can specify the transaction date for closed periods, so agree which period those entries post to before the books are frozen. The deferral balance report leaves out billing schedules that are on hold. Setup and schedules are covered in revenue recognition in D365 F&O.
Cash flow. A cash flow forecast does not update itself when its sources change. It is recalculated on the Calculate cash flow forecasts page, either in full or for new transactions only, or on a schedule through process automation, one schedule per company. After each calculation, Microsoft says to refresh the related Entity store measurement for the analytics to show it. Setup is covered in cash flow forecasting in D365 F&O.
Budgets and rebudgeting. A budget register entry is completed when budget balances are updated, and a completed entry cannot be reopened, so every revision or transfer is a new entry, recorded under a budget code of the matching type, such as Revision or Transfer. Budget control is tied to the fiscal period status: with a feature available since 10.0.49, a budget-controlled purchase requisition or purchase order dated in a closed or on-hold period can move to the next open period automatically, but never into a new fiscal year. Budget-versus-actual reports move with every posting during the close, so label which budget version and which as-of time a report shows. More in budgeting in D365 F&O.
Late postings and reconsolidation
When an entry lands after consolidation has run, Rerun consolidation on the Consolidate online page processes the same template and dates again, removing the earlier consolidation transactions and posting them again. Consolidation in Financial reporting can be generated at any time instead. Fresher data does not change either mechanism; it shows the late entry sooner, so the decision to rerun is made on the close day rather than after the statements are out.
Numbers keep moving until the period is on hold
Fresher data means more people see numbers that are still changing. A period on hold can be reopened for adjustments, and Microsoft says most organizations run year-end close more than once. D365 offers several ways to freeze a version:
- Account reconciliation snapshots give a final summary for a module and legal entity, but only for periods that are on hold or permanently closed and fully reconciled.
- Trial balance snapshots, available since 10.0.39, can be scheduled daily, weekly, or monthly through process automation and exported through an OData entity.
- Customer aging snapshots calculate aging as of a date, but Microsoft allows one snapshot per aging period definition, so keep an exported copy of each month-end run if you need the history.
Change Data Feed is not one of them: once enabled in the Power Platform admin center, it keeps record changes for about 24 hours, and Microsoft warns it can increase sync latency.
The working pattern: put the period on hold, freeze the reporting version at that moment, label every report with the time its data is as of, and compare the frozen version with the live one if the period is reopened. For close automation more broadly, see financial close automation in D365 F&O.
Where Metrixs fits
Metrixs runs in your own Microsoft Fabric environment on Link to Fabric or Azure Synapse Link. On the Standard plan, reports use Direct Lake and refresh every 15 to 30 minutes, depending on data volume, the number of reports, and Fabric capacity. Its receivables aging works by invoice date and by due date, is recalculated at each refresh, and keeps month-end snapshots. A report reconciles inventory value to the general ledger. Metrixs adds 150+ pre-built Power BI reports with 1,200+ metrics for D365 F&O. See D365 F&O analytics, or request a demo and see if you qualify for a free 6-month trial.
FAQs
1. How fast does Link to Fabric sync D365 F&O data now?
Microsoft Learn says incremental updates typically take up to one hour to appear and gives no minutes figure for low-latency sync, only throughput of up to 1 million or more records per hour per table. Microsoft’s Fabric blog says low-latency sync brings sync times under 15 minutes for most observed cases. Measure it in your own environment, at month-end volumes.
2. Does near-real-time data shorten the month-end close in D365 Finance?
It shortens the wait to see the result of each step, not the steps themselves. Ledger settlement, foreign currency revaluation, inventory close, revenue recognition journals, cash flow calculation, and consolidation still run as jobs in F&O. What changes is how soon finance can review each result: under 15 minutes for most observed cases with low-latency sync, per Microsoft’s Fabric blog, against up to an hour documented on Microsoft Learn, plus the report’s own refresh.
3. Which D365 F&O month-end steps still run as batch jobs?
Subledger transfer to the general ledger, ledger settlement, foreign currency revaluation, inventory close, revenue recognition and deferral journals, the cash flow forecast calculation, and consolidation. Microsoft recommends running inventory close off-peak.
4. Should we relink to low-latency sync before or during month-end?
Not during. Unlinking deletes the Fabric lakehouse and fails while semantic models or pipelines still reference it, and relinking triggers a full initial sync of every table. Microsoft recommends off-peak hours or weekends, so plan it for the quiet days after the close.
5. What is the difference between On hold and Permanently closed in D365 Finance?
A period that is On hold accepts no postings but can be reopened for adjustments. A period that is Permanently closed can never be opened again. Microsoft recommends setting periods to On hold at month-end and not to Permanently closed.
Sources
All pages below were checked on November 2, 2026.
- Link your Dataverse environment to Microsoft Fabric
- Microsoft Fabric link FAQ
- Power Platform blog: Announcing low-latency sync for Dataverse to Fabric in GA, June 9, 2026
- Fabric Updates blog: What’s new for Dataverse Fabric link, July 2026
- Financial reporting FAQ
- When to reset the Financial reporting data mart
- Automated Entity store refresh
- Business performance analytics home page
- ERP analytics MCP FAQ
- Financial dimension sets
- Data refresh in Power BI
- Direct Lake overview
- Financial period close workspace
- Update period status and module access
- Close the general ledger at period end
- Ledger settlements
- Foreign currency revaluation for the general ledger
- Inventory close
- Subledger transfer to the general ledger
- Account reconciliation workspace
- Intercompany accounting setup
- Revenue recognition overview
- Recognize deferred revenue
- Revenue and expense deferral schedules
- Cash flow forecasting
- Basic budgeting overview
- Budget control overview
- Consolidate online
- Consolidation and elimination overview
- General ledger account balances and trial balance snapshots
- Customer aging snapshots
- Year-end close
- Close financial periods business process overview
Senior functional consultant for Microsoft Dynamics 365 Finance and Operations, certified in MB-330, MB-300, and MB-920, and a Six Sigma Green Belt. Experience covers end-to-end F&O implementations and close work with end users, plus Azure DevOps and Power Platform. Specializes in the Crowe Metals Accelerator (CMA) for the metals industry, including cross-docking, pricing, production, and advanced warehouse management.
