Skip to main content
Question

Non-Order Fees entity not syncing after Amazon Finances API v0 removal — anyone else seeing this?

  • September 30, 2026
  • 3 replies
  • 33 views

Build 25.101.0153.11

 

We run the native Amazon Connector (BC201020) with the Non-Order Fees entity active, importing Amazon's non-order-related fees as cash transactions on CA304000. That synchronization stopped returning data at the end of August 2026 and has not recovered.

 

The timing lines up with Amazon's removal of the Finances API v0 operations listFinancialEvents, listFinancialEventsByGroupId and listFinancialEventsByOrderId on August 28, 2026 (deprecated July 21, 2025). The stated replacement is the listTransactions operation in Finances API v2024-06-19.

 

Through our partner, Acumatica support has confirmed that there is currently no workaround other than manually creating the required cash transactions, and that upgrading to 2025 R2 or 2026 R1 does not restore Non-Order Fees synchronization. We were told Engineering is evaluating whether a customization is technically feasible as a temporary measure.

 

A few questions for the community and moderators:

1. Is anyone else running the Non-Order Fees entity and seeing the same behavior? I'm trying to establish whether this is universal to the entity or specific to our configuration.

2. Is there a Known Issue ID or KB article covering this? I did not find one on the Known Issues list.

3. Is the Finances v0 to v2024-06-19 migration targeted for a specific release or patch? An Action Required notice was posted for the Orders API v2026 migration, but I have not seen an equivalent for Finances.

4. Related question on sequencing: GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE and GET_V2_SETTLEMENT_REPORT_DATA_XML have a removal date of November 11, 2026, replaced by GET_V2_SETTLEMENT_REPORT_DATA_FLAT_FILE_V2, which restructures the price columns into amount-type, amount-description and amount. Is the connector's settlement import already reading the V2 report, or is that a second migration still ahead of us?

 

We are on 2025 R1 and planning a 2026 R1 upgrade this quarter, so understanding the sequencing matters for our cutover planning.

 

Happy to share trace detail if that is useful. Thanks in advance.

3 replies

Forum|alt.badge.img
  • Acumatica Employee
  • September 30, 2026

Hello, ​@Tom DeGrave 

The Retail Commerce team is currently investigating the Non-Order fees sync issue related to Amazon settlement groups that have the same date range. We will provide details and available options through our support team.

Migration of the Amazon connector to the Finances API v2024-06-19 was completed in 2025 R2 GA Patch 8, 2025 R2 Update 1 Patch 5, 2026 R1 Update 1, 2026 R1 GA Patch 3, and 2026 R2 versions while the mentioned 2025 R1 version is still using the v0 API.

Synchronization of settlement data and Amazon transactions through the Payments, Non-Order Fees, and Settlement Reports entities uses only the Amazon Finances  API. Therefore, removal of the reports mentioned above will not affect synchronization.


  • Author
  • Freshman I
  • September 30, 2026

Thank you Boris for explaining this in more detail, in that the issue with the date range duplication not with the API version. We are seeing the same duplication per the below, starting 8/28/2026.

 

 

Do you know how many customers this is impacting? I am surprised we are the first to post about this since it has been ongoing since 8/28/2026, over 1-month now.


Forum|alt.badge.img
  • Acumatica Employee
  • September 30, 2026

​@Tom DeGrave  

Amazon generates Settlement Reports and related Financial Event Groups based on its internal logic. In the past, we observed a few rare cases where settlement data was generated for overlapping periods, but the periods were never completely duplicated.

This issue may not affect many customers, as the number of event groups generated can depend on several factors, such as transaction volume, settlement period length, and other processing rules.