Skip to content

Guides

Decision review

Review findings, record verification outcomes, and retain an audit trail.

  • Guides
  • 1 min read

Scope

This guide covers the reviewer path once a case is ready_for_review: inspect findings, request remediation, and record an outcome. Prerequisites: Verification workflows and Document processing.

Load a case for review

const detail = await client.cases.get(caseId, {
  include: ['documents', 'findings', 'review', 'history'],
})

Reviewers should treat findings as the primary evidence summary and history as the append-only trail of prior actions.

Record an outcome

await client.cases.review(caseId, {
  outcome: 'verified',
  notes: 'Income documents consistent for stated employment period',
})

Typical outcomes (tenant-configurable) include verified, partially_verified, needs_remediation, and rejected. The product records actor, timestamp, and notes for each review action.

Request remediation

await client.cases.review(caseId, {
  outcome: 'needs_remediation',
  notes: 'Most recent pay stub missing; re-request from applicant',
  remediation: {
    requiredDocuments: ['pay_stub'],
  },
})

Remediation returns the case to an intake-capable state after the requested evidence is attached and processing succeeds again.

Auditability expectations

  • Review actions are append-only; they are not silently overwritten
  • Prior findings remain available for comparison after re-processing
  • Exports for audit use the case history API (see API overview)

FinCheckers does not claim external compliance certifications in this documentation. Auditability refers to product-retained history and actor attribution.

Related