Skip to main content

Tango AR Outbound — File

Generated from Tango AR Outbound Integration Design Specification V1.1.docx in SharePoint folder 02 Lease Integrations. OAS spec: ar-outbound-file.yaml

Overview

SFTP file-based outbound. Tango writes approved receivables (billings) as a pipe-delimited file. Once exported, billings are flagged Exported to AR. Owner: Tango Analytics Spec version: 1.1 Status: Draft (auto-generated — needs review)

Transport

Integration logic

  • LEASE_BILLING_ID is the reconciliation key.
  • Billings missing CUSTOMER_NUMBER are excluded and an email is sent to client.
  • Zero-dollar billings excluded.
  • Only Approved billings exported; after export flagged Exported to AR.
  • No billings to process → no file generated.

Data fields (required ✅)

Validations

Open Questions / Assumptions

  • SFTP credentials are <TBD>.
  • Timing/frequency is <TBD>.
  • Lookup codes are <TBD> in Appendix.
  • Error message inconsistency: validation uses customer ID though the field is CUSTOMER_NUMBER.

Changelog