Skip to main content

​
Tango Currency Conversion — File

Generated from Tango Currency Conversion Integration Design Specification V0.5.docx in SharePoint folder 01 Common Integrations. OAS spec: currency-conversion-file.yaml

​
Overview

SFTP file-based inbound. Client drops a pipe-delimited file with forex rate entries; Tango inserts new rates into its forex table. Insert-only — does not update existing rates. Owner: Tango Analytics Spec version: 0.5 Status: Draft (auto-generated — needs review)

​
Transport

​
Integration logic

  • Insert-only — never updates existing rate entries.
  • Duplicate currency combinations for the same exchg_rate_date are NOT allowed (e.g., MEX→USD cannot appear twice for the same date).
  • Pipe characters inside data must be removed/replaced before delimiting.
  • Leading/trailing whitespace, embedded CR/LF, and non-ASCII bytes must be stripped from cell values.

​
Data fields (required ✅)

​
Validations

​
Open Questions / Assumptions

  • Field name casing inconsistency: source mapping mixes source_currency_code (snake_case) with Effective_From / Effective_To / Avg_rate (PascalCase). Preserved verbatim — confirm which the actual file headers use.
  • Field names differ from the API version: this file spec uses source_currency_code / to_currency_code / exchange_rate / Avg_rate / exchg_rate_date; the API uses source_currency / converted_currency / spot_exchange_rate / avg_exchange_rate / exchange_rate_date. The two integrations are functionally equivalent but won’t share parsers.
  • SFTP path is <TBD> — placeholder inbound/currency-conversion used.
  • SFTP credentials are <TBD>.
  • Date format ambiguity in test scenario #3 mentions either MM/DD/YYYY or MM-DD-YYYY — the mapping table only documents MM/DD/YYYY.

​
Changelog