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.
