- Contents
- Index
- Search
Display results with all search words
File Specifications
Learn about the detail about how the supplier's file must be formatted in order for the import process to work.
The file must be separated into three sections:
- Header section - Contains information of the invoice header;
- Transaction section - Contains information of the invoice line;
- Detail section - Contains information of the lot and dimension detail linked to the invoice line.
Each line in the file must have a Record ID, which identifies the section it relates to. The file is comma delimited, and must contain:
Header Section:
|
Field |
Type |
Size |
Comment |
|
Record ID |
Character |
1 |
Must equal 1 |
|
Transaction Type |
Character |
5 |
Must equal APINV |
|
Invoice Reference |
Character |
20 |
Maps to AP Invoice Reference |
|
Date |
Character |
10 |
Maps to AP Invoice Document Date (must be dd/mm/yyyy) |
|
Supplier No. |
Character |
6 |
Maps to Greentree Supplier Code |
|
Warehouse |
Character |
2 |
Maps to valid Greentree stocking location (this is the receiving location for all invoice lines). |
|
Narration |
Character |
20 |
[Optional] Maps to AP Invoice header narration |
|
Net Invoice Value |
Numeric |
12,2 |
Represents total net invoice value.
|
|
Total Tax Value |
Numeric |
12,2 |
Represents total invoice tax value. |
|
Gross Invoice Value |
Numeric |
12,2 |
Represents total invoice gross value. |
See
Header Line Example:
1,'APINV','3782457640','08/11/2005','CHHW','01','ROTOITI 810',26391.70,2639.17,29030.87
Transaction Section:
|
Field |
Type |
Size |
Comment |
|
Record ID |
Character |
1 |
Must equal 2 |
|
Inventory Item |
Character |
20 |
Maps to Supplier Inventory Item Code for an active Greentree Item Code - invoice line will be populated with the Greentree Inventory Item Code. |
|
Quantity |
Numeric |
8,4 |
Total quantity for invoice line.
A transaction line will be repeated within a file where the are multiple detail lines for it multiple lots and/or dimensions). |
|
Unit Cost |
Numeric |
8.4 |
Maps to invoice line unit cost, exclusive of tax.
|
|
Pricing Unit |
Character |
4 |
Maps to invoice line unit of measure. This must be a valid UOM defined for the inventory item. It can be either the stocking UOM or the purchasing UOM - Greentree will handle any UOM conversions if they exist. |
|
Tax Rate |
Numeric |
2,2 |
Maps to invoice line tax percentage. |
|
Net Value |
Numeric |
12,2 |
Maps to net value of the line (tax exclusive). |
|
Narration |
Character |
20 |
[Optional] Maps to AP invoice line narration. |
Transaction Line Example 1:
2,'2026696',1036.803,1.32,'MTR',10,1368.58,'3532565458',,
Transaction Line Example 2:
2,'2026696',1036.803,1.32,'MTR',10,1368.58,'3532565458',,
3,'RM00102138',16,64.8,'B',,,,,
2,'2026696',1036.803,1.32,'MTR',10,1368.58,'3532565458',,
3,'RM00102139',16,64.8,'B',,,,,
2,'2026696',1036.803,1.32,'MTR',10,1368.58,'3532565458',,
3,'RM00102137',16,64.8,'B',,,,,
2,'2026696',1036.803,1.32,'MTR',10,1368.58,'3532565458',,
3,'RM00102140',16,64.8,'B',,,,,
2,'2026696',1036.803,1.32,'MTR',10,1368.58,'3532565458',,
The second example demonstrates how lot or dimension detail lines are for transaction lines within the file. Where quantities associated with multiple lots and/or dimensions make up the line quantity, the transaction line (Record ID = 2) repeats within the file - this is identifiable because the same item number is referenced in each repeating line.
Following each repeating line is the detail line (Record ID = 3), which contains lot/dimension detail of the line. The example above indicates that there is one transaction line for item 2026696, and this consists of 4 lots: RM00102138, RM00102139, RM00102137, RM00102140. See the next section for information about what is contained in the detail line (Record ID = 3).
|
|
As indicated in the mapping specification for transaction lines, the total line quantity for the line will be calculated using the sum of quantities for each detail line attached to it. |
Detail (Lot/Dimension) Section:
|
Field |
Type |
Size |
Comment |
|
Record ID |
Character |
1 |
Must equal 3 |
|
Lot Number |
Character |
12 |
Maps to the lot number associated with the transaction line. |
|
Quantity |
Character |
4 |
Maps to the integer piece) quantity for lot and dimension. The process applies dimension conversions and UOM conversions (where the transaction line Pricing Unit is not equal to item's stocking UOM) to convert this value into the stocking unit of measure, so that the total transaction line quantity can be derived.
The transaction line quantity is calculated using the sum of the stocking UOM quantities of the detail lines. |
|
Dimension |
Numeric |
2,2 |
Maps to the dimension associated with the lot and quantity in the line. |
|
Unit Type |
Character |
1 |
Must equal P (indicates line quantity is a piece count). |
Detail Line Example 1:
3,'436951',10,2.4,'P'
Detail Line Example 2:
2,'1234',380.4,4.8,'MTR',0,1825.92,'J323',,
3,'436951',10,2.4,'P',,,,,
3,'436951',40,3.9,'P',,,,,
3,'436951',15,4.2,'P',,,,,
3,'436951',23,4.8,'P',,,,,
3,'436951',5,5.4,'P',,,,,
The second example demonstrates a repeating lot detail line, indicating that there are multiple dimensions of the lot. In this example, there are 5 dimensions for lot 436951. They are: 2.4, 3.9, 4.2, 4.8, and 5.4.
When the file is processed, Greentree calculates transaction line quantities using the sum of dimension quantities, derived from detailed lines where the piece count for each dimension is converted into a stocking unit of measure quantity for each dimension). This quantity is then multiplied by the unit cost in the transaction line (Record ID = 2).
The sum of all calculated transaction line quantities is then compared to the total net invoice value in the header line (Record ID = 1). If this values are equal, no adjustment is required. If they are not equal, a GL adjustment line is created and added to the AP Invoice, using the general ledger account specified on the import process form.
Adjustments may be required due to roundings of the conversions of dimension piece quantities to stocking UOM quantities.