FinCheckers

Roadmap

Product direction for FinCheckers — current focus, near-term themes, future evolution, and recently shipped releases. Not a delivery calendar.

The Roadmap explains where FinCheckers is heading as a financial verification platform.

It is directional — not a project board, backlog, or delivery calendar. Dates and contractual commitments are not published here.

Product vision

FinCheckers aims to be the system of record for verification work — cases, documents, findings, and decision review — with auditability that stands up to operational scrutiny.

Longer term, the product should make verification policy, explainable decisions, and governance durable across operators, integrations, and regulated environments — without absorbing lending underwriting or credit decisioning.

Product page

Current focus

Areas of present investment. Details live in Documentation and Resources — not in this list.

Current focus

Verification lifecycle

Improving how cases move from intake through findings and decision capture with clearer status and ownership.

Related guide

Current focus

Document processing

Tightening attachment handling, extraction review, and evidence linkage on verification cases.

Related guide

Current focus

Decision review

Strengthening how reviewers revisit recommendations with structured rationale and evidence references.

Related guide

Current focus

Operational reporting

Clearer visibility into queue health, SLA signals, and audit-oriented operational summaries for supervisors.

Implementation guide

Near-term direction

Themes labelled planned, in progress, or under consideration. No delivery dates.

In progressIn progress

In progress — Workflow enhancements

More consistent stage rules, assignment patterns, and exception handling for production verification teams.

Workflows guide

PlannedPlanned

Planned — Integrations

Broader API and callback patterns for case lifecycle events consumed by adjacent systems — no delivery date.

API overview

In progressIn progress

In progress — Review automation support

Better tooling around recommendation surfacing and review queues without replacing human decision authority.

Decision review

Under considerationUnder consideration

Under consideration — Reporting depth

Whether operational reporting needs dedicated surfaces beyond filtered case lists and audit exports.

Architecture

PlannedPlanned

Planned — Scalability hardening

Capacity and tenancy guidance for larger document volumes and concurrent review workloads.

Deployment checklist

Under considerationUnder consideration

Under consideration — Packaging clarity

Publishing clearer commercial packaging once terms are finalized — amounts remain placeholders today.

Pricing

Future evolution

Longer-term strategic themes. Not promises, contracts, or a release calendar.

Future

AI-assisted verification

Assistance for extraction, finding prioritisation, and review triage — with human decision ownership retained.

Architecture

Future

Knowledge-driven verification

Richer policy and knowledge context attached to findings so operators share a durable reference model.

Concepts

Future

Advanced governance

Stronger controls for approvals, segregation of duties, and regulated review workflows.

Product

Future

Multi-organisation capabilities

Clearer support for institutions that operate multiple business lines or legal entities under shared verification standards.

Product overview

Future

Explainability depth

Richer decision narratives and evidence trails so outcomes remain revisitable under audit.

Decision review

Recently shipped

Latest published entries from the Release Notes collection.

Release Notes

v0.3.0

Decision review APIs, remediation flows, and documentation catalog expansion.

July 10, 2026Read

Release Notes

v0.2.0

Document processing, findings includes, and formal case status transitions.

June 15, 2026Read

Release Notes

v0.1.0

Initial public API surface for verification cases, authentication, and document intake.

May 15, 2026Read

All release notes

Frequently asked questions

Roadmap process questions. Support policies are not published here.

How often is the roadmap updated?

The public roadmap is updated when direction changes meaningfully. It is not synchronized to an internal sprint cadence.

Can priorities change?

Yes. Themes labelled planned, in progress, or under consideration can shift as operator needs and platform durability evolve. This page does not guarantee sequencing.

How is feedback handled?

Use Contact to send product feedback. Mention your organisation context and the workflow area (cases, documents, review, reporting, or integrations).

Are near-term items guaranteed?

No. Labels describe directional themes — not committed delivery dates or contractual scope.

Where are completed changes published?

Published releases are listed under Release Notes and summarised in Recently shipped on this page.