Skip to main content

​
Tango CPI Inbound

Generated from Tango CPI Integration Design Specification_Standard_v0.3.docx in SharePoint folder 02 Lease Integrations. OAS spec: cpi.yaml

​
Overview

Internal, product-wide automated integration. Tango’s scheduled job pulls Consumer Price Index (CPI) data from external public data sources (BLS, IMF, World Bank) into Tango’s internal index tables. Clients consume the result via the CPI/Indexed Rent tab in the UI; they do not call any endpoint themselves. Once indices are loaded, CPI calculations can be triggered manually via the Calculate Adjustment button against leases with recurring-cost setups. Owner: Tango Analytics Spec version: 0.3 Status: Draft (auto-generated — needs review)

​
Transport

​
Integration logic

  • On a pre-defined frequency, Tango’s program connects to approved data sources and retrieves the latest index values.
  • The index values are upserted into Tango’s internal index tables, mapped via configured index codes.
  • A notification email is sent to the client once indices have been integrated.
  • When the client applies CPI calculations on a lease, Tango computes adjustments based on the Previous Index → Current Index delta.
  • Retroactive adjustments generate a one-time payment in the current period to capture the change.

​
Data fields

​
Open Questions / Assumptions

  • Data source per index is <TBD>: each index can come from BLS, IMF, or World Bank — the actual binding for each INDEX_CODE is not enumerated in the design doc.
  • Up to ~100 indices is the stated cap in the source.
  • Timing within the month is <TBD> (to be aligned with CPI standard release).
  • Per-source API contracts are not part of this design doc; the YAML models the post-fetch row shape only.

​
Changelog