All Collections
Onboarding
Payment File Specification
Payment File Specification
C
Written by Chris Wyatt
Updated over a week ago

This Finexio payment file specification defines the data structure necessary for Finexio to process your supplier payments. A buyer submits a payment file to Finexio for processing, and the file must have the structure given in this specification.

A payment file contains field names in the first row; values that correspond to those fields appear in second row and all rows thereafter. 

Here is an example of rows 1-3 of a payment file:

BuyerID,BuyerName,BuyerAcct,SupplierID,....
vch,Vizcaya Hilltop Apartment Homes,,hdsupply, ...
vch,Vizcaya Hilltop Apartment Homes,,nv46878, ...

The first row is the header:

BuyerID,BuyerName,BuyerAcct,SupplierID,....

These are the payment details in rows 2 and 3:

vch,Vizcaya Hilltop Apartment Homes,,hdsupply, ...
vch,Vizcaya Hilltop Apartment Homes,,nv46878, ...

Field names can either be separated by commas (comma-delimited), or by pipes (pipe-delimited). The file must be a simple text file, and the file name suffix should be either .csv or txt.

The first row is the header:
BuyerID,BuyerName,BuyerAcct,SupplierID,....

These are the payment details in rows 2 and 3:
HAH,Hilltop Apartment Homes,,hdsupply, ...
HAH,Hilltop Apartment Homes,,nv46878, … 

Field names can either be separated by commas (comma-delimited), or by pipes (pipe-delimited). The file must be a simple text file, and the file name suffix should be either .csv or txt. 

Preparing the payment file

When preparing the payment file, ensure that it conforms to each of the following requirements: 

  1. Each payment must have its own row in the payment file. 

  2. Do not include any commas or currency symbols (such as $) in the  value for the payment amount. For example, $5,325.98 is not  permissible, while 5325.98 = is correct. 

  3. Ensure that each line break is formatted as [CR][LF], also known as a hard return. It is important to avoid creating an extra field.  

  4.  Ensure all non-numeric fields are not truncated or abbreviated.    

    Here is an example of a value containing leading zeros, which should remain intact     in the file:  0024245242    

    A large number such as the following should not be converted to scientific
    notation: 235436262343 

Using double quotes to wrap special  characters

Any text fields that contain non-alphabetic characters—such as, | \ * & or @ —  should be wrapped in quotes.

Here’s an example of how to enclose with double quotes a phrase that  contains pipes or commas: 

“Miller, Franklin and Jones | LLC”

In this example, a phrase containing asterisks is enclosed with a pair of double quotes: 

“ABC Co. * 1245484 * Invoice” 

Aggregation of multiple payments

If more than one payment to a supplier appears in a single payment file, Finexio will aggregate these payments into a one consolidated payment to that supplier. 

Field definitions 

Required fields

It’s important to include values for all required fields, which appear in bold in  the table below. Finexio insists on these required fields as the minimum necessary for successful payment delivery. These fields are used as  remittance advice, which the supplier can use to process the payment for the correct invoice.  Accurate values in these fields will ensure timely delivery of your payments.  

Unique fields

When submitting the payment file, there are a few fields for which Finexio  requires all values to be unique. This is because the values in the unique fields  serve as a key and reference for the associated payment.  

Please ensure any values in red are unique (appearing in red in the table below) and have no duplicate elsewhere in the payment file. This will prevent processing errors and delays.

Though they are not required fields, Buyer Account Number (BuyerAcct) and supplier address information is often very valuable if we encounter any issues delivering your payments.. Though it may not always be possible, doing so will help avoid delay in processing your payment files.


And click here to download payment file specification template.

If you are experiencing issues that none of our articles has helped you solve, please contact by clicking the button below:

Don't have an account yet? Book a demo today to see our product, first-hand.🚀

New to Finexio? Check out our getting started collection🐣

Looking for Finexio rates? Talk to us to better understand our pricing💰

Security Questions? We are certified to PCI Service Provider Level 1, learn more.🔒
Looking for answers to faq's? Please refer to Finexio faq's💬

Want to know more about AP payment solution? Check out our blog📣
Anything related to help topics? Please visit our helpcenter🚨

Check out our Website
Follow us on LinkedIn
Tweet with us on Twitter
Subscribe to our official Youtube channel

WANT TO KNOW MORE?🔎

👉 Optimize

If you'd like to know more, chat to us in the Messenger 😊


Did this answer your question?