Data Panda pulls every file your partners drop on SFTP into your warehouse alongside the rest of your business data. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
SFTP is the SSH file transfer subsystem standardised in the IETF SECSH working group. It carries files over a single SSH-2 channel, with no separate data port like classic FTP, and is what most B2B partners settle on when an API is too much to ask for.
The folders are full of business: bank statements as CODA in Belgium and MT940 globally, EDI exchanges of orders, invoices and shipping notices in flat files, payroll exports per pay run, retailer feeds of stock and sell-through, partner price lists, PGP-encrypted batches from your bank. Most of that data lives one folder deep on a server somewhere and never touches a dashboard.
The point of pulling SFTP into a warehouse is not to replace SFTP. It is to make the drops auditable and queryable: which file landed when, was it processed, how old is it, which partner is late, which file format suddenly changed shape this morning.
See which partner files landed, which got processed, and which folders are quietly piling up.
Turn file events into the next step in finance, ops and procurement.
Use file contents and patterns to spot anomalies humans usually miss.
Tools your finance and ops team open to chase a late drop without logging into the SFTP server.
A list of concrete reports, automations and AI features we have built on SFTP data. Pick the one that matches your situation.
Did every bank statement we expect today land?
A daily reconciliation between the list of accounts you expect a CODA or MT940 file for and what arrived on the SFTP server. The treasurer sees the missing ones at nine in the morning, not at month-end during the bank reconciliation.
Which EDI partners are slipping their delivery windows?
Days since the last order, invoice or ASN per partner, ranked worst first. Procurement and customer service see which partners need a phone call before the missing file becomes a missing shipment.
Did anything change in the file format overnight?
Schema drift between this morning's batch and the last good one: new columns in a CSV, missing EDI segments, encoding changes. Catches a partner's silent system upgrade before it breaks the downstream import.
Treasurer sees CODA and MT940 landings versus the daily expectation, with missing accounts visible before lunchtime instead of at month-end. Reconciles bank file content against booked invoices without a manual download.
Customer service spots EDI orders that did not arrive from a key retailer before the customer calls to chase. Account managers see partner SLA in one place per customer, not per inbox.
Logistics and procurement get a single view of inbound EDI throughput, processing time and quarantined files. The Friday afternoon panic about a missing ASN turns into a Monday morning trend on a dashboard.
CODA statements landing on SFTP from your bank are parsed into the warehouse and matched against open invoices in Exact Online. Finance sees which lines reconcile automatically and which need a manual touch, with the original CODA file one click away.
EDI order files dropped by retailers on SFTP are validated in the warehouse and pushed into Business Central as sales orders, with the partner reference on the line. Schema drift gets flagged in the warehouse before a malformed file ever reaches the ERP.
For account managers on Salesforce, each partner account shows the days since the last expected SFTP drop and the count of files in quarantine. The customer call about the late shipment turns into a heads-up the AM gives the customer first.
Specific file events from SFTP, such as a new partner onboarding batch or a contract renewal export, fire workflows in HubSpot. Lifecycle outreach reflects what just happened in the back-office, not what marketing assumed last quarter.
When a bank file is more than a day late, or a partner's batch lands in the quarantine folder, a focused Slack message goes to the right channel with the partner name, file name and a link to inspect it. The team chases the issue without watching the SFTP server.
Each parse failure on an inbound SFTP file becomes a card on the data-ops board in monday.com, with partner, file name and the parser error. Recurring failures by the same partner cluster on the board so the team sees the pattern, not just today's incident.
You keep the reporting tool you already have. We connect it to the warehouse where your SFTP 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.
SFTP is the SSH file transfer subsystem and runs over a single SSH-2 channel on one port. FTPS is the older FTP protocol wrapped in TLS, and still uses a separate command and data connection, which makes it harder to firewall. We connect to either, but the warehouse view is the same once files land.
Yes. Banks frequently encrypt CODA, MT940 or remittance batches with PGP before drop. We hold the private key in a secrets store, decrypt on ingest and only then write the parsed contents to the warehouse. The encrypted blob remains the audit artefact.
Both, but SSH key auth is the default. Most B2B partners now require it, and it removes the password rotation burden. We store keys in a secrets manager and rotate them per the partner's policy without touching the warehouse pipelines.
We review your SFTP setup and the systems around it. Together we pick the first thing worth building.