Skip to main content
POST
Create payment configuration for an organisation

Authorizations

X-Auth-Token
string
header
required

Access token obtained from OAuth2 client credentials flow

X-Org-Id
string
header
required

Organisation to scope the request to. Required when the principal can access more than one organisation; optional for single-organisation principals (the authorizer resolves it automatically).

Path Parameters

payrollConfigId
string
required

Body

application/json
method
string
required
Example:

"BACS"

format
string
required
Example:

"Barclays"

fileFormat
string
default:txt

Optional. Defaults to txt when omitted. Use csv only when listed in supportedFileFormats for this method/format.

Example:

"csv"

reference
string | null

Single reference expression. Supports static text and tokens in any order: {payDate}, {payPeriodStart}, {payPeriodEnd}, {year}, {period}, {frequency}, {separator:space}, {separator:dash}, {separator:underscore}, {separator:slash}, {separator:custom:}.

Example:

"Payroll May 2024"

referenceDateFormat
enum<string> | null
default:DMY_SLASH

Optional date format enum applied to date tokens ({payDate}, {payPeriodStart}, {payPeriodEnd}). If omitted, the system defaults to DMY_SLASH(01/02/2026). Supported values: DMY_COMPACT(01022026), DMY_SLASH(01/02/2026), YMD_DASH(2026-02-01), MDY_SLASH(02/01/2026), DMY_DASH(01-02-2026), DMY_DOT(01.02.2026).

Available options:
DMY_COMPACT,
DMY_SLASH,
YMD_DASH,
MDY_SLASH,
DMY_DASH,
DMY_DOT
Example:

"DMY_SLASH"

bacs
object
Example:

Response

Payment Configuration Created

message
object
content
object
validationIssues
object[]
messageToken
string