August 17, 2026

Application Stats gains PO, functionality, per-quarter fiscal-year spend, and cost-center fields, plus a new join to Applications; Application Security adds CCPA/GDPR compliance flags; Savings Events adds audit fields and a manual/system indicator.

Added

Application Stats

  • Added charge_count (total payment transactions for the application) and users_expensing_count (distinct users who submitted expense payments).
  • Added primary_cost_center, a breakdown of the top-spending cost center for the application (cost_center, annual_spend, total_cost_centers_count).
  • Added bill_frequency, contract_notification_length, and contract_term_spend from the application's primary contract.
  • Added active_functionalities and inactive_functionalities arrays.
  • Added purchase order fields: po_count, active_po_count, total_approved_po, and total_po_software_spend.
  • Added per-quarter fiscal-year spend fields: current_fiscal_year_q_1_spend through q_4_spend, and last_fiscal_year_q_1_spend through q_4_spend.
  • Application Stats can now be joined to Applications in POST /v2/query requests.

Application Security

  • Added ccpa and gdpr compliance fields.

Savings Events

  • Added zylo_created_by and zylo_modified_by, showing who created or last modified a savings event.
  • Added quantity, the numerical value of a savings event combined with its unit of measure (e.g. "10 licenses").
  • Added manual, indicating whether the savings event was entered manually rather than generated by the system.