Data Panda brings your Horus bookings together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
Horus is the cloud accounting software of Horus Software, a Belgian family-run SaaS company based in the Liège region and founded by Philippe Tailleur and his sons. The platform is used by around 4,000 accountants across Belgium and Luxembourg, with a companion app called Falco that lets SME clients submit purchase invoices and bank documents straight to their accountant. The Horus AI engine pre-codes those documents on arrival, with the company reporting recognition accuracy in the high nineties and time savings of around 40% on the bookkeeping itself.
Underneath the bookkeeping screen, Horus exposes a documented REST API on Apiary, with OAuth 2.0 authorization-code flow and a per-client architecture: every fiduciary or SME on Horus Office runs on its own dedicated database with its own API endpoint. The API gives access to the things a Belgian accountant works in every day, folders, companies (with VAT number, IBAN and payment modes), book entries across the purchase, sales, financial and miscellaneous journals, sales and purchase invoices and account histories with reconciliation matching. That is what makes Horus reachable as a structured source of revenue, spend, AR, AP and VAT data outside the bookkeeping screen, per client file or rolled up across an entire firm.
Revenue, spend, AR and VAT-position data tied to Horus bookings, ready for the operational side of the business.
Let operational systems and the accountant act on the same Horus events.
Use the booked Horus history to coach the next document instead of correcting it after the fact.
Internal tools on Horus data for people who shouldn't sit in the bookkeeping screen.
A list of concrete reports, automations and AI features we have built on Horus data. Pick the one that matches your situation.
Which clients on Horus are growing in revenue but slipping in payment behaviour?
Twelve-month trend of booked turnover per customer crossed with their average payment lag from the open AR file and the matched account history. Picks up the customer who's quietly become more important to the SME and at the same time more expensive to finance, before the conversation about a payment plan reaches the accountant.
What is the real VAT position weeks before the next aangifte?
Live position per VAT code, per period and per journal, on the bookings already in Horus. Tells the accountant and the SME owner whether the next BTW-aangifte will be a payment or a refund early enough to plan cash, instead of finding out the week the file has to be sent in.
How long does a document really take from Falco to a booked entry?
Time between a Falco submission, the AI pre-coding step and the final booking in Horus, per client and per document type. Shows the accountant where the bottleneck sits, in the inflow, in the AI suggestion or in the human review, instead of the gut-feel that some clients are slow.
Revenue, AR aging, VAT position and posted cost from Horus tied to one another in real time. The accountant keeps owning the close in Horus, and finance leadership at the SME stops waiting for the close to find out where the business stands.
Open invoices, payment behaviour and customer revenue history in front of the salesperson at the moment they renew or upsell. Stops the conversation where the rep is the last person in the room to know the customer is two months overdue.
Booked spend per supplier and analytical code visible inside the operational system, without the team needing access to the full Horus folder. Operations sees the cost the day the supplier invoice is processed in Horus, not three weeks later in a PDF.
Client masters and engagement data in AdminPulse stay in step with the Horus folders and bookings the same client generates. Belgian fiduciaries running both stop maintaining two parallel client lists, and time, billing and the actual books reconcile against the same source.
Booked journals, open AR and AP and VAT-position data from Horus folders land in Silverfin so the periodic and year-end working papers reconcile against what the SME already approved with the accountant. Working-paper review starts on the same numbers the client sees in their own portal.
Sales invoices issued and sent through Billit and posted into Horus end up in one warehouse, with the invoice document, payment status and final booking joined per document. The SME keeps issuing in Billit, the accountant keeps booking in Horus, and revenue and AR live in one place.
Bank movements pulled through Ponto and reconciled inside Horus end up joined per booked invoice and per supplier. Treasury sees the cash position based on what Horus has matched, not on a balance the bank app showed three days ago.
Customer matches between HubSpot and Horus put booked revenue, open invoices and average payment lag on the CRM record. Account managers see whether the customer they're about to renew is one whose invoices keep landing two weeks overdue, before the proposal goes out.
Booked journals, open AR, AP and VAT lines from one or many Horus folders feed Power BI without exporting from each folder by hand. Accounting firms get a single firm-wide view across the portfolio, and SMEs get one dashboard their accountant and their internal team look at together.
These are the 10 tables we currently pull from Horus 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 Horus 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.
Yes. Horus runs a separate database per client, with its own API endpoint, so each folder lands in its own schema in the warehouse, with shared customer, supplier and chart-of-accounts dimensions on top. Accounting firms with tens or hundreds of client folders can report per client, per portfolio and at firm level without exporting from each folder by hand.
Yes, once the document is booked in Horus, the resulting entry, the linked invoice and the account-history line all sync over. The warehouse can then show how long it took from a Falco submission to a final booking, and how often the AI suggestion was accepted versus corrected by the accountant.
We review your Horus setup and the systems around it. Together we pick the first thing worth building.