Transaction Volume definitions and usage

Version of 12 February 2026

This Transaction Volume Definitions and Usage Addendum ("Addendum") defines and clarifies the applicable modules and their usage in connection with Kyriba's SaaS Services ("SaaS Services") accessed by Customer pursuant to the applicable Order Schedule, Renewal Schedule or Change Order (collectively, "Order Schedule").

1. ERP Transaction Volumes

a. "ERP Transaction Volumes" refers to any single instance of data interaction between the SaaS Services and Customer's internal or external systems, encompassing a variety of treasury functions. This includes, but is not limited to, the following activities:

1. Bank Statements Transactions: Each individual bank statement line exported from the SaaS Services is considered a transaction, including but not limited to a transaction, a transaction summary, a balance, a position.
2. Cash Flows: Each individual cash flow serving for forecast or other purposes. Imports and Exports constitute a transaction.
3. Accounting Entries: Each discrete accounting entry, either generated from a cash flow or financial transaction.
4. General Ledger Entries: Integrated for reconciliation purposes, imported into or exported from the SaaS Services is a transaction.
5. Financial Transactions: Each individual transaction related to borrowing, financing activities, securities, and commodities management imported or exported through the SaaS Services. This also includes foreign exchange and interest rate derivative transactions, including but not limited to currency conversions, hedging operations, and exposure management activities, imported or exported through the SaaS Services.
6. Payment and Collection Transactions: Each payment instruction or collection entry or transfer orders import and export (status update) including routing, as well as each payment dashboard status update exported from the SaaS Services.

2. Bank Reporting Volumes

a. "Bank Reporting Volumes" means the total amount of Bank Statement Data transmitted through bank connectivity services during the Contract Year, as measured by the Kyriba platform. "Bank Statement Data" includes, but is not limited to, all file components transmitted by financial institutions, including transaction records, account identifiers, balances, file headers and trailers, and control summaries.

b. A "Transaction" in this context is defined as each discrete line item made available within the SaaS Services through bank statement reporting, encompassing prior-day and intra-day statements retrieved from financial institutions as designated by Customer regardless of the channels. The volume calculation for Bank Reporting will include all statement records that are reportable and legible within the SaaS Services, inclusive of account Initial Balance, individual transaction lines, and account End of Day Balances.

1. For the purposes of usage, each discrete line item within a bank statement — that is, each entry that records a financial movement or a status update — shall be deemed one (1) Transaction. This includes, without limitation, all types of entries typically reported in bank statements, such as:
   • Credits (e.g., deposits, incoming transfers, interest income)
   • Debits (e.g., payments, outgoing transfers, withdrawals, fees, charges)
   • Balance adjustments and reversals
   • Status or informational entries (e.g., rejected items, cancellations, holds, releases)
   • Any other line item provided by the financial institution as part of the bank statement reporting.

3. Payment Volumes Definition

a. "Payment Volumes" means payment instructions issued through external bank connectivity payment services. This service item is dedicated to the management of electronic payment instructions sent via chosen communication channels.

b. "Payment Transaction" means an individual payment instruction issued through the SaaS Services, instructing a financial institution to transfer funds from one account to another. In instances where multiple payment transactions are aggregated into a single fund transfer request, each individual payment instruction within the batch will be counted as one (1) distinct "Payment Transaction."

4. Fraud Screen Data Volume Definition

a. "Fraud Screen Data Volume" means the aggregate number of individual Payment Transactions that are subjected to scrutiny by the Kyriba Fraud Detection Module.

b. "Fraud Screen Data Transaction" means any Payment Transaction that is submitted to the Fraud Detection Module for screening.

5. Transaction Volume Review

a. The minimum subscription includes an allowance of transactions per month as specified for each applicable volume type as set forth in the Order Schedule, provided that the total number of transactions during the applicable Contract Year shall not exceed the annual allowance set forth on the Order Schedule.

b. Kyriba may monitor and review Customer usage of the SaaS Services for the purpose of calculating applicable transaction volumes. In the event the total number of transactions during a Contract Year exceeds the applicable annual allowance ("Overages"), Kyriba and Customer shall meet in good faith to review the overages. If Kyriba reasonably determines that such Overages reflect a recurring usage trend, Kyriba may propose a change order for any Overages or may, upon reasonable prior notice, restrict access to the applicable overages until the Parties agree on the purchase of additional quantities of Transactions.