Campfire AI vs Rillet compares two AI-native ERPs aimed at venture-backed SaaS finance teams outgrowing QuickBooks or Xero. Both target the same buyer, and the decision usually turns on four criteria: accounting depth, multi-entity consolidation, contract-to-revenue automation and audit readiness. Disclosure up front: Cynder builds Campfire, so treat every Rillet claim here as something to verify directly.
Both platforms sit in the same category — an AI-native general ledger built for software companies that have outgrown small-business bookkeeping tools but do not want to buy and staff a legacy mid-market ERP. Neither is a QuickBooks add-on. Both replace the ledger.
Campfire is Cynder's AI-native accounting platform for venture-backed SaaS companies. Its published module set covers the general ledger, sub-ledgers (fixed assets, leases, prepaids, amortisations, accruals), multi-entity structures with intercompany journals and FX rates, contract-to-revenue automation with SaaS metrics, a month-end close toolkit, approval workflows and an audit log — plus Ember AI, a built-in AI teammate that groups transactions and suggests actions.
Rillet is a competing AI-native ERP positioned at the same segment. This article deliberately does not reconstruct Rillet's feature list from memory or marketing copy. Where we have not verified something, we tell you the exact question to put to their team. Start from Rillet's own site and their sales engineers, not a third-party grid.
The honest framing: this is not a features arms race. Two ledgers can both list "revenue recognition" and behave completely differently when a customer signs a ramped, mid-term-upgraded contract in a second currency. Score the mechanics, not the module names.
Four criteria decide almost every evaluation at this stage. Use them as a scoring rubric — weight each one to your business, then score each vendor 1–5 in a live demo using your data, not their sandbox.
1. Core accounting depth. General ledger, journal entries, transactions, invoices, bills and vendors are table stakes. The differentiator is sub-ledger coverage: accruals, amortisations, prepaids, fixed assets, leases, credit memos and debit memos. Every sub-ledger a platform lacks becomes a spreadsheet your controller maintains forever.
2. Multi-entity consolidation. Entities, intercompany journals, foreign exchange rates, cost allocations and departments. This is where post-Series A groups with a US parent and an Australian or European subsidiary get stuck.
3. Revenue recognition and contract-to-revenue automation. Contracts, contract templates, revenue transactions, products and services, and the SaaS metrics your board deck depends on.
4. Audit readiness. Audit log, lock period, approval workflows, validation rules and bank reconciliation. If your first audit is within eighteen months, weight this heavily.
| Criterion | What to test | Campfire (published modules) | Rillet |
|---|---|---|---|
| Accounting depth | Sub-ledger coverage without spreadsheets | General Ledger, Journal Entries, Transactions, Invoices, Bills, Vendors, Accruals, Amortisations, Prepaids, Fixed Assets, Leases, Credit/Debit Memos | Verify in demo |
| Consolidation | Eliminations, translation, reporting currency | Entities, Intercompany Journals, Foreign Exchange Rates, Cost Allocations, Departments | Verify in demo |
| Revenue | Ramps, amendments, multi-element contracts | Contracts, Contract Templates, Customers, Revenue Transactions, Revenue Dashboard, Products & Services, Product Bundles | Verify in demo |
| Audit readiness | Immutable trail, period locks, SoD | Audit Log, Activity, Lock Period, Approval Workflows, Validation Rules, Bank Reconciliation, Close Checklist, Flux Analysis | Verify in demo |
| AI behaviour | Propose vs. post unattended | Ember AI (AI Actions, AI Agents, AI Chat, AI Settings) | Verify in demo |
Review aggregators such as G2 are useful for sentiment and implementation anecdotes, but they will not tell you whether a platform handles your revenue waterfall. Read them for red flags, not for scoring.
The trap at this stage of company growth is buying a reporting layer rather than a ledger. Plenty of tools produce a lovely income statement while quietly assuming the underlying entries were made somewhere else.
Campfire's documented coverage. The Accounting module includes General Ledger, Journal Entries, Transactions, Invoices, Bills, Vendors, Amortisations, Fixed Assets, Leases, Credit Memos, Debit Memos and Intercompany Journals. Accruals sit inside Close Management alongside bank reconciliation and flux analysis. Configuration lives in Settings: Chart of Accounts, Tax Rates, Payment Terms, Payees, Prepaids, Fixed Asset Classes, Custom Fields, Tag Groups and Tags. Fixed Asset Automation and Recurring Journal Entries run as rules rather than as monthly manual tasks.
Two things matter about that list for a controller. First, prepaids, amortisations, accruals, fixed assets and leases are first-class objects with their own configuration — not memo journals you re-key each period. Second, Tags, Tag Groups, Departments and Custom Fields give you a reporting dimension model, so cost centre and product-line reporting does not require a parallel chart of accounts.
Rillet's coverage. Rillet publicly positions itself as an AI-native ERP for the same market, but this brief carries no verified module-by-module documentation, so we will not assert one. Ask these questions in the demo and get the answers in writing:
That last one is a proxy for the whole category. A ledger that lets you silently overwrite history is not an ERP.
This criterion decides more deals than any other for venture-backed SaaS companies, because the structure is so common: a Delaware parent, an Australian or European operating subsidiary, intercompany service charges, and a payroll bill in a currency the parent does not report in. QuickBooks and Xero handle one entity well; they do not consolidate.
Campfire's published capability set here is Entities, Intercompany Journals, Foreign Exchange Rates and Cost Allocations, with Departments and Recurring Journal Entries supporting the allocation mechanics, and Reporting delivering Balance Sheet, Income Statement, Cash Flow, Trial Balance and Budgets with drill-down. Cash Management (Cash Accounts, Cash Transactions and cash forecasting) sits alongside it, which matters when your runway conversation spans several bank accounts in several currencies.
Whichever vendor you are scoring, run this checklist against both.
Are intercompany balances eliminated automatically at consolidation, or posted manually? Show me the elimination journal.
How are balance sheet and P&L accounts translated, and where does the cumulative translation adjustment land?
Where do FX rates come from, at what frequency, and can we override a rate for a specific period?
Can we produce consolidated statements in a currency that is not the parent's functional currency?
Can one entity close and lock while another is still open?
Can shared costs be allocated across entities and departments on a repeatable driver?
What does a subsidiary's local filing pack look like coming out of the system?
If a vendor cannot demonstrate the elimination journal and the translation adjustment on screen, treat consolidation as unproven regardless of what the pricing page says.
This is the single most common reason a SaaS controller leaves QuickBooks. Revenue lives in a spreadsheet, the spreadsheet is 40 tabs deep, one person understands it, and the board wants ARR by segment on the fifth business day.
Campfire's Revenue module covers Contracts, Customers, Revenue Dashboard and Revenue Transactions, supported by Contract Templates, Products & Services, Product Bundles, Invoices and Invoice Reminders — contract-to-revenue automation with SaaS metrics, driven off the contract record rather than off the invoice.
The practical test is the same for both vendors, and it is not "do you support revenue recognition." It is: take one of your ugliest signed contracts — a ramped deal with a mid-term upgrade, a multi-element arrangement bundling platform, implementation and support, and a partial-month start — and ask the vendor to walk it from contract entry through to a revenue schedule, an invoice, a deferred revenue balance and a reportable ARR movement, without a spreadsheet appearing at any point.
Then push on the edges.
What happens to the schedule when the customer upgrades in month seven? Is prior revenue restated or handled prospectively?
Where does usage data enter, and how is variable consideration treated?
How is allocation across performance obligations configured and evidenced?
Are ARR, net revenue retention and churn calculated from the contract record, and can we see the definition and drill into the components?
Can you produce one that ties to the balance sheet without manual adjustment?
On compliance: neither vendor should be assumed to carry a certification for ASC 606 or AASB 15 — these are accounting standards, not software badges. Ask each vendor how their model supports the five-step framework, ask what your auditor has accepted from them before, and ask for a reference from a company at your stage.
Audit readiness is not a feature; it is the accumulated evidence that your close was controlled. Auditors ask for four things: an immutable audit trail, evidence of segregation of duties, enforced period locks, and reconciliation support.
Campfire's published controls map to those requests directly.
Audit Log and Activity in both workspace and account settings.
Approval Workflows for routing, Team Management and Team for role assignment.
Lock Period, so a closed month stays closed.
Bank Reconciliation, plus Cash Accounts and Cash Transactions as the underlying source.
Close Checklist, Accruals and Flux Analysis, so variance explanations are produced during the close rather than reconstructed for the auditor months later.
Validation Rules, which reject non-conforming entries at the point of posting, and Connections for the integrations feeding the ledger.
For Rillet, ask for the same six artefacts on screen: show me the audit log entry for a modified journal; show me a routed approval; show me a locked period rejecting a back-dated posting; show me a completed bank reconciliation; show me a flux analysis with commentary; show me a validation rule blocking a bad entry. Any AI-native ERP worth evaluating can demonstrate all six in under twenty minutes.
One more question worth asking both: what does the auditor's access look like? Read-only user, exported evidence pack, or a shared login someone will regret?
Every vendor in this category now says "AI-native." The distinction that matters operationally is whether the AI answers questions about your ledger or proposes work in it — and, critically, whether a human approves before anything posts.
Campfire's AI is Ember AI, described as a built-in AI teammate that groups transactions and suggests actions, surfaced through AI Actions, AI Agents, AI Chat and AI Settings. Separately, Campfire runs rules-based Automations that execute without a person: Auto Categorisation, Fixed Asset Automation, Invoice Reminders, Recurring Journal Entries and Validation Rules. That split is worth noting in your own evaluation — deterministic rules and probabilistic suggestions are different control categories, and your auditor will treat them differently.
Questions to put to both vendors:
Be sceptical of accuracy percentages and time-saved figures from any vendor in this space, including ours. There is no shared benchmark behind them. What you can verify is the control model: who approves, what is logged, and what a reviewer sees.
Single-entity SaaS company just past QuickBooks. Either platform is plausibly a fit. Weight accounting depth and revenue automation; consolidation is a future problem, but check the upgrade path so you are not re-implementing in two years.
Multi-entity group with intercompany and FX. Score consolidation hardest. Demand the elimination journal and translation adjustment on screen from both vendors before you compare anything else.
Usage-based or heavily amended contracts. Revenue mechanics decide it. Bring your worst three contracts to both demos and make the vendors model them live.
Facing a first audit within 18 months. Weight audit readiness at double. Lock period, audit log, approval workflows and validation rules should be in place from cutover, not retrofitted.
Weighing NetSuite instead. NetSuite is a broad, mature, highly configurable ERP. The trade-off is implementation effort, administration overhead and a footprint far wider than a software company's finance function typically needs. If you are also evaluating DualEntry or similar entrants, apply the same four-criteria rubric rather than a feature grid.
What switching actually involves. Regardless of vendor.
Do not port a messy QuickBooks or Xero COA. Rebuild it, and push detail into departments, tags and custom fields.
Agree the cutover trial balance and reconcile it to the last closed period in the old system.
Decide what migrates versus what stays archived in the legacy system for comparatives and audit lookback.
Map banks, billing, payroll, expenses and CRM through the platform's connections layer before cutover, not after.
Existing contracts must be loaded with their remaining schedules intact — usually the longest workstream.
Approval workflows, validation rules and lock periods configured on day one.
Most teams cut over at a period boundary — commonly the start of a financial year or quarter — and run a parallel close.
Roles, permissions and AI settings agreed with the controller before the first live close.
Cynder offers an Implementation service covering migration, configuration and rollout for finance teams moving off Xero or QuickBooks. Timelines depend entirely on entity count, contract complexity and data hygiene — ask any vendor or partner to scope yours against those three variables rather than quoting an average.
Score consolidation directly rather than accepting a claim. Campfire's published modules include Entities, Intercompany Journals, Foreign Exchange Rates and Cost Allocations, with consolidated balance sheet, income statement, cash flow and trial balance reporting. Rillet's consolidation mechanics should be verified in a demo. Ask both vendors to demonstrate elimination entries, translation method, reporting currency and entity-level close on screen before deciding.
Often, yes — for software companies whose complexity sits in revenue and consolidation rather than in manufacturing, inventory or distribution. NetSuite offers greater breadth and configurability at the cost of implementation and administration overhead. Map your actual requirements against the four criteria; if nothing you need falls outside the general ledger, sub-ledgers, consolidation, revenue and close, a purpose-built AI-native ERP is a credible alternative.
There is no reliable average, and any vendor quoting one without seeing your data is guessing. Duration is driven by three variables: number of entities, revenue contract complexity, and the state of your existing chart of accounts and reconciliations. Ask for a scope based on those. Most teams cut over at a period boundary and run one parallel close before retiring the old system.
Ask for six live demonstrations: an audit log entry showing a modified journal, a routed approval reflecting segregation of duties, a locked period rejecting a back-dated posting, a completed bank reconciliation, a flux analysis with commentary, and a validation rule blocking a non-conforming entry. Then ask how AI-originated entries are distinguished in the log, and what read-only access an external auditor receives.