Data Panda brings the worksheets, ranges and tables your team types into Excel 365 alongside the data from the rest of your business. From one place, we turn budget files, forecast tabs and KPI submissions into dashboards, automations, AI workflows and apps your team uses every day.
Excel 365 is Microsoft's spreadsheet on the cloud, the subscription edition that lives in your browser and stores its workbooks in OneDrive for Business and SharePoint. The Excel 365 connector talks to those workbooks through the Microsoft Graph workbook API: read worksheets, ranges, tables and named ranges; write rows back into a table; open a session that either persists the change to the file or keeps it scoped to the API call. Auth runs through Microsoft Entra with the standard Files.Read or Files.ReadWrite scopes.
Excel is also the system of record nobody chose but every SMB ends up with. The annual budget gets built in a workbook with a tab per cost centre. The sales forecast gets typed into a forecast file every Friday. The HR headcount plan and the production target sheet live as cells in OneDrive. Pulling that into a warehouse alongside Exact actuals, Salesforce pipeline and Business Central GL turns the file finance has been emailing around into a table the rest of the business can join, version and trust.
The cells, tables and named ranges your team edits, joined to the systems they describe.
Let an Excel row or a tab change drive the rest of your stack, without somebody re-typing the same number into the ERP on Monday morning.
Put your real workbooks behind AI that answers on the numbers a CFO would defend, not on the ones a chat box guesses.
Small tools on top of your workbooks for people who shouldn't need to open the file to do their job.
A list of concrete reports, automations and AI features we have built on Excel 365 data. Pick the one that matches your situation.
Where do the numbers in our Excel forecast disagree with what the ERP says happened?
Forecast cells from the workbook joined line-by-line to Exact or Business Central actuals on the same period and account, with the variance and the user who saved the last forecast version. Surfaces the lines where the forecast is structurally optimistic, the lines where the ERP posting category drifted from what finance assumed, and the cost centres where the gap is large enough to redo before the board pack ships.
Which branches still owe us their KPI submission, and how often does it come in late?
Per-branch KPI workbook tracked against deadline, last-saved-by, and a check against the source system the cell is supposed to match. Tells you which managers consistently miss the cut-off, which branches submit numbers that the ERP cannot back up, and which workbooks have not been touched at all this period.
How do we know the budget that finance approved is the same budget the ops team is working from?
The approved budget workbook in SharePoint is the source, and every other working copy is reconciled against it on cost-centre, account and period. Differences land as a flag on the cost centre that owns them, with the cell, the tab and the timestamp where the divergence started, so the conversation is on a row instead of on a feeling that 'last quarter's budget got changed somewhere'.
The forecast file, the budget workbook and the cost-centre tabs land beside Exact, Business Central and the rest of the GL. Variance analysis stops being a Friday-afternoon copy-paste and becomes a query against one source, with the cell and the user who saved it both visible.
Pricing sheets, quota worksheets and the forecast tab the VP keeps in Excel land next to the live Salesforce or HubSpot pipeline. The number on the call is the same number the workbook says, with the date and the cell to back it up.
Headcount plans, production targets and KPI submissions stop living as files in someone's OneDrive and start showing up next to the operational systems they describe. Ops sees who submitted, who is late, and where a target cell no longer matches the system it was supposed to track.
The forecast workbook in SharePoint is matched line by line to Exact Online actuals on period, account and cost centre. Variances land back in a comment column or a side-tab, refreshed on every save, so finance opens the same workbook and sees where the forecast already disagrees with what the ERP booked.
Per-cost-centre budget tabs in Excel are consolidated and pushed into the matching Dynamics 365 Business Central budget version, with one entry per dimension and period. Finance keeps editing the workbook the controllers know, and Business Central holds the same numbers the rest of the ERP reports against.
The weekly forecast workbook is matched to Salesforce opportunities on account, owner and close date. Forecast cell changes update the matching opportunity stage or amount, and Salesforce changes flow back into the next forecast snapshot, so the VP's spreadsheet and the CRM stop telling two stories.
HubSpot deals and forecast amounts are pushed weekly into the finance forecast workbook, on the tab and rows finance already uses. The CFO opens Excel and sees a pipeline figure that matches what HubSpot reports, instead of waiting for sales to email a fresh export every Friday.
Branch KPI workbooks are checked against the monthly deadline. When a branch has not saved its workbook by the cut-off, a monday.com card opens on the right board with the branch, the responsible manager and a link to the empty workbook, so the chase happens on the board the team already lives in.
Edits to flagged cells, tabs or named ranges in a finance or ops workbook post a compact update to the Slack channel that owns the file, with the user, the value before and after, and a link back to the workbook. Owners stop chasing 'who changed the budget tab', because the change is on the channel where the work happens.
These are the 1 tables we currently pull from Excel 365 into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your Excel 365 data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Through the Microsoft Graph workbook API on a file stored in OneDrive for Business or a SharePoint document library. Auth runs through Microsoft Entra with the <code>Files.Read</code> scope for read-only sync or <code>Files.ReadWrite</code> when the connector needs to push rows back into a table or update a range. Microsoft documents that consumer OneDrive workbooks are not supported by the Graph Excel API, and only Office Open XML (.xlsx) files work, not the legacy .xls format.
An Excel table (a named range with a header row that Excel knows is a table) is the easy case: the connector reads it as rows with column names and writes new rows back through the table API, no fragile cell coordinates involved. A free-form range like <code>A1:G500</code> can also be pulled, but the contract is weaker because columns shift when somebody inserts a header. For workbooks that the warehouse will have to read every day, converting the relevant area to a real Excel table once is usually the cheapest investment.
Microsoft publishes a per-tenant cap on the Excel resource family of 1,500 requests per app per 10 seconds, with a per-app-across-tenants cap of 5,000. On a tenant with hundreds of workbooks under sync that matters. We schedule reads in off-hours batches, open a persistent workbook session per file so a sequence of reads counts efficiently, and back off cleanly on a 429 instead of hammering the same file.
We review your Excel 365 setup and the systems around it. Together we pick the first thing worth building.