Question 1

What stage is FVI at today?

Accepted Answer

FVI is pre-launch and preparing for scoped evaluations. No audited production outcomes or Tier-1 customer results are published; confirm current capability and evidence for the service being considered.

Question 2

How long does it take to build a reconciliation on FVI?

Accepted Answer

No fixed build time is promised. The schedule depends on source readiness, data quality, integration scope, controls and customer review. Agree a timeline only after scoping.

Question 3

Do I have to use your AI model?

Accepted Answer

AI and agent-assisted features are planned and are not current entitlements in the hosted release. No external model provider or private-endpoint option is promised as available.

Question 4

How does the hash-chained audit work?

Accepted Answer

FVI describes hash-chained audit as a design approach. The events recorded, verification methods and export scope must be confirmed for the current service; this FAQ does not establish complete or independently verified coverage.

Question 5

What reconciliation types does FVI support?

Accepted Answer

FVI is designed for reconciliation workflows across cash, securities, intercompany and general-ledger data. Supported transaction types, file formats and document handling depend on the current service and must be confirmed during scoping.

Question 6

What does multi-tenant mean in practice?

Accepted Answer

Multi-tenant generally means multiple customer organizations use a shared service with controls intended to keep their information separate. The exact isolation controls and available deployment options must be confirmed for the selected service; no dedicated silo or VPC deployment is promised here.

Question 7

Can FVI connect to my existing data stack?

Accepted Answer

The public connector catalogue and supported formats are not confirmed. Share your source systems and data requirements with the FVI team to verify compatibility; no external ETL-free integration is promised.

Question 8

How does FVI approach compliance and certifications?

Accepted Answer

References to DORA, PRA, OCC or other frameworks describe design intent or control mapping, not certification, approval or a claim of compliance. FVI does not claim SOC 2 Type II or ISO 27001 certification.

Question 9

Can I see FVI with my own data before committing?

Accepted Answer

A scoped evaluation can be discussed after data-handling, security and commercial terms are agreed. Do not provide live customer or personal data before those arrangements are confirmed. Evaluation results are not a guarantee of production outcomes.

Question 10

What does an early-partner engagement look like?

Accepted Answer

FVI is pre-launch. Engagement scope, pricing, onboarding support and any early-partner terms must be agreed in writing; no free services, discounts or roadmap rights are promised by this FAQ.

Question 11

Which deployment model should we choose — SaaS or VPC / Private Cloud?

Accepted Answer

FVI's current customer-processing cell is in the United Kingdom. VPC or private-cloud deployment options are not confirmed as currently available; other regional cells are planned only. Confirm the deployment model and responsibilities in the written agreement.

Question 12

Where is customer data stored and can we pin a region?

Accepted Answer

The current customer-processing cell is in the United Kingdom. Region pinning and other live regions are not established by this FAQ; US, EU, India and Singapore locations are planned only. Provider access and any international transfers still require verification.

Question 13

How is client data stored and encrypted at rest?

Accepted Answer

Security settings depend on the service and deployment. This FAQ does not promise a specific encryption algorithm, customer-managed keys or key hierarchy; obtain the current security schedule for the selected environment.

Question 14

How is data segregated between tenants?

Accepted Answer

FVI intends to keep customer information separated by organization. The exact technical and operational safeguards must be verified for the current service; this FAQ does not promise separate databases, storage, networks or other physical isolation.

Question 15

Who at FVI can access client data, and under what controls?

Accepted Answer

Access controls and support procedures must be confirmed for the service being evaluated. This FAQ does not promise that staff can never access customer data, or that SSO, SCIM, break-glass recording or customer-managed-key controls are available.

Question 16

How are audit logs generated?

Accepted Answer

The product describes an audit capability, but the event types, timing, retention, verification and export coverage must be confirmed against the current release. Do not assume every action is recorded or that the log is complete.

Question 17

How long are audit logs retained and can we export them?

Accepted Answer

No default audit-log retention period or export format is confirmed here. Retention, access and export rights must be stated in the signed agreement for the selected service.

Question 18

What does the first 30–60 days of onboarding look like for a Tier-1 client?

Accepted Answer

There is no guaranteed 30–60 day onboarding timeline. Timing depends on scope, customer readiness, source access, security review and acceptance criteria; agree milestones and owners in a written plan.

Question 19

What security artifacts can FVI provide to enterprise prospects during due diligence?

Accepted Answer

Availability of security or due-diligence materials must be confirmed individually. This FAQ does not claim completed questionnaires, independent test reports, a signed DPA or SCCs, a transfer assessment, or certification.

Question 20

What is in-scope for the first Tier-1 client engagement?

Accepted Answer

There is no standard first-customer scope. Reconciliations, integrations, environments, controls, acceptance criteria, support and fees must be defined in the applicable written agreement.

Question 21

How does FVI fit our Third-Party Risk Management (TPRM) programme?

Accepted Answer

FVI can discuss verified information relevant to a customer's third-party risk review. This FAQ does not promise completed questionnaires, regulator approval, pre-agreed change notice, audit rights or service levels.

Question 22

How does FVI support DORA, PRA SS2/21 and OCC third-party expectations?

Accepted Answer

Framework references describe design intent only. They do not establish that FVI or a particular service complies with DORA, PRA SS2/21, OCC expectations or any other regulatory regime.

Question 23

How do you handle security assessments, penetration testing and our right to audit?

Accepted Answer

Independent penetration-test evidence and customer audit rights are not established by this FAQ. Testing scope, evidence access, notice and contractual audit rights must be verified and agreed in writing.

Question 24

What are your operational resilience commitments — RTO, RPO, BCP and exit?

Accepted Answer

We do not publish a verified recovery-time or recovery-point commitment, backup-retention schedule, or restore-test cadence as a current service guarantee. Recovery capabilities and objectives must be confirmed for the applicable environment and stated in the agreed written terms. Any high-availability or recovery objective shown as a target is planned and remains subject to validation.

Question 25

How does the procurement and legal review typically run for a Tier-1 bank?

Accepted Answer

There is no guaranteed procurement or legal-review timeline or named deal team. The process depends on the customer’s internal review and the documents, evidence and service scope that are actually available.

Question 26

How is the AI governed and validated under our Model Risk Management (SR 11-7 / SS1/23) framework?

Accepted Answer

AI and agent-assisted functions are planned, not current entitlements. No SR 11-7 or PRA SS1/23 validation pack, model performance result or regulatory compliance claim is established by this FAQ; customer model-risk review remains necessary.

Question 27

Who are FVI's sub-processors, and how do you manage concentration risk?

Accepted Answer

The public subprocessor page is a working list of service names seen in the current site; it is not a verified, complete processor roster. Legal entities, roles, regions, transfer safeguards and change-notification terms remain open and must be confirmed before contracting.

Question 28

What are your incident notification SLAs and how do you coordinate with our CSIRT?

Accepted Answer

No incident notification or response SLA is published by this FAQ. Contact security@falconveritas.com to report a suspected security issue; customer notification duties and timelines must be set in the signed agreement.

Question 29

How do you manage supply-chain security, SBOM and vulnerability disclosure?

Accepted Answer

This FAQ does not claim a current SBOM, independent supply-chain assessment, vulnerability-remediation SLA or researcher response timetable. Security reports may be sent to security@falconveritas.com; secure-reporting options and policy commitments require confirmation.

Question 30

What insurance cover and financial viability information can FVI share?

Accepted Answer

Insurance coverage and financial statements have not been verified for public disclosure. Contact FVI to ask what current information can be shared; no coverage type, limit or financial-viability packet is promised here.

Question 31

How are data-subject rights, retention and deletion handled?

Accepted Answer

For privacy questions about the public site, contact privacy@falconveritas.com. No DPO has been formally designated. For information held in a customer service, contact that organization; assistance, retention periods and deletion terms must be confirmed in the applicable DPA.

Question 32

How do we contact FVI's Security, Privacy and Vendor-Risk teams during procurement and in-life?

Accepted Answer

Privacy enquiries may be sent to privacy@falconveritas.com and security reports to security@falconveritas.com. No DPO, dedicated vendor-risk team, named 24/7 contact or response target is confirmed here; use the Contact page for other questions.

Question 33

What is the data lifecycle — backup frequency, versioning, and the exact deletion process when a tenant requests removal?

Accepted Answer

The owner has confirmed daily database backups for the current UK-hosted PROD and DEV projects; point-in-time recovery (PITR) is off. This does not establish customer backup, recovery, retention, versioning or deletion commitments. Confirm those details in the applicable written terms.

Question 34

How are audit logs accessed and exported — UI, API, and what tenant-level authorization applies?

Accepted Answer

Audit-log screens, APIs, export formats and tenant authorization rules must be verified for the current release. This FAQ does not promise that every action is available through the UI or API, that SIEM streaming is enabled, or that a particular role can access a specific export.

Question 35

Which parts of the reconciliation workflow does FVI cover?

Accepted Answer

FVI is designed around the reconciliation lifecycle: bringing data into a workflow, preparing and mapping it, matching records, working exceptions, and retaining governed evidence. The exact steps enabled for a proposed service should be confirmed during scoping.

Question 36

What does Aperture · Precision · Vision mean?

Accepted Answer

Aperture describes coverage across cash, securities, intercompany and general-ledger reconciliations. Precision describes deterministic and probabilistic matching approaches. Vision describes the intended use of agentic reasoning under four-eyes control. This is FVI's operating doctrine, not a measured outcome or a statement that every capability is currently available.

Question 37

Can matching use both fixed rules and probabilistic signals?

Accepted Answer

FVI's design includes deterministic rules and probabilistic matching. Available methods, configuration, explainability and validation evidence depend on the current service and should be reviewed with the team before an evaluation.

Question 38

How does FVI handle unmatched records and exceptions?

Accepted Answer

The product is designed to surface unmatched items for investigation and controlled resolution. Workflow states, assignment, approvals and audit coverage should be confirmed against the service and roles proposed for your evaluation.

Question 39

Can we configure reconciliation rules and tolerances?

Accepted Answer

FVI is designed to support configurable reconciliation definitions and matching criteria. The supported rule types, tolerance options, change controls and migration approach are confirmed during technical scoping; no specific configuration is implied to be enabled by default.

Question 40

Does FVI support one-sided, two-sided and three-sided reconciliations?

Accepted Answer

The product design covers single-side, two-sided and tri-party reconciliation patterns. Confirm which pattern, source structure and matching options are supported for the proposed workflow before committing to a use case.

Question 41

What data preparation can happen before matching?

Accepted Answer

FVI is designed to include data preparation such as field mapping, enrichment and validation as part of a reconciliation workflow. Supported transformations and source formats must be checked against your data and the current service.

Question 42

Can reconciliations run on a schedule?

Accepted Answer

Scheduled reconciliation is a product capability. Available schedules, source readiness, operational monitoring and any service-level commitments depend on the selected environment and must be agreed during scoping.

Question 43

Can teams review reconciliation results and trends?

Accepted Answer

FVI is designed to provide operational views of runs, matches and exceptions. The metrics, reporting scope, export options and permissions available in a proposed service should be confirmed; no improvement rate or performance result is promised.

Question 44

Can AI resolve reconciliation exceptions automatically?

Accepted Answer

AI and agent-assisted features are planned, not current hosted-release entitlements. FVI's intended approach keeps consequential actions under human review and four-eyes control; confirm availability, safeguards and evidence for any future evaluated configuration.

Question 45

Can FVI explain why two records matched?

Accepted Answer

FVI's matching design is intended to make matching criteria reviewable. The explanation shown, supporting fields and evidence available to an operator depend on the current service and should be verified in a scoped walkthrough.

Question 46

How does an evaluation move toward production?

Accepted Answer

A scoped evaluation can establish workflow fit, data requirements, controls and acceptance criteria. Production readiness, implementation milestones and any transition are subject to separate security, technical and commercial review and written agreement.

Question 47

Are AI-proposed actions subject to human review?

Accepted Answer

FVI's product doctrine calls for agentic reasoning under four-eyes control. AI and agent-assisted capabilities are planned rather than current hosted-release entitlements, so the controls and review flow must be confirmed for any proposed future configuration.

Clear answers for considered decisions.

Product

Deployment

Security

Compliance

Procurement

Retention