Skip to main content

​
Tango Vendor Inbound — File

Generated from Tango Vendor Integration Design Specification V0.6.docx in SharePoint folder 01 Common Integrations. OAS spec: vendor-inbound-file.yaml

​
Overview

SFTP file-based inbound. Client drops a pipe-delimited file of vendor / supplier records. Tango creates new vendors or updates existing ones; inactivation via status = I. Tango never deletes vendors. Owner: Tango Analytics Spec version: 0.6 Status: Draft (auto-generated — needs review)

​
Transport

​
Out-of-scope

  • Linking the vendor to a lease (UI only).
  • Adding / updating contacts attached to the vendor (UI only).

​
Integration logic

  • Tango never deletes vendors. To remove a vendor, send status = I.
  • No-update day → client sends no file.
  • Empty / header-only file → no data sent in the file warning.
  • Multiple files at the same time → processed FIFO.

​
Data fields (required ✅)

​
Validations

​
Open Questions / Assumptions

  • Field names differ from API variant — file uses vendor_number, phone_number, address_1 (snake_case with underscore numbers); API uses Supplier_number, business_phone, address1. Confirm both are correct and intentional.
  • SFTP credentials are <TBD>.
  • Timing/frequency is <TBD>.
  • No payment_* / bank_* / tax_id fields in this file variant (API has them). Confirm whether banking info is intentionally out of scope here.
  • Lookup codes are <TBD> in Appendix.

​
Changelog