# Create or Update Batch GroupPayorAccount Create or Update multiple GroupPayorAccount at once. If the entity exists, it will be updated. If the entity does not exist, it will be created. Endpoint: PUT /groups/{groupID}/payor-account-settings-batch Version: v1 Security: apiKeyAuth, bearerAuth ## Header parameters: - `vbasoftware-database` (string, required) Target database ## Path parameters: - `groupID` (string, required) Group ID ## Request fields (application/json): - `group_ID` (string, required) References Groups.Group_ID value on the parent record. - `setting_ID` (string, required) Unique identifier for each payor/account setting. - `account_Key` (integer,null) The Account_Key to be assigned on the claim if subsequent criteria values match the claim. - `check_Incurred` (boolean, required) Indiciates if Service_Date should be interrogated for this setting. If so, use Incurred_From and Incurred_Thru values. Note: This field is marked as NOT NULL in the database and therefore required by the API. - `check_Received` (boolean, required) Indiciates if Received_Date should be interrogated for this setting. If so, use Received_From and Received_Thru values. Note: This field is marked as NOT NULL in the database and therefore required by the API. - `currency_ID` (string,null) If this payor/account setting should be applied only to specific currency, you would note that currency here. - `description` (string,null) A brief description of this payor/account setting for reporting and admin purposes. - `division_ID` (string,null) Optionally, set the Division_ID (reference GroupDivision.Division_ID) if this setting is Division level. - `entry_Date` (string) Date when the record was first added to the system. - `entry_User` (string,null) User that first added the record to the system. - `ex_Code` (string,null) If an Ex_Code should be placed on the claim when this setting is hit during adjudication, you would assign that Ex_Code here. - `incurred_From` (string,null) The date range for this setting if Check_Incurred is flagged. - `incurred_Thru` (string,null) The date range for this setting if Check_Incurred is flagged. - `payor_ID` (string,null) The Payor_ID to be assigned on the claim if subsequent criteria values match the claim. - `received_From` (string,null) The date range for this setting if Check_Received is flagged. - `received_Thru` (string,null) The date range for this setting if Check_Received is flagged. - `update_Date` (string) Date when the record was last updated in the system. - `update_User` (string,null) User that last updated the record in the system. ## Response 207 fields (text/plain): - `data` (array,null) - `data.id` (array, required) List of key/value pairs that represent the unique id for the entity operation. - `data.id.key` (string,null) - `data.id.value` (any,null) - `data.status` (integer, required) http status of the operation (eg, 200, 201, 500) - `data.body` (string, required) operation message (eg, Updated, Created, Error message) - `error` (object) - `error.detail` (string,null) A human-readable explanation specific to this occurrence of the problem. - `error.instance` (string,null) A URI reference that identifies the specific occurrence of the problem.It may or may not yield further information if dereferenced. - `error.status` (integer) The HTTP status code([RFC7231], Section 6) generated by the origin server for this occurrence of the problem. - `error.title` (string,null) A short, human-readable summary of the problem type.It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization(e.g., using proactive content negotiation; see[RFC7231], Section 3.4). - `error.type` (string,null) A URI reference [RFC3986] that identifies the problem type. This specification encourages that, when dereferenced, it provide human-readable documentation for the problem type (e.g., using HTML [W3C.REC-html5-20141028]). When this member is not present, its value is assumed to be "about:blank". - `debug` (object) - `debug.activityID` (string, required) ## Response 401 fields