Import Pre-Mapped Transactions (Reconciliation Compliance)

Imports pre-mapped transactions for a particular period, and returns the success or failure status.

REST Resource

POST       /armARCS/rest/{api_version}/jobs


Supported Media Types: application/json


The following table summarizes the client request parameters specific to this job.


Name Description Required
api_version Version of the API you are working with, such as v1 Yes
jobName The name of a job, IMPORT_PREMAPPED_TRANSACTIONS Yes
transactionType Transaction Type is one of the following:
  • BEX for loading Balance Explanations
  • SRC for loading Source System Adjustments
  • SUB for loading Subsystem Adjustments
  • VEX for loading Variance Explanations
file The file name, such as transactions.csv  
dateFormat Date Format, such as DD/MM/YYYY, MMM d, yyyy, or All Yes

Example of request body

 "parameters": {
                              "dateFormat": "MMM d,yyyy"


Supported Media Types: application/json


Table 11-14 Parameters

Name Description
details In case of errors, details are published with the error string
status See Migration Status Codes
links Detailed information about the link
href Links to API call or status API
action The HTTP call type
rel Relationship type
data Parameters as key value pairs passed in the request

Example of Response Body


{ "type": "ARCS", "status": -1, "details": "In Process", "links": [ { "rel": "self", "href": "https://<SERVICE_NAME>-<TENANT_NAME>.<SERVICE_TYPE>.<dcX>", "action": "GET" } ], "error": null, "items": null, "link": null }

The following is an example of the response body in JSON format.

  "type": "ARCS",
  "status": -1,
  "details": "In Process",
  "links": [
      "rel": "self",
      "href": "https://<SERVICE_NAME>-<TENANT_NAME>.<SERVICE_TYPE>.<dcX>",
      "action": "GET"
  "error": null,
  "items": null,
  "link": null