AP reverse feed file specifications
AP reverse feed fields
- INVOICE_NUMBER
- PAYMENT_DATE
Header row label | Type | Max length | Required | Notes |
---|---|---|---|---|
INVOICE_ID | Integer | Variable (32 bits) | No | Designed to be an ‘exclusive OR’ (XOR) with INVOICE_NUMBER. If you use INVOICE_ID, Legal Tracker scans for a matching invoice with that ID before using INVOICE_NUMBER.
If an invoice isn't found or INVOICE_ID isn't specified, then use the INVOICE_ NUMBER to find the invoice. |
INVOICE_NUMBER | String | 31 | Ye | Designed to be an ‘exclusive OR’ (XOR) with INVOICE_ID.
If you have multiple invoices with identical invoice numbers, then use the Office Vendor ID as the secondary, required identifier. |
INVOICE_DATE | Date | Variable | No | You'll need to match the format selected during upload. |
OFFICE_VENDOR_ID | String | 30 | No | Needed if vendors submitted invoices with matching invoice numbers.
However, if you include the INVOICE_ID column, this ID is always unique so you don’t need the office vendor ID. |
FIRM_NAME | String | 100 | No | |
PAYMENT_DATE | Date | Variable | No | You'll need to match the format selected during upload. |
PAYMENT_EXCHANGE_RATE | Decimal | Variable | No | Use this field if you need to change the currency of the invoice.
If there was no conversion of the invoice total to a different currency for the purposes of issuing payment, this column should be left blank. |
PAYMENT_NUMBER | String | 100 | No | |
PAYMENT_STATUS | String | 50 | No | |
PAYMENT_COMMENTS | String | 250 | No |
- Fields not listed in this table will be ignored.
- INVOICE_NUMBER is required. You can remove any other columns you don’t plan to use.
- The 1st row in the file should be the header row that lists the columns present in the data file.
- The fields can be in any order.
- If the Tracker interface is used to manually upload the file, the file delimiter and date format must match the formats chosen when the file is uploaded.