Console overview

The Definite console lives at app.usedefinite.com. Navigation is one flat, role-gated list: anything your role cannot use is not rendered. Settings are reached from the account menu rather than the sidebar.

Overview

The Overview page shows the current period's metrics and open review work — for example missing cost postings, unmatched transactions, margin exceptions, and proposed backfills — with each row deep-linking to the queue or workpaper section that resolves it. A close-progress strip tracks how far the period has moved, from expected records through to journals your team has posted in your own systems and exact matches Definite has verified.

Reconciliation workspace

Each reconciliation opens a workspace with tabs for the workbook, matches, reconciling items, evidence, drafts, and approval.

• Workbook. A spreadsheet surface whose bound cells are rebuilt from Definite state on every load. Definite owns every result shown; the grid is an interaction surface, not a source of truth. Cells that are not bound to Definite state are flagged as such. A review panel resolves the selected cell against live Definite payloads — never against grid contents — and exposes match decisions, item reviews, evidence, and agent rationale.
• Matches. Accept or reject match candidates between bank and ledger transactions, with the difference shown per candidate. Decisions use optimistic concurrency, so two reviewers cannot silently overwrite each other.
• Reconciling items and draft adjustments. Agent-drafted adjustments stay drafts: Definite drafts adjustment packages but never posts them to any source system.
• Ask Definite. A question-answering assistant scoped to the reconciliation. Its answers are drafts for a human reader; it does not emit verdicts or change any result.
• Approval and exports. Submit and approve the reconciliation and export its artifacts.

Reconciliation Controls

The controls surface is the independent testing side: every deterministic control with its conclusion, period, population, and review state. Conclusions come from the rules engine, never from the preparer. A control run's workpaper shows per-attribute results as independently computed versus stated values with the delta, the rule ID, version, and citation behind each result, a receipt-verification badge, and findings a reviewer responds to in place.

Exceptions, Approvals, and Evidence queues

The three queues share one anatomy: a metric strip, a filterable table, and a row drawer with the record's evidence and a deep link into the workpaper section that resolves it. No queue row dead-ends, and no queue row mutates anything — resolution and approval are workpaper actions.

An evidence record opens into a workspace showing the reconciliation equation, per-source freshness (current, delayed, or missing), and an ordered lineage trace from source nodes through transforms to the result. Each source node carries its locator (sheet, cell, row, field, or page), observation time, and snapshot hash, plus a link to the source replica. The result carries a proof badge indicating whether its cryptographic proof verified.

Data and Mappings

Data has three tabs. Sources is the connector catalog for read-only connections to your systems. Map renders the connected estate as a graph. Tables browses the compiled tables with profile summaries and confidence labels.

Mappings shows the compilation graph that binds source documents and tables to finance concepts, one binding per source document. Corrections go through an override drawer with reason codes, and mapping analyses export matched and unmatched records with an integrity hash header.

Workflows and runs

Workflow programs (for example a regulatory report program) are configured under Workflows, where you create a program, bind its definitions, and start runs. A run's detail page shows its immutable stage events. Agent stages carry provenance; only the deterministic check stage produces verdicts.

Controls-testing workspaces

For engagements that test documented controls, Definite provisions a dedicated workspace profile with four surfaces: a Controls inventory with lifecycle status, Control Testing, Evidence, and Workpapers.

Control Testing is document-driven: upload the control description and test steps, and the tested attributes are parsed from the test-steps document rather than assumed. Choose a sampling method and size — sampling is seeded and reproducible for the reporting period — then upload per-sample evidence. The run reconciles population completeness before sampling, evaluates every attribute deterministically, and reports an overall conclusion where incomplete evidence takes precedence over failures. Exceptions and CANNOT_VERIFY items route to a human review queue; uploading more evidence never changes a conclusion by itself — the run must be executed again so the engine re-evaluates fail-closed.

The evidence index shows one row per sampled item and opens a lineage viewer that reconstructs the evidence document's pages, tints every tested line, and shows each input's source chain, raw and normalized values, the deterministic test with per-step outcomes, and the verdict. Workpapers lists run artifacts with SHA-256 digests, downloadable workpapers, and evidence packs.

This profile is enabled per workspace; ask your Definite contact if your engagement needs it.

Accounts, onboarding, and settings

• Sign-up (/signup) creates an organization with email verification; workspace provisioning is asynchronous, and the console shows a provisioning screen until the tenant is ready. Invited teammates join through invite links with admin or viewer roles.
• Onboarding is a five-step wizard: institution, entity and period, reports, definitions, and review. Definitions are versioned — Definite Standard or your private definitions set.
• Settings covers appearance, account, password, two-factor authentication, notifications, and API keys. Raw API keys are shown only once at creation. Admins also manage Decision Streams and Audit Exports destinations from Settings, and members and invites from organization settings.

Enterprise SSO (SAML) and SCIM provisioning are available for tenants that need identity-provider-managed access.