Skip to main content

Tango GL Outbound API

Generated from Tango GL Outbound API Integration Technical Specification V1.4.docx in SharePoint folder 02 Lease Integrations. OAS spec: gl-outbound-api.yaml

Overview

Async REST API: client fetches approved Journal Entries (batch accruals) from Tango for booking to its general ledger. Tango’s internal 3-step process — generate accruals → approve JEs → transmit on request — feeds this API. Owner: Tango Analytics Spec version: 1.4 Status: Draft (auto-generated — needs review)

Base URLs

Authentication

Headers x-client + x-api-key.

Endpoints

GET /v1/leasemgmt/accurals

Optional query params: fiscal_year, fiscal_period, country, financial_group. Response — 200 OK

GET /v1/batch/status?gu_id=...&page_no=...

Default page_no = 1, page size 5000. Null fields omitted from JSON.

Integration logic

  • Only accruals on Active leases are returned.
  • Only batches in APPROVED status are picked up.
  • All line items from approved batches are returned.
  • After successful processing, posting status on the accounting schedule transitions to PROCESSED for the current period (and any error-correcting prior periods).

Data model (required ✅)

Open Questions / Assumptions

  • /accurals typo: the documented endpoint is /v1/leasemgmt/accurals. Likely should be /accruals. Schema preserved verbatim — confirm.
  • lease_finacials_group typo in source (“finacials” not “financials”). Preserved verbatim.
  • debit_Account mixed case: the doc uses capital A in debit_Account while credit_account is lowercase. Preserved verbatim; confirm wire format.
  • period_amount typed VARCHAR — likely numeric. Preserved per source.
  • Required-fields: per data mapping, most fields are optional, but business validations (e.g., Lease Number not available, Posting Date not available, GL Account not available) effectively require additional fields.
  • Pagination page size 5000 (non-configurable per the doc).
  • Reference documents (Journal Entry Descriptions, Journal Entry Model, JE accrual design xlsx, Plain Language JEs) live alongside this spec in SharePoint — not consumed by this generation per your direction.

Changelog