> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tangoanalytics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Ar outbound file

# 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`](./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

| Attribute | Value | |
| - | - | - |
| Direction | Outbound (Tango → Client) | |
| Mechanism | SFTP file drop | |
| File format | Pipe-delimited (\` | `) text, `.txt\` |
| File naming | `{ClientName}_arout_MMDDYYYYHHMMSS.txt` | |
| Path | `outbound/ar/` | |
| Auth | SFTP user/password (TBD) | |
| Frequency | TBD | |

## 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 ✅)

| Field | Type | Req | Notes |
| - | - | - | - |
| `LEASE_NUMBER` | VARCHAR | ✅ | |
| `LEASE_STATUS` | VARCHAR | ✅ | |
| `TERM_STATUS` | VARCHAR | ✅ | |
| `LOCATION_NUMBER` | VARCHAR | – | |
| `LEGAL_ENTITY` | VARCHAR | – | |
| `CUSTOMER_NUMBER` | VARCHAR | – | Supplier site number for the customer |
| `INVOICE_DESC` | VARCHAR | – | e.g., RENT |
| `PAYMENT_TYPE` | VARCHAR | ✅ | |
| `EFFECTIVE_DATE` / `APPLIES_FROM_DATE` / `TO_DATE` / `DUE_DATE` | DATE | ✅ | `MM/DD/YYYY` |
| `GROSS_AMOUNT` | NUMBER | ✅ | |
| `TAX_AMOUNT1` / `TAX_AMOUNT2` / `TAX_AMOUNT` | NUMBER | – | |
| `NET_AMOUNT` | NUMBER | – | |
| `CHARGE_STATUS` | VARCHAR | – | Billing status |
| `TAX_RATE` | NUMBER | – | |
| `CURRENCY` / `PAYMENT_CURRENCY` | VARCHAR | – | |
| `ACCOUNTING_STRING` / `GL_ACCOUNT` | VARCHAR | – | |
| `INVOICE_NUMBER` / `INVOICE_DATE` / `INVOICE_ID` | various | – | |
| `LEASE_BILLING_ID` | NUMBER | ✅ | Reconciliation key |
| `REMIT_MESSAGE` | VARCHAR | – | |
| `SEGMENT1`–`SEGMENT6` / `SEGMENT*_GL` | VARCHAR | – | |
| `EXTATTRIBUTE1`–`EXTATTRIBUTE9` | VARCHAR | – | |

## Validations

| Condition | Error message |
| - | - |
| `CUSTOMER_NUMBER` missing | `customer ID is not present` |
| No approved receivables | `No data found` (no file generated; service log + email sent) |

## 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

| Ver | Date | Description | Author |
| - | - | - | - |
| 0.1–1.0 | 2020-2023 | (see source doc) | Various |
| 1.1 | 11/12/2025 | Removed lookup names | Jasmin Thasleem |