Pulse
Product

A controlled path from source data to board-ready evidence.

FinQ Pulse brings Excel ingestion, portfolio analytics, stress-scenario computation, multi-role approval and PDF reporting into one auditable workflow for risk and finance teams.

Request a demoSee the workflow
01
UploadExcel workbook
→
02
ValidateSheets, rows, issues
→
03
ScenarioPortfolio and ratio impacts
→
04
ApproveAnalyst → CRO
→
05
ReportApproved PDF
01 · DATA INTAKE

Start with the workbooks your team already uses.

FinQ Pulse accepts Excel workbooks, stores the original file in tenant-scoped object storage and creates a SHA-256 fingerprint for integrity and idempotency.

  • Reads all workbook sheets and records detected sheet names
  • Calculates per-sheet and total row counts
  • Separates unreadable or invalid files from retryable processing failures
  • Encrypts parsed upload data before database storage
[SCREENSHOT: upload flow]Replace with the production upload and validation screen.
02 · SCENARIO BUILDER

Connect stress assumptions to portfolio and regulatory metrics.

The workbench combines uploaded portfolio and regulatory data with configurable macro and operational-risk inputs.

Stress inputsExchange rate, local and USD rates, inflation, growth, sanctions exposure and probability, ESG exposure and severity, and operational-risk rows.
Calculated viewsCAR, Tier 1, CET1, leverage, LCR, NSFR, NPL, coverage, NIM, ROA, ROE and cost of risk where source data is available.
Portfolio analysisLoans, deposits, securities, capital, liquidity and income sheets are identified by name and column structure.
ProvenanceScenario runs record engine version plus deterministic SHA-256 input and output hashes.
[SCREENSHOT: scenario builder]Replace with the macro inputs, ratios and portfolio charts screen.
03 · APPROVAL GOVERNANCE

Make review responsibilities explicit.

The workflow state machine separates scenario creation, risk review and executive approval.

  • Analyst creates and submits the scenario
  • Risk manager approves or returns it with a required comment
  • CRO provides final approval or returns it for revision
  • Creators cannot approve their own scenarios
  • Returned scenarios increment their version number
  • CRO-approved scenarios are locked against editing
A
ANALYSTBuild and submit
Submitted
RM
RISK MANAGERReview and challenge
Approved
CRO
CHIEF RISK OFFICERFinal decision
Locked
Every transition is written to workflow history and the central audit log.
04 · REPORTING

Generate reports from an approved, immutable snapshot.

PDF generation is restricted to CRO-approved or archived scenarios. Each report is tied to a workflow state, scenario version, methodology version, template version and content checksum.

  • Branded A4 PDF with KPI cards, ratio tables, charts and scenario metrics
  • Deterministic output for the same approved snapshot
  • Versioned report records and SHA-256 content hashes
  • Cyrillic-capable embedded report fonts for regional bank teams
FinQ PulseSTRESS TEST REPORT
[SCREENSHOT: generated PDF report]
Approved scenario snapshot · Versioned output
Security and compliance

Controls embedded below the user interface.

The product combines application-layer encryption, database isolation and governed access with AWS application infrastructure selected in Frankfurt.

TOTP MFA

Privileged roles require MFA setup; tenant policy can require MFA for all users.

Fernet encryption

Parsed uploads, computed outputs and MFA secrets are encrypted at field level with key-rotation support.

PostgreSQL RLS

Tenant-owned tables use forced row-level security tied to request-scoped tenant context.

Audit history

Security and workflow events retain actor, resource, access and correlation context.

View the security architecture
Demo and pilot phase

Bring a real workflow to the conversation.

We are working with selected banks to evaluate FinQ Pulse against practical stress-testing and governance requirements.

Request a demo