Upload Manually
How to upload files manually.
Last updated
How to upload files manually.
Last updated
Files can be uploaded manually by navigating to Transactions>File Uploads and clicking on 'Upload File'. You can then drag and drop the file into the box area, or click inside it to select and upload from your computer:
There is an option to Auto commit uploaded invoices, by selecting this toggle in advance of loading a file, the bookings will be automatically submitted to the Buyer for review, provided there is no error in the file:
Once you select 'upload' you will receive an on screen notification that your file upload is in progress. For smaller files, you may find that once you close the notification box that your transactions are ready to review. For larger files, you can view the progress of your file submission immediately in Settings>Data Delivery. An email notification summarising the upload is sent upon completion of the load. These are configurable under the Notifications Settings page.
If Auto commit uploaded invoices has not been selected, once the transactions upload is complete they are displayed in the grid on the upload page. You can commit them to the Buyer by using the 'select all function' and then clicking the commit button on the bottom left:
Once you have selected 'commit' the transactions are then available in the bookings grid for review by both the Buyer and Seller.
Transactions may be flagged in the Upload grid, requiring action before they can be committed. This is a validation step in which any missing or incorrect fields such as Partner name or Commercial link name can be manually updated before the transactions are submitted to the buyer.
The status column will show whether transactions match, or not. If there is no match then details of the issue will be shown in the Description column and the fields with missing data will be underlined in red. A warning exclamation mark and underlining will be used to highlight a possible duplicate booking.
You can apply a filter to view the transactions with warnings only.
If a file is uploaded with records that have Commercial Links on 'pending' status, the Seller will be notified with a yellow warning tag with a hover over message detailing the CL status. The CL description field will also be highlighted. It is important to note that these records can be committed to the Buyer for review, however unless the CL is changed to 'Live' status by the CL owner prior to the end of the Buyer review period the transaction will be voided at cycle start. Sellers using automated file submission (FTP and email delivery methods) will receive email notification of the CL status.
Below is an overview of the Upload grid, with each column header, and a description of the content. As with other grids, you can use the 'columns' button to add and remove columns you find useful or not.
Column
Description
Checkbox selector
Gives the ability to select single or multiple records. Note - when the status is 'not Matched' the checkbox selector can be ticked, however a=items with this status cannot be committed.
Partner name
Buyer Name – pulled from Seller Invoice File through the ABTA number. Can be empty and edited by the user
Partner ID Type
The ID Type associated with the Buyer (ABTA, IATA, TIDS)
Partner ID
The ID associated with the Buyer
Booking Ref
Transaction Reference – pulled from the Seller Invoice file – non-editable
Lead Name
Lead passenger name – pulled from the Seller Invoice file – non-editable
Dep date
Booking departure date – pulled from the Seller Invoice file – non-editable
Due
Transaction payment due date – matches the transaction upload date.
Amount
Amount due for the transaction – pulled from the transaction amount field of the Seller Invoice file - non-editable
CL Description
This will be the commercial link between the seller and the buyer, based on ABTA IDs in the file
Status
Transaction status.
Matched – Partner Name and CL Description matching values in the database.
Not Matched (see Description column for details)
Description
Error description when the status is not matched.