Integrations
What works gets connected. And reused in every module.
Xophia connects to your ERP, banks, the SII, your payroll, sales and CRM systems, and your data. Your ERP stays the system of record, and every connection stays available to the modules that follow.
Systems we connect
The systems the reference modules work with, grouped by what they bring to your operation.
ERP
It stays your system of record. Xophia reads its accounting state and only writes to it with approval.
- Odoo
- NetSuite
- SAP Business One
- SAP S/4HANA
- Microsoft Dynamics 365
- Softland
- Laudus
- BCI
- Santander
- Itaú
- BancoEstado
- Banco de Chile
Payments and cards
Card and payment settlements, including deposits that bundle several days of sales.
Explore financial reconciliation- Cardda
- Transbank
- Webpay
- Mercado Pago
Tax documents and invoicing
Purchase, sales and contractor-fee ledgers, and the documents in your invoicing systems, cross-checked against what the ERP recorded.
Explore financial reconciliation- SII
- Nubox
- Facturación.cl
- QuickBooks
Payroll
Payroll centralizations, which reach the ERP as compound entries.
Explore financial reconciliation- Buk
- Talana
CRM
The pipeline is read as the system of record, and every alert cites the record behind it.
Explore sales supervision- HubSpot
- Salesforce
- Pipedrive
Sales and e-commerce
Orders, sales and bookings from your digital channels, to cross-check them against what gets invoiced and collected.
- Shopify
- Mercado Libre
- Playtomic
Data warehouse and semantic layer
Questions are answered with SQL compiled from agreed metric definitions.
Explore the KPI copilot- Snowflake
- BigQuery
- Databricks
- SAP HANA
- PostgreSQL
- Cube
- dbt Metrics
- MetricFlow
Dashboards
Read to cross-check figures: if one doesn't match, it shows which definition each one used.
Explore the KPI copilot- Power BI
- Looker
- Tableau
- Metabase
Messaging
Where questions, alerts and approvals arrive.
- Slack
- Microsoft Teams
Reference integrations. The exact adapter and its permissions are confirmed during implementation.
How it connects
What IT usually asks before a system is connected.
Read-only by default
Xophia reads with the user's identity when the system supports it, or with a least-privilege service account.
Writes need approval
Whatever is written to your systems goes through a person and is logged with who approved it.
One connection, many modules
What gets connected for one module is reused by the next ones: it isn't built again.
Connection patterns
- MCP
- REST
- GraphQL
- SQL
- Events
- Webhooks
Questions about integrations
Do we have to change any system to start?
No. What works gets connected and stays your system of record. If a tool creates friction, it can be replaced by a module, one at a time, with its data migrated and validated. Your company makes that call, with data.
What permissions does Xophia need?
The minimum for the agreed scope: read-only by default, with the user's identity when the system supports it. Writes and high-impact actions require human approval. Identities and service accounts are documented for the deployment.
My system isn't on the list. Can it be connected?
If it exposes an API, a database, events or webhooks, it can be assessed. We review it in the diagnostic; the exact adapter and its permissions are confirmed during implementation.
Don't see your system?
Tell us what you use. In a 20-minute diagnostic we review how it connects and which module makes sense to start with.