Skip to content

Avaloq

Atfinity onboards clients and External Asset Managers into Avaloq and maintains their master data, through two integrations: CLM and CAPI. Use CLM to onboard a client as one transaction, and CAPI to read or change single master data objects. Between them they reach most of what Avaloq stores about a client.

CLM

Client Lifecycle Management (CLM) is Avaloq's Business API for changing client data. It builds on CAPI, but groups the changes to persons, business partners, containers and accounts into one transaction, which Avaloq verifies as a whole and applies only when it is submitted. Examples of what banks use it for:

  • Onboarding a natural person, a legal person, a joint account, a partnership, a sole proprietorship or a community of heirs, straight from the fields of a case
  • Creating a prospect early, even before its person type is clear, and onboarding it as a client once the case is approved
  • Building up an onboarding transaction as the case progresses: persons with their addresses and documents, the business partner with its account ownerships, authorities and beneficial owners, containers with their money accounts and investment policy statements, and credit and debit cards
  • Verifying the transaction against Avaloq's checks, reading its hints and overrides, and submitting it
  • Following a client operation through its status and validations, and reading who is responsible for it

CAPI

The Community API (CAPI) works on Avaloq's master data directly, one object at a time. Examples of what banks use it for:

  • Creating, updating or deleting a person, a business partner, an address, a container or a document
  • Reading the current state of a client before a case changes it, including money accounts, contacts and CRM issues
  • Keeping Avaloq in step with a lifecycle case, by writing only the objects that changed

The CAPI EAM integration builds on it to onboard an External Asset Manager in one action: the company with its address, every employee with their address, a power of attorney from the company to each employee, the business partner with its owner and contact authorities, and the container. It reads back every object it writes and stops at the first call that fails, naming it.

dgArchive

The dgArchive integration uploads documents from a case into the Avaloq document archive and reads its stamps.

OAuth

The Avaloq OAuth integration fetches an Avaloq access token, for a custom integration to authenticate with.

Building further Avaloq integrations

Atfinity keeps detailed documentation and guidance for CLM and CAPI, including the API specifications and the order in which calls have to be made. Atfinity uses them to build integrations for more complex Avaloq processes as a custom integration for one client, outside the release cycle.

XML onboarding interface

Installations that onboarded clients into Avaloq before CLM and CAPI were available export cases as an XML client onboarding request instead. It is a custom enterprise feature that has to be enabled for your installation, and a new integration uses CLM or CAPI.

Each process that exports has its own XML template, and the template has to match the Avaloq schema before you can put the configuration live. Atfinity hands the file over through a folder or an SFTP server, optionally encrypted with GnuPG, and reads Avaloq's response from the same place. A successful response writes the identifiers Avaloq created back into the case: the business partner, the container, the persons, the e-banking logins and the money accounts with their IBANs, each into the information you choose on the process. A failed response shows Avaloq's error on the export.