AP reverse feed file specifications

Companies can post invoice payments using AP reverse feed. You can use either the data in Legal Tracker or the AP data exchange web service. This gives legal vendors a way to check payment status and reconcile spending amounts in Legal Tracker compared to their AP systems.

AP reverse feed fields

It's recommended to use 2 fields at a minimum in any reverse feed upload:
  • INVOICE_NUMBER
  • PAYMENT_DATE
AP reverse feed fields
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