Dynamics 365 Finance reporting without a Synapse project.
Between SSRS reports that need X++ and Power BI that needs a data model, most Finance and Supply Chain teams still hand-build the operational reports. Tau reads the data you already export and turns it into printed packs, dashboards, and scheduled deliveries.
Where Dynamics 365 Finance reporting becomes a project.
Out of the box, printed output is SSRS reports maintained in X++, which means a developer, a build, and a deployment for every change. Financial reporting (the Management Reporter successor) covers the statements. Operational reports, such as open sales orders by site, vendor invoice aging, or on-hand inventory by warehouse and batch, are an SSRS change or an Excel export.
For analysis, the supported paths are the Entity store, Synapse Link for Dataverse, and now Fabric link, each feeding Power BI. They work, and each one is a project with its own latency, its own cost, and a data model to build before the first dashboard. Bring your own database (BYOD) exports data entities to an Azure SQL database on a schedule, which is the simplest of the lot and the one most customers already have.
The OData data entities are there for integration, paged and throttled, and not something you want a report querying on every open.
What Tau reads from Dynamics 365 Finance, honestly.
Tau does not have a native Dynamics 365 Finance connector today. What Tau reads is what you already export. The BYOD Azure SQL database is a SQL Server to Tau: a read-only login and the entities you export are ready to query. A data warehouse export from Synapse Link or Fabric works the same way, and the OData data-entity feed can be mirrored locally, with Tau polling every minute and using webhooks when it has an HTTPS address.
A direct connector that reads data entities without an intermediate database is on the roadmap. If BYOD is not something you run, tell us and we will say how far along that is.
Runs on your server. One service on Windows or Linux, or a container. A read-only login. Reports are plain files with version history. Nothing leaves your network unless you schedule a delivery.
Reports Dynamics 365 Finance teams build first.
The demo runs on Northstar Coffee, an invented company in a real database. It shows the same report types below on sample data, not on Dynamics 365 Finance.
Open sales orders by site and warehouse
Grouped by legal entity, site, and warehouse with delivery status per line, page N of M, delivered as a PDF to each site manager every morning.
See this report type in the demo →Vendor invoice aging
A paginated aging by vendor and bucket per legal entity, plus a dashboard version with a right-click drill to the invoices.
See this report type in the demo →On-hand inventory matrix
Item groups down the side, sites and warehouses across the top, physical and available quantity in each cell, with totals on both axes.
See this report type in the demo →Customer statements per legal entity
One PDF per customer, with the right legal entity's header, invoices, payments, and aged balance, bursted on a schedule.
See this report type in the demo →Tau and Dynamics 365 Finance: the questions we get asked.
Which export does Tau need?
The simplest is BYOD: Tau reads the Azure SQL database as a SQL Server with a read-only login. A warehouse export from Synapse Link or Fabric, or the OData data-entity feed mirrored locally, also works. A direct connector is on the roadmap.
Does Tau handle multiple legal entities?
Yes. The data area or legal entity is a column in every exported entity, so a report can filter to one, group by it, or burst one PDF per entity to different recipients.
How fresh will the reports be?
As fresh as the export. BYOD incremental exports run on the schedule you set; a mirrored OData feed refreshes every minute. Each report shows when its data was last refreshed.
See it on your Dynamics 365 Finance data.
Tell us how you run Dynamics 365 Finance and the one report you wish you had. We will build it with you, live, and tell you plainly how Tau would connect.