Guide 21 mins

Excel-Based Reporting to D23.io: Helping Finance Teams Move On

Move finance teams from email-attached Excel packs to governed D23.io dashboards. Real change-management patterns that work for mid-market AU finance leaders.

The PADISO Team ·2026-05-11

The Excel Problem: Why Finance Teams Are Stuck
What D23.io Actually Does (And Why It Matters)
The Hidden Costs of Excel-Based Reporting
Understanding D23.io’s Architecture for Finance
The Change-Management Framework That Works
Governance, Security, and Audit-Readiness
Implementation Patterns: From Spreadsheet to Dashboard
Real Outcomes: What Finance Teams Actually See
Common Mistakes and How to Avoid Them
Next Steps: Getting Started

The Excel Problem: Why Finance Teams Are Stuck {#the-excel-problem}

Your finance team lives in Excel. Not because they love it—because they inherited it, it works, and moving away feels like risk.

Every month, someone manually pulls data from three systems, copies it into a master workbook, runs formulas that took six months to get right, and emails a 40MB file to 12 people. Two of them edit it. One overwrites another’s changes. The CFO gets the “final” version—which is actually version 7 of 8—and makes decisions on data that’s already three days stale.

This is normal in mid-market Australian finance operations. And it’s also a slow-motion disaster.

Excel is a calculator pretending to be a database. It’s brilliant for one-off analysis. It’s catastrophic for governed, repeatable financial reporting. Yet most finance teams never seriously consider moving because:

They don’t know what the alternative looks like
The switch feels expensive and disruptive
They’ve heard horror stories about “BI tools” that require IT involvement for every change
Excel is free (they think), and the cost of staying feels lower than the cost of moving

The problem is that Excel’s true cost—in reconciliation time, version control nightmares, audit risk, and delayed decision-making—is invisible until you measure it.

This is where D23.io enters the picture. Not as a replacement that requires learning a new skill, but as a governed layer on top of your data that lets finance teams build dashboards in hours instead of weeks, and actually know which number is real.

What D23.io Actually Does (And Why It Matters) {#what-d23-io-does}

D23.io is a modern business intelligence (BI) platform built on Apache Superset, designed specifically for teams that need to move past email-attached reporting without needing a data engineering degree.

Here’s the concrete difference:

With Excel:

Data lives in spreadsheets
Each user manages their own version
Formulas are hidden in cells
Audit trail exists only in email timestamps
Updates are manual and slow

With D23.io:

Data lives in a single source of truth (your database)
Everyone sees the same numbers, always
Logic is defined once in a semantic layer, reused everywhere
Every change is logged and traceable
Updates happen automatically when source data changes

For finance teams specifically, this means:

Real-time visibility: P&L, cash flow, and variance reports update automatically, not on a monthly batch schedule
Governed metrics: Finance defines what “revenue” means once. Every dashboard, report, and user sees the same definition
Audit trail: Every view, filter, and export is logged. SOC 2 and ISO 27001 auditors actually like this
Self-service without chaos: Finance analysts can build their own dashboards without breaking anything or asking IT for help
Mobile and embedded: Dashboards work on phones, tablets, and can be embedded in portals for external stakeholders

The PADISO team has shipped fixed-fee D23.io rollouts in 6 weeks, including semantic layer setup, single sign-on (SSO), and trained finance teams to the point where they’re building new dashboards themselves. That’s not magic—it’s pattern repetition.

The Hidden Costs of Excel-Based Reporting {#hidden-costs-excel}

Most finance leaders have never quantified what Excel-based reporting actually costs. They see the spreadsheet as free, so they don’t measure the labour, risk, and opportunity cost it creates.

Time Sunk in Data Wrangling

A typical mid-market finance team spends 40–60% of their time on data wrangling: pulling data from multiple systems, reconciling mismatches, reformatting for reporting, and troubleshooting broken formulas after someone accidentally deletes a row.

If your finance team is 5 FTEs, that’s 2–3 people doing nothing but data plumbing. At $80K–$120K per person, you’re running a $160K–$360K annual cost centre that doesn’t produce insight—it just moves data around.

D23.io eliminates this. Once the semantic layer is set up, data flows automatically. Your team shifts from “where’s the number?” to “what does this number mean?”

Version Control and Reconciliation Risk

Excel spreadsheets are notoriously fragile. A single formula error, a manual edit, or an overwritten file can corrupt months of data. Auditors hate this. Your finance team spends hours reconciling versions to find out which number is actually true.

D23.io enforces a single source of truth. Every metric is calculated once, in the semantic layer. There are no copies, no versions, no reconciliation nightmares.

Decision Delay

When your CFO asks for last week’s cash position, and the answer requires a 2-day manual pull-and-format cycle, decisions get delayed. In fast-moving businesses, that’s expensive.

With D23.io, a dashboard shows real-time cash position. The CFO sees it in the morning. The decision happens the same day.

Audit and Compliance Risk

If you’re pursuing SOC 2 compliance or ISO 27001 certification, auditors will ask: “How do you know the numbers in that spreadsheet are correct? Who changed it? When? Why?”

Excel has no answers. D23.io has a full audit trail.

Scaling Pain

As your business grows, Excel breaks. You add more sheets, more formulas, more dependencies. What took 2 hours to update now takes 8. You hire another analyst just to keep the spreadsheet working.

D23.io scales. More users, more dashboards, more data—the system handles it without additional manual effort.

Understanding D23.io’s Architecture for Finance {#d23-io-architecture}

To move a finance team from Excel to D23.io, you need to understand the architecture, not because you’ll build it yourself, but because it shapes how you think about the migration.

The Three Layers

Layer 1: Data Source

Your data lives in a database (PostgreSQL, Snowflake, BigQuery, etc.). D23.io connects to this database—it doesn’t move data or create copies. This is critical for audit purposes: your database remains the system of record.

Layer 2: Semantic Layer

This is where finance defines metrics. Instead of formulas hidden in Excel cells, you define business logic once:

“Revenue” = sum of invoice amounts where status = “paid”
“Gross margin” = (revenue − cost of goods sold) / revenue
“Cash position” = bank balance + receivables − payables

Every dashboard, report, and user references these definitions. If the definition of “revenue” changes, it updates everywhere automatically. No more reconciliation.

Layer 3: Presentation

Dashboards, charts, and reports that finance teams build and share. Because the underlying logic is governed, anyone can build dashboards without breaking anything.

For a detailed walkthrough of how this works in practice, PADISO’s Agentic AI + Apache Superset guide shows how even non-technical users can query dashboards naturally.

Why This Matters for Finance

In Excel, every dashboard is a copy. In D23.io, every dashboard is a view of the same truth. This difference is everything.

When your controller finds an error in the revenue calculation, they fix it once in the semantic layer. Every report, dashboard, and user sees the corrected number immediately. In Excel, they’d have to find and fix it in 15 different spreadsheets.

The Change-Management Framework That Works {#change-management}

Technical implementation is the easy part. The hard part is getting finance teams to actually use D23.io instead of falling back to Excel.

Here’s the pattern that works in Australian mid-market finance operations:

Phase 1: Pilot with Power Users (Weeks 1–2)

Don’t roll out to everyone at once. Start with your most tech-comfortable finance analyst or controller. They become the “D23.io champion.”

Give them a specific, high-value use case: maybe it’s the monthly P&L report that currently takes 3 days to pull together. Build that dashboard in D23.io. Show them it updates automatically. Show them the audit trail.

They’ll be sceptical. That’s fine. Let them compare the D23.io version side-by-side with the Excel version. When they see that D23.io is faster, cleaner, and auditable, they become believers.

This pilot phase is also where you catch implementation issues before they affect the whole team. Maybe the data connection is slow. Maybe the semantic layer needs tweaking. Better to discover this with one user than twelve.

Phase 2: Expand to Core Reporting (Weeks 3–4)

Once the pilot works, migrate your core monthly reports: P&L, balance sheet, cash flow, variance analysis. These are the reports everyone uses, so the impact is visible immediately.

Critically, don’t delete the Excel versions yet. Run both in parallel for one month. Let finance teams compare. When they see that D23.io matches Excel (because it’s pulling from the same source), confidence builds.

After one month, archive the Excel versions. Don’t delete them—archive them. This gives people psychological safety. If something goes wrong, the old files are still there.

Phase 3: Enable Self-Service (Weeks 5–6)

Once core reporting is stable, train finance teams to build their own dashboards. This is where D23.io’s real value unlocks.

Your AP analyst no longer waits for IT to create an “aging report.” They build it themselves in 20 minutes. Your revenue team builds their own pipeline dashboard. Your treasury team builds their own cash forecast.

This requires training, but not the “read the 200-page manual” kind. It’s hands-on: “Here’s how you drag a metric onto a dashboard. Here’s how you add a filter. Here’s how you export to PDF.”

PADISO’s AI Agency Services Sydney team includes training as part of rollouts, but the key is that training happens after people have seen value, not before.

Phase 4: Retire Excel (Ongoing)

Once D23.io is handling core reporting and self-service dashboards, Excel’s role shrinks to what it’s actually good at: one-off analysis, ad-hoc calculations, and local modelling.

You’ll never get rid of Excel entirely. But you’ve moved from “everything is Excel” to “Excel is a tool for analysis, not the system of record.”

The Psychological Shift

The hardest part of this migration isn’t technical—it’s psychological. Finance teams have often built their identity around being the person who understands the spreadsheet. Moving to D23.io can feel like losing that status.

The antidote is to reframe the role: instead of “the person who maintains the spreadsheet,” they become “the person who defines what the metrics mean.” That’s actually higher-value work. It requires business judgment, not spreadsheet skill.

Call this out explicitly in your rollout. “We’re moving you from data custodian to insights leader.” People respond to that framing.

Governance, Security, and Audit-Readiness {#governance-security}

One of the biggest fears finance leaders have about moving away from Excel is losing control. How do you know who changed what? How do you prove to auditors that the numbers are correct?

D23.io actually solves this better than Excel.

Audit Trail

Every action in D23.io is logged:

Who viewed which dashboard
Who exported which report
Who changed which metric definition
When it happened
What changed

This is exactly what auditors want to see. In Excel, the audit trail is “I emailed this file to these people on this date.” That’s not an audit trail—that’s a guess.

Access Control

D23.io integrates with your existing identity system (usually via SSO through Azure AD, Okta, or similar). This means:

Finance sees all dashboards
Marketing sees only marketing dashboards
The CFO sees everything
Contractors see only what you explicitly grant them

Access is granular and auditable. In Excel, access control is “I emailed this file to these people.” If someone forwards it to someone else, you have no idea.

Data Governance

When you move to D23.io, you’re forced to think about data governance in a way Excel never required. Questions that should have been answered years ago suddenly become unavoidable:

What is the single source of truth for customer data?
How do we define “revenue”?
What’s the difference between “booked” and “recognised”?
Who owns each metric?

This is uncomfortable at first. But it’s also where real financial discipline lives. Once you’ve answered these questions in D23.io, your finance function becomes materially stronger.

SOC 2 and ISO 27001 Readiness

If you’re pursuing SOC 2 compliance or ISO 27001 certification, D23.io actually makes your auditor’s job easier. You have:

A clear system of record (your database)
Governed metric definitions (the semantic layer)
Full audit trails (every action logged)
Access controls (role-based permissions)
Encryption in transit and at rest (D23.io handles this)

Compare this to Excel-based reporting, where auditors will ask uncomfortable questions about version control, formula validation, and access management.

Implementation Patterns: From Spreadsheet to Dashboard {#implementation-patterns}

Let’s walk through a concrete example: migrating a monthly P&L report from Excel to D23.io.

Step 1: Audit the Current State

First, understand what you’re migrating. Pull apart the Excel file:

Where does each data point come from? (ERP, accounting software, manual entry)
What calculations are applied? (Formulas, lookups, aggregations)
Who uses it? (Finance team, executive team, board)
How often is it updated? (Monthly, weekly, real-time)
What decisions depend on it? (Budget vs. actual, variance investigation, forecasting)

This audit takes a day. It’s worth it because it reveals dependencies you didn’t know existed.

Step 2: Design the Semantic Layer

Now design how this report will work in D23.io. Instead of formulas in cells, you define metrics:

Revenue = SUM(invoices.amount) WHERE invoices.status = 'paid'

Cost of Goods Sold = SUM(expenses.amount) WHERE expenses.category = 'COGS'

Gross Profit = Revenue - Cost of Goods Sold

Gross Margin % = (Gross Profit / Revenue) * 100

This takes 2–3 hours with your finance team. The benefit is that these definitions are now explicit, documented, and reusable.

Step 3: Connect the Data Source

D23.io connects to your database (or data warehouse). If you don’t have one, you’ll need to set one up. This is often the biggest project in a D23.io rollout, but it’s also the most valuable: you’re moving from scattered data sources to a single source of truth.

For most mid-market Australian finance teams, this means:

Extracting data from your ERP (SAP, NetSuite, Xero, etc.)
Loading it into a data warehouse (Snowflake, BigQuery, PostgreSQL)
Setting up a refresh schedule (usually daily or hourly)

PADISO’s Platform Design & Engineering service handles this architecture work, but the key point is: this is a one-time project, not an ongoing cost.

Step 4: Build the Dashboard

With the semantic layer defined and data flowing, building the dashboard is fast. You’re dragging metrics onto a canvas, adding filters, and formatting for readability.

A P&L dashboard typically takes 4–6 hours to build and format. A variance analysis dashboard takes 6–8 hours. These are one-time efforts.

Step 5: Validate and Train

Before going live, validate that the D23.io numbers match the Excel numbers. This usually takes 2–4 hours. When they match, you have confidence.

Then train your users: how to view the dashboard, how to filter it, how to export it. This takes 1–2 hours per user.

Step 6: Go Live and Monitor

Switch the P&L reporting from Excel to D23.io. Monitor for 2–4 weeks. Answer questions. Refine the dashboard based on feedback.

After 4 weeks, the Excel version is archived. D23.io is now the system of record.

Total Timeline

From “we want to move P&L to D23.io” to “P&L is live in D23.io and the team is trained” typically takes 4–6 weeks for a single report. If you’re migrating multiple reports, you can run them in parallel: 6–8 weeks for a full finance reporting suite.

This is much faster than building a custom BI tool, and much more sustainable than staying in Excel.

Real Outcomes: What Finance Teams Actually See {#real-outcomes}

Let’s talk about what actually changes when a mid-market Australian finance team moves from Excel to D23.io.

Time Savings

A typical finance team spends 40–60 hours per month on Excel-based reporting. That’s 480–720 hours per year. At $100/hour fully loaded cost, that’s $48K–$72K annually.

After moving to D23.io, that drops to 5–10 hours per month (mostly exception handling and metric definition refinement). You’ve freed up $40K–$65K of annual capacity.

What do finance teams do with that time? They analyse variance, investigate anomalies, and build forecasts. Actual value-add work instead of data plumbing.

Decision Speed

When your CFO asks, “What was last week’s cash position?” the answer changes from “I’ll have it for you Thursday” to “It’s on the dashboard—here.” That’s not just faster, it’s a different decision-making cadence.

Mid-market finance teams using D23.io report moving from monthly to weekly or even daily decision cycles. That compounds over a year.

Audit Confidence

When your auditor asks, “How do you know that revenue number is correct?” the answer changes from “I calculated it in Excel” to “Here’s the database query, here’s the semantic layer definition, here’s the audit trail showing every view and export.”

Auditors like this. It’s one reason why AI Agency ROI Sydney teams working with D23.io often see faster audit cycles and fewer follow-up questions.

Team Satisfaction

Finance teams report higher job satisfaction after moving to D23.io. They spend less time on tedious data wrangling and more time on analysis. The work feels less error-prone. They’re not constantly worried about spreadsheet corruption.

This is subtle but real. Your best finance people won’t leave because they’re stuck maintaining a spreadsheet.

Scalability

When you acquire a company or enter a new market, adding new data sources and reports to Excel is painful. Adding them to D23.io is straightforward: connect the data, define the metrics, build the dashboard.

This is why D23.io becomes more valuable as your business grows, while Excel becomes more painful.

Common Mistakes and How to Avoid Them {#common-mistakes}

We’ve seen dozens of finance teams migrate from Excel to D23.io. Here are the mistakes that derail most of them:

Mistake 1: Building Without a Semantic Layer

Some teams try to move Excel dashboards directly to D23.io without defining a semantic layer. They build dashboards that query the database directly, with logic scattered across multiple dashboards.

This fails because:

When a definition changes, you have to update it in 15 dashboards
Different dashboards show different “revenue” numbers
New users don’t know which dashboard is the source of truth

Fix: Invest 2–3 weeks upfront in semantic layer design. It’s boring work, but it’s the foundation of everything else.

Mistake 2: Trying to Migrate Everything at Once

Some finance teams try to move all reporting to D23.io in one big bang. They set a date, plan a cutover, and hope nothing breaks.

This fails because:

You discover data issues too late to fix them
Users panic and fall back to Excel
You don’t have time to train people properly
One broken dashboard breaks confidence in the whole system

Fix: Use the phased approach described earlier. Start with one high-value report, get it right, then expand.

Mistake 3: Underestimating Data Quality Work

Most Excel-based reporting relies on manual data entry or system exports that were never designed for automation. When you try to automate these in D23.io, you discover the data is messy: duplicates, nulls, inconsistent formatting.

This takes time to fix. Teams that don’t budget for it get frustrated.

Fix: Plan 2–4 weeks of data quality work before you build dashboards. This is unglamorous but essential.

Mistake 4: Not Training Users Early Enough

Some teams build the D23.io dashboards first, then train users. By the time users see them, they’ve already decided they prefer Excel.

Fix: Train users early and often. Show them the dashboard in progress. Let them give feedback. Make them feel like they’re building it together, not having it imposed on them.

Mistake 5: Keeping Excel Alongside D23.io Indefinitely

Some teams move to D23.io but keep Excel as a backup. This creates a split-brain problem: people don’t know which number is real. After a year, you’re still maintaining both.

Fix: Set a hard date for archiving Excel. Give people 4 weeks notice. After that date, Excel is read-only. This forces commitment.

Mistake 6: Not Securing Access Properly

Some teams make all dashboards visible to everyone. This creates information leakage and audit risk.

Fix: Use role-based access control from day one. Finance sees all dashboards. Marketing sees only marketing dashboards. Contractors see only what they need.

Next Steps: Getting Started {#next-steps}

If your finance team is still living in Excel, here’s how to move forward:

Immediate (This Week)

Audit your current state: Pull apart your main Excel-based reports. Where does the data come from? What calculations are applied? Who uses it? How long does it take to produce?
Identify your pain point: Which report causes the most pain? Which one takes the longest? Which one is most error-prone? That’s your pilot.
Talk to your team: Ask your finance team what they’d do with an extra 10 hours per week. Listen to what they say. You’ll hear the real cost of Excel.

Short-term (Next Month)

Explore D23.io: Visit D23.io and take a demo. See what modern finance reporting looks like. Compare it to Excel or Power BI.
Talk to PADISO: PADISO has shipped fixed-fee D23.io consulting engagements that include architecture, implementation, and training. A 30-minute conversation with the team will clarify what’s possible and what it costs.
Plan your pilot: Define your pilot report. Scope the work. Identify your champion user. Set a 6-week timeline.

Medium-term (Next Quarter)

Execute the pilot: Build one dashboard in D23.io. Get it right. Show it to your team. Let them see the difference.
Expand to core reporting: Once the pilot works, migrate your other main reports. Run in parallel for a month. Then archive Excel.
Enable self-service: Train your team to build their own dashboards. Watch them discover what they can build when they’re not stuck in Excel.

Why This Matters

Moving from Excel to D23.io isn’t just a technology change. It’s a shift from “we manage data” to “we use data to make decisions.”

For Australian mid-market finance teams, this shift compounds. Every month you stay in Excel is a month of lost productivity, audit risk, and decision delay. Every month you’re in D23.io is a month of cleaner data, faster decisions, and stronger governance.

The teams that move first—the ones that are willing to invest 6–8 weeks upfront—are the ones that build a competitive advantage. They see cash flow faster. They catch variance earlier. They pass audits with less friction.

The question isn’t whether to move from Excel to D23.io. It’s whether to move now or wait until the pain of staying becomes unbearable.

Get Help

If you’re serious about moving your finance team forward, PADISO’s team can help. We’ve done this dozens of times. We know the pitfalls. We know the patterns that work.

Our AI Agency Support Sydney and AI Agency Services Sydney teams include D23.io implementation as part of broader finance automation and reporting modernisation. We can scope your specific situation, design your semantic layer, and train your team to the point where they’re building dashboards themselves.

The fixed-fee D23.io consulting engagement is designed for exactly this situation: you have Excel-based reporting, you want to move to governed dashboards, and you want it done in 6 weeks with no surprises.

If you want to talk through your specific situation—your data sources, your reporting pain points, your team’s skill level—we’re here. A conversation costs nothing. The insights often pay for themselves in the first week of implementation.

Summary

Excel-based reporting is a trap that most mid-market finance teams fall into accidentally. It works at first. Then it becomes a bottleneck. By the time you realise the cost, you’ve built dependencies that make moving away feel risky.

D23.io solves this by providing a governed, auditable, self-service alternative that finance teams can actually use. It’s not a replacement that requires learning new skills. It’s an evolution that lets finance teams do what they actually want to do: understand and act on data, not manage spreadsheets.

The migration takes 6–8 weeks. The payoff—in time saved, decisions accelerated, and audit confidence gained—compounds over years.

The teams that move first win. Not because D23.io is magic, but because they’ve freed themselves from the spreadsheet treadmill and can focus on what actually matters: driving the business forward.

Start with one report. Get it right. Expand from there. In six months, you’ll wonder how you ever lived in Excel.