Cadres Keystone

Finance and CRM tied to product truth.

Keystone is the Cadres finance and CRM product. It covers the full stack: pipeline and deal management, self-serve billing with Stripe handoff that keeps contract authority in Keystone, invoicing with GL posting, a close engine that runs nine sequential accounting steps and posts adjusting entries, three-way PO matching, bank reconciliation, multi-entity consolidated statements with intercompany eliminations, quarterly tax estimates from GL data, and an annual reporting package. Built for teams that want product truth, customer truth, and financial truth to share one ledger instead of syncing across separate tools.

CRM Billing Invoicing Close engine Bank reconciliation Three-way matching Multi-entity Tax filing

Keystone Scope

Finance and CRM that share one ledger from first deal to year-end close.

CRM with finance-native context

Pipeline covers prospect through closed-won with product-scoped deals, stage automation that queues follow-up work on advance, and a forecasting report with win/loss trends and weighted pipeline. Activity queues surface fit-and-intent scoring with ranked worklists and a next-best-action per row — eligibility is guidance only, with finance-blocked rows disabled at the CTA rather than hidden. The customer workspace shows every product subscription with sold-contract details. Deal conversion creates the subscription and emits product_contract.changed. Explainable duplicate detection blocks creation on exact billing-email matches or same normalized name with matching domain. Churn risk alerts dispatch via notification and comms engine when daily health scoring crosses the threshold — only newly deteriorated customers trigger alerts, not ones already flagged.

Billing without authority scatter

First Portal login auto-provisions a customer record and trial subscription — no manual setup. Plans carry a shared_plan_key, readiness flags (billing_ready + product_ready = is_sellable), and billable dimensions. Every subscription creates a versioned sold-contract foundation. Plan changes create a durable contract_change_request before any mutation — auto-approved changes apply immediately; approval-exception policies leave the request in pending_approval rather than guessing. Stripe is integrated but downstream products do not receive Stripe credentials, price IDs, or subscription authority: they use a product-authenticated hosted handoff endpoint and Keystone resolves the checkout session, validates return URL allowlists, and reconciles via webhooks. Revenue recognition performance obligations are seeded automatically from sold-contract line items.

Close engine that does accounting work

The close engine executes nine sequential steps in a single database transaction: posting integrity check (debits equal credits on every entry), depreciation run, recurring accrual posting, FX revaluation, monthly tax provision, deferred tax computation and posting (depreciation timing, bad debt allowance, deferred revenue, prepaid differences → DTA/DTL adjusting entries), prepaid amortization, bad debt estimation (aging-bucket expected credit losses against Allowance for Doubtful Accounts), financial statement snapshot, and material variance check with per-category evidence. A step failure sets status to blocked and requires an override reason plus approver audit record. Three-way PO matching (PO → goods receipt → bill) validates quantities and prices against configurable tolerance thresholds, with exception escalation levels and SoD: the bill creator cannot approve match exceptions on their own bill.

Reporting from a real ledger

Financial statements cover trial balance, P&L with compare-period option, balance sheet (with synthetic current-year net income equity line before year-end close), cash flow (indirect method), AR and AP aging, and cash position. Multi-entity consolidation aggregates across an entity hierarchy with intercompany elimination entries. The annual reporting package generates on demand: trial balance, income statement, balance sheet, deduction schedule, depreciation schedule, tax payment ledger, 1099-NEC candidates, and K-1 summaries. A filing readiness checklist validates approximately 19 standard obligations, tax table freshness, all fiscal periods closed, and 1099 vendor review before flagging the package as ready to file. Quarterly tax estimates compute from live GL data through bracket tables with entity-type-aware breakdown.

Why Teams Start Here

Keystone answers the financial questions that matter before and after a period ends.

01

What did we actually earn this period?

The close engine runs nine sequential steps and posts adjusting entries — depreciation, accruals, FX revaluation, tax provision, deferred tax adjustments, bad debt estimation — before snapshotting statements. A blocked run with a variance or integrity failure requires an explicit override reason and records the approver. Financial statements come from the GL, not a manual spreadsheet layer.

02

How does a new customer become revenue?

First Portal login auto-provisions a customer and trial subscription. Deal conversion in CRM creates the subscription and emits product_contract.changed to downstream products. Sending an invoice posts to the GL immediately. Deferred revenue schedules track recognition over the service period. The customer workspace shows every product contract with sold-contract details alongside open AR and credit balances in one surface.

03

Are we ready to file?

The filing readiness checklist validates approximately 19 standard obligations, tax table freshness, all fiscal periods closed, and 1099 vendor review — including flagging vendors missing W-9 or ineligible due to entity type. Quarterly tax estimates compute from live GL revenue and expense data through bracket tables. The annual package generates on demand: trial balance, income statement, balance sheet, deduction schedule, depreciation schedule, tax payment ledger, 1099 candidates, and K-1 summaries.

Evaluation

Evaluate Keystone when you want finance, CRM, and billing to share one ledger instead of syncing across three.

Keystone stands on its own as a finance and CRM system. It pairs naturally with Portal and Meridian when identity-linked billing, access governance, and audit evidence need to share the same commercial truth.