DocsSolutions › Corporate Treasury

Originator

Corporate Treasury.

Clean every payment address before the file leaves your ERP or TMS — one deterministic call, sub-50ms. After 15 Nov 2026 your bank legally cannot fix your beneficiary addresses for you.

The hinge — you assemble the payment, so the liability for a rejected payment is yours as originator (EPC §3.2). The fix has to live where the payment is assembled: at source, on your master data and your pain files.

Where you call ARSYour corner of the model.

PlacementAt-Source
ScopeParty Address + Message (pain.001 / pain.008)
Channel presetsepa-sct-out
PatternSidecar beside the ERP / TMS (SAP, Oracle, Kyriba, GTreasury, ION)
TransportsREST · SFTP · JDBC · File Upload

Your channel presetRegister once with EP-25, then send channelName + payload.

{
  "channelName": "sepa-sct-out",
  "channelSelection": {
    "channel": "sepa", "scheme": "SCT", "schemeVersion": "SR2026",
    "direction": "OUTBOUND", "pspCountry": "DE", "timezone": "Europe/Berlin"
  },
  "corridor": { "sendingCountry": "DE", "receivingCountry": "FR", "currency": "EUR" },
  "preferences": {
    "outputMode": "EPC", "targetFormat": "FULLY_STRUCTURED",
    "quality": "standard", "repairConfidenceThreshold": 0.8
  }
}

Endpoints you'll useTry every one in the API reference.

EndpointDoes
EP-02 Process Batch Party AddressOne-time master-data scrub, up to 10,000 addresses per call.
EP-16 / EP-17 MandateDecide whether an address is even required for the scheme + corridor.
EP-10 Check Message AddressesValidate every address in a pain file before you transmit.
EP-12 Convert Message AddressesAuto-correct the file in place; receive a transmit-ready pain.
EP-08 Process Message AddressesThe all-steps pipeline on a pain message in one call.

Recommended use casesAll At-Source, on your own data and pain files.

ink_eraserScrub beneficiary master data

Correct

Data At-Source

Batch-clean stored beneficiary addresses in your ERP before they ever enter a payment file.

EP-02 Process Batch Party Address Batch

balanceDecide whether an address is even required

Validate · mandate

Data At-Source

Determine if the scheme and corridor legally mandate a party address before you prompt for one.

EP-16 / EP-17 Mandate Party Address Single

fact_checkValidate a pain.001 before submitting to the bank

Validate

Message At-Source

Confirm every party address in the file is compliant before you transmit it.

EP-10 Check Message Addresses Single-msg · pain

auto_fix_highAuto-correct a pain.001 before submission

Correct

Message At-Source

Repair addresses in place and receive a corrected pain.001 ready to send.

EP-12 Convert Message Addresses Single-msg · pain

Watch out for — your bank may not correct your counterparty's address (EPC §3.2), so clean it at source. Batch calls (EP-02) require an Idempotency-Key header. Returns and recalls are exempt from modification (EPC §8.3) — route them through the R-transaction endpoints.