Backoffice Insurance 8.1.1

October 28th, 2026

This release focuses on strengthening renewal automation, underwriting workflows, and payment management, helping insurers process policies more efficiently while reducing manual effort.

The release introduces enhanced support for recurring card payments, new visibility into unpaid invoices, and expanded underwriting capabilities through APIs that provide richer offer data and controlled decision overrides.

Additional improvements to policy renewals, offer evaluation, and pricing integrations deliver greater flexibility, transparency, and operational consistency across the insurance platform.

What's New

Recurring Card Payments on Renewal

Policy renewals now automatically carry over saved card payment tokens for recurring payments, eliminating the need for customers to re-enter their card details.

  • New policy renewals: Automatically adds and links the existing payment card when recurring payment is selected and the card remains valid past the first installment due date.
  • Same policy renewals: Seamlessly retains card payment information across policy versions.

New Unpaid Invoices Views

We’ve introduced dedicated views for unpaid invoices to make tracking and managing outstanding balances faster and simpler across your billing workflows.

  • Billing & Collection Menu: Quickly view all invoices with outstanding balances in a new dedicated Unpaid Invoices menu.

  • Customer Form: Access complete invoice history and open unpaid balances directly from the customer record.

Retrieve Quote Offer Data and Underwriting Evaluation Results (FTOS_QA_GetOfferData)

The FTOS_QA_GetOfferData endpoint allows client applications and portals to retrieve complete quote information, offer card configurations, pricing breakdowns, participant details, and rule-level underwriting outcomes across both Insurance and Banking product lines.

Key Capabilities

  • Flexible Identification: Retrieve quote and offer data using either the internal system identifier (offerId) or the business-facing quote reference number (offerNo).

  • Underwriting Formula Protection: To safeguard proprietary business logic and risk assessment formulas against reverse engineering, the API returns final evaluation outcomes by default while concealing internal calculation steps.

  • Selective Step Visibility (includeStepResult): Callers can request specific intermediate formula step outputs (such as evaluated underwriter competence thresholds) by supplying target step names, providing only the required operational data without exposing the broader underwriting formula structure.

Status Visibility & Lifecycle States

The endpoint exposes the evaluation status of offer cards and quotes across their lifecycle:

  • Proposed: The offer card is approved and available for customer review and binding.

  • Referred: The offer card requires manual review or derogation handling by an underwriter.

  • Declined: The offer card failed underwriting criteria and cannot be bound or accepted.

  • Version closed: An archived card iteration superseded by a subsequent underwriting decision.

Override Underwriting Decisions with Automated Card Versioning (FTOS_QA_OverwriteUWDecision)

Overview

The FTOS_QA_OverwriteUWDecision endpoint enables authorized underwriters to manually update automated underwriting evaluation decisions on referred offer cards, enabling quotes held for referral to progress toward approval. You can only send the cards that are in the referred status.

Key Capabilities

  • Audit Trail Integrity: Original automated rule results generated during initial evaluation remain permanently stored in the system for auditing and compliance tracking.

  • Mandatory Action Logging: Automatically logs the updated decision along with mandatory business justification and acting user identity directly on the decision record.

  • Automated Card Versioning: Manages offer card state changes by archiving the current card iteration and generating a new active version reflecting the applied override.

  • Inline Response Refresh (returnQuoteData): Supports returning either a standard execution confirmation or the fully updated quote payload in a single round trip.

Status Transitions

Offer Card Versioning & Status Changes

  • Eligibility: Overrides can only be executed on offer cards currently in Referred status. Offer cards in Declined status cannot be overridden.

  • Card Lifecycle:

    • Original Card Version: Referred ➔ Version closed

    • New Card Version Generated:

      • ➔ Proposed: If all underwriting decisions for the card evaluate to Approved.

      • ➔ Referred: If one or more criteria remain under Manual analysis.

      • ➔ Declined: If at least one underwriting decision is Rejected.

Quote-Level Status Transitions

Applying manual overrides updates the overarching quote status based on the collective outcome of its active offer cards:

Previous Quote Status Condition / Trigger Resulting Quote Status Impact / Next Action
Locked by UW At least one offer card transitions to Proposed Offers Submitted Customer can view and bind the proposed offer.
Locked by UW All active offer cards evaluate to Declined Declined by UW Quote processing concludes; no binding allowed.
Locked by UW One or more cards remain Referred (none Proposed) Locked by UW Quote remains held pending remaining underwriting reviews.

 

Policy Renewal Process Enhancements

The policy renewal process has been updated to align with the latest data model and integrate asynchronous processing, improving overall system performance and streamlining quote and policy generation.

  • Expanded policy renewals: Renew existing policies or generate new replacement policies, with automatic mandate creation when direct debit is selected.

  • Asynchronous job processing: Background jobs for policy renewals, master policies, and quote approvals now run asynchronously for faster, more reliable execution.

  • Updated renewal APIs: Upgraded ftos_qa_registerrenewalquote and FTOS_QA_ClientDecisionRenewal to support the new data model and the latest policy generation framework.

Bindable Offers API Response Updates

The FTOS_QA_GetBindableOffersEvaluation API has been updated to provide clearer underwriting details and support partial pricing when evaluating bindable offers.

  • Card-specific decisions: Underwriting decisions (instancesCardsDecisions) now include the corresponding card name (cardName) for easier identification.

  • Pricing for eligible cards: If underwriting is declined for a specific card, pricing details are still returned for the cards that passed or require manual analysis.

  • Simplified response structure: Removed redundant overall underwriting fields to streamline the API payload.

Automated Transaction Context for Pricing

When calculating premiums or evaluating underwriting rules during new quotes, alterations, renewals, or cancellations, policy workflows now automatically pass transaction context to Product Factory:

  • transactionType: Sent during quote generation, mid-term adjustments, renewals, or cancellations (NewBusiness, MTA, Renewal, Cancelation).

  • mtaTypes: Sent during mid-term adjustments (MTA) as an array of the specific alteration types applied to the policy.