Skip to main content

​
Tango GL Outbound — File

Generated from Tango GL Outbound Integration Technical Specification V1.1.docx in SharePoint folder 02 Lease Integrations. MD only — no OAS YAML generated per request. (See gl-outbound-api.yaml for the API counterpart.)

​
Overview

SFTP file-based outbound. Tango writes approved Journal Entries (batch accruals) as a pipe-delimited file to its SFTP server on a periodic (monthly) basis for booking Straight-Line Journal Entries and General Ledgers, lease-related assets, liabilities, and other expense accruals/amortizations. The 3-step internal flow is identical to the API variant:
  1. Generate accruals from all sources → Batch Journal Entries screen.
  2. Approve the JEs.
  3. Transmit to SFTP file (this integration).
Owner: Tango Analytics Spec version: 1.1 Status: Draft (auto-generated — needs review)

​
Transport

Prior files are moved to Processed/<timestamp> before each write; no file is written when there is no data.

​
Integration logic

  • Only accruals on Active leases are exported.
  • Only APPROVED batches are picked up.
  • All line items from approved batches → file.
  • After processing, posting status on the accounting schedule transitions to PROCESSED (covers current and prior periods for error-correcting JEs).
  • Notifications and emails are generated on validation failures.

​
Data fields

​
Validations

​
Open Questions / Assumptions

  • LEGAL ENTITY field name has a space in source — likely should be LEGAL_ENTITY. Confirm.
  • SFTP credentials are <TBD>.
  • Timing/frequency specifics are <TBD>.
  • TRANSACTION_AMOUNT sign convention: positive = debit, negative = credit (per Test Scenario #7).
  • PERIOD_END_DATE referenced in test scenarios but not in the data-mapping table — likely a synonym for POSTING_DATE.
  • 30-character limit on Tango batch description (Test Scenario #3) — applies in Tango UI, not enforceable at file load.
  • Pre-opening / opening JE logic (Test Scenarios 8, 9) handled inside Tango’s accrual generation, not in the file format.
  • Reference documents (Journal Entry Descriptions, JE Model.xlsx, JE accrual design.xlsx, Plain Language JEs) sit alongside in SharePoint — not used for this generation.

​
Changelog