Data Panda reads the budget workbooks, vendor registers and KPI submissions your team parks in a SharePoint document library, and lands the rows alongside the data from Exact, Salesforce and the rest of your stack. The file finance has been emailing around becomes a table the warehouse refreshes every night.
SharePoint Excel 365 is shorthand for one specific corner of Microsoft 365: the .xlsx files that live in a SharePoint site's document library, opened from the team channel rather than from somebody's personal OneDrive. The connector reads them through the Microsoft Graph workbook API, addressing the file as /sites/{site-id}/drive/root:/Finance/Budget%202026.xlsx:/workbook and pulling the worksheets, tables, named ranges and ranges your team curates inside it. Auth runs through Microsoft Entra with Sites.Read.All and Files.Read.All at the application tier, or the matching delegated scopes when a user signs in.
Operationally, the SharePoint variant matters because that is where the workbooks the rest of the company depends on quietly accumulate. The annual budget gets built once, dropped in Finance/Budgets/, and re-edited by three controllers for the next eleven months. The vendor register lives in Procurement/Vendors with macros nobody dares to touch. The KPI intake template is duplicated per branch and uploaded back to the same document library every month-end. Pulling those workbooks into the warehouse lets the rows sit beside Business Central postings, Exact invoices and Salesforce opportunities, so the numbers in the workbook can be checked, joined and historised instead of trusted on the strength of the last person who saved the file.
The cells, tables and named ranges your team edits in the SharePoint document library, joined to the systems they describe.
Let an edit in a shared SharePoint workbook drive the rest of your stack, without somebody re-typing the same number into the ERP on Monday morning.
Put the workbooks the team edits behind AI that answers on the numbers a CFO would defend, not on what a chat box guesses.
Small tools on top of shared 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 SharePoint Excel 365 data. Pick the one that matches your situation.
Where do the numbers in our shared SharePoint forecast disagree with what the ERP says happened?
Forecast cells from the workbook in the SharePoint document library 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 in the SharePoint folder, and how often does it come in late?
Per-branch KPI workbook in the document library 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 workbook in the folder has not been touched at all this period.
How do we know the shared budget workbook in SharePoint matches what ops is working from?
The approved budget workbook in the SharePoint site 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 workbook, the consolidated budget and the cost-centre tabs in the Finance document library 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 workbooks shared per region and the forecast tab the VP keeps in SharePoint 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.
Vendor registers, headcount plans and KPI submissions in the SharePoint folder stop living as files only the team knows about, and start showing up next to the operational systems they describe. Ops sees who submitted, who is late, and where a row in the register no longer matches the system it was supposed to track.
The forecast workbook in the Finance SharePoint folder 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 from SharePoint and sees where the forecast already disagrees with what the ERP booked.
Per-cost-centre budget tabs in the shared SharePoint workbook are consolidated and posted into the matching Dynamics 365 Business Central budget version, one entry per dimension and period. Finance keeps editing the workbook the controllers know in the document library, and Business Central holds the same numbers the rest of the ERP reports against.
The weekly forecast workbook in the SharePoint sales folder 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 shared workbook and the CRM stop telling two stories.
HubSpot deals and forecast amounts are written weekly into the shared finance forecast workbook in SharePoint, on the tab and rows finance already uses. The CFO opens the workbook from the document library 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 in the SharePoint document library 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 in SharePoint, 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 in SharePoint 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 in the document library. Owners stop chasing 'who changed the budget tab', because the change is on the channel where the work happens.
You keep the reporting tool you already have. We connect it to the warehouse where your SharePoint 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.
We review your SharePoint Excel 365 setup and the systems around it. Together we pick the first thing worth building.