Rillet is an accounting operations layer that connects transactional systems to your close process, so reconciliations, schedules, journal entries, and reporting are produced from the same source data—with review controls and a complete audit trail.

Who this is for

• Staff & senior accountants: reduce manual tie-outs, rollforwards, and repetitive JE prep.

• AR owners: reconcile cash application, payouts, and deferred revenue inputs with fewer spreadsheets.

• AP owners: streamline accruals, prepaid/amortization schedules, and vendor-related reconciliations.

What Rillet automates (without losing control)

Automated reconciliations

Rillet continuously pulls activity from connected systems and organizes it into reconciliation-ready datasets.

Typical use cases:

• Bank and cash reconciliations: match bank activity to settlements, deposits, and transfers.

• Stripe payouts and fees: tie payouts to underlying charges, refunds, disputes, and fees.

• Card spend and reimbursements: reconcile Ramp/Brex activity to GL mapping and policy categories.

• Payroll and benefits: reconcile totals and liabilities from Rippling and related providers.

Schedules and rollforwards

Maintain supporting schedules that update as source data changes.

Examples:

• Prepaids and amortization: build schedules from AP/card transactions and generate period amortization entries.

• Accruals: create repeatable accrual logic tied to source activity (e.g., usage, services, or payroll periods).

• Deferred revenue support: support inputs from billing/collections data (e.g., Stripe) and CRM signals.

Journal entry creation (with approvals)

Rillet can propose or generate journal entries based on the reconciled data and schedule outputs.

Controls built in:

• Approval workflows (prepare → review → post)

• Role-based permissions

• Locked periods and change controls

• Audit trail showing data sources, calculations, and edits

Reporting and close-ready outputs

Because reconciliations and schedules are driven from the same underlying data, reporting can be produced with fewer manual steps.

Outputs commonly supported:

• Close packages and variance support

• Reconciliation summaries by account

• Source-to-GL tie-out documentation for auditors

Integrations (common accounting data sources)

Rillet is designed to connect to the systems where accounting evidence already lives.

Common integrations include:

• Payments and billing: Stripe

• CRM / revenue signals: Salesforce, HubSpot

• Spend management: Ramp, Brex

• HRIS / payroll: Rippling

• Banks: major bank connections for statement/transaction data

(Exact availability can depend on your environment and configuration.)

How the workflow typically looks

1. Connect sources (e.g., Stripe + bank + Ramp/Brex + Rippling + CRM)

2. Map and classify transactions and events to the appropriate accounts and dimensions

3. Auto-match and reconcile (with clear exception queues)

4. Generate schedules and journal entries

5. Route for approvals and post using your team’s controls

6. Export close support for reporting and audit requests

Practical examples

Example 1: Stripe payout reconciliation

• Import Stripe charges, refunds, disputes, fees, and payout events

• Tie each payout to the underlying activity

• Identify unmatched items (e.g., timing differences, reversals, chargebacks)

• Produce a monthly reconciliation summary and suggested JE(s) for fees or clearing accounts

Example 2: Ramp/Brex spend to GL support

• Pull card transactions and metadata

• Apply account mappings and policy categories

• Flag missing documentation or unclear classifications

• Produce an accrual/prepaid schedule and amortization JE proposal

Example 3: Payroll liability reconciliation (Rippling)

• Pull payroll totals and related liabilities

• Reconcile bank outflows to payroll runs and tax/benefit payments

• Generate recurring JE templates tied to payroll periods, with review steps

Controls, approvals, and audit readiness

Rillet is built to reduce manual work while preserving accounting oversight.

Typical controls include:

• Preparation vs. approval separation

• Evidence linking (what data drove the number)

• Version history for reconciliations, schedules, and entries

• Exception handling workflow (investigate, annotate, resolve)

• Consistent outputs for auditors and internal reviews

FAQs

Can we require approvals for AI-posted journal entries?

Yes. Teams can configure workflows so entries are drafted or proposed first, then require review and approval before posting. Permissions, locked periods, and an audit trail help ensure appropriate control.

How does bank rec auto-match work?

Bank transactions are matched using common reconciliation signals such as amount, date windows, descriptions, and known counterparties/merchant patterns. Matching logic can be tuned to your environment, and Rillet surfaces match confidence and supporting detail so reviewers can verify.

How are exceptions handled (unmatched or suspicious items)?

Unmatched items are placed into an exception queue with context from connected systems. Accountants can investigate, add notes, adjust mappings, split/merge matches when appropriate, and resolve items with documentation. Resolutions are tracked in the audit trail.

What does implementation look like and how long does it take?

Implementation typically includes connecting data sources, configuring mappings and workflows, and validating outputs against prior closes. Timeline depends on the number of integrations and complexity, but many teams can reach a first close-ready setup in weeks, not months.

What does Rillet replace vs. keep (e.g., Bill.com, Ramp)?

Rillet generally does not replace operational tools used to run payables or spend (e.g., Bill.com, Ramp, Brex). Instead, it connects to them to automate the accounting layer—reconciliations, schedules, journal entry preparation, approvals, and close support—while you keep the systems your teams already use for execution.