Description
This document outlines the specifications of the generic file formats for Purchase Orders and Supplier Invoices used by SwiftPOS Software.
Note : Please ensure that you have ALL of the Suppliers set up correctly with all the relevant information for this import to work correctly.
It is intended for use by both internal and external developers and any other POS Suppliers who are interested in developing an industry standard for integration between Wholesalers and POS Systems. The basis of the design is that the Purchase Order structure matches the Supplier Invoice structure so it is possible to create a Purchase Order and lifecycle it into the software as a Suppliers' Invoice for testing purposes.
To Be Considered
- When requesting electronic invoices from LMG, request format 6. This format is described below. Note : Do not request format 5 and attempt to import it as a Metcash invoice as it will not be successful.
- Prior to Creating Purchase Orders
- Ensure the Supplier Details held in SwiftPOS Back Office are correct.
- Ensure the Business/Venue's ABN is recorded in the SwiftPOS Registration screen. This identifies the Business/Venue as the source of the document.
Operation
- Save the Invoice files from the emails received from the Suppliers in the default folder.
- Merge and append all the Invoice files into one large text (CSV) file.
- Once all Invoice files have been merged into one, delete the individual Invoice files from the folder.
- Using the Import File button from the Invoice Import menu item, import the text (CSV) file created in step 4 above.
Purchase Order File Format (PO)
- File Name Convention
The PO File Name structure is as follows:
Convention: YYYYMMDD00000*.txt Example: 2014052422464Metcash.txt |
- File Format Pre-Requisites
The PO File must comply with the following formatting rules:
|
- PO Header (Record Type H)
H, Account ID/Customer ID/Supplier ABN, Location ID, Clerk ID, Site ABN, PO Number, PO Date,,,
|
- PO Item (Record Type I)
I, Supplier Code, Item Description, Cost, Case Qty, Cases, Qty/Units, Total Excl Tax, Total Incl Tax, Total Tax,
|
- PO Delivery Details (Record Type D)
D, Delivery Address,,,,,,,,,
|
- PO Totals (Record Type T)
T, Item Count, Purchase Order Total Inc Tax,,,,,,,,
|
- Example of a PO File
H, "12223255", "0001", 1, "123456", "00011", 03/24/2014,,,, I, "500042", "THEAKSTONS OLD PECUL 330ML", 1.88, 24, 2, 3, 95.88, 95.88, 0.00, I, "500131", "MCCALLUMS SCOTCH 1125ML", 31.20, 12, 2, 0, 748.80, 748.80, 0.00, I, "500173", "RENMANO R/BRZ RIESLING 750ML", 2.85, 12, 0, 6, 17.10, 17.10, 0.00, D, "Ring the bell at the back door Deliveries only between 8am and 2pm Monday to Friday",,,,,,,,, T, 3, 312.00, 0.00,,,,,,, |
Supplier Invoice File Format (INV)
- File Name Convention
The INV File Name structure is as follows:
Convention: YYYYMMDD*.inv Example: 20140524Metcash.inv |
- File Format Pre-Requisites
The INV File must comply with the following formatting rules:
|
- INV Header (Record Type H)
H, Account ID, Location ID,, Supplier?s ABN, INV Number, INV Date, Admin Fees, Document Type, PO Number,
|
I, Stock Code, Description,, Case Qty, Cases, Qty/Units, Total Excl Tax,, Total Tax,
|
- INV Delivery Details (Record Type D)
D, Delivery Address,,,,,,,,,
|
- INV Totals (Record Type T)
T, Item Count, INV Total Excl Tax, INV Total Tax, Freight Excl Tax, Freight Tax, Discount,,,,
|
Note : Invoice Total + Tax is the amount the Supplier is to be paid net of freight/discounts & rounding. |
- Example of a INV File with multiple Invoices
The software will attempt to match the ?A/c ID ? field supplied in the Invoice Header with the field called ?Account No:? in the Supplier Details menu. If there is no match it will try matching the ?Supplier?s ABN? field with the field called ?Supplier ABN? in the Supplier Details menu.
|
Related Topics