Production Release Notes – AMS360 (AN_AMS360_V7)

Adds AMS360 bank account configuration for receipt posting

What’s new

Merchants can now link their AMS360 bank accounts to the platform and designate a default bank under Business Settings. The available bank options are pulled directly from the accounts already configured in AMS360. When posting receipts, the system automatically suggests the default bank but allows merchants to override it on a per-transaction basis. Once posted, receipts appear in AMS360 under the bank name selected during the posting process.

Why it matters

Before this change, there was no way to associate payments made through the platform with specific AMS360 bank accounts. Merchants can now post receipts directly to the correct bank in AMS360, keeping their records organized and reconciliation straightforward.

Introduces individual and bulk receipt posting to AMS360

What’s new

A new “Post Receipts” tab is now available on the Payment Listing page, displaying AMS360-eligible transactions based on the merchant’s selected filters. Merchants can select one or multiple transactions and submit them for posting in a single action. Only transactions in an Authorized or Settled status are eligible — Failed, Refunded, and Chargeback transactions are excluded. The system requires full posting only; partial posting is not supported. Eligible transactions can also be re-posted individually from their Transaction Details page if needed.

Why it matters

You can now post receipts to AMS360 in bulk directly from the payment listing, eliminating the need to handle transactions one by one. The eligibility rules are enforced automatically, reducing the risk of posting transactions in invalid states.

Adds Invoice Count column to Authorization and Settlement reports

What’s new

The Authorization and Settlement reports now include a new “Invoice Count” column that displays the number of AMS360 invoices associated with each transaction.

Why it matters

You can now see at a glance how many AMS360 invoices are tied to a given transaction without needing to navigate to individual transaction records, making it faster to audit and reconcile payment data.

Updates CSV filename convention for AMS360 compatibility

What’s new

The naming convention for exported CSV files has been shortened to comply with AMS360’s 35-character filename limit, which was causing filenames to be truncated. Authorization reports are now named AMS360_auth_yyyy_mm_dd_D and Settlement reports are named AMS360_settled_yyyy_mm_dd_D, where D is a sequence counter (e.g. _01) to differentiate multiple files exported on the same day. Previously generated files retain their original names and must be manually re-exported if the new naming convention is required.

Why it matters

Before this change, long filenames were being cut off by AMS360’s character limit, which could cause files to be unreadable or misidentified on import. Exported files now import cleanly into AMS360 without truncation issues.

Production Release Notes – AMS360 (AN_AMS360_V7)

Release Date: Jan 8, 2026

Release Status: Deployed to Production

This release bundle includes functionality related to AMS360 receipt posting through APIs.

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

AMS360 Bank Configuration for Receipt Posting

This update allows merchants to integrate AMS360 bank accounts with the AndDone platform for accurate recording of payments and receipts.

• Set a Default Bank: Merchants can choose a preferred bank name under Business Settings. The available options are based on the bank accounts already set up in AMS360. This will act as the “Default Bank,” and the system will automatically suggest it for all receipt postings.
• Flexible Posting Options: While a default bank is set, the merchant is not locked into it. When posting receipts to AMS360, the merchant can manually override the default and select a different bank for specific transactions if needed.
• Seamless Integration: Once posted, all receipts will appear in the AMS360 system under the specific bank name selected during the process, ensuring the merchant’s records remain organized and easy to reconcile.

Client Facing: Yes

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

Individual and Bulk Posting of Receipts to AMS360

A new “Post Receipts” tab is now available on the Payment Listing page, displaying AMS360 transactions based on the merchant’s selected filters. The merchant can select one or multiple transactions and submit them by clicking the “Post Receipts” button.

Important Rules for Posting:

• Eligible Statuses: Only transactions marked as Authorized or Settled can be selected for bulk posting.
• Exclusions: Transactions that are Failed, Refunded, or Chargeback cannot be posted.
• Full Posting Only: The system does not allow partial posting of transactions.
• Re-posting: If necessary, eligible transactions can be re-posted through their individual Transaction Details page.

Client Facing: Yes

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

New “Invoice Count” Column in Reports

The Authorization and Settlement reports now include an “Invoice Count” column, which displays how many AMS360 invoices are associated with each transaction.

Client Facing: Yes

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

Updated CSV Filename Convention for AMS360 Compatibility

To prevent filenames from being truncated (cut off) due to AMS360’s 35-character limit, the naming convention for CSV files has been shortened. Merchants will now see files named in the following formats:

• Authorization Reports: AMS360_auth_yyyy_mm_dd_D
• Settlement Reports: AMS360_settled_yyyy_mm_dd_D

(Note: “D” represents a sequence counter, such as _01, to distinguish between multiple files on the same day.)

Important: Previously generated files will retain their original names. The merchant must re-generate any older files if the new naming convention is required for those records.

Client Facing: Yes