• Release date: April 17, 2026
• Release status: Deployed to UAT
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 291–291

References

• AN-25194
• AN_ALMGMT_V4

Original release notes excerpt

UAT Release Notes – Ally Management (AN_ALMGMT_V4)
UAT Release: Ally Management (AN.ALMGMT.V4)
Release Date: UAT APR 17,2025
Release Status: Deployed to UAT
With this version of release, Ally Payout APIS and webhooks will be delivered that are key for
Ales to be able to payout the required amounts to their sub-merchants
Features Deployed to Production Client Facing Impact
AndDone Aly Ver 1 Payouts (AN-25194) ves
Following capabilities are included into ths epic
Allys able to make payouts to thelr sub merchants using the
secure payouts api
Allis able to receive updates after subscribing to the
PAYOUT webhook module

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

The post UAT Release Notes – Ally Management (AN_ALMGMT_V4) appeared first on AndDone.

• Release date: April 07, 2026
• Release status: Deployed to UAT
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 288–290

Highlights

• Alles can submit payments on behalf oftheir sub merchants

References

• AN_ALMGMT_V3

Original release notes excerpt

UAT Release Notes – Ally Management (AN_ALMGMT_V3)
UAT Release: Ally Management (AN.ALMGMT.V3)
Release Date: UAT APR 07,2025
Release Status: Deployed to UAT
With this version of release, All the Ally changes required for IPFS Total pay migration will be
released to UAT enabling IPFS to perform an integration testing with AndDone environment.
Features Deployed to Production Client Facing Impact
AndDone Ally Ver1 Secure Payment APIs Changes (AN- YES
25193)
« Alles can submit payments on behalf oftheir sub merchants
For an Ally to submit @ payment, he would need an API key (
associated with Ally user) and a APP key (associated with
the sub-merchan)
This epic encompasses all the changes to be made tothe

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

The post UAT Release Notes – Ally Management (AN_ALMGMT_V3) appeared first on AndDone.

Release Date: August 13, 2025

Status: Live

Overview

This release adds new ways to search, pay, and track AMS360 invoices directly through AndDone. Customers can now look up invoices by number, and merchants get better tools to filter and identify AMS360 transactions.

What’s New

1. Search Invoices by Invoice Number

What it does: Customers can now pay specific AMS360 invoices by entering the invoice number directly on the payment page.

How it works:

• Customers choose between standard Anytime Payments or the new Invoice Lookup option
• Enter a valid AMS360 invoice number to instantly pull up invoice details (customer info, amount due, dates)
• If the invoice number is invalid, a helpful error message appears

Why it matters: Faster payments with fewer errors. Customers get exactly what they need without extra steps.

Customer-facing: Yes

2. Automatic Invoice Payment Limit Checks

What it does: The system now prevents customers from paying invoices that exceed your account’s payment limits for ACH or card transactions.

How it works:

• AndDone automatically checks invoice totals against your configured limits
• If an invoice exceeds the limit, customers see a clear message explaining why the payment can’t be processed that way

Why it matters: Keeps all payments within compliance and prevents failed transactions.

Customer-facing: Yes

3. Complete AMS360 Invoice Payments

What it does: Customers can now complete payments for validated AMS360 invoices with an automatic receipt.

How it works:

• After invoice validation, customers only see payment methods that work for their invoice amount
• Once payment is successful, a receipt is automatically generated

Why it matters: Streamlined checkout with built-in safeguards and instant confirmation.

Customer-facing: Yes

4. View AMS360 Transactions in Payment Listings

What it does: AMS360 payments are now clearly marked in your payment dashboard for easier tracking.

How it works:

• AMS360 transactions show a Vertafore logo in the “Ref Value” column on the payment listing page
• Payment detail pages display “AMS360” under “Initiated From”
• Customer and merchant receipts still show “Anytime Payments” for consistency

Why it matters: Quickly identify where payments originated without changing the customer experience.

Customer-facing: Yes

5. Filter Payments by Source

What it does: Merchants can now filter payment listings by payment source: Anytime Payments, AndDone.js, or AMS360.

How it works:

• New filter options appear based on your active Feature Access settings
• Only see filters for features you’re currently using
• Historical AMS360 transactions remain visible even if the feature is later disabled, but the filter option will be hidden

Why it matters: Better control and visibility into payment data. Easier to analyze transactions by source.

Customer-facing: Yes

The post AMS360 Enhanced Invoice Payments & Transaction Management  appeared first on AndDone.

Release Date: November 25, 2025

Status: Deployed to UAT

Overview

This release expands outbound payment capabilities in AndDone with improvements across vendor management, payment remittance, and check controls. The updates focus on giving insurance teams more flexibility, clearer validation, and better visibility when sending outbound payments.

What’s New

1. Optional DBA Field in Vendor Profiles

What it does:

The DBA (Doing Business As) field is now optional when creating or editing a vendor profile.

How it works:

• Users can save vendor profiles without entering a DBA name.
  
• Vendor creation continues even when a business operates under a single legal name.
  

Why it matters:

Speeds up vendor setup and removes unnecessary blockers during outbound payment preparation.

Customer-facing: Yes

2. Multiple Amount Fields in Payment Remittance

What it does:

Merchants can add multiple amount fields within payment remittance and choose which amount is applied to the check total.

How it works:

• Multiple amount columns can be entered in the remittance table.
  
• Users select the desired amount using the “$” icon.
  
• Only the selected amount is summed and reflected in Check Details.
  

Why it matters:

Supports more complex remittance scenarios while keeping check totals accurate.

Customer-facing: Yes

3. Validation for Check Amounts Over $1,000,000

What it does:

The system now blocks remittance submissions when the total check amount exceeds $1,000,000.

How it works:

• During save or submit, the system evaluates the summed remittance total.
  
• If the amount exceeds $1,000,000, an error message appears and the action is blocked.
  

Why it matters:

Prevents oversized check payments and reduces downstream processing issues.

Customer-facing: Yes

4. Bank Account Selection on Check Details Page

What it does:

Merchants can select which bank account is used before creating a check.

How it works:

• A dropdown lists all merchant-linked bank accounts with check capability.
  
• The default account appears at the top with a star indicator.
  
• If no selection is made, the default account is used automatically.
  

Why it matters:

Gives teams more control over funding sources for outbound payments.

Customer-facing: Yes

5. Vendor Listing Pagination

What it does:

Vendor listings now support pagination instead of a fixed date filter.

How it works:

• Pagination options include 10, 25, or 50 records per page.
  
• The automatic “Last 7 Days” filter has been removed.
  
• All available vendor records are visible by default.
  

Why it matters:

Improves navigation and visibility for teams managing larger vendor lists.

Customer-facing: Yes

Admin Portal Updates

Admin Notifications for Vendor Edits

What it does:

Administrators receive notifications when merchants create or update vendor records.

Why it matters:

Improves oversight and awareness of vendor changes across the platform.

Customer-facing: No

Payment Reference Visibility in Admin Portal

What it does:

Admins can view payment reference details for each outbound payment to help trace check transactions.

Why it matters:

Supports investigation and tracking of outbound payment activity.

Customer-facing: No

Key Takeaway

This release strengthens outbound payment workflows by improving vendor setup, remittance accuracy, and check-level controls. With clearer validation and expanded visibility, insurance teams gain more confidence and flexibility when managing outbound funds.

The post Outbound Payments – Enhanced Vendor Management & Check Controls appeared first on AndDone.

1. Define PCI Scope and Ownership Across Systems and Vendors

PCI compliance for your insurance agency starts with clearly defining scope and ownership. Finance teams must understand every system, workflow, and vendor involved in accepting, processing, refunding, or adjusting card payments, especially when payment activity extends beyond internal systems.

Finance leaders should inventory every touchpoint where card data could appear, including:

• Customer-facing payment portals and hosted checkout experiences.
• Embedded payment links used in emails, invoices, or AMS workflows.
• Internal systems that process, reconcile, refund, or adjust transactions.
• Reprocessed or corrected payments handled outside the original workflow.
• Third-party vendors involved in payment acceptance, processing, tokenization, refunds, chargebacks, or reporting.

Just as important as defining ownership, PCI compliance in insurance depends on documented internal accountability and clearly outlined third-party vendor compliance responsibilities. While technical controls may live with IT teams or vendors, finance remains responsible for oversight.

Finance leaders should document:

• Who owns PCI oversight internally, including validation of scope, controls, and ongoing compliance.
• Which vendors are responsible for PCI controls related to payment acceptance, processing, and tokenization.
• How PCI evidence is collected, reviewed, and stored for audits.
• Where escalation occurs when compliance questions or control gaps arise.

2. Verify How Card Data Is Handled and Stored

Understanding how card data is handled is essential for limiting compliance burden.

Key areas to review include:

• Where card data is captured.
• Whether tokenization occurs immediately.
• Whether any system stores raw card data.
• How long payment data is retained.
• How data is removed or invalidated.

Platforms that rely on tokenization and limit data exposure help finance teams reduce audit scope while maintaining reporting visibility. Less exposure means fewer controls to manage and fewer questions to answer later.

Finance teams should confirm these controls are applied consistently across collections, refunds, and payment adjustments, not only initial transactions.

Look for platforms such as AndDone that tokenize payment data at capture and avoid storing raw card information to reduce audit scope and limit risk.

3. Restrict and Review Access to Payment

Access control is both compliance and financial security.

Finance teams should regularly review:

• Who can view payment details.
• Who can initiate refunds or adjustments.
• Who can export transaction data.
• How role changes are logged and approved.

Role-based permissions and access logs protect against internal risk and support clean audit trails in platforms like the AndDone Portal.

4. Validate Daily Reconciliation and Audit Trails

Reconciliation is where compliance becomes operational.

Strong payment workflows support:

• Transaction-level detail.
• Time-stamped audit logs.
• Clear linkage between payments, refunds, and accounting entries.
• Visibility into paid, pending, failed, and reversed transactions.

Manual reconciliation increases compliance risk. Finance teams benefit from systems that support daily reconciliation.

When payment records are tied to policies and customers with time-stamped logs, reconciliation becomes faster and more accurate. 

5. Make Exceptions Easy to See and Prove

Refunds, chargebacks, and adjustments are part of every payment operation. But when they aren’t documented or visible, they become compliance risks.

Finance teams should ensure:

• All exceptions are tracked with complete transaction history.
• Refunds follow standardized and documented workflows.
• Chargebacks remain visible in reporting.
• Exceptions do not bypass approval or logging controls.

Auditors focus on the moments when processes break. That’s why visibility matters.

Exception workflows should stay connected to the original transaction and remain visible to the full team. This makes it easier to demonstrate control, even when workflows don’t follow the standard path.

6. Confirm Third-Party and Vendor PCI Compliance

Third-party vendors are part of your compliance footprint. As industry coverage regularly highlights, payment complexity in insurance often increases when responsibility for data handling and reporting is spread across multiple platforms and partners. Finance leaders should verify each vendor’s PCI status and document third-party service provider responsibilities across data handling, reporting, and audit support.

Key areas to confirm include:

• Each vendor’s current PCI certification and scope.
• Which party captures, processes, tokenizes, or stores card data.
• How vendors support audits, including access to evidence and documentation.
• Where responsibility shifts between internal teams and external partners.

When vendors manage payment data correctly, finance teams stay in control without taking on extra compliance work. The right platform provides visibility, reporting, and audit support without adding PCI scope to your internal systems. 

The right partner keeps finance in control without adding technical PCI risk. In this short video, Chase Courtney from AndDone shares how their team helps reduce audit complexity by managing tokenization, routing, and reconciliation in one system.

7. Maintain PCI Evidence and Audit Readiness

Audit readiness depends on evidence that reflects how your business actually operates.

Finance teams should centralize:

• PCI policies and procedures.
• Access logs and activity records.
• Transaction and reconciliation reports.
• Vendor compliance documentation.

Evidence should remain current and aligned with live workflows, because faulty or outdated records can directly lead to compliance problems and audit obstacles. When documentation matches real operating conditions, audits move faster. 

8. Schedule Ongoing PCI Reviews for the Year

PCI compliance in your insurance agency must remain current as systems, vendors, and workflows change.

Finance leaders should:

• Align PCI reviews with monthly close cycles.
• Reassess PCI scope whenever payment systems, vendors, or workflows change.
• Review vendor compliance on a regular cadence.
• Update documentation proactively as processes evolve.

Routine reviews prevent compliance drift and reduce last-minute remediation. Keeping PCI oversight tied to financial operations supports consistent audit readiness throughout the year.

The post The CFO’s Compliance Checklist: Key Insurance Requirements and Where PCI Fits appeared first on AndDone.

What Is Insurance Payment Processing?

Insurance payment processing includes the systems used to collect, route, track, and reconcile premium payments. It goes beyond simply accepting a payment. It covers everything from how funds are submitted to how they’re matched and confirmed.

A complete payment process answers several essential questions:

• How does the customer submit payment?
• Where do funds go after submission?
• How is the payment matched to the correct policy?
• When do teams receive confirmation?

Insurance payment processing includes:

• Payment methods, such as ACH and credit cards.
• Fund movement through banking or card networks.
• Payment matching tied to the correct customer and policy.
• Payment status visibility, including paid, pending, or failed.
• Accurate records for service, finance, and reporting.

Because insurance payments often involve binding deadlines, installments, and premium financing, this process carries more complexity than standard ecommerce transactions.

Why Insurance Payment Processing Matters for Service Teams and Owners

Payment processing affects every team in an insurance operation. Friction usually appears first in service interactions, then creates cash flow gaps and operational strain across the business.

Impact on Service Teams

Clear payment processes shape the daily workload for service teams.

When payment handling works well:

• Fewer steps make it easier to send payment links quickly.
• Clear confirmation reduces customer back and forth.
• Visible payment status prevents unnecessary follow ups.
• Faster payments help policies move forward without last minute pressure.

When payment status remains unclear, service teams spend time tracking, checking, and explaining instead of supporting customers.

Impact on Owners and Leadership

For business owners, payment processing influences both stability and reputation.

Reliable payment operations support:

• Better visibility into cash flow.
• Lower operational strain on staff.
• Consistent customer experiences that reflect professionalism.
• Modern payment options that meet customer expectations without disrupting familiar processes.

Delayed payments reduce visibility into cash flow, manual steps increase strain on staff, and inconsistent experiences can erode trust over time. As insurance operations become more data-driven and interconnected, operational efficiency plays a growing role in sustaining performance across billing, servicing, and financial oversight.

How Insurance Payment Processing Works

While specific tools may vary, insurance payment processing follows a predictable flow. Understanding each step helps teams identify where delays and confusion often begin.

Payment processing often operates behind the scenes, but it serves as the connective layer between payment collection, premium finance, and accounting. This foundational layer helps manage fund availability and ensures money moves in a way that supports both current operations and future growth.

What Slows Insurance Payments Down

Even small gaps in the payment process can create friction. These issues often appear repeatedly across service and finance teams.

Why do payments get delayed or returned?

Payment delays often stem from incorrect customer information, bank verification holds, or manual review that slows settlement. ACH returns from incorrect account details are one of the most common issues across the industry and frequently require additional follow up before funds can be posted correctly.

What happens when systems do not connect?

When systems don’t connect, teams face duplicate work and inconsistent updates. Disconnected tools lead to duplicate data entry, missed updates between service and finance, and unclear ownership of follow ups. Approaches that balance automation with human oversight help reduce these gaps by keeping processes aligned and communication clear.

Why do customers struggle to complete payments?

Customer friction often comes from unclear or complex steps. Too many screens, confusing instructions, and the lack of immediate confirmation can cause customers to assume something went wrong. This uncertainty increases inbound calls and slows payment completion.

How Modern Payment Platforms Support Insurance Payment Processing

Modern payment platforms designed for insurance focus on supporting existing processes while reducing manual effort.

With the right platform in place, teams can:

• Centralize payment collection.
• View payment status without switching tools.
• Reduce manual follow-ups tied to unclear or delayed payments.
• Provide service teams with intuitive tools.
• Give owners clearer visibility into payment activity.

Coverage from Digital Insurance highlights how insurance specific technology supports modernization without disrupting established operations.

Why Insurance Payment Processing Is Worth Getting Right

Insurance payment processing shapes service speed, staff workload, and customer confidence, and broader industry shifts toward technology that streamlines core operations reinforce why clarity and efficiency in payment workflows matter.

When payments move clearly and predictably:

• Teams stay focused on customer needs.
• Leadership gains stronger insight into cash flow.
• Customers feel supported throughout the process.

The right setup supports familiar processes while reducing friction across the business.

The post What is Insurance Payment Processing and Why Does it Matter? appeared first on AndDone.

• Release date: March 27, 2026
• Release status: Deployed to UAT
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 330–331

Highlights

• collection mode (AN-26017)
• settlement reports

References

• AN-26017
• AN_REPRED_V2

Original Release Notes Excerpt

UAT Release Notes – Reports Changes (AN_REPRED_V2)

UAT Release: Reports Changes (AN_REPRED.V2)

Release Date: UAT Mar 27, 2025

Release Status: Deployed to UAT

With this version of release, Sub-merchants will have an ability to include or exclude some transactions from the authorization report and settlement reports. Additionally swash buckle integration and few miscellaneous items are included. Features Deployed to Production Client Facing Impact Report settings (feature) & Reporting changes based on YES collection mode (AN-26017)

This feature enables sub-merchants to be able to include or exclude certain type of transactions from the following reports « settlement reports

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

The post UAT Release Notes – Reports Changes (AN_REPRED_V2) appeared first on AndDone.

• Release date: March 18, 2026
• Release status: Deployed to UAT
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 286–287

Highlights

• Ally Webhooks (AN-24831 & AN-23848) YES (Not Immediately)

References

• AN-23848
• AN-24831
• AN-25935
• AN_ALMGMT_V2

Original Release Notes Excerpt

UAT Release Notes – Ally Management (AN_ALMGMT_V2)

UAT Release: Ally Management (AN_ALMGMT.V2)

Release Date: UAT Mar 18,2025Release Status: Deployed to UAT

With this version of release, Ales shall be able to create secure payment intents, subscribe to a webhook and get list of subscribed webhooks. A new secure APIs also crested for Ales to onboard sub-merchants on to AndDone platform, Features Ally Payments, Changes to Secure Payment Intents API. YES (Not Immediately) aN-25935) Ailes shall be able to use secure payment intent API to create payment intents.

They will need to use the Private API key assigned to them Ally Webhooks (AN-24831 & AN-23848) YES (Not Immediately)

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

The post UAT Release Notes – Ally Management (AN_ALMGMT_V2) appeared first on AndDone.

• Release date: February 27, 2026
• Release status: Deployed to Prod
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 99–100

Highlights

• Set & Get Allowed transaction types

References

• AN-23671
• AN_ALMGMT_V1

Original release notes excerpt

PROD Release Notes – Ally Management (AN_ALMGMT_V1)
PROD Release: Ally Management (AN_ALMGMT_V1)
Release Date: Feb 27,2025
Release Status: Deployed to Prod
With this version of release, A new persone willbe available on the AndDone Platform called
Aly ~ an ingurtech platform capebilty to onboard and oversee multiple sub-merchants and
post payments to AndDone platform on behalf of them
Features Deployed to Production Client Facing Impact
AndDone Ally Ver1 Ally Management (AN-23671) YES (Not Immediately)
APIs with Bearer token access are crested to
Create/Modity an Ally and configure the Ally
List lies
Update & Get Fees
«+ Set & Get Allowed transaction types

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

The post PROD Release Notes – Ally Management (AN_ALMGMT_V1) appeared first on AndDone.

• Release date: February 25, 2026
• Release status: Deployed to UAT
• Source pages: ANDDONE-ALL RELEASE NOTES.pdf pp. 318–320

Highlights

• Internal Invoicing Merchant Interaction (AN-13678) ves

References

• AN-13678
• AN_FEEINV_V2

Original release notes excerpt

UAT Release Notes – Merchant Invoicing & Notifications (AN_FEEINV_V2)
UAT Release: Merchant Invoicing & Notifications (AN_FEEINV_V2)
Release Date: UAT Feb 25,2025
Release Status: Deployed to UAT
With this version of release, Merchant Interaction of the Invoice feature along with changes to
Notifications feature is delivered. Platform notifications is a new notification type introduced to
manage the templates for notifications sent by platform to the Sub-Merchants (ex: Invoicing,
Fee updates). Along with these features change requests that accounts for Invoice feature and
technological updates to improve the performance are included in this release.
Features Deployed to Production Client Facing Impact
Internal Invoicing Merchant Interaction (AN-13678) ves
After this release, The Sub-merchants who has the Invoicing
feature enabled can view the invoice details and pay the
invoice for processing fee ete depending on their

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

The post UAT Release Notes – Merchant Invoicing & Notifications (AN_FEEINV_V2) appeared first on AndDone.