Skip to main content
Question

Export Batch Payment action API returns HTTP 204 without generating XML

  • Nov 13, 2026 6:38 PM UTC
  • 1 reply
  • 10 views
  • Translate All

Hi,

I am trying to automate the generation of a SEPA XML file by executing the Export action on the Batch Payments screen in Acumatica (for example, batch 000435).

To achieve this, I have:

  1. Created a custom REST API entity named BatchPayment in the endpoint DefaultExtended, version 24.200.001, including the Batch Summary fields.

  2. Added the Export action to this entity.

  3. Configured the action parameters corresponding to the Settings dialog that normally appears when clicking the Export button in the Acumatica interface.

I am calling the following REST API endpoint:

Method: POST

Endpoint:
/entity/DefaultExtended/24.200.001/BatchPayment/Export

Request body:

{
"entity": {
"id": "efd710ef-cb9b-f111-a84a-000d3ae74153"
},
"parameters": {
"BatchbookingBtchbookgtag": {
"value": "Unity (False)"
},
"Executiondate": {
"value": "2026-11-13T00:00:00+00:00"
},
"PaymentInformation": {
"value": "One level per Batch"
},
"PriorityInstrPrtytag": {
"value": "None"
}
}
}

The API returns HTTP 204 (No Content) without any error message. However, the SEPA XML file is not generated for the batch payment.

When performing the same operation through the Acumatica interface, clicking Export opens a Settings dialog, and the XML file is generated only after clicking OK.

My questions are:

  1. Am I missing any configuration or parameter in the REST API request?

  2. Is it possible to execute the Export action, including the confirmation of the Settings dialog, directly through the REST API?

  3. Is there a native Acumatica API or another recommended method to generate and retrieve the SEPA XML file programmatically?

My objective is to reproduce the complete Export operation through the API without requiring manual interaction with the graphical interface.

Thank you.

1 reply

Steve Milner
Varsity III
Forum|alt.badge.img+7
  • Varsity III
  • Nov 14, 2026 12:25 AM UTC

My replies are created in part with the help of proprietary AI, built with my AI skills, curated and maintained myself. Most replies are tested on local instances before they go up, and all are reviewed before posted.

@Mido97 That Settings dialog isn’t part of the stock Export action. Stock Export saves the batch and runs the Export Method set on the Settings for Use in AP tab of Payment Methods (CA204000). That’s either an export scenario or a plug-in. Plug-in options are kept on that form’s Plug-In Settings tab, and nothing is asked at export time. It’s the same from 2024 R2 through 2026 R2. The dialog you see comes from the SEPA add-on or customization on your site.

The REST API can answer an action’s dialog. Change ID on Customers (AR303000) opens a Specify New ID dialog, and it runs through an endpoint with one parameter for the new ID. Your parameters only reach the dialog if they’re mapped to the object it actually uses. If it’s a workflow dialog, map them from the Transition Parameters object on Web Service Endpoints (SM207060). Whoever supplied the SEPA export can tell you which object that is.

A 204 means the call finished. It doesn’t mean a file was made. Stock Export runs the export as a long-running operation, so a working call can come back 202 with a Location header. Poll that URL until it returns 204.

If your UI export leaves the XML under Files on the batch, you can pull it the same way. GET the BatchPayment record with $expand=files and download the file from its href.

Translate