Platform implementation

Kyriba

We implement Kyriba as the treasury hub for cash visibility, payments and FX risk, with every bank connected and every payment screened before money leaves.

Dubai towers at dusk seen across a calm creek

Kyriba work usually starts with bank connectivity and daily cash visibility across all accounts, then moves to cash forecasting, payments and FX exposure. Gulf treasuries pay through local rails, UAEFTS in the UAE and SARIE in Saudi Arabia, and salary payments still have to meet WPS in the UAE and Mudad in Saudi Arabia even when payroll prepares the file. Because most Gulf currencies are pegged to the US dollar, FX work tends to focus on euro, sterling and Asian exposures rather than the dollar itself.

We set up Kyriba's bank connectivity over SWIFT or host-to-host channels, map statement formats such as MT940 and camt.053, and build payment templates and approval workflows for each entity. Kyriba's payment fraud detection screens outgoing payments against rules and behaviour patterns, and ERP connectors carry invoices and accounting entries in both directions.

Kyriba and related product names may be trademarks of their respective owners.

How we implement Kyriba

Implementation, customisation, deployment and ongoing support, with governance your steering committee can follow.

  • Blueprint and governance

    The bank account structure, payment types per bank, approval rules and cash forecasting categories are agreed with the treasurer, finance controls and IT before any bank is connected.

  • Cash forecasting

    Forecast categories, inputs from the ERP and business units, and variance analysis of forecast against actual by week and month.

  • FX exposure and hedging

    Exposure capture, hedge proposals and deal records for the currencies that are not pegged to the dollar.

  • Bank account management

    A register of every bank account, signatory and mandate, with changes approved and audited in Kyriba.

  • Hypercare and managed support

    Kyriba is delivered as SaaS and updated by the vendor, so after go-live we test bank formats and payment workflows against each release and follow up rejected or delayed payments. We also onboard new banks and accounts as the group grows.

When Kyriba is the right treasury hub

Kyriba fits corporate treasuries that want a vendor-hosted platform with wide bank connectivity and payment controls, independent of whichever ERP each entity runs.

  • Many banks and accounts across several countries
  • Several ERPs in use, or an ERP change planned
  • A treasury team ready to own payment workflows and bank formats
  • A defined cash forecasting process, even one run in spreadsheets today

Plan Kyriba with Hosn Al Tomoh

Tell us what the platform needs to do and when. We will propose a first phase with scope, team and an itemised quotation.

Talk to our team