Introduction to Integrations
The Dattos platform was designed to operate as a secure hub between your environment and the financial data ecosystem. Instead of relying on manual extractions, you connect the platform to your sources — ERP, banks, internal systems, files — and it starts fetching and delivering data automatically, with protected credentials and auditable access. This article is the starting point: it presents the integration options and points you to the right article for each path.
What you can connect
ERPs with a native connector: SAP S/4HANA, SAP Business One, Dynamics 365 Finance & Operations, Dynamics 365 Business Central, Oracle NetSuite, Oracle E-Business Suite, and Sankhya — through the ERP step in the data preparation flow, which extracts ready-made reports via each system’s official APIs.
Any system with an API or database: the Rest API and Database steps cover custom integrations with systems that do not have a native connector — or reports that the connector does not provide.
Files and storages: spreadsheets, text files, PDFs (with extraction by Dattos AI), XML, and specialized financial formats (CNAB, OFX, SPED, NF-e, acquirer EDI, SWIFT), with automatic collection in SFTP, SharePoint, and OneDrive through the Source Directory.
Banking institutions: statements and account data via Open Finance (with consent) or via banking VAN (financial file exchange), in addition to direct bank APIs.
Outputs for other systems: export steps generate Excel spreadsheets, text files, PDF/HTML documents, and direct loads into databases; the Output Directory delivers the files to external storages.
BI tools and spreadsheets: the Data Lake exposes results as an SQL/ODBC source for Power BI, Tableau, dbt, or Excel — without exporting files.
Scripts, pipelines, and artificial intelligence assistants: the Dattos CLI operates the platform from the command line (automation, CI/CD), and the MCP server connects assistants such as Claude and ChatGPT to your processes and data.
Where each integration is configured
Most integrations are configured directly in the data preparation flow of Turbo AI processes — each source and each export is a step in the flow. Three integrations are the exception:
SFTP and storages: enabled in the credentials/integrations registration and selected in the Source and Output Directories of the processes.
Open Finance: done through the Integrations menu, with authorization from the account holder.
Banking VAN: enabled as a service by the Dattos implementation team, upon request.
How to choose the path
Start with the native connector. If your ERP is on the list and the report exists, the ERP step is the path with the least technical configuration.
No connector or no report? Use custom integrations: Rest API step (system with API) or Database step (direct SQL access or via an intermediate database).
High volume? Above 500 thousand records per run, avoid API — prefer database or file exchange.
Banking data? Prefer Open Finance when the bank is available; use VAN for file-based operations.
Destination is a BI tool? Do not export files — connect the tool to the Data Lake.
Internal network systems: when the ERP or database is not accessible over the internet, the connection can be made through site-to-site VPN/VPC — a private, encrypted tunnel between the Dattos environment and yours, without exposing any service publicly. Contact support for assessment.
What to continue with
Custom integrations via Rest API and SQL connectors.
Connect external storages (SFTP, SharePoint, OneDrive).
Bank integration: overview.
Data Lake: connect your BI tool or spreadsheet.
ERP step — and the configuration articles for each connector (ERP Integration: SAP S/4HANA, SAP Business One, Dynamics 365, Oracle NetSuite, Oracle E-Business Suite, Sankhya).
Export steps: Excel Export, Text File Export, Document Export, Database Export.
Dattos CLI: installation and first steps — and Connect artificial intelligence assistants via MCP.