What’s new

A new API service is available in Premium Finance Lite that allows a manual sync to be triggered for updating IPFS GA (General Agent) data in the system for a specific merchant. This gives operators an on-demand alternative to waiting for the regularly scheduled cron job to run.

Why it matters

You can now trigger a GA sync programmatically at any time, making it easier to recover from data discrepancies or push updates immediately after a GA change in IPFS without waiting for the next scheduled run.

Adds manual GA sync button to the Admin Portal

What’s new

A new button has been added to the PF Lite feature page in the Admin Portal, allowing admins to trigger a manual GA sync directly from the UI at any time without waiting for the regular cron job.

Why it matters

Before this change, initiating a sync required either waiting for the scheduled job or triggering the API directly. Admins can now initiate a sync on demand from the portal without any technical intervention.

Introduces automated GA sync for Premium Finance Lite

What’s new

A new scheduled API service has been introduced that runs automatically at a configured time, retrieves all GAs from IPFS, and syncs them into the system for each relevant merchant. This replaces the need for manual intervention to keep GA data current on a routine basis.

Why it matters

GA data in the system now stays automatically up to date with IPFS on a scheduled basis, reducing the risk of stale GA records being used in quote creation and other downstream flows.

Adds GA search API by name

What’s new

A new API service allows callers to search for a General Agent by their unique name. This provides a targeted lookup mechanism for GA records without needing to retrieve the full list.

Why it matters

You can now look up a specific GA by name in a single API call, making it straightforward to integrate GA selection into quote creation flows or other workflows that require identifying a GA by name.

Integrates GA search into the quote creation UI

What’s new

A dropdown search field has been added to the quote creation flow in the UI, allowing users to find and select a General Agent to associate with a new quote. The field is powered by the GA search API and supports searching by GA name.

Why it matters

Before this change, there was no UI mechanism to associate a GA with a quote at creation time. Users can now search for and add a GA directly within the quote creation workflow without leaving the page.

Adds GA support to the Draft Quote JWT API

What’s new

The existing Draft Quote API has been updated to accept a GA object in the policy request body, enabling GA details to be included when creating a draft quote. The API for fetching quote details has also been updated to return the GA in the policy object.

Why it matters

Integrations that create draft quotes via the JWT API can now include GA information as part of the initial quote creation request, and retrieve it back when fetching quote details, without requiring a separate update step.

Changes

Maps GA object to quote creation UI fields

What’s new

The GA object returned from the API is now mapped to the corresponding UI text fields in the quote creation flow, enabling both adding and displaying a GA when creating or viewing a quote.

Why it matters

GA data entered or retrieved via the API is now consistently reflected in the quote creation UI, ensuring that what is stored in the system matches what the user sees and interacts with on screen.

Includes GA details in quote generation

What’s new

The existing quote creation flow has been updated to include GA details in the generated quote. When a GA is associated with a quote, that information is now carried through to the final quote output.

Why it matters

Before this change, GA information entered during quote creation was not reflected in the generated quote. GA details are now included end-to-end, from selection through to the final quote document.

Displays GA on saved policies in search results

What’s new

When a GA is added during quote creation, it is now mapped to the resulting policy and displayed when that policy is retrieved via the saved policy search. This ensures GA association is visible throughout the policy lifecycle, not just at quote time.

Why it matters

Before this change, a GA associated with a quote was not surfaced when searching saved policies, making it difficult to identify which GA was linked to a given policy. GA information is now consistently visible at both the quote and policy level.

UAT Release – GA Support to Premium Finance Lite (AN_GASPFL_V1)

Release Date: Mar 31, 2026

Release Status: Deployed to UAT

────────────────────────────────────────────

Create GA Manual Sync in Existing Premium Finance Lite [AN-46447]

An API service in premium finance lite to perform manual sync for updating IPFS GA in our system for a merchant.

Client Facing: No

────────────────────────────────────────────

Integrate Manual Sync API in Admin Portal [AN-46462]

UI to display a button on PF lite feature page to perform a manual sync at any time without waiting for regular Cron job.

Client Facing: Yes

────────────────────────────────────────────

Create Auto Sync for GA in Premium Finance Lite [AN-45696]

An API service which will execute on a given time and retrieve all GAs from IPFS and sync in our system for a specific merchant.

Client Facing: No

────────────────────────────────────────────

Create Get API for GA with Search by Name [AN-45749]

An API service which will be able to search a GA with its unique name.

Client Facing: No

────────────────────────────────────────────

Integrate Get GA Details to Fetch and Search GA [AN-46419]

UI to display a dropdown search option to find GA and add it in quote creation.

Client Facing: Yes

────────────────────────────────────────────

Add GA for Draft Quote in JWT API [AN-45768]

Update existing draft quote to support GA in the policy request for quote creation.

Client Facing: No

────────────────────────────────────────────

Return GA in the Draft JWT API [AN-46116]

Update existing API to fetch quote details for GA in policy object.

Client Facing: No

────────────────────────────────────────────

Integrate GA Object in Policy Details [AN-46394]

UI to map GA Object with UI text field for Add and get GA in quote creation.

Client Facing: Yes

────────────────────────────────────────────

Generate a Quote with GA Object [AN-46888]

Update existing quote creation to support GA details in the generated quote.

Client Facing: Yes

────────────────────────────────────────────

Search Saved Policies Should Show GA When Added [AN-47244]

The GA added while quote creation should be mapped to Policy and should be displayed when policy is searched.

Client Facing: Yes

The post UAT Release – GA Support to Premium Finance Lite (AN_GASPFL_V1) appeared first on AndDone.

What’s New

You can now create, read, update, and delete Coverage entities through the API. Additional actions include status updates, as well as lock and unlock controls to manage editability. The system also supports both manual and scheduled synchronization with external data sources to keep coverage data current.

Why It Matters

You no longer need separate workflows or tools to manage coverage data. You can now fully manage Coverage entities programmatically and keep them in sync automatically, reducing manual overhead and data inconsistencies.

Adds Full CRUD Support for Policy Entities

What’s New

The API now supports full lifecycle management for Policy entities, including create, read, update, and delete operations. It also introduces manual and scheduled synchronization with external policy data sources to ensure records remain up to date.

Why It Matters

You can now manage policies entirely through the API without relying on external processes. Automated sync ensures your policy data stays consistent across systems with minimal effort.

Introduces Admin Portal Data Sync Framework

What’s New

A new data synchronization framework is implemented in the Admin Portal UI. This enables direct interaction with backend entity APIs such as Program, Carrier, Coverage, General Agent, and Broker management.

Why It Matters

You can now trigger and manage data sync operations directly from the UI instead of relying solely on backend processes. This improves visibility and control over how data flows between systems.

Updates OpenAPI Specification Across All Modules

What’s New

The OpenAPI (Swagger) documentation is updated across all modules. This includes standardized naming, consolidated program definitions, improved version metadata, and support for manual sync endpoints.

Why It Matters

You now have a more consistent and accurate API contract. This makes integration easier, reduces ambiguity, and ensures your client applications align with the latest API behavior.

Enforces Required and Unique Alias for QuoteConfig

What’s New

The alias field in QuoteConfig is now mandatory for both create and update operations. The system enforces case-insensitive uniqueness, and requests with missing or duplicate values will fail with validation errors.

Why It Matters

You can rely on alias as a stable and unique identifier across configurations. This prevents duplication issues and improves consistency when referencing QuoteConfig records.

Upgrade

1. Ensure all create and update requests include a non-empty alias field.
2. Validate that the alias is unique (case-insensitive) before sending requests.
3. Update any existing records that may not meet the new requirement.

Enforces Required and Unique Alias for CommsConfig

What’s New

The alias field in CommsConfig is now required for all create and update operations. The API enforces case-insensitive uniqueness and rejects invalid or duplicate values with clear error responses.

Why It Matters

You can now depend on a consistent and unique identifier for communication configurations. This reduces ambiguity and prevents conflicts across records.

Upgrade

1. Update all create and update requests to include the alias field.
2. Ensure alias values are unique across all existing configurations.
3. Handle validation errors for missing or duplicate aliases in your integration logic.

Release Date: UAT Mar 26, 2026

Release Status: Deployed to Production

This release bundle primarily consists of premium finance development for the coverage, policy, and data sync between IPFS and anddone system using the admin portal.

PFTAD | Coverage Management (Entity API) [AN- 28221]

Introduced full CRUD support for Coverage entities (create, update, status update, lock/unlock, delete).
Added manual and scheduled (cron) sync with Datalink Coverages to keep coverage data up-to-date.

Client facing impact: No

PFTAD | Policy Management (Entity API) [AN-28221] Introduced full CRUD support for policy entities (create, read, update, and delete). Added manual and scheduled (cron) sync with Datalink policy to keep data up-to-date.

Client facing impact: No

PFTAD | Admin Portal – Data Sync [AN-38556]
Implemented front-end data sync framework for the Admin Portal
Enables UI integration with new entity-based APIs (Program, Carrier, Coverage, GA, Broker Management).

Client facing impact: Yes

Required PFTAD swagger update for all modules
Updated PFTAD Open API/Swagger specs across all modules, including PF4 → PFTAD renaming, consolidated program definition, added Manual Sync

Client facing impact: No

API, corrected naming, and standardized missing x- version metadata.

[CR] Quote Config – make alias unique and required
Enforced that alias in quote Config is now mandatory for both Create and Update APIs.
Added case-insensitive uniqueness validation for alias ; requests with missing alias return
MISSING_REQUIRED_FIELD and duplicate aliases return DULPICATE_ALIAS .

Client facing impact: No

[CR] CommsConfig – Make alias field required and unique
Enforced that alias in communication Config is now mandatory for both Create and Update APIs; requests without it return MISSING_REQUIRED_FIELD .
Implemented case‐insensitive uniqueness validation on alias ; if the value matches any existing alias , the API returns DUPLICATE_ALIAS .

Client facing impact: No

The post Production Release Notes – PFTAD (AN_PFTADN_V4) appeared first on AndDone.

• Release date: 2026-03-04
• Release status: Deployed to UAT
• Version: AN_PFTADN_V4

Highlights

• PFTAD | Coverage Management (Entity API) [AN-28221] – Full CRUD support for Coverage entities; manual and scheduled cron sync with Datalink Coverages.
• PFTAD | Policy Management (Entity API) [AN-28221] – Full CRUD support for policy entities; manual and scheduled sync with Datalink policy.
• PFTAD | Admin Portal – Data Sync [AN-38556] – Front-end data sync framework; UI integration with entity-based APIs (Program, Carrier, Coverage, GA, Broker Management).
• Required PFTAD swagger update for all modules – Updated OpenAPI/Swagger specs; PF4 → PFTAD renaming; standardized x-version metadata.
• [CR] Quote Config – make alias unique and required – alias in quoteConfig is now mandatory; case-insensitive uniqueness validation; MISSING_REQUIRED_FIELD and DUPLICATE_ALIAS error codes.
• [CR] CommsConfig – Make alias field required and unique – alias in communicationConfig is now mandatory; DUPLICATE_ALIAS returned on conflict.

References

• AN-28221
• AN-38556

The post UAT Release Notes – PFTAD (AN_PFTADN_V4) appeared first on AndDone.

What’s New

A new set of API services is now available for managing broker records within the system. Developers can sync, create, update, delete, and retrieve broker details through these endpoints. This forms the foundational data layer for broker management within the platform.

Why it Matters

You can now programmatically manage the full lifecycle of a broker record without manual intervention or workarounds. Teams building broker onboarding or management flows have a complete, consistent API surface to integrate against.

Introduces Admin UI Controls for Merchant IPFS Configuration and Permissions

What’s New

Admins can now configure merchant feature access and permissions directly from the onboarding page in the admin portal. This includes the ability to set up IPFS (Insurance Premium Finance Settings) configuration for a merchant through the UI, without requiring a backend intervention.

Why it Matters

Before this change, configuring merchant-level IPFS settings required non-UI intervention. Admins can now complete this configuration entirely from the onboarding flow, reducing setup time and dependency on engineering teams.

Adds Full CRUD Support for Communication Config Entities via API

What’s New

A new set of API services is now available for managing communication configuration records. Developers can create, update, delete, and retrieve communication details through these endpoints, enabling programmatic control over how communication settings are defined within the system.

Why it Matters

You can now manage communication configurations as first-class entities via API, making it straightforward to automate setup or integrate communication management into existing workflows.

Adds Full CRUD Support for GA Entities via API

What’s New

A new set of API services is now available for managing General Agent (GA) records. Developers can create, update, delete, and retrieve GA details through these endpoints, completing the core entity API layer for GA management.

Why it Matters

You can now manage GA records programmatically with the same API patterns used across other entities in the system, enabling consistent integration and automation across the platform.

Extends GET Carriers Endpoint With Additional Filter Parameters

What’s New

The GET multiple Carriers API now accepts additional filter parameters, allowing callers to narrow results by columns that were not previously searchable. This expands the query flexibility of the endpoint without breaking existing integrations.

Why it Matters

You can now search and filter carrier records more precisely in a single API call, reducing the need for client-side filtering of large result sets.

Standardizes Error Response Format Across Agent, Insured, Program, and Quote Config APIs

What’s New

Validation and exception handling across the Agent, Insured, Program, and QuoteConfig APIs have been updated to produce a consistent, standardized error response structure. Previously, error formats varied across these services, making it difficult to handle errors uniformly on the client side.

Why it Matters

Before this change, integrations had to account for inconsistent error shapes depending on which API returned the error. Error handling logic can now be written once and applied consistently across all four API surfaces, improving reliability and reducing integration complexity.

Verifies System Performance for Create and Get Insured on New Infrastructure

What’s New

Performance testing has been completed for the Create Insured and Get Insured endpoints running on the new PFTAD infrastructure. This validates that the system meets performance expectations under load before broader rollout.

Why it Matters

Teams integrating with these endpoints can proceed with confidence that the underlying infrastructure has been verified for performance, reducing the risk of unexpected latency or degradation in production.

Consolidates Default Program Handling into Program Sync and Removes Dedicated Endpoint

What’s New

The default program is now returned directly in the response to manual and cron job sync requests from IPFS, eliminating the need for a separate dedicated endpoint. The standalone default program API endpoint has been decommissioned as part of this change.

Why it Matters

Before this change, retrieving the default program required a separate API call to a dedicated endpoint. The default program is now included inline with sync responses, simplifying integration flows. Any existing calls to the standalone default program endpoint will need to be removed.

Upgrade

1. Remove any calls in your integration to the dedicated default program endpoint.
2. Update your sync response handler to read the default program from the IPFS sync response payload instead.

Migrates Monitoring From Lumigo to Dynatrace for the Premium Finance ECS Project

What’s New

The Transaction project within the Premium Finance ECS infrastructure has been migrated from Lumigo to Dynatrace for observability and monitoring. This is an internal infrastructure change with no impact on API behavior or response contracts.

Why it Matters

Operational monitoring and alerting for the Transaction project now runs through Dynatrace. Teams relying on Lumigo dashboards or alerts for this project should update their observability workflows accordingly.

────────────────────────────────────────────

Production Release Notes — PFTAD (AN_PFTADN_V3)Release Date: UAT Feb 9, 2026Release Status: Deployed to Prod

This release bundle primarily consists of premium finance development for the broker communication and GA along with merchant features and permissions.

────────────────────────────────────────────

PFTAD | Broker Management (Entity API) [AN-26446]

All API service to sync, create, update, delete, and retrieve details of the broker within the system.

Client Facing: No

────────────────────────────────────────────

PFTAD | Admin Portal – Merchant Features and Permissions [AN-30054]

Admin feature access and permission setting from UI for setting up merchant IPFS configuration from onboarding page.

Client Facing: Yes

────────────────────────────────────────────

PFTAD | Communication Config Management (Entity API) [AN-29019]

All API service to create, update, delete, and retrieve details of the Communication within the system.

Client Facing: Yes

────────────────────────────────────────────

PFTAD | GA Management (Entity API) [AN-28206]

All API service to create, update, delete, and retrieve details of the GA within the system.

Client Facing: Yes

────────────────────────────────────────────

[CR] Additional filter params to GET multiple [AN-40597]

Additional filter parameters added to the GET multiple Carriers API, so users can search on additional columns.

Client Facing: No

────────────────────────────────────────────

Standardize Error Code Format for Agent, Insured, Program, and QuoteConfig APIs [AN-39853]

Update all validation and exception handling layers to produce standardized error responses to improve debugging, integration consistency, and client-side error handling.

Client Facing: No

────────────────────────────────────────────

Performance Testing for Create and Get Insured [AN-38225]

Verify system performance on new infrastructure of PFTAD for create and get details of insured.

Client Facing: No

────────────────────────────────────────────

[CR] – Incorporate isDefault into Program sync and remove dedicated endpoint [AN-42014]

IPFS will send the default program in response to requests. Manual and cron job request.Decommission of default program API.

Client Facing: No

────────────────────────────────────────────

Migrate Monitoring from Lumigo to Dynatrace – PremiumFinance ECS Project [AN-38797]

Migrate the Transaction project from Lumigo to Dynatrace.

Client Facing: No

The post Production Release Notes — PFTAD (AN_PFTADN_V3) appeared first on AndDone.

What’s New

A new set of API services is now available for managing broker records within the system. Developers can sync, create, update, delete, and retrieve broker details through these endpoints. This forms the foundational data layer for broker management within the platform.

Why it Matters

You can now programmatically manage the full lifecycle of a broker record without manual intervention or workarounds. Teams building broker onboarding or management flows have a complete, consistent API surface to integrate against.

Introduces Admin UI Controls for Merchant IPFS Configuration and Permissions

What’s New

Admins can now configure merchant feature access and permissions directly from the onboarding page in the admin portal. This includes the ability to set up IPFS (Insurance Premium Finance Settings) configuration for a merchant through the UI, without requiring a backend intervention.

Why it Matters

Before this change, configuring merchant-level IPFS settings required non-UI intervention. Admins can now complete this configuration entirely from the onboarding flow, reducing setup time and dependency on engineering teams.

Adds Full CRUD Support For Communication Config Entities via API

What’s New

A new set of API services is now available for managing communication configuration records. Developers can create, update, delete, and retrieve communication details through these endpoints, enabling programmatic control over how communication settings are defined within the system.

Why it Matters

You can now manage communication configurations as first-class entities via API, making it straightforward to automate setup or integrate communication management into existing workflows.

Adds Full CRUD Support For GA Entities via API

What’s New

A new set of API services is now available for managing General Agent (GA) records. Developers can create, update, delete, and retrieve GA details through these endpoints, completing the core entity API layer for GA management.

Why it Matters

You can now manage GA records programmatically with the same API patterns used across other entities in the system, enabling consistent integration and automation across the platform.

Extends GET Carriers Endpoint With Additional Filter Parameters

What’s New

The GET multiple Carriers API now accepts additional filter parameters, allowing callers to narrow results by columns that were not previously searchable. This expands the query flexibility of the endpoint without breaking existing integrations.

Why it Matters

You can now search and filter carrier records more precisely in a single API call, reducing the need for client-side filtering of large result sets.

Standardizes Error Response Format Across Agent, Insured, Program, and QuoteConfig APIs

What’s New

Validation and exception handling across the Agent, Insured, Program, and QuoteConfig APIs have been updated to produce a consistent, standardized error response structure. Previously, error formats varied across these services, making it difficult to handle errors uniformly on the client side.

Why it Matters

Before this change, integrations had to account for inconsistent error shapes depending on which API returned the error. Error handling logic can now be written once and applied consistently across all four API surfaces, improving reliability and reducing integration complexity.

Verifies System Performance for Create and Get Insured on New Infrastructure

What’s New

Performance testing has been completed for the Create Insured and Get Insured endpoints running on the new PFTAD infrastructure. This validates that the system meets performance expectations under load before broader rollout.

Why it Matters

Teams integrating with these endpoints can proceed with confidence that the underlying infrastructure has been verified for performance, reducing the risk of unexpected latency or degradation in production.

Consolidates Default Program Handling into Program Sync and Removes Dedicated Endpoint

What’s New

The default program is now returned directly in the response to manual and cron job sync requests from IPFS, eliminating the need for a separate dedicated endpoint. The standalone default program API endpoint has been decommissioned as part of this change.

Why it Matters

Before this change, retrieving the default program required a separate API call to a dedicated endpoint. The default program is now included inline with sync responses, simplifying integration flows. Any existing calls to the standalone default program endpoint will need to be removed.

Upgrade

1. Remove any calls in your integration to the dedicated default program endpoint.
2. Update your sync response handler to read the default program from the IPFS sync response payload instead.

Migrates Monitoring from Lumigo to Dynatrace for the Premium Finance ECS Project

What’s New

The Transaction project within the Premium Finance ECS infrastructure has been migrated from Lumigo to Dynatrace for observability and monitoring. This is an internal infrastructure change with no impact on API behavior or response contracts.

Why it Matters

Operational monitoring and alerting for the Transaction project now runs through Dynatrace. Teams relying on Lumigo dashboards or alerts for this project should update their observability workflows accordingly.

UAT Release Notes – PFTAD (AN_PFTADN_V3)Release Date: UAT Jan 19, 2026 Release Status: Deployed to UAT

This release bundle primarily consists of premium finance development for the broker communication and GA along with merchant features and permissions.

────────────────────────────────────────────

PFTAD | Broker Management (Entity API) [AN-26446]

All API service to sync, create, update, delete, and retrieve details of the broker within the system.

Client Facing: No

────────────────────────────────────────────

PFTAD | Admin Portal – Merchant Features and Permissions [AN-30054]

Admin feature access and permission setting from UI for setting up merchant IPFS configuration from onboarding page.

Client Facing: Yes

────────────────────────────────────────────

PFTAD | Communication Config Management (Entity API) [AN-29019]

All API service to create, update, delete, and retrieve details of the Communication within the system.

Client Facing: Yes

────────────────────────────────────────────

PFTAD | GA Management (Entity API) [AN-28206]

All API service to create, update, delete, and retrieve details of the GA within the system.

Client Facing: Yes

────────────────────────────────────────────

[CR] Additional filter params to GET multiple [AN-40597]

Additional filter parameters added to the GET multiple Carriers API, so users can search on additional columns.

Client Facing: No

────────────────────────────────────────────

Standardize Error Code Format for Agent, Insured, Program, and QuoteConfig APIs [AN-39853]

Update all validation and exception handling layers to produce standardized error responses to improve debugging, integration consistency, and client-side error handling.

Client Facing: No

────────────────────────────────────────────

Performance Testing for Create and Get Insured [AN-38225]

Verify system performance on new infrastructure of PFTAD for create and get details of insured.

Client Facing: No

────────────────────────────────────────────

[CR] – Incorporate isDefault into Program sync and remove dedicated endpoint [AN-42014]

IPFS will send the default program in response to requests. Manual and cron job request.Decommission of default program API.

Client Facing: No

────────────────────────────────────────────

Migrate Monitoring from Lumigo to Dynatrace – PremiumFinance ECS Project [AN-38797]

Migrate the Transaction project from Lumigo to Dynatrace.

Client Facing: No

The post UAT Release Notes – PFTAD (AN_PFTADN_V3) appeared first on AndDone.

What’s new

A new PFA (Premium Finance Agreement) alias field has been introduced to the premium finance workflow. The alias name is stored in quote details at the time a new quote is created and is used to determine which PFA format to apply for a given merchant. The selected format controls where insured details are placed for e-signature and how merchant details are included in the agreement.

Why it matters

Before this change, the platform had no way to distinguish between different PFA formats on a per-merchant basis. You can now configure a PFA alias per merchant so that IPFS sends the correct agreement format for e-signature, ensuring the right fields are presented to the insured and merchant details are accurately reflected in the document.

Production Release Notes – PFA Alias (AN_PFALAS_V1)

Release Date: Jan 8, 2026

Release Status: Deployed to Production

The main component of this release bundle is premium finance development for the alias name, which would specify the kind of PFA IPFS would be sending for e-signature.

────────────────────────────────────────────

Premium Finance Workflow to Support Merchant Specific PFA [AN-38177]

• PFA format will determine where to e-sign insured details and add merchant details.
• PF alias will help to determine the type of PFA format.
• To store PF alias name in quote details in new quote.

Client Facing: Yes

The post Production Release Notes – PFA Alias (AN_PFALAS_V1) appeared first on AndDone.

• Release date: December 26, 2025
• Release status: Deployed to UAT
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 272–272

Highlights

• PFA [AN-3817]

References

• AN-3817
• AN_PFALAS_V1

Original release notes excerpt

UAT Release Notes – PFA Alias (AN_PFALAS_V1)
Release Date: UAT Dec 26, 2025
Release Status: Deployed to UAT
The main component of this release bundle is premium finance development for the alias name,
Which would specify the kind of PFA IPFS would be sending for e-signature,
Features Deployed Client
Facing
Impact
Premium Finance workflow to support Merchant Specific Yes,
PFA [AN-3817]
PFA format will determine where to e-sign insured details
and add merchant details
PF alias will help to determine the type of PFA format

Source: Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 272–272.

The post UAT Release Notes – PFA Alias (AN_PFALAS_V1) appeared first on AndDone.

• Release date: December 10, 2025
• Release status: Deployed to Production
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 164–165

Highlights

• PPFTAD Program Management (Entity API) [AN-28722] No
• PFTAD Quote Config Management (Entity API)[AN- No

References

• AN-28722
• AN_PFTADN_V2

Original release notes excerpt

Production Release Notes – PFTAD (AN_PFTADN.V2)
Release Date: Dec 10, 2025
Release Status: Deployed to Production
This release bundle primary consists of premium finance development fr the program, quote
cartier, and agent management.
Features Deployed Client
Facing
Impact
PPFTAD Program Management (Entity API) [AN-28722] No
All API services forthe program to be sync between IPFS
and the anddone system.
PFTAD Quote Config Management (Entity API)[AN- No
29008]

Source: Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 164–165.

The post Production Release Notes – PFTAD (AN_PFTADN.V2) appeared first on AndDone.

• Release date: December 10, 2025
• Release status: Deployed to Production
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 220–222

Highlights

• Program Sync (CRON) [AN-28723] No
• Get Programs (multiple) [AN- No

References

• AN-28723
• AN_PFTADN_V1

Original release notes excerpt

Production Release Notes – PFTAD (AN_PFTADN_V1)
Release Date: Dec 10, 2025
Release Status: Deployed to Production
Features Deployed Client Facing Impact
Program Sync (CRON) [AN-28723] No
An APL service which will run for
Programs to created, updated
and deleted by internal system
workflows
Get Programs (multiple) [AN- No
28728)

Source: Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 220–222.

The post Production Release Notes – PFTAD (AN_PFTADN_V1) appeared first on AndDone.

• Release date: November 25, 2025
• Release status: Deployed to UAT
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 273–274

Highlights

• PPFTAD Program Management (Entity API) [AN-28722] No
• PFTAD Quote Config Management (Entity API)[AN- No

References

• AN-28722
• AN_PFTADN_V2

Original release notes excerpt

UAT Release Notes – PFTAD (AN_PFTADN_V2)
Release Date: UAT Nov 25, 2025
Release Status: Deployed to UAT
This release bundle primary consists of premium finance development fr the program, quote
cartier, and agent Management
Features Deployed Client
Facing
Impact
PPFTAD Program Management (Entity API) [AN-28722] No
All API services forthe program to be sync between IPFS
and the anddone system.
PFTAD Quote Config Management (Entity API)[AN- No
29008]

Source: Compiled internal release notes PDF (ANDDONE-ALL RELEASE NOTES.pdf), pages 273–274.

The post UAT Release Notes – PFTAD (AN_PFTADN_V2) appeared first on AndDone.