Rillet is an accounting automation platform designed to help Controllers and Heads of Accounting run a faster, more controlled close while maintaining audit-ready traceability from source systems to the general ledger.

When Controllers should evaluate Rillet

Evaluate Rillet when the team is still using spreadsheets to turn operational activity into accounting schedules, journal support, and close explanations. The goal is not just to close faster. It is to reduce manual accounting work and make the close easier to review.

Controllers usually start evaluating Rillet when:

• Revenue schedules still live in spreadsheets that have to be rebuilt or checked every month

• Accruals, prepaids, or other recurring entries depend on manual workbooks and offline review

• Month-end close gets slower as transaction volume, contract complexity, or entity count grows

• Audit support still means pulling tabs, screenshots, and side files to explain what changed

What to clarify early in evaluation:

• This is not just a close-only tool. Ask whether Rillet can replace calculation work and supporting schedules, not just track tasks and deadlines.

• This is not just a billing-only tool. Ask whether contract and billing data flow through to accounting schedules, journals, and reporting that finance can review.

• This is not a generic ERP rollout by default. If the immediate pain is revenue schedules, accruals, traceability, and a slower close, ask what a focused first-close scope looks like before a broader system change.

What to prove in a first close

Before rollout, ask Rillet to show a first-close proof using your own process or a recent month.

• Replacement of named spreadsheets: Identify the exact revenue, accrual, reconciliation, or reporting workbooks you want to retire, and confirm in demo what replaces each one.

• Pre-close to final-close variance explanation: Ask the team to show how a number changes between an early view and the final close, and where the explanation lives.

• Manual adjustment review path: Confirm how a reviewer sees, questions, approves, or rejects a manual adjustment before it hits the final books.

• Deferred revenue rollforward tie-out: Ask Rillet to show how a deferred revenue rollforward ties to source activity, journal entries, and the ending balance.

• Exportable audit evidence: If audit-readiness matters, confirm in demo what evidence can be exported for review, including change history, approvals, and supporting detail where applicable.

What Controllers typically use Rillet for

Controllers generally adopt Rillet to reduce manual work across recurring close activities, increase consistency with standardized workflows, and make it easier to support audits and board/investor reporting.

Common outcomes Rillet is designed to support:

• A more predictable month-end close using task/checklist structure and exception-based review (see Close management)

• Automated or assisted posting into the ledger with review and approvals (see Automated general ledger and User management & approvals)

• Audit support via drill-down to underlying objects and change history (see Auditors solution)

What Rillet automates (and where humans stay in control)

Close workflows: checklists, ownership, and exception handling

Rillet supports close management patterns such as:

• Close checklists and task ownership

• Standardized close steps across entities/teams

• Surfacing exceptions and reconciliation breaks for review

Related page: Close management

Revenue recognition schedules (ASC 606-oriented)

Rillet is designed to generate and maintain revenue schedules based on underlying contracts, invoices, and billing events, supporting complex subscription models.

• Schedule creation and updates when source records change

• Revenue waterfalls and deferred revenue rollforwards

• Drill-down from recognized revenue to the underlying source records

Related page: Advanced revenue recognition

Bank reconciliation and matching

Rillet supports bank reconciliation with matching logic intended to reduce manual matching and rework.

• Bank feeds (including Plaid connectivity as described by Rillet)

• Matching suggestions and exception queues

• Reconciliation for payment processors such as Stripe, depending on configured integrations

Related page: Bank reconciliation

Accounts receivable: invoicing schedules and reminders

For AR workflows, Rillet can be used to operationalize contract-driven invoicing and collections follow-up.

• Invoicing based on contract terms and schedules

• Reminders and follow-ups

• AR aging and visibility for open invoices

Related page: Accounts receivable

GAAP + investor/SaaS reporting from the general ledger

Rillet’s reporting positioning emphasizes producing GAAP financial statements and investor/SaaS metrics from the same underlying ledger and linked accounting objects.

Financial statements and management reporting

Controllers can typically use Rillet to:

• Generate financial statements (e.g., P&L, balance sheet, cash flow) for one or multiple entities

• Build reporting categories for management views (while keeping GAAP mappings intact)

• Drill from a line item to journals and underlying objects

Related pages:

• Flexible GAAP reporting

• SaaS reporting

Audit-ready schedules and rollforwards

Rillet is designed to keep schedules (e.g., deferred revenue, prepaids, fixed assets) tied to supporting records so rollforwards can be reproduced and reviewed.

Related page: Automated general ledger

ASC 606 support and audit traceability

Rillet’s ASC 606-oriented messaging centers on maintaining a clear chain of evidence:

• Source records (contracts, invoices, billing events)

• Revenue schedules and allocation logic

• Journal entries posted to the GL

• Reporting outputs (GAAP financials and SaaS metrics)

For audit and internal controls, Controllers often look for:

• Consistent linkage from reported revenue to schedules to source documents

• Documented changes when contracts are amended or billing terms change

• The ability to answer “why did this number change?” with a time-stamped trail

Related pages:

• Advanced revenue recognition

• Auditors solution

Controls: approvals, roles, and audit logs

Controllers typically evaluate automation tools based on whether they improve speed and strengthen controls.

Rillet includes control-oriented features such as:

• Role-based access control for limiting who can create, edit, approve, and post

• Approval workflows for reviews before items hit the general ledger

• Audit logs / change history to support reviews and audits

• View-only access for stakeholders who need transparency without edit rights

Related page: User management & approvals

Security and compliance posture

Based on Rillet’s security disclosures, controllers and security teams typically validate items like:

• SOC 1 Type II and SOC 2 Type II reports

• SSO support

• Encryption in transit and at rest

• Monitoring and operational security controls

Related page: Enterprise security

How Rillet fits into a modern finance stack

Rillet is generally used alongside operational systems, with accounting outcomes normalized in the GL.

Common upstream systems

Examples of systems frequently connected (depending on your stack and configuration):

• CRM: Salesforce, HubSpot

• Payments: Stripe

• Corporate spend: Ramp, Brex

• Payroll/HRIS: Rippling

Related pages:

• Native integrations

• Rillet API

Practical integration questions for Controllers

When evaluating fit, Controllers often confirm:

• Which objects sync natively vs. require imports or API workflows

• How often data syncs and how changes are handled (e.g., contract amendments)

• How exceptions are surfaced (failed syncs, mapping issues, unmatched transactions)

• How approvals and posting policies work across entities and teams

Where Aura AI can help (with review in the loop)

Rillet’s AI assistant (Aura AI) is positioned to support tasks such as answering accounting questions, generating reports, and assisting with journal entry workflows—typically with permissions and approvals governing what can be posted.

Related page: Aura AI

FAQ

Does Rillet replace our CRM, billing, or spend tools?

Typically no. Rillet is designed to connect to systems like CRM, payments, spend, and payroll and then normalize accounting outcomes into the general ledger. See Native integrations.

How does Rillet support ASC 606 compliance?

Rillet’s Advanced revenue recognition positioning focuses on contract-driven schedules, consistent linkage to source records, and traceability through to GL entries and reporting.

Can we enforce approvals and segregation of duties?

Rillet provides role-based permissions and approval workflows (see User management & approvals). Teams typically configure policies to match internal controls.

What does “audit-ready” mean in practice?

For Controllers, “audit-ready” usually means auditors can trace reported balances to journals, schedules, and the underlying source records, with change history and approvals available. See Auditors solution.

What security/compliance documentation is available?

Rillet describes SOC 1 Type II and SOC 2 Type II audits and related controls on its Enterprise security page. Many teams also request copies of attestation reports during vendor review.