---
title: "Shared Service Centres / GBS"
url: "https://dev.ionova.ai/solutions/shared-services"
image: "https://dev.ionova.ai/_og/d/c_Ocean.takumi,title_~U2hhcmVkIFNlcnZpY2UgQ2VudHJlcyAvIEdCUw,props_eyJ0aGVtZSI6eyJtb2RlIjoibGlnaHQiLCJjb2xvcnMiOnsicHJpbWFyeSI6IiMyRTUwOTAifX19,p_Ii9zb2x1dGlvbnMvc2hhcmVkLXNlcnZpY2VzIg,s_-1d1WPSBpkNegAFp.png"
---

[Docs](https://dev.ionova.ai/) › [Solutions](https://dev.ionova.ai/solutions) › Shared Service Centres / GBS

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 _ARS_One 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 _use_The 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 cases_Run per entity; report across the group.

radarScan a message portfolio for SR2026 readiness

Classify · profile

Message At-Source

Inventory every address across your traffic and flag which would fail after the 15 Nov 2026 cutover.

EP-14 Extract Message Addresses Single / Batch · any

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 Batch

fact\_checkValidate a pain.001 before submitting to the bank

Validate

Message At-Source

Confirm every party address in each entity's file is compliant before transmission.

EP-10 Check Message Addresses Single-msg · pain

stacksEnd-of-day batch compliance run

Process · all-steps

Message Both

Process up to 100 complete ISO 20022 messages in a single call.

EP-09 Process Batch Message Batch · any

**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`.

Where next

[Channels](https://dev.ionova.ai/channels)[Treasury](https://dev.ionova.ai/solutions/treasury)[Banks & PSPs](https://dev.ionova.ai/solutions/banks)[API reference](https://dev.ionova.ai/apis)