Integrations and implementation
SMPL.ai connects the systems your Finance team already runs, including your ERP, CRM, billing platform, and HRIS, into one SaaS financial model. That model supports reporting, forecasting, budgeting, and Plan Assurance. Connecting your systems is part of what SMPL delivers: SMPL leads the integration and implementation, including data mapping, configuration, and financial validation.
How SMPL connects your systems
During implementation, SMPL connects to each system with read-only access or works from structured extracts, depending on the system and your security requirements. Where your data already sits in a warehouse such as Snowflake or in scheduled exports, SMPL can read from there instead. Teams with their own data pipelines can send data through SMPL's ingest API.
SMPL then maps the data into one model, applies your company's definitions, and reconciles the results to your source systems. For multi-entity companies, SMPL builds on your ERP's consolidated results, including its currency translation and intercompany eliminations, so the ERP remains the system of record for consolidation.
After go-live, your team initiates each refresh when your books close, on your own close calendar, and can load intra-month cash or pipeline data whenever you need a current view.
Systems with dedicated pages
Each page covers the data SMPL uses from that system, the reporting and planning it supports, and how SMPL connects it to the rest of your stack.
Other systems SMPL works with
These systems supply one part of the model and are connected through the same implementation process.
Accounting and ERP
- QuickBooks Online
Chart of accounts, journal entries, invoices, and classes for the financial statements, departmental reporting, and cash.
CRM
- HubSpot
Deals, pipelines, and stages for pipeline, bookings, and revenue forecasting, in the same way as Salesforce.
Billing and subscriptions
- Stripe Billing
Customers, subscriptions, invoices, and payments for the ARR waterfall, retention, and cash timing.
- Chargebee
Subscriptions, plans, and invoices for ARR, churn, expansion, and billing-to-cash timing.
- Recurly
Subscription and invoice data for ARR and retention reporting.
HRIS and payroll
- Rippling, Gusto, BambooHR, Workday, HiBob, and Deel
Employees, departments, start dates, and compensation for the headcount plan, payroll cost, and the effect of hiring on opex and cash.
Data warehouses and file delivery
- Snowflake, cloud storage, and secure file transfer
Where your data already sits in a warehouse or scheduled exports, SMPL can read a secure share or a file drop instead of each source system.
Using something else? If it can provide read-only access or structured exports, SMPL can usually map it into the model. Tell us what you use and we will confirm the approach during scoping.
Who does what
SMPL is responsible for
Connecting to your systems or working from structured extracts, mapping accounts, customers, products, and departments, configuring the model, and reconciling the results to your source systems.
Your team provides
Read-only access or structured extracts, your company's definitions for metrics such as ARR and bookings, review of the mapping decisions SMPL documents, validation of the first results, and the decisions about what goes to the board. After go-live, your team initiates each refresh when your books close, on your own close calendar.
Your systems keep doing their jobs
SMPL reads from your ERP, CRM, billing platform, and HRIS and does not write back to them. Each remains the system of record for its own domain.
What the connected model produces
Once your systems are connected, the same numbers feed every output: ARR and retention, the three financial statements, the management P&L, cash and runway, headcount, a driver-based budget tested with Plan Assurance, and the board package. A change in bookings, churn, or hiring flows through ARR, revenue, cash, and headcount together.
Discuss your environment
Bring a list of your systems and a copy of what your board package looks like today. We will walk through how SMPL would connect them and what your team would see at the end of implementation.
NetSuite, Sage Intacct, QuickBooks Online, Xero, Rillet, Campfire, Salesforce, HubSpot, Maxio, Stripe, Chargebee, Recurly, Rippling, Gusto, BambooHR, Workday, HiBob, Deel, Snowflake, and other product names are trademarks of their respective owners. They are used only to identify the systems SMPL.ai works with. SMPL.ai is not affiliated with, sponsored by, or endorsed by these companies, and no partnership or certification is implied.
Frequently asked questions
- Which systems does SMPL.ai integrate with?
- SMPL works with the ERP, CRM, billing, and HRIS systems SaaS Finance teams commonly use, including NetSuite, Sage Intacct, QuickBooks Online, Xero, Rillet, and Campfire for accounting; Salesforce and HubSpot for CRM; Maxio, Stripe, Chargebee, and Recurly for billing; and Rippling, Gusto, BambooHR, Workday, HiBob, and Deel for workforce data. SMPL leads the integration as part of implementation.
- How does data get from our systems into SMPL.ai?
- As part of implementation, SMPL connects to each system with read-only access or works from structured extracts, a warehouse share, or secure file delivery, depending on the system and your security requirements. Teams with their own data pipelines can also send data through SMPL's ingest API. SMPL maps and validates the data. After go-live, your team initiates each refresh when your books close, on your own close calendar, and can load intra-month cash or pipeline data whenever you need a current view.
- Does SMPL.ai work with multi-entity, multi-currency companies?
- Yes. For ERPs such as NetSuite and Sage Intacct, SMPL uses the ERP's consolidated financial actuals, including its currency translation and intercompany elimination adjustments, and for USD-reporting companies the consolidated USD results. The ERP remains the system of record for consolidation: SMPL supports reporting and planning on that consolidated foundation rather than recreating the consolidation engine. During implementation, SMPL confirms that the extraction method delivers the required consolidation context, reconciles the imported results to the ERP's consolidated reports, retains entity and currency information, and scopes the subsidiary views you need.
- Our system is not listed. Can SMPL.ai still work with it?
- Usually, yes. If a system can provide read-only access or structured exports of the data SMPL needs, SMPL can map it into the model as part of implementation. Tell us what you use and we will confirm the approach during scoping.
- Who does the data mapping and reconciliation?
- SMPL does. Mapping accounts, customers, products, and departments across systems and reconciling the results to your source systems is part of SMPL's implementation. Your team reviews the decisions and confirms the definitions.
- Does SMPL.ai write data back to our ERP or CRM?
- No. SMPL reads from your systems and does not post journal entries, invoices, or changes back to them.
More from FP&A for SaaS
Related reading: Why FP&A implementations shouldn't take months · Connected systems vs aligned financial data · The SMPL.ai platform · FP&A software for SaaS companies