Sales invoices are used in Scan-Based Trading (SBT), Scan-sales Invoicing (SSI), and other services. The invoice is based on the quantity (Qty) of supplier items sold at the store. Sales invoices begin with a Data Type of SLSINV.
These invoices are generated automatically based on the schedule set up for your trading partnership. They cannot be run online.
Note: As long as one or more line items are present, invoices are generated even when the net amount is zero. For example, an item is sold for $1.00 (debit), but another item is returned for $1.00 (credit). Generating a zero invoice ensures that all financial item movement is tracked.
Seq |
Col |
Field Name |
Description |
1 |
A |
Data Type |
The type of item movement being invoiced. SLSINV for Sales Invoices. |
2 |
B |
Supplier Name |
Supplier's corporate name. |
3 |
C |
Supplier ID |
Supplier's Park City Group Business Unit ID (BU ID). |
4 |
D |
Retailer Invoice ID for Supplier |
ID used by retailer to reference supplier in invoices. This can be set up in the Store Supplier Profile, or it can be defaulted based on the Service Agreement established for the trading partnership.
|
5 |
E |
Supplier DUNS |
Supplier's 9-digit DUNS (Dun & Bradstreet assigned) number. |
6 |
F |
Supplier DUNS Suffix |
The 4 digits of a supplier's DUNS +4. This is a suffix to the supplier's 9-digit DUNS.
|
7 |
G |
Supplier Address 1 |
First line of supplier's street address. |
8 |
H |
Supplier Address 2 |
Second line of supplier's street address. |
9 |
I |
Supplier City |
City associated with supplier's street address. |
10 |
J |
Supplier State |
State associated with supplier's street address. |
11 |
K |
Supplier Zip |
ZIP or other postal code associated with supplier's street address. |
12 |
L |
Retailer Name |
Retailer's corporate name. |
13 |
M |
Retailer ID |
Retailer's Park City Group Business Unit ID (BU ID). |
14 |
N |
Supplier Invoice ID for Retailer |
ID used by supplier to reference retailer. |
15 |
O |
Retailer DUNS |
Retailer's 9-digit DUNS (Dun & Bradstreet assigned) number. |
16 |
P |
Retailer DUNS Suffix |
The 4 digits of a retailer's DUNS +4. This is a suffix to the retailer's 9-digit DUNS. |
17 |
Q |
Retailer Address 1 |
First line of retailer's street address. |
18 |
R |
Retailer Address 2 |
Second line of retailer's street address. |
19 |
S |
Retailer City |
City associated with retailer's street address. |
20 |
T |
Retailer State |
State associated with retailer's street address. |
21 |
U |
Retailer Zip |
ZIP or other postal code associated with retailer's street address. |
22 |
V |
Store ID |
Park City Group internal ID used to reference store. |
23 |
W |
Store Name |
Retailer's name for the store. |
24 |
X |
Retailer Store ID |
ID used by retailer to reference the store. |
25 |
Y |
Supplier Store ID |
ID used by supplier to reference the store. |
26 |
Z |
Store Address 1 |
First line of stores street address. |
27 |
AA |
Store Address 2 |
Second line of stores street address. |
28 |
AB |
Store City |
City associated with stores street address. |
29 |
AC |
Store State |
State associated with stores street address. |
30 |
AD |
Store Zip |
ZIP or other postal code associated with stores street address. |
31 |
AE |
Warehouse ID |
The retailer's ID for the warehouse or distribution center to which the sales / delivery store is assigned. Empty if no warehouse assignment |
32 |
AF |
Invoice ID |
The invoice number or ID. If this is an original invoice, it is the same as the Original Invoice Number. If this is a replacement or reversal invoice, this number will be different from the original. |
33 |
AG |
Invoice Date |
The date of the invoice in 8-character calendar-date format YYYYMMDD. |
34 |
AH |
Julian Invoice Date |
The date of the invoice in 7-character Julian-date format YYYYDDD. |
35 |
AI |
Invoice Type |
Code designating whether this is an original invoice or part of an update. Valid values: Original, Original Addendum ##, Replacement Addendum ##, Error Reprocessed Addendum ##. If invoice is an addendum to the original, a two-digit number is included to list the addendum sequence. Replacement Addendums are sent when the original invoice was incorrect. For example, when an incorrect go-live date was set in a Store Supplier Profile. In a Replacement Addendum, all item quantities are signed negative to zero-out the original invoice amount. Error Reprocessed Addendums are the result of automatic sales or delivery reprocessing in Park City Group. |
36 |
AJ |
Original Invoice ID |
The ID of the original invoice. Relevant if the invoice sent in this record is a reversal or replacement invoice. |
37 |
AK |
Source |
Why the invoice was generated. For example:
|
38 |
AL |
Invoice Total |
Total net amount due.
|
39 |
AM |
Deposit Total |
The net amount charged by the seller (Supplier) to the buyer (Retailer) for deposit charges on items sold in the store. Calculated as the Debit portion of Deposits minus the Credit portion of Deposits, with rounding and extending rules applied. If no item deposits are included in the store's transactions, this field will contain a zero value. |
40 |
AN |
Total Low CU Invoiced |
Total quantity of items included in this invoice. Quantity calculation is based on the lowest consumer unit (CU) or sell unit of every item. This is normally the each (versus the case). Important: Quantity is conditional on the "Invoice is Debit/Credit" field.
|
41 |
AO |
Nbr of Line Items in Invoice |
Total number of items invoiced. For example, Item A, Item B, and Item C equals three line items. This is not the quantity moved for each item.
|
42 |
AP |
Invoice is Debit/Credit |
Designates whether this is a debit invoice or a credit invoice.
|
43 |
AQ |
Document ID |
The supplier's document number or ticket number associated with the invoiced transactions.
|
44 |
AR |
Addendum Nbr |
Sequential number automatically assigned to updated sales or deliveries. If the invoice is based on scan-sales, this number is incremented as a result of a manually-submitted sales addendum or automatic error reprocessing. If the invoice is based on deliveries, this number is incremented for deliveries that underwent automatic error reprocessing. This field will contain a 0 (zero) if no addendums or reprocessing occurred. |
45 |
AS |
Tracking ID |
This is any ID provided by the data sender to identify a batch sent to Park City Group. Usually originating from the retailer, this is commonly used to track transactions by supplier. |
46 |
AT |
Item Nbr |
Supplier's item order number. |
47 |
AU |
Item Description |
Supplier's description or name of the item. |
48 |
AV |
UPC Type |
Format of the product code. Value Description UABC...... UPCA 10 digits in format 0-5-5-0 UAUI........ UPCA 11 digits in format 1-5-5-0 UAUA...... UPCA 12 digits in format 2-5-5-0 UAUP...... UPCA 12 digits in format 1-5-5-1 UACD...... UPCA 11 digits in format 0-5-5-1 UAAD...... UPCA 13 digits in format 2-5-5-1 UA3D....... UPCA 14 digits in format 3-5-5-1 UA30....... UPCA 13 digits in format 3-5-5-0 UAZS....... UPCA 6 digits zero suppressed EAUA...... EAN 12 digits in format 2-5-5-0 EAAD...... EAN 13 digits in format 2-5-5-1 GT3D....... GTIN 14 digits in format 3-5-5-1 ZZ Private Product Code up to 15 characters.
|
49 |
AW |
UPC |
UPC or other product code. |
50 |
AX |
SKU |
If available, the retailer's stock keeping unit (SKU) assigned to the item. |
51 |
AY |
Item is Debit/Credit |
Designates whether this item is a debit or a credit on the invoice. |
52 |
AZ |
Unit of Measure |
The unit of measure associated with the items moved. For example, EA for each, CA for case, or OZ for ounce. |
53 |
BA |
Qty |
Quantity of the number of units moved (sold, delivered, counted). Important: Value is conditional on the whether the invoice is a debit or credit.
|
54 |
BB |
Net Cost |
The net cost of the item, after any allowance. |
55 |
BC |
Allowance |
Any allowance against the base cost. |
56 |
BD |
Base Cost |
The base cost of the item in Park City Group. The amount is based on the item level reported to Park City Group, such as by the case, inner-pack, or each. For example, if the supplier-item cost is based on the case, and the:
|
57 |
BE |
Total Retail Amount |
Total Retail units sold x Retail Price. |
58 |
BF |
Retail Selling Class |
The retail pricing classification of the units sold. RG Sold at the regular retail price PR Sold at the promotional price MC Manufacturer coupon RC Retailer coupon SC Store coupon M1 through M9 Sold at the 1st to 9th markdown price OT Other
|
59 |
BG |
Retail Unit Multiple |
Units sold for the Retail Price. For example, 2 for $1.30. The 2 is the Retail Unit Multiple. |
60 |
BH |
Retail Unit Price |
The retail price of the item. For example, 2 for $1.30. The $1.30 is the Retail Price. |
61 |
BI |
Extended Product Cost |
The Qty x Net Cost. |
62 |
BJ |
Deposit |
Any deposit assigned to the item in the jurisdiction in which it is sold. The amount is based on the item level reported to Park City Group, such as by the case, inner-pack, or each. |
63 |
BK |
Extended Deposit |
The Qty x Deposit |
64 |
BL |
Extended Cost |
The (Qty x Net Cost) + Extended Deposit Amount. |
65 |
BM |
Movement Type Code |
Will always be empty unless the trading partnership is set up to send/receive Movement Type information. Also called "Sales Type," a Movement Type can be included in sales or delivery data sent inbound to Park City Group. When sent with sales data, it is used to describe the type of sales-transaction performed on the item. For example, it can contain a code stating that an item sale was: Invoiced at the regular cost. Invoiced at a special cost. An inventory adjustment only. A store-to-store transfer. A core exchange, such as an automotive part. Movement Types are pre-defined by the retailer or supplier, in cooperation with Park City Group. When received, Park City Group performs the defined type-specific processing for invoicing and other functions. When included in an invoice, this field simply passes on the Movement Type sent to Park City Group, and is included for the receiver's information only. |
66 |
BN |
Retailer Defined Value 1 |
Contains extra information requested by the retailer for special processing or tracking. For example, a Sales / Distribution Code or a Department Number. This field will be empty if not pre-defined or applicable to the transaction. |
67 |
BO |
Retailer Defined Value 2 |
Contains extra information requested by the retailer for special processing or tracking. For example, a Sales / Distribution Code or a Department Number. This field will be empty if not pre-defined or applicable to the transaction. |
68 |
BP |
Retailer Defined Value 3 |
Contains extra information requested by the retailer for special processing or tracking. For example, a Sales / Distribution Code or a Department Number. This field will be empty if not pre-defined or applicable to the transaction. |
69 |
BQ |
Invoice Service Fee Total
|
Empty for most clients. This fee can be used in place of shrink quantities for reimbursing supplier item loss. Based on a simple percentage of total sales, fee can be configured for calculation before or after deposits are added. "Capping" limits and other rules can also be applied. For example, a typical service fee might be 1.5% of sales before deposits. Please note that service fee is NOT included in "Invoice Total".
|
70 |
BR |
Customer Defined Net Cost |
Customer-provided net cost used in invoice calculations. Normally used when transactions rely on retailer-provided data instead of supplier-maintained PCG item catalog. |
71 |
BS |
Customer Defined Allowance |
Customer-provided cost allowance used in invoice calculations. Normally used when transactions rely on retailer-provided data instead of supplier-maintained PCG item catalog. |
72 |
BT |
Customer Defined Base Cost |
Customer-provided base cost used in invoice calculations. Normally used when transactions rely on retailer-provided data instead of supplier-maintained PCG item catalog. |
Updated 1/24/2012