OData queries have long been used to populate Business Intelligence platforms like PowerBI or similar. Using a reporting software like Calxa you connect directly to accounting system data to create budgets and detailed financial reports for month-end. An OData connector then helps move this financial data on into an external visualisation platform. Here it can be merged with other business data to paint a holistic picture of an organisation.
These external systems can include:
- BI tools,
- Spreadsheets,
- Data warehouses,
- Or other operational platforms.
Used well, OData queries become a powerful way to extend Calxa beyond reporting and into broader decision‑making, analytics, and governance workflows.
Calxa now has an Outbound Data Feed to facilitate OData queries. This guide explains when to use it, what it’s best suited for, and how to use it effectively.
What the Outbound Data Feed is (From a CFO Perspective)
Calxa’s Outbound Data Feed is not a formatted report export. What it does is to provide structured financial datasets.
Why OData Queries?
OData (Open Data Protocol) is a widely adopted, standards-based approach to exposing and consuming data. For CFOs and IT teams, this provides confidence that Calxa data can be accessed securely, refreshed reliably, and integrated with common tools without proprietary connectors or fragile custom integrations. Using OData also supports strong data governance, auditability, and scalability as reporting needs to grow.
What Datasets Are Accessible
These can include:
- Budgets,
- Forecasts,
- Scenarios,
- Time Periods,
- Accounts,
- And Cost Centres.
Calxa’s Outbound Data Feed is built on OData, allowing finance teams to securely extract budgeting, forecasting, and reporting data directly into Excel, Power BI, and other analytics or reporting tools. This makes it easy to integrate Calxa data into existing executive dashboards, board reporting packs, and enterprise reporting environments.
Where CFOs See the Biggest Return on Investment
By feeding dashboards directly from Calxa datasets, CFOs ensure executives are working from finance-approved numbers, reducing reconciliation debates and improving decision velocity. Simply put, it combines finance and non-financial data.
When to Use the Calxa Outbound Data Feed
The outbound feed is most valuable when:
- Reports need to be consumed outside Calxa
- Data must be combined with non-financial or operational data
- You want a single source of truth feeding other systems
- You need automated access to Calxa data
Common scenarios include:
- Board dashboards in Power BI / Tableau
- Feeding budgets and forecasts into:
- Data warehouses
- KPI platforms
- Sharing approved budgets with non-finance stakeholders like:
- Operations teams
- Grant managers
- Parent organisations
What Data is Best Shared via the OData Feed
Use the Outbound Data Feed for structured, reusable data, not one-off reporting.
Well suited data:
- Budgets (by account, cost centre, period)
- Forecasts and scenarios
- Actuals (from your accounting system via Calxa)
- Variance data
- Organisational structures (business units, cost centres, entities)
Not suitable:
- Highly formatted reports
- Narrative commentary
- Presentation ready summaries
These remain better handled within Calxa using the standard or dynamic report templates and report bundles.
Tips for OData Query Performance and Volume Considerations
If consuming the feed regularly:
- Avoid pulling queries that have:
- Excessively long date ranges
- Unused historical scenarios
- Export only what your downstream tool actually needs. You will benefit from:
- Refresh speed
- Reliability
- User trust in the data
Common Pitfalls to Avoid with OData Queries
To get the most from the Calxa Outbound Data Feed, it helps to follow some simple guidelines.
- Avoid using the outbound feed as a “report replacement”. Instead use it as a data supply, not a presentation layer.
- Don’t expose draft or working scenarios. Only query reviewed and approved data.
- Treat it as a one‑off integration. Design and build it as an ongoing data pipeline.
Using the Outbound Data Feed with Power BI
For Power BI users, the OData-based outbound feed allows Calxa data to be connected as a refreshable data source, supporting scheduled updates without manual exports. Finance teams can model relationships, measures, and KPIs directly in Power BI while retaining Calxa as the system of record for budgets and forecasts. This enables consistent budget vs actual reporting, forecast comparison, and executive dashboards that remain aligned with finance governance and scenario approvals.
Final Thoughts on OData Queries from Calxa
For CFOs, the Calxa Outbound Data Feed is more than a technical feature—it is a governance and decision-support mechanism. Used well, it ensures leaders consume the right numbers, at the right time, with clear ownership and trust.
Getting Started with the Outbound Data Feed
Creating OData queries via the Calxa Outbound Data Feed isn’t for everyone and some advanced technical skill is required in the external systems to make good use of it. You may feel more comfortable creating Dashboards in Calxa. Having said that, the Calxa side is quick and easy to set up.
- Go to Settings, then Billing & Admin,
- Select Outbound Data Feed
- Here, you simply add credentials to your provided URL.
- Now copy that information to set up the connection in your external system, whether that is Excel, Power BI or whatever tool you are using.
Use this help material to set up your first Outbound Data Feed.