Your numbers, tied out to the bank, the SII and your ERP.
We connect your ERP, banks, the SII and Buk. Every figure arrives with its source.
First reports in hours · Read-only on your ERP · Every query logged
What your data looks like in Xophia
- Receivables
- CLP 412.6M
- +3.1% vs. September
- Overdue past 60 days
- CLP 48.2M
- 17 invoices
- Matched this month
- 96.6%
- 398 of 412 movements
Collected per month · last 12 months
Target CLP 380M
October: CLP 391.0M collected, above target.
Receivables by aging bucket
- 0–30 daysCLP 286.4M
- 31–60 daysCLP 78.0M
- 61–90 daysCLP 31.5M
- Over 90 daysCLP 16.7M
398 matched14 pending, each with a reason412 movements this month
Who holds the debt past 60 days?
CLP 48.2M across 17 invoices. The distributor channel accounts for 61%.
select channel, sum(amount) as overdue
from reconciled_receivables
where days_overdue > 60
group by channel| channel | overdue | % |
|---|---|---|
| Distributors | CLP 29.4M | 61% |
| Retail | CLP 12.1M | 25% |
| Direct sales | CLP 6.7M | 14% |
3 rows · ERP and bank statements · query logged
Agent proposal
14 unmatched payments add up to CLP 6.3M. I can propose matches using the bundled-deposit rule for you to review.
Reports on the same base
Income statement
34.2%
gross margin · +1.2 pts
Cash flow
CLP 128.4M
balance with scheduled payments
Payables
CLP 203.9M
42 invoices coming due
Reconciliation
96.6%
bank, SII, Buk and cards
What it takes today to answer one question
Before anyone answers a single question, someone has to gather, cross-check and reconcile. Pick yours above and Xophia shows how it would be solved on your sources.
Our data is spread across many sources
The ERP, banks, the SII, Buk and spreadsheets each hold part of the same story. Every report starts with exporting, pasting and cross-checking.
Every dashboard calculates differently
Customer debt or margin is calculated one way in a dashboard and another way in a spreadsheet. The meeting goes into arguing which figure is right.
The accounting close holds up our data
Until finance reconciles bank, SII and ERP, the month's figures stay in draft and the reports wait.
Every new integration is a project of its own
Adding a source means another project, another mapping and another definition to maintain, without reusing what was already built.
How many steps stay in your hands
The question is the same: “How much do customers owe us past 60 days?”. What changes is how many steps stay with you or your team.
| Path | 01 Connect | 02 Reconcile | 03 View | 04 Ask | 05 Act | 06 Build | In your hands |
|---|---|---|---|---|---|---|---|
| Spreadsheet | You | You | You | You | You | — | 5 |
| Traditional BI | You | You | Included | You | You | — | 4 |
| Generic AI chat | You | You | — | Included | You | — | 3 |
| Xophia | Included | Included | Included | Included | You approve | Included | 1 |
What doesn't tie out isn't hidden
Before a figure reaches a report, every bank movement, SII document, card settlement and Buk payroll posting ends in one of three states.
In the bank statements · OctoberCLP 384,691,820
Matched
In the ERP · OctoberCLP 384,691,820
Pending reviewCLP 6,312,400
14 movements: card deposits that bundle several days of sales. The agent proposes how to match them and waits for your approval.
Matched
Linked to its ERP entry, with the rule or evidence behind it.
Dismissed, with a reason
Whatever shouldn't be posted is marked with the reason, not deleted.
Pending review
Whatever the agent can't resolve with confidence goes to a person, with the rows from both sides in view.
Nothing is posted to the ERP without an approval, and every decision records who made it. Reports are built on that same base: income statement, balance sheet, cash flow, receivables and payables.
Explore financial reconciliationConnect what you already use
Your ERP stays the system of record. Banks, the SII, payroll and CRM join the same base.
- OdooERP
- NetSuiteERP
- SAP Business OneERP
- SAP S/4HANAERP
- Microsoft Dynamics 365ERP
- SoftlandERP
- LaudusERP
- SAP HANADatabase
- SIITax documents
- BukPayroll
- TalanaPayroll
- Bank statementsBanking
- HubSpotCRM
- SalesforceCRM
First reports in hours, not months
There's no data project before the first figure. With read-only access ready, work starts the same day.
Hour 0
You connect your sources
Your team creates a read-only ERP user and enables banks, the SII and payroll. Your ERP stays untouched.
Within hours
First reports
Income statement, cash flow, receivables and payables, built from your sources.
Then
It adapts to your operation
Metrics, reconciliation rules and approvals are defined with your team, one module at a time.
Your data and your actions, from your AI assistant
Through MCP, Claude or another compatible assistant works on the same base, with each person's permissions.
Extract
Query reconciled figures, reports and movements without leaving your assistant. Each person sees only what their role allows.
Act
Ask it to match a payment, post a movement or prepare a report. Reading and writing are separate permissions, and whatever is written to your systems goes through approval.
Log
Every query and every action is logged with who asked for it and what was run.
Where to start
One module at a time, on your current sources. What gets connected and defined in the first one stays for the next.
- Finance reconciliationBank, cards, SII and Buk matched against the ERP. It's the base that makes every later report tie out.
- KPI copilotQuestions in your own words on reconciled figures, with each metric's definition and the SQL in view.
- Sales supervisionThe CRM pipeline read with the same definitions, and every alert citing the record behind it.
For your IT team
What IT usually asks before a source is connected.
Read-only, role-scoped access
Xophia reads your systems with the user's identity when the system supports it, or with a least-privilege service account. Reading and writing are separate permissions.
Nothing is written without approval
Writes to the ERP go through a person and use their account. Every query and every decision is logged with who made it.
Your data stays yours
We work on your sources and your definitions. Region, retention and data flows are confirmed and documented before anything is connected.
Reading before you build the next report
See the whole blog- Five versions of the truthMeetings end up arguing about numbers instead of decisions. Sometimes the data is wrong; sometimes nobody wrote down the definitions.
- Data doesn't create value. Decisions do.Forty dashboards published, and leadership still asks for the report in Excel. Before buying another BI tool, review the data, definitions and decisions.
- If it can't be audited, it doesn't go to productionEvery figure an agent delivers and every action it takes should be traceable to its origin. Traceability isn't bureaucracy: it's what makes trust possible.
Questions about data
Which ERPs does it work with?
With the ERP you already use as your system of record: Odoo, NetSuite, SAP Business One, SAP S/4HANA, Microsoft Dynamics 365, Softland or Laudus. The connector, permissions and scope are confirmed for each implementation.
How long until the first reports?
Hours, not months. With read-only access ready, the first reports (income statement, cash flow, receivables and payables) are built the same day. Then metrics and rules are adjusted to your operation, one module at a time.
Do we have to change our ERP?
Not to start. The ERP stays your system of record: Xophia reads it and only writes to it with approval. If a tool creates friction over time, 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 happens to what doesn't tie out?
It stays pending, with the rows from both sides in view, until a person reviews it. It isn't hidden or quietly adjusted, and every decision is logged.
Can I use Xophia from Claude or another assistant?
Yes, through MCP. You can query your data and ask for actions from a compatible assistant, with your role's permissions. Whatever is written to your systems goes through approval and everything is logged.
Can the agent make up a number?
It's designed not to: it answers through agreed metric definitions, and every numeric answer points to the definition and the SQL that produced it. The policy blocks unsupported answers.
What if we already have a data warehouse?
It gets used. The KPI copilot works on warehouses such as Snowflake, BigQuery, Databricks or Postgres, and semantic layers such as Cube, dbt Metrics or MetricFlow. The exact adapter is confirmed for each implementation.
What happens to our current dashboards?
If they work, they stay: they read the same definitions and the copilot uses them to cross-check figures. 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.
Bring the metric that gets argued about most.
In a 20-minute diagnostic we look at where it comes from today and which sources need cross-checking. If your case fits, we prepare a demo with your data.