Data Panda brings your Salt Edge data 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.
Salt Edge was founded in 2013 by Dmitrii Barbasura and a small team out of Chișinău and Toronto, with later offices in London. The platform connects to over 5,000 banks across 50+ countries through PSD2 and open-banking APIs, so a fintech, an accounting product or a lender can read account information and initiate payments without holding its own AISP or PISP licence.
The reason to pull Salt Edge into a warehouse is that the connector is the only place where your live bank position lives next to the rest of the books. Connections, accounts, balances and categorised transactions land as their own tables, and once they sit alongside revenue, AR, AP and your forecast, the cash question stops needing a screenshot from the banking app. Late-arriving transactions reconcile against the journal, supplier payment patterns become a query, and a sudden volume change on a connection becomes a signal instead of a surprise on the next statement.
Bank balances and categorised transactions on the same timeline as revenue, AR and AP.
Let the rest of the stack react to what cleared the bank.
Use Salt Edge categorisation history to spot fraud, churn and supplier risk early.
Internal tools around the bank data that otherwise lives in the Salt Edge dashboard.
A list of concrete reports, automations and AI features we have built on SaltEdge data. Pick the one that matches your situation.
What is our real cash position right now, across every account and entity?
Salt Edge balances per account, per currency and per legal entity in one rolled-up view, refreshed daily. The cash number on the Monday status sits on top of the same connections finance reconciles against the books, instead of an export the controller pulls from each banking portal one by one.
Which suppliers are quietly drifting on payment timing or amount?
Recurring outflows per vendor, with the typical window and amount learnt from history. A supplier whose monthly payment slipped by two weeks, or whose amount jumped 30 percent, surfaces as a flag against its own baseline rather than getting lost in a long bank-statement export.
Is a customer about to churn based on how they pay us?
Inbound payment regularity per customer joined to the CRM and subscription state. A customer whose previously-monthly payment goes irregular, partial, or late shows up next to the renewal date, instead of after the renewal lapsed and the account team noticed in the churn report.
Salt Edge balances and categorised transactions next to AR, AP, journal entries and the forecast. Daily cash is one number that ties to the books, the late transaction that landed two weeks after close gets posted in the right period without re-opening the month, and the controller stops chasing exports across separate banking portals.
Last cleared payment, payment regularity and total inbound per customer on the CRM record. Account owners walk into a renewal call knowing whether the customer pays on time and in full, instead of finding out from the churn report that the last three invoices went late or partial.
Connection health, refresh status and transaction volume per Salt Edge connection in one view. The team that runs onboarding and the team that runs reconciliation both use the same source of truth, so a stale connection or a sudden volume spike becomes an actionable signal instead of a discovery.
Cleared transactions from Salt Edge land in Exact Online as bank journal entries and match to the open invoice they settle. Categorised outflows post against the right cost account, and a late transaction that landed after a previous close gets booked in the period it cleared, so the open-invoice list reflects what the bank says cleared.
Salt Edge feeds the bank lines that Yuki needs to reconcile against the customer and supplier ledger. The accountant sees one source for the bank, the AR and the AP, and the categorised description that Salt Edge attaches helps Yuki suggest the right journal account on lines that don't auto-match an invoice yet.
Salt Edge balances and cleared transactions sit next to the AR and AP ledger from Business Central in one warehouse view. A 13-week cash forecast joins realised bank movement to open invoices and supplier obligations, and the daily cash report finance sends out runs on the same numbers that Business Central reconciles against, not on a separate manual export.
Last cleared inbound payment, payment regularity and total inbound per customer push onto the HubSpot company record. Account owners walking into a renewal or upsell conversation see whether the customer pays on time and in full, instead of asking finance for an aged-receivables export the day before the call.
A sudden jump in transaction volume or amount on a Salt Edge connection, scored against its own historical baseline, posts to the finance or fraud channel in Slack. The team sees the outlier the same day instead of catching it on the next bank statement, and the message links straight to the connection, the account and the transactions that drove the alert.
When a recurring supplier payment misses its usual window or jumps in amount, an AP review task opens automatically in monday.com with the supplier, the expected window and the actual Salt Edge transactions on the card. The AP team works the exception list instead of scrolling a bank export, and the resolution stays attached to the task for audit later.
These are the 5 tables we currently pull from SaltEdge 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 SaltEdge 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.
The connector pulls the core Salt Edge entities: customers, connections (the bank-tenant pair), accounts, transactions with their assigned category, holder info and consents. Each lands as its own table with the Salt Edge identifiers preserved, so joins to the rest of your stack (CRM, ERP, subscription tool) work on stable keys instead of free-text descriptions.
Salt Edge assigns a personal-finance or business category to every transaction it returns. The connector keeps that category as a column on the transaction row, so spend dashboards, supplier-pattern queries and forecast models can group on it without you running a second classifier on the same data.
Banks sometimes post a transaction with a value date in a period you already closed. The connector keeps the value date and the post date both, and downstream models can route the late transaction to the period it settled in, so reconciliation does not need to re-open a closed month.
We review your SaltEdge setup and the systems around it. Together we pick the first thing worth building.