BASALT connects every system you run, translates the data into business concepts, and turns them into reports, answers and actions your teams and AI can trust.
SAP S/4HANAERPAPI · incremental · 5 min✓ 2 min ago
OdooERPAPI · incremental · 10 min✓ 6 min ago
SageERPExport · nightly✓ 06:00
SalesforceCRMAPI · change events✓ just now
Exact OnlineAccountingAPI · incremental · 15 min✓ 4 min ago
Toggl TrackTime trackingAPI · every 15 min✓ 9 min ago
LinearProjectsWebhooks · live✓ just now
SD WorxHR and payrollPayroll export · monthly✓ 1 Oct
And many moreSharePoint, CRM, accounting, spreadsheets, any API or database
BASIN
Stored as is · every version kept
Tables46
Rows2.4M
Versions kept100%
Last load2 min
TableRowsVersions
basin.sap.kna118,204v7
basin.odoo.account_move41,380v2
basin.exact.transaction128,410v3
basin.toggl.time_entry212,940v1
basin.linear.issue9,312v4
basin.sdworx.payroll_line3,860v2
Context layer
8 concepts · validated by your teams
Customer99%CoreSAP · Salesforce · Odoo
Employee100%CoreSD Worx · Toggl
Entity100%Core6 ERPs
Invoice98%FinanceOdoo · SAP · Sage
Payment97%FinanceExact Online
Opportunity96%SalesSalesforce
Project98%ProjectsLinear · Odoo
Time entry100%ProjectsToggl
Reports
12 reports · one definition each
Group P&LEntityInvoice2 min ago
Outstanding and DSOInvoicePayment4 min ago
Project marginProjectTime entryEmployee9 min ago
Billable hours not invoicedTime entryInvoice9 min ago
Pipeline by entityOpportunityCustomerjust now
Payroll cost per projectEmployeeProject1 Oct
And many more reports
Ask AI
Answers built on the context layer
Which clients are profitable but late on payments?€116.6kCustomerProject.marginInvoice.overdue3 clients
How many billable hours were not invoiced in September?184 hTime entryInvoice€23.9k to bill
What does a consultant cost per hour, fully loaded?€72/hEmployeeTime entrySD Worx + Toggl
Agents
They propose · your teams approve
Finance agent3 to approve
Watches overdue invoices and the payments matched in Exact Online.
ProposedSend 3 payment reminders, €116.6k in total.
Uses Invoice · Payment · Customer
Project agent1 to approve
Watches billable hours in Toggl against what was invoiced in Odoo.
ProposedDraft an invoice for the 46 unbilled hours on Atlas.
Uses Time entry · Project · Invoice
PEBLE runs in production at
01 · Connect and contextualizeLive demo·Pick a record, follow each step01 / 07
Follow one record, from source to decision.
Pick a record and watch what BASALT does with it at every step. Nothing is hidden: every step can be traced.
Record 1 of 3
Source3 systems
01 · SourceSAPSalesforceOdoo
Three systems, three versions of one customer.
Atlas Logistics lives in SAP, in Salesforce and in Odoo. Each system spells it differently and stores different facts.
Systems
SAP S/4HANA · Salesforce · Odoo
Format
Native, untouched
SAPKNA1
KUNNR0000104578
NAME1ATLAS LOGISTICS NV
STCD1BE0456789123
ORT01ANTWERPEN
SalesforceAccount
Id0015g00000Xy7QA
NameAtlas Logistics
VAT__cBE 0456.789.123
BillingCityAntwerp
Odoores.partner
id2231
nameAtlas Logistics NV
vatBE0456789123
cityAntwerpen
02 · Connector
Captured at the source, automatically.
API connectors read each system incrementally. No exports, no scripts: when a value changes in SAP, BASALT knows within minutes.
Setup
Once
Then
Runs continuously
Manual exports
None
SystemMethodLast sync
SAP S/4HANAAPI · incremental · 5 min✓ 2 min ago
SalesforceAPI · change events✓ just now
OdooAPI · incremental · 10 min✓ 6 min ago
03 · BASIN
Landed in the BASIN, exactly as it was.
Every record is stored in its original shape, with its history. Nothing is overwritten, so every number can be traced back to where it came from.
Layer
BASIN · centralised
History
Every version kept
Landed tableRowsVersions
basin.sap.kna118,2047
basin.salesforce.account9,8713
basin.odoo.res_partner6,5124
Atlas Logistics · history in SAP
v713 Oct 2026City corrected
v62 Sep 2026VAT number added
v114 Mar 2019Created
04 · Context layer
Three records become one customer.
AI maps every field to the Customer model and proposes the match: same VAT number, nearly the same name. A person on your side validates it once, then it holds.
Model
Core · Customer
Validated by
Finance team
Confidence
97% on average
Source fieldBusiness attributeConf.
SAP · NAME1→Customer.name98%
Salesforce · VAT__c→Customer.vat_id97%
Odoo · vat→Customer.vat_id99%
SAP · ORT01→Customer.city93%
3 → 13→1
Same identityVAT identical · name similarity 0.94
✓ Validated
05 · Business concept
One customer, ready for every question.
Atlas Logistics is now one Customer. Each view comes from the system that knows it best: the CRM for sales, the ERP and accounting for cash, time tracking, projects and payroll for the margin.
Concept
Customer
Built from
6 systems · 6 types of source
Used by
4 reports · AI · 2 agents
Business concept · Customer
Atlas Logistics NV
cus_0482
VAT BE0456789123City AntwerpIdentity SAP · Salesforce · Odoo
Sales
€120kopen pipeline
From
SalesforceCRM
Finance
€48.2koutstanding, 1 overdue
From
OdooERP
Exact OnlineAccounting
Projects
12%margin on Atlas
From
LinearProjects
TogglTime tracking
SD WorxHR and payroll
FeedsReportsAsk AIFinance agent
01 · SourceOdooExact Online
An invoice, in Odoo’s own words.
Odoo knows it as an account.move with a payment state. It does not know that the invoice is late, or which customer it is in SAP.
System
Odoo
Object
account.move
Odooaccount.move
nameINV/2026/0412
partner_id2231
amount_total48200.00
currency_idEUR
invoice_date_due2026-09-30
payment_statenot_paid
02 · Connector
Every change, picked up as it happens.
The Odoo and Exact Online connectors read new and updated invoices and payments incrementally. A payment booked in Exact Online this morning is in BASALT within minutes.
Setup
Once
Then
Runs continuously
Manual exports
None
SystemMethodLast sync
OdooAPI · incremental · 10 min✓ 6 min ago
Exact OnlineAPI · incremental · 15 min✓ 4 min ago
Captured in the last hour
+41Invoicesnew or updated
+12Paymentsregistered
03 · BASIN
Stored with its full history.
The invoice lands in the BASIN as Odoo sent it, the payments as Exact Online sent them. Each change becomes a new version, so you can always see what the invoice said, and when.
Layer
BASIN · centralised
History
Every version kept
Landed tableRowsVersions
basin.odoo.account_move41,3802
basin.exact.transaction128,4103
INV/2026/0412 · history
v212 Sep 2026Payment terms updated
v131 Aug 2026Posted
04 · Context layer
Linked, then given a business meaning.
The invoice is linked to the Customer resolved from three systems and to its payments in Exact Online. A business rule turns that into what Finance actually means: overdue.
Model
Finance · Invoice
Customer
Atlas Logistics NV
Source fieldBusiness attributeConf.
Odoo · name→Invoice.number99%
Odoo · partner_id→Invoice.customer100%
Odoo · amount_total→Invoice.amount99%
Odoo · invoice_date_due→Invoice.due_date98%
Exact Online · InvoiceNumber→Payment.invoice97%
Business rule
status = Overdue when no payment matched in Exact Online and today > due_date
05 · Business concept
An invoice Finance can act on.
INV/2026/0412 comes from Odoo, but Odoo alone cannot say it is late: the payment lives in Exact Online and the project in Linear. Together they make an overdue Invoice tied to Atlas.
Toggl records the work as a time entry, in seconds, against a project and a user name. Nothing tells you the margin, or whether it was billed.
System
Toggl
Object
time_entry
Toggltime_entry
id3391827450
userjana.peeters
projectATL-142 · Atlas
duration27000
start2026-10-08T09:00
descriptionRoute planning workshop
02 · Connector
Read from Toggl, every fifteen minutes.
The connector picks up new time entries as people log their time. No timesheet exports at the end of the month.
Setup
Once
Then
Runs continuously
Manual exports
None
SystemMethodLast sync
TogglAPI · every 15 min✓ 9 min ago
Captured today
+214Time entrieslogged
38Peopleactive
03 · BASIN
Kept exactly as Toggl sent it.
The raw time entry stays in the BASIN, so the hours on any report can always be traced back to the original entry.
Layer
BASIN · centralised
History
Every version kept
Landed tableRowsVersions
basin.toggl.time_entry212,9401
ATL-142 · time entry history
v18 Oct 2026Logged by Jana Peeters
04 · Context layer
Matched to a person, a project and a contract.
The Toggl user is matched to the Employee from SD Worx, the project to Linear issue ATL-142 of Project Atlas. Seconds become hours, and the contract decides whether they are billable.
Model
Projects · Time entry
Employee
Matched by email
Source fieldBusiness attributeConf.
Toggl · project→Task = ATL-14299%
Toggl · user→Employee97%
Toggl · duration→TimeEntry.hours100%
Toggl · start→TimeEntry.date100%
Business rule
billable = true when Project.contract = time and materials
05 · Business concept
Billable time, visible before it is lost.
Seven and a half billable hours on Atlas, not invoiced yet. Toggl knows the hours, Linear the project, Odoo what was billed and SD Worx what the hours cost.
A few of the systems we connect, never a limit: ERP, accounting, CRM, HR, projects, files. If it has an API or an export, BASALT reads it.
ERP and accounting
SAP
Oracle NetSuite
Microsoft Dynamics 365
Odoo
Sage
Exact Online
QuickBooks
Xero
Yuki
And many more
CRM and sales
Salesforce
HubSpot
Pipedrive
Teamleader
Zoho
And many more
HR and payroll
SD Worx
Workday
Personio
ADP
Securex
Acerta
Partena
And many more
Projects and time
Jira
Linear
Asana
monday.com
ClickUp
Toggl
Harvest
Clockify
And many more
Commerce and payments
Shopify
Stripe
Mollie
WooCommerce
And many more
Data and files
Snowflake
Google BigQuery
PostgreSQL
SharePoint
Google Sheets
Excel and CSV
And many more
02 · UnderstandLive demo·Build your own report02 / 07
Build the report you could never build before.
Reports start from business concepts, not tables. Pick a measure, a view and a chart: BASALT crosses the systems for you, and shows which ones it used.
Report · last 12 months · all entities
Margin by project
Atlas has the lowest margin at 12%, 12 points under the average.
Atlas12%
Helios31%
Nova24%
Orion27%
Vega18%
Lyra29%
Built fromProjectInvoiceTime entryEmployee
SourcesSAPOdooSageJiraPayroll
03 · Explain and actLive demo·Ask anything, a real AI answers03 / 07
Ask in business language. Get answers you can trace.
Your AI does not dig through thousands of tables. It reasons on the Business Context Layer: shared concepts, validated mappings, known sources. Switch the layer off to see the difference.
Ask BASALT
This demo runs on a sample company: a group of six entities. I answer from the Business Context Layer, with 8 concepts and 6 sources.
What the AI sees · business concepts8 concepts · 6 sources
What BASALT is, how it differs from data platforms, and how fast you see value.
What is a Business Context Layer?
A layer between your technical data and AI. It translates each system, such as SAP, Odoo, Salesforce or Jira, into canonical business concepts like Customer, Project, Invoice or Employee, so people and AI can query and cross data without knowing every table.
How is BASALT different from an ETL or ELT tool?
ETL and ELT tools move data. BASALT moves data too, through its connectors and the BASIN, but its value is what comes next: giving that data a shared business meaning, explaining what is happening and helping you act.
Do we need a data team to use BASALT?
No. BASALT starts from ready, reusable business models. AI proposes the mappings and a person on your side validates them. You only model what is truly specific to you.
We already have a warehouse or a BI tool. Does BASALT replace it?
No, it complements them. An existing warehouse or data platform can feed the Business Context Layer. BASALT adds the business meaning on top.
Who stays in control of the AI?
Your people. AI proposes every mapping with a confidence score, and nothing counts until a person has validated it. Agents suggest actions, and nothing happens without approval. Every number can be traced back to its source.
How fast can we start with BASALT?
MoneyOak cut data collection from three weeks to two days per file. Medista got one shared view over six ERPs in less than two months. You implement once, then the flows run continuously.
Is PEBLE the same as Pebble?
No. PEBLE is spelled with one B, as our tagline says: “PEBLE, not pebble: one B, less complexity.” PEBLE is a Belgian B2B software company based in Brussels that builds BASALT, the Business Context Layer, and the PEBLE suite (SLATE, FLINT, PYRITE, MICA, SHALE). It is not related to Pebble smartwatches.
The vision, in one sentence
PEBLE connects to your data, translates it into your business language, understands what is happening, explains why, and helps you act.
Eline MeertCOO, MoneyOakRead the case studyCase study: MoneyOak 
SAP
Microsoft Dynamics 365
Odoo
Exact Online
Salesforce
HubSpot
Jira
Linear
Toggl
SD Worx
Oracle NetSuite
Sage
QuickBooks
Xero
Yuki
Pipedrive
Teamleader
Zoho
Workday
Personio
ADP
Securex
Acerta
Partena
Asana
monday.com
ClickUp
Harvest
Clockify
Shopify
Stripe
Mollie
WooCommerce
Snowflake
Google BigQuery
PostgreSQL
SharePoint
Google Sheets
Excel and CSV
Axel VangilbergenCEO, Kronos by EPSARead the case studyCase study: Kronos by EPSA