Rillet Review
Rillet is an AI native general ledger and ERP for multi entity B2B SaaS, fintech and healthcare tech companies that have outgrown QuickBooks, pairing native ASC 606 revenue recognition and consolidation with a first party MCP server that lets an agent such as Claude read and write the ledger under the connected user's own permissions.
What you are buying is a young general ledger designed after the problems it solves. Rillet posts ASC 606 allocations and deferred revenue schedules from contracts synced out of Salesforce, HubSpot or Stripe, consolidates multiple legal entities with automatic intercompany eliminations and FX revaluation, locks periods by entity, and exposes the whole thing through 121 REST endpoints and a remote MCP server at api.rillet.com/mcp that its own docs show being added from the Claude connector directory. Nothing else in this category ships an agent surface that complete. TechCrunch reported on 19 August 2026 that the company had passed 600 customers and raised 100 million dollars at a 1 billion dollar valuation, so the vendor risk is no longer what it was in 2024.
The catch is that almost every claim beyond the documentation is the vendor's own, and several of them do not agree with each other. The integrations page names 58 connectors, llms.txt says more than 100 and the help centre says more than 12,000. The customers page says 93 percent of journal entries post without human intervention while the enterprise page says 99.7 percent of transaction posting is automated, and neither figure is defined. The 5.0 G2 rating quoted on the about page could not be read independently because G2 returns 403 to every fetch, and the Capterra listing held zero reviews on 6 September 2026, so the public review corpus a controller normally leans on does not exist yet. An August 2026 r/Accounting thread relays a controller inside Rillet's own customer Slack saying billing is the weakest area of the product, and a NetSuite consultant's August 2026 short argues that Rillet's product updates are features NetSuite shipped decades ago.
Get four things in writing. The subscription price and what drives it, because no price is published anywhere and the help centre says the fee tracks features used and business complexity rather than seats or revenue. The renewal mechanics, because the published master services agreement renews for one year automatically, needs 60 days written notice to stop, allows a price increase on 75 days notice, and makes paid fees non refundable. The exit path, because that agreement gives a CSV export only on a request made within 30 days of termination, after which Rillet may delete the data. And a sandbox proof of your own billing model end to end, usage tiers and minimum commitments included, before the ledger is cut over.
- ✓Multi-state or multi-jurisdiction payroll where compliance is the real exposure
- ✓Mid-market to enterprise (50 to 1,000+) needing benefits, HR, and audit-ready reporting
- ✓CFOs who want one accountable vendor to absorb tax and penalty risk
- !Cost-sensitive teams under ~25 employees with simple single-state payroll, where Gusto is cheaper
- !Buyers who need all-in pricing transparency upfront
- !Software-first teams wanting native real-time API and GL sync as a core workflow
The jobs a controller actually hires Rillet for
Watch the same task in each tool
Forget the 40-row feature grid. Pick a finance workflow and see how ADP, Gusto, and Rippling actually do it, with our verdict on who wins for whom.
Most controls and the deepest audit trail, but the most clicks before money moves.
Fewest steps to approve and run; cleanest for a simple single-state shop.
Most automatable via native API; the workflow can run itself once configured.
Compare on what matters
What it actually costs
Here's what it really costs: published rates where a vendor lists them, aggregated quote data where they don't, plus a path to your own number.
Get your real number
Tell us your setup and we will line up a tailored ADP quote and benchmark it against what similar companies pay.
Free. We benchmark your quote; vendors pay us, never you.
What it actually takes to go live
The vendor runs the implementation and puts it at 4 to 8 weeks in llms.txt, 4 to 6 weeks in the help centre and six weeks on the implementation page. Its own CPA team accesses the legacy system, extracts and cleans the data, migrates it and stays through the first close, with the customer validating rather than filling in templates. What still takes finance time is the chart of accounts and entity design, the billing model, and the decision on how much history to carry across. A sandbox exists at sandbox.api.rillet.com for integration work before cutover. It is a genuine ledger migration rather than a signup, but it is a fraction of a traditional ERP programme.
Rillet is the only ledger in this category with a first party remote MCP server that an agent can both read from and write to, and its own docs show it being added straight from the Claude connector directory.
Rillet hosts a remote MCP server at api.rillet.com/mcp over HTTP with OAuth2. The documentation walks through three routes in: searching for Rillet in the Claude connector directory and authorising an organisation, adding it in Claude Code with the claude mcp add command, or pointing Cursor at it through mcp-remote. An API key can be passed as a bearer token instead of using OAuth.
The MCP page states that the server offers tools implementing the same features as the public API, and that an agent only has access to the tools the connected Rillet user has access to, so the permission model is the product's own roles rather than a separate grant. The public API behind it documents 121 operations covering the chart of accounts, subsidiaries, members, roles and role assignments, approval workflows, products, contracts, invoices, credit memos, bills, charges, reimbursements, journal entries, bank accounts and transactions, tax rates, books and custom fields, plus report endpoints for trial balance, balance sheet, income statement, cash flow, executive P and L and the ARR waterfall.
Inside the product, Aura is documented as three surfaces: chat against the live ledger, embedded agents for accruals, flux, cash reconciliation, AR and AP that propose work for human approval, and an always on layer that watches for anomalies. The security page commits to nothing posting without approval, every AI action logged, materiality tiered thresholds and model changes flowing through IT general controls.
The honest caveats: API access has to be enabled by the Rillet team before keys exist, the rate limit is 60 requests a rolling minute, and every claim about agent accuracy is the vendor's own. The founder said on the Upflow podcast in June 2025 that a natural language reporting feature that sounded excellent in theory was harder in practice because finance workflows need consistency.
The demos that matter, none of the noise
Rillet, kept current
Rillet FAQ
What does Rillet cost for a 300 person SaaS company?
Rillet publishes no price. The pricing URL resolved to a sales contact page rather than a price list when checked on 6 September 2026, and the Capterra listing showed no starting price and no free trial. The help centre states that Rillet does not charge per seat or on revenue, and that the fee is set by the features used and the complexity of the business, which means entity count, billing model and module list move the number rather than headcount.
The only price the vendor publishes is 10,000 dollars for implementation, in its own llms.txt file, next to its claim that comparable NetSuite quotes come in at 150,000 to 400,000 dollars or more. That comparison is the vendor's own framing and no independent quote for either product could be verified. Treat the subscription as unknown until quoted, and ask for the three year price at your projected entity count alongside the renewal uplift terms.
What are Rillet's contract terms, and how do you get your data out?
The published master services agreement sets an initial term in the order form, then renews automatically for one year periods. Either party has to give written notice of non renewal at least 60 days before the end of the current term. Rillet may raise the price for a renewal term by giving notice at least 75 days before that term ends. Fees are non cancelable and amounts paid are non refundable, late balances accrue 1.5 percent a month, and access can be suspended once a payment is 10 days overdue.
On exit, Rillet delivers an export of customer data in CSV format, or another mutually agreed format, only if the request is made within 30 days of termination or expiry. After that window Rillet may delete the data. Liability is capped at three times the fees paid in the preceding 12 months, with a separate 250,000 dollar cap for a data security incident. The agreement is governed by Delaware law with JAMS arbitration seated in Delaware.
How long does a Rillet implementation take, and who does the work?
The vendor runs it. The implementation page describes a CPA led team that accesses the legacy system, extracts the data, combs it for quality issues, migrates it and then sits with the finance team through the first close, with the customer only validating. The published timeline is not consistent: llms.txt says 4 to 8 weeks, the help centre says 4 to 6 weeks and the implementation page says six weeks, so treat 4 to 8 weeks as the honest range and get the go live date into the order form.
A sandbox environment is documented at sandbox.api.rillet.com for integration work before cutover. On the independent side, a September 2026 r/CFO thread has a usage based SaaS company of roughly 150 million dollars of ARR describing a switch from QuickBooks Online in late 2024 that it is happy with, and a finance lead in the same thread calling support responsive with the Stripe, Ramp and Rippling connections working.
Can Claude or another AI agent operate Rillet?
Yes, more directly than any other ledger in this category. Rillet hosts a remote MCP server at api.rillet.com/mcp over HTTP with OAuth2, and its documentation walks a user through adding Rillet from the Claude connector directory, adding it in Claude Code with the claude mcp add command, or pointing Cursor at it. An API key can be passed as a bearer token instead of using OAuth. The docs state that the MCP tools implement the same features as the public API and that an agent only gets the tools the connected Rillet user has access to.
The practical limits are worth knowing before planning around it. API access is not on by default, and the getting started page says to contact the Rillet team to enable it. Requests are capped at 60 a rolling minute, pages return at most 100 records, and an organisation can register only five webhook endpoints. Inside the product, Aura agents propose entries and wait for a human approval rather than posting on their own, which is a control feature rather than a limitation.
Rillet alternatives
Rillet publishes no pricing and offers no free trial, so a demo request is the only route to a number. Click below to reach the sales team, and ask for the three year price at your projected entity count along with the renewal uplift terms before you get to an order form.
Rillet Review
Rillet is an AI native general ledger and ERP for multi entity B2B SaaS, fintech and healthcare tech companies that have outgrown QuickBooks, pairing native ASC 606 revenue recognition and consolidation with a first party MCP server that lets an agent such as Claude read and write the ledger under the connected user's own permissions.
Independently scored across six dimensions. Every dimension is sourced, and we say whether a claim is published, reported, or estimated.
Rillet hosts a remote MCP server at api.rillet.com/mcp with OAuth2, and its own setup guide walks a user through finding Rillet in the Claude connector directory as well as adding it in Claude Code and Cursor. The MCP docs state the server exposes the same features as the public API and that an agent only reaches the tools the connected Rillet user can reach, which is the permission model a controller needs. Aura is documented as three surfaces: chat against the live ledger, embedded agents that propose and wait for approval, and always on anomaly detection, with every proposal, approval and rejection logged. The agent quality claims are the vendor's own, and the founder said on the Upflow podcast in June 2025 that natural language reporting proved harder in practice than in theory.
The vendor runs the work rather than handing over a spreadsheet: the implementation page describes its own CPA team entering the legacy system, extracting and cleaning the data, migrating it, and sitting alongside the finance team through the first close. The published timeline is 4 to 8 weeks at 10,000 dollars in llms.txt, 4 to 6 weeks in the help centre and six weeks on the implementation page, so the range is real but the number moves by page. A sandbox environment exists at sandbox.api.rillet.com for integration work before cutover. A September 2026 r/CFO thread has a usage based SaaS company of roughly 150 million dollars of ARR reporting a move off QuickBooks Online in late 2024 that it is happy with.
The public reference documents 121 operations plus 23 signed webhook event types, covering the chart of accounts, subsidiaries, roles and role assignments, approval workflows, contracts, invoices, bills, journal entries, bank transactions and reports including trial balance, balance sheet, cash flow and ARR waterfall. The engineering detail is unusually complete for a young vendor: a sandbox host, keyset pagination, idempotency keys held 24 hours, an explicit version header and RFC 9457 error bodies. Webhooks carry an HMAC-SHA256 signature with documented retry groups and a 30 second acknowledgement window. The ceilings are the catch: 60 requests a rolling minute, a maximum page size of 100, five webhook endpoints per organisation, and API access that the docs say the Rillet team has to switch on.
Close management ships a configurable checklist with owners, deadlines and documents, period locking by entity, reconciliation error highlighting and AI drafted flux analysis, and the API exposes trial balance, balance sheet, income statement, cash flow, executive P and L and ARR waterfall as report endpoints. Consolidated and subsidiary views switch without a rebuild, with eliminations and FX handled in the platform. The automation claims do not reconcile: the customers page says 93 percent of journal entries post without human intervention while the enterprise page says 99.7 percent of transaction posting is automated, and neither figure is defined. An August 2026 r/Accounting thread relays a controller inside Rillet's own customer Slack saying billing is the weakest area.
The product pages document ASC 606 allocations posted automatically, deferred revenue schedules, intercompany eliminations with FX revaluation, and period locking with granular subledger locks by entity, and the security page lists SOC 1 Type II and SOC 2 Type II audited annually with every AI action logged and nothing posting without approval. The API reference adds multi-book support and read and write access to approval workflows, which is the control definition an auditor asks for. What is missing is age and breadth: the about page dates the company to a 2024 exit from stealth, there is no fund or grant accounting, and no statutory or country localisation list is published. SOX readiness is asserted on the security page rather than evidenced by a named public filer.
Support surfaces that can be checked are a public status page, a documented MCP support address, a nine question help centre, the Close Club community, and a customer success page describing CPA led implementers who stay after go live. A September 2026 r/CFO thread has a finance lead calling support responsive, with the Stripe, Ramp and Rippling connections working. What cannot be checked is any published SLA, response target or support tier, and review site evidence is absent: the Capterra listing carried zero reviews when read on 6 September 2026 and the G2 profile returned 403 to every fetch, so the 5.0 G2 rating on the about page stays vendor claimed.
The most agent ready ledger in the category, sold entirely behind a sales call.
Written by the Audit Friendly research team. No vendor edits, no sponsored placement.
What you are buying is a young general ledger designed after the problems it solves. Rillet posts ASC 606 allocations and deferred revenue schedules from contracts synced out of Salesforce, HubSpot or Stripe, consolidates multiple legal entities with automatic intercompany eliminations and FX revaluation, locks periods by entity, and exposes the whole thing through 121 REST endpoints and a remote MCP server at api.rillet.com/mcp that its own docs show being added from the Claude connector directory. Nothing else in this category ships an agent surface that complete. TechCrunch reported on 19 August 2026 that the company had passed 600 customers and raised 100 million dollars at a 1 billion dollar valuation, so the vendor risk is no longer what it was in 2024.
The catch is that almost every claim beyond the documentation is the vendor's own, and several of them do not agree with each other. The integrations page names 58 connectors, llms.txt says more than 100 and the help centre says more than 12,000. The customers page says 93 percent of journal entries post without human intervention while the enterprise page says 99.7 percent of transaction posting is automated, and neither figure is defined. The 5.0 G2 rating quoted on the about page could not be read independently because G2 returns 403 to every fetch, and the Capterra listing held zero reviews on 6 September 2026, so the public review corpus a controller normally leans on does not exist yet. An August 2026 r/Accounting thread relays a controller inside Rillet's own customer Slack saying billing is the weakest area of the product, and a NetSuite consultant's August 2026 short argues that Rillet's product updates are features NetSuite shipped decades ago.
Get four things in writing. The subscription price and what drives it, because no price is published anywhere and the help centre says the fee tracks features used and business complexity rather than seats or revenue. The renewal mechanics, because the published master services agreement renews for one year automatically, needs 60 days written notice to stop, allows a price increase on 75 days notice, and makes paid fees non refundable. The exit path, because that agreement gives a CSV export only on a request made within 30 days of termination, after which Rillet may delete the data. And a sandbox proof of your own billing model end to end, usage tiers and minimum commitments included, before the ledger is cut over.
- A multi entity B2B SaaS or usage based business that has outgrown QuickBooks Online and needs ASC 606 allocations, deferred revenue schedules and intercompany eliminations posted by the system rather than rebuilt in a spreadsheet each month.
- A finance team that wants an AI agent inside its controls: Aura proposes accruals, flux analysis and reconciliations for human approval, and the MCP server at api.rillet.com/mcp lets Claude query and update the ledger under the connected user's own permissions.
- A controller who cannot give six months to an ERP programme: the vendor's own CPA team extracts, cleans and migrates the legacy data and stays through the first close, published at 4 to 8 weeks for 10,000 dollars.
- A company that moves physical product or files statutory returns in many countries: there is no inventory, warehouse, manufacturing or published country localisation surface anywhere on the product pages.
- A buyer who needs a price before a sales call: rillet.com/pricing serves a demo form, the Capterra listing shows no starting price and no free trial, and the only published number is the 10,000 dollar implementation fee.
- A team that needs a deep public reference base or heavy bulk data movement: Capterra held zero reviews on 6 September 2026, and the documented API ceiling is 60 requests a rolling minute with five webhook endpoints per organisation.
The jobs a controller actually hires Rillet for
Six jobs, each with the two-minute clip that shows it. Hover a card to preview, click to watch.
Watch the same task in each tool
Forget the 40-row feature grid. Pick a finance workflow and see how Workiva, BlackLine, and FloQast actually do it, with our verdict on who wins for whom.
Linked numbers, native iXBRL, and EDGAR submission in one document. Most setup up front, least tie-out work at deadline.
Governs the close and the numbers feeding the filing, but has no SEC document or XBRL layer. You still export to a printer or Workiva.
Keeps the Excel workpapers your team already built and layers checklist and review on top. Fastest to stand up, thinnest on filing.
Compare on what matters
What it actually costs
Here's what it really costs: published rates where a vendor lists them, aggregated quote data where they don't, plus a path to your own number.
The help centre states that Rillet does not charge per seat or on revenue, and that the fee is set by the features used and the complexity of the business. The Capterra listing shows no starting price and no free trial.
The Rillet team accesses the legacy system, extracts and cleans the data, migrates it, and stays through the first close. The same file compares this to NetSuite quotes of 150,000 to 400,000 dollars or more, which is the vendor's own framing rather than an independent quote.
Non renewal takes 60 days written notice before the end of the current term, and Rillet may raise the price for a renewal term on at least 75 days notice. Fees are non cancelable and amounts paid are non refundable.
What it actually takes to go live
Vetted Workiva partnersFind a partner →
SEC reporting manager or controller as owner, technical accounting for disclosures and tagging decisions, the SOX or internal audit lead for controls solutions, the sustainability controller for ESG scope, light IT involvement for SSO and data connectors, Workiva customer success plus its Professional Services team, and often an advisory partner (the Big 4 and firms like Riveron implement on Workiva; Deloitte has built CSRD compliance solutions on the platform).
The integrations page named 58 connectors when counted on 6 September 2026, llms.txt says more than 100 native integrations, and the help centre and about page both say more than 12,000 platforms. The larger number describes reach through aggregators rather than integrations Rillet builds and maintains. Ask which of your specific systems are native, which route through an aggregator, and who owns the connector when a field mapping breaks.
An August 2026 r/Accounting thread relays a controller inside Rillet's own customer Slack saying billing is said to be its weakest area. The revenue recognition engine and the contract to invoice schedule are well documented, and the API even exposes a preview of the invoice schedule a contract would produce before it is created. Prove your own billing model end to end in the sandbox before cutover, usage tiers, minimum commitments and mid term amendments included.
The getting started page states a maximum of 60 API requests over a rolling minute, with anything above returning HTTP 429, a maximum page size of 100 records, and cursors that expire after two hours. The webhooks page caps an organisation at five webhook endpoints. The same getting started page says to contact the Rillet team to enable API access before keys can be created, so a warehouse sync has to be paced and provisioned rather than assumed.
The customers page says 93 percent of journal entries are booked without human intervention. The enterprise page says 99.7 percent of transaction posting is automated. Both figures are vendor claimed, neither is defined, and no measurement period or customer sample is given. Ask for the definition, the sample and the period, and ask what the number looked like in the first three months for a business with a transaction mix like yours.
The published master services agreement renews automatically for one year periods and needs 60 days written notice of non renewal, Rillet may raise the renewal price on at least 75 days notice, and fees paid are non refundable. On termination Rillet delivers customer data in CSV or another mutually agreed format only if the request is made within 30 days, after which it may delete the data. Liability is capped at three times the fees paid in the preceding 12 months, with a separate 250,000 dollar cap for a data security incident.
Governed AI is strong inside the platform; the external agent surface is real REST APIs plus an MCP gateway that is announced but not yet self serve.
Rillet hosts a remote MCP server at api.rillet.com/mcp over HTTP with OAuth2. The documentation walks through three routes in: searching for Rillet in the Claude connector directory and authorising an organisation, adding it in Claude Code with the claude mcp add command, or pointing Cursor at it through mcp-remote. An API key can be passed as a bearer token instead of using OAuth.
The MCP page states that the server offers tools implementing the same features as the public API, and that an agent only has access to the tools the connected Rillet user has access to, so the permission model is the product's own roles rather than a separate grant. The public API behind it documents 121 operations covering the chart of accounts, subsidiaries, members, roles and role assignments, approval workflows, products, contracts, invoices, credit memos, bills, charges, reimbursements, journal entries, bank accounts and transactions, tax rates, books and custom fields, plus report endpoints for trial balance, balance sheet, income statement, cash flow, executive P and L and the ARR waterfall.
Inside the product, Aura is documented as three surfaces: chat against the live ledger, embedded agents for accruals, flux, cash reconciliation, AR and AP that propose work for human approval, and an always on layer that watches for anomalies. The security page commits to nothing posting without approval, every AI action logged, materiality tiered thresholds and model changes flowing through IT general controls.
The honest caveats: API access has to be enabled by the Rillet team before keys exist, the rate limit is 60 requests a rolling minute, and every claim about agent accuracy is the vendor's own. The founder said on the Upflow podcast in June 2025 that a natural language reporting feature that sounded excellent in theory was harder in practice because finance workflows need consistency.
Rillet, kept current
Rillet FAQ
Rillet publishes no price. The pricing URL resolved to a sales contact page rather than a price list when checked on 6 September 2026, and the Capterra listing showed no starting price and no free trial. The help centre states that Rillet does not charge per seat or on revenue, and that the fee is set by the features used and the complexity of the business, which means entity count, billing model and module list move the number rather than headcount.
The only price the vendor publishes is 10,000 dollars for implementation, in its own llms.txt file, next to its claim that comparable NetSuite quotes come in at 150,000 to 400,000 dollars or more. That comparison is the vendor's own framing and no independent quote for either product could be verified. Treat the subscription as unknown until quoted, and ask for the three year price at your projected entity count alongside the renewal uplift terms.
The published master services agreement sets an initial term in the order form, then renews automatically for one year periods. Either party has to give written notice of non renewal at least 60 days before the end of the current term. Rillet may raise the price for a renewal term by giving notice at least 75 days before that term ends. Fees are non cancelable and amounts paid are non refundable, late balances accrue 1.5 percent a month, and access can be suspended once a payment is 10 days overdue.
On exit, Rillet delivers an export of customer data in CSV format, or another mutually agreed format, only if the request is made within 30 days of termination or expiry. After that window Rillet may delete the data. Liability is capped at three times the fees paid in the preceding 12 months, with a separate 250,000 dollar cap for a data security incident. The agreement is governed by Delaware law with JAMS arbitration seated in Delaware.
The vendor runs it. The implementation page describes a CPA led team that accesses the legacy system, extracts the data, combs it for quality issues, migrates it and then sits with the finance team through the first close, with the customer only validating. The published timeline is not consistent: llms.txt says 4 to 8 weeks, the help centre says 4 to 6 weeks and the implementation page says six weeks, so treat 4 to 8 weeks as the honest range and get the go live date into the order form.
A sandbox environment is documented at sandbox.api.rillet.com for integration work before cutover. On the independent side, a September 2026 r/CFO thread has a usage based SaaS company of roughly 150 million dollars of ARR describing a switch from QuickBooks Online in late 2024 that it is happy with, and a finance lead in the same thread calling support responsive with the Stripe, Ramp and Rippling connections working.
Yes, more directly than any other ledger in this category. Rillet hosts a remote MCP server at api.rillet.com/mcp over HTTP with OAuth2, and its documentation walks a user through adding Rillet from the Claude connector directory, adding it in Claude Code with the claude mcp add command, or pointing Cursor at it. An API key can be passed as a bearer token instead of using OAuth. The docs state that the MCP tools implement the same features as the public API and that an agent only gets the tools the connected Rillet user has access to.
The practical limits are worth knowing before planning around it. API access is not on by default, and the getting started page says to contact the Rillet team to enable it. Requests are capped at 60 a rolling minute, pages return at most 100 records, and an organisation can register only five webhook endpoints. Inside the product, Aura agents propose entries and wait for a human approval rather than posting on their own, which is a control feature rather than a limitation.
Rillet alternatives
Ask us anything
Answered only from our own published research on this tool, never from general internet noise. If we cannot answer it well, our research agents will dig in and publish a sourced answer.
