Issue description
Issue 1. Last/Next Statement Date is not updated after running Prepare Statements
After running the process to prepare statements on the Prepare Statements (AR503000) form, the Last Statement Date (and consequently the Next Statement Date) is not updated for a customer, even though the process appears to have completed.
Issue 2. The Another process has added the 'ARStatement' record error occurs when preparing consolidated statements
When users paid a customer invoice with a payment associated with its parent account and then changed the parent account to a different one, the user could not prepare the consolidated customer statements on the Prepare Statements form due to the following error (shown below): Another process has added the 'ARStatement' record. Your changes will be lost.
Issue 3. Running the process to prepare statements does not update the Last Statement Date if an AR document was released during the process
On the Prepare Statements form, if an accounts receivable document was released while customer statements were being prepared, the statement cycle's Last Statement Date might not update after the process completes.
Root cause
Issue 1. During the prepare statements run, the client continued to add/release documents to the previous (statement) period while the process was executing. The system detects that not all records for the period were processed at the time the statement was generated, and therefore intentionally does not update the Last Statement Date, since doing so could result in an incomplete statement.
For example:
Invoice ARI00872592 has a Document Date of 2026‑01‑29 but was actually created/released on 2026‑02‑04 at 9:00 AM
The prepare statements process for the period ending 2026‑01‑31 ran on 2026‑02‑04 from 07:00 to 23:00.
Because this invoice was released after the process started but was still dated within the statement period, the process correctly identified that not all documents for the period had been processed and left the Last Statement Date unchanged.
Issues 2, 3. These are known issues in all supported versions of Acumatica ERP.
Solution
Issues 1, 2, and 3. We are planning to improve the system's behavior in future versions of Acumatica ERP.
Workaround
Issues 1, 2, 3. Contact your Acumatica support provider to receive the workaround instructions and any assistance with using them.
To avoid this situation going forward, consider one of the following:
Schedule the prepare statements process to run during off-hours (e.g., overnight), when no users are actively releasing documents, to avoid concurrent document entry.
Review and revise internal processes around releasing backdated documents (documents dated in a prior, already-closing period) so they are not added while prepare statements is running.