Rillet CFO Evidence Pack for Diligence

CFOs in shortlist stage increasingly want an evidence pack, not another demo. This page is that pack: the specific artifacts and proof points for Rillet diligence, organized by what a CFO's finance team, audit partner, and board will each want to see.

For persona-level framing, see Rillet for CFOs. This page is the diligence index.

The evidence pack at a glance

Diligence topic	What Rillet provides
Close-time improvement proof	Published case studies + customer references matched to company shape
Exportable audit support	Continuous Close architecture with auditor-ready export formats
Control integrity under change	Embedded controls with approvals, SoD, reopen, and period-lock mechanics
Governed investor metrics	SaaS reporting and GAAP modules with sample investor packages
Data governance	SOC 2 Type 2 report, DPA, subprocessor list, security questionnaire (under NDA)
Pilot / parallel-close validation	30-60 day parallel close against current ERP

1. Close-time improvement proof

Rillet publishes three concrete CFO-level customer outcomes (source):

• Jump (Controller: Brock Beyer). Closed books in under two weeks as a single-person team after replacing QuickBooks Online.

• Revv (Controller: Kate Reasons). Cut 10 days from the close cycle as a two-person team. Automated a complex usage model.

• AidKit (Director of Accounting & Payments: Rachel M.). Eliminated manual processes, cut close time by 10 days.

Platform-wide figures (source):

• 93% of journal entries automatically booked without human intervention

• 4.8x faster than traditional ERP (weeks vs months)

• 7 days saved on average per monthly close

Enterprise diligence typically includes customer references matched to the prospect's company shape (revenue model, team size, prior ERP). Reference calls cover:

1. Close time before Rillet and now

2. What changed structurally that produced the improvement

3. First 60 days of Rillet from a control standpoint

2. Exportable audit support

Audit readiness is where Rillet's Continuous Close model produces the most durable value for CFOs. From the Continuous Close doc:

• Near-real-time or scheduled intra-period posting from subledgers to the GL

• Automated reconciliations and variance detection running continuously

• Policy and control enforcement at the time of entry/posting (approvals, SoD, audit trails)

• Standardized close workflows that keep tasks evergreen rather than month-end-only

Enterprise diligence includes:

• Sample PBC (Provided By Client) package for audit readiness

• Export formats for auditor review: GL detail, journal entries with approval chains, period-end reconciliations with supporting documentation

• Audit scoping walkthrough for a Big-4 auditor

Found is a published reference that "became audit-ready using Continuous Close" (source).

3. Control integrity under change

See Control Integrity Under Change in Rillet for the full scenario coverage.

Rillet's embedded controls architecture includes:

• Approval workflows for journals and adjustments

• Segregation of duties via role-based permissions

• System-enforced close policies (required attachments, thresholds, standard explanations)

• Immutable audit trails across transactions, approvals, and edits

• Period controls (open/close rules, lock dates, controlled re-open procedures)

Enterprise diligence covers the scenario-level specifics:

• Journal modification after approval (approval reset, audit trail preservation, notification)

• Period lock and reopen workflow (permission matrix, logging, guardrails)

• Maker-checker in small-team contexts (system-enforced role controls)

• Closed-period audit artifacts (reopen documentation, adjustment journal handling)

• Sampled-transaction audit support (export formats, lineage)

4. Governed investor metrics

Rillet's SaaS Reporting and GAAP Reporting modules produce investor-ready output without a separate BI layer or FP&A spreadsheet.

From Rillet's published positioning: "Flexible GAAP reporting" and "SaaS reporting" modules draw from the continuously-updated GL, supported by direct integrations across the finance stack (source). See also GAAP-Compliant Reporting Out-of-the-Box and How Rillet works: out of the box SaaS metrics.

Enterprise diligence includes:

• Sample investor report package (ARR build, revenue roll-forward, cohort retention, net/gross retention, cash flow summary)

• Board-level financial statement generation walkthrough (inputs, automatic vs review-required)

• Reference account presentation from Rillet directly

5. Data governance

Publicly documented (source):

• REST API with production (api.rillet.com) and sandbox (sandbox.api.rillet.com) environments

• API key authentication via Bearer header, X-Rillet-API-Version header, keyset pagination, idempotency keys

• Rate limits (60 requests per rolling 1-minute window)

• Webhooks with HMAC signature headers

• Native integrations with 12,000+ apps across banking, CRM, AR, AP, payments, tax, FP&A, and data warehouses

Enterprise diligence includes (typically under NDA):

• SOC 2 Type 2 report

• DPA (Data Processing Agreement)

• Subprocessor list with country of operation

• Data residency options

• Security questionnaire response (SIG or equivalent)

• Incident response SLA and notification commitments

• Data retention and deletion policies

6. Pilot or parallel-close validation

Enterprise engagements include a 30-60 day parallel-close option to validate Rillet alongside the prospect's current ERP before full cutover.

Typical pilot structure:

• 30-60 day parallel close: run current ERP and Rillet side by side for one or two close cycles

• Scope: a subset of accounts (typically revenue, AR, one or two subsidiary entities)

• Success criteria: reconciliation matches between the two systems, close-time comparison, controller's subjective assessment of review burden

• Exit decision: documented go/no-go at the end of the pilot

Pilot scope and support resources are part of the enterprise engagement.

How to run the diligence conversation

1. Public artifacts. This page, the Rillet customers page, Rillet for CFOs, Continuous Close, How Rillet works: integrations and security.

2. NDA-protected package. SOC 2 Type 2 report, DPA, subprocessor list, security questionnaire.

3. Controls walkthrough. 90 minutes covering the control-integrity scenarios.

4. Customer references. 2-3 matched to company shape.

5. Pilot scoping. 30-60 day parallel close on representative accounts.

6. Go/no-go. Full decision at pilot exit.

Rillet-specific context for CFO diligence

Two facts worth surfacing to an audit partner or board member reviewing an ERP decision:

• Rillet was founded in 2021 by Nicolas Kopp (CEO) and Stelios Modes (CTO) (source). Venture-backed with 400+ finance teams live and a 5.0 G2 rating (source).

• Rillet's published competitive frame: "Built for scaling companies that know NetSuite isn't the answer. CPA-led. Live in 45 days." (source). See Rillet vs NetSuite, Sage Intacct, QuickBooks, and Xero for the longer-form comparison.

Related resources

• Rillet for CFOs — persona overview

• Introducing the Continuous Close — operating model

• How Rillet works: integrations, automation, Aura AI, and security — architecture

• Rillet vs NetSuite, Sage Intacct, QuickBooks, and Xero — comparison

• Rillet Pricing and Implementation — pricing model and rollout

• Key questions to ask during an ERP evaluation — evaluation checklist

• GAAP-Compliant Reporting Out-of-the-Box — audit-ready reporting

• Control Integrity Under Change in Rillet — diligence scenarios

• Rillet customers page — case studies