---
title: "Corporate Treasury"
url: "https://dev.ionova.ai/solutions/corporate-treasury"
image: "https://dev.ionova.ai/_og/d/c_Ocean.takumi,title_Corporate+Treasury,props_eyJ0aGVtZSI6eyJtb2RlIjoibGlnaHQiLCJjb2xvcnMiOnsicHJpbWFyeSI6IiMyRTUwOTAifX19,p_Ii9zb2x1dGlvbnMvY29ycG9yYXRlLXRyZWFzdXJ5Ig,s_yXW44I0aFMEaTvai.png"
---

[Docs](https://dev.ionova.ai/) › [Solutions](https://dev.ionova.ai/solutions) › 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 _ARS_Your corner of the model.

|                |                                                                    |
| :------------- | :----------------------------------------------------------------- |
| Placement      | At-Source                                                          |
| Scope          | Party Address + Message (pain.001 / pain.008)                      |
| Channel preset | sepa-sct-out                                                       |
| Pattern        | Sidecar beside the ERP / TMS (SAP, Oracle, Kyriba, GTreasury, ION) |
| Transports     | REST · SFTP · JDBC · File Upload                                   |

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

```json
{
  "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 _use_Try every one in the API reference.

| Endpoint                          | Does                                                                  |
| :-------------------------------- | :-------------------------------------------------------------------- |
| EP-02 Process Batch Party Address | One-time master-data scrub, up to 10,000 addresses per call.          |
| EP-16 / EP-17 Mandate             | Decide whether an address is even required for the scheme + corridor. |
| EP-10 Check Message Addresses     | Validate every address in a pain file before you transmit.            |
| EP-12 Convert Message Addresses   | Auto-correct the file in place; receive a transmit-ready pain.        |
| EP-08 Process Message Addresses   | The all-steps pipeline on a pain message in one call.                 |

Recommended _use cases_All 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.

Where next

[Channels](https://dev.ionova.ai/channels)[TMS & ERP](https://dev.ionova.ai/solutions/tms-erp)[Shared services](https://dev.ionova.ai/solutions/shared-services)[API reference](https://dev.ionova.ai/apis)