Originator
Solve it once. Every entity inherits.
You run payments for many legal entities — you don't have N problems, you have one, multiplied. Tune the engine once; each entity onboards as its own channel profile and inherits compliance.
The hinge — every entity faces the same 15 Nov 2026 cutover at once. Centralise the fix as a shared service and you turn N parallel remediation projects into one, with a single audit trail across the group.
Where you call ARSOne engine, per-entity isolation.
| Placement | At-Source |
| Scope | Party Address + Message (pain) |
| Channel preset | One channel profile per entity (e.g. sepa-sct-out, corp-host-to-host) |
| Pattern | Multi-tenant sidecar — per-entity data, thresholds & scorecards on shared infrastructure |
| Transports | REST · SFTP · JDBC · File Upload |
Endpoints you'll useThe originator set, run per entity and rolled up.
| Endpoint | Does |
|---|---|
EP-14 Extract Message Addresses | Group-wide readiness scan — what would fail, by entity. |
EP-02 Process Batch Party Address | Centralised master-data scrub, up to 10,000 addresses per call. |
EP-10 / EP-12 Check / Convert Message | Validate then correct each entity's pain files. |
EP-09 Process Batch Message Addresses | End-of-day sweep of up to 100 messages in one call. |
Recommended use casesRun per entity; report across the group.
ink_eraserScrub beneficiary master data
Correct
Data At-Source
Batch-clean stored beneficiary addresses across every entity before they enter a payment file.
EP-02 Process Batch Party Address
Watch out for — each entity is a channel profile, not a separate integration — onboard new entities by config, not code. Multi-tenant isolation keeps each entity's data and scorecards separate while rolling up to a group view. Batch calls require an Idempotency-Key.