NOTE: This solution is only used by existing suppliers who already submit customer-specific price information in this way.
Other suppliers should use the Excel template and the procedure described there.
Text file (file specification)
The price file is provided as a text file, i.e. a DOS/ASCII file.
Instructions
The record type code in position 1 determines how a record is to be interpreted.
A = Agreement record
P = Price record
R = Discount record
F = Packaging price record
T = Text record for messages
The first record must always be an Agreement record. The other record types are not mandatory. This means that it is not necessary to submit Price records when submitting Discount records, or vice versa.
All numeric fields (Type=N) in a record must always be completely filled with the specified number of characters. If a field is to be left without a value, it must be filled with the correct number of 0s (zeros). If the number of characters is fewer than the number that fit in the field, the field must be filled with leading 0s before the specified value. No decimal separators are used; the decimal places are determined by the position of the number within the field.
All information in alpha fields (Type=A) must be left-aligned.
Several price lists can be included in the same file, provided that the same Agreement ID is not used for different customers in the same file and that there are no blank lines.
File description
Layout post type A (Agreement record)
|
Pos |
Len |
Dec |
Type |
Description |
Mandatory |
Remarks / Explanation / Example |
|
1 |
1 |
|
A |
"A" |
YES |
Agreement record, always written as A. |
|
2 |
20 |
|
A |
Avtals-id |
YES |
The supplier’s ID for the agreement.
|
|
22 |
12 |
0 |
N |
Leverantör |
YES |
The supplier’s ID with Finfo.
|
|
34 |
15 |
|
A |
Kund-id |
YES |
The supplier’s customer number for the party covered by the agreement.
|
|
49 |
8 |
0 |
N |
Första aktiverings-datum |
YES |
The date when the agreement should first be activated in Finfo. Should be entered at least 2 weeks before the agreement takes effect, to allow time for the subscriber’s calculations, etc. Written as YYYYMMDD. Future agreement updates (effective date or distribution date) are handled in R or P records. |
|
57 |
8 |
0 |
N |
Gäller t.o.m. |
YES |
The date when the agreement expires. Written as YYYYMMDD. 99999999 = until further notice. |
|
65 |
1 |
|
A |
Ansvarskod |
YES |
L/A/K (Supplier/Subscriber/Chain). Indicates who submitted the agreement and who should be notified if errors are found in the file. |
|
66 |
12 |
0 |
N |
Ansvarig abo |
YES |
The chain’s order number with Finfo. Only entered if the responsibility code is "K". Otherwise, enter 000000000000. |
|
78 |
1 |
|
A |
Avtalstyp |
YES |
N = Net price agreement
|
|
79 |
1 |
|
A |
Renskod |
NO |
Blank = no clearing.
|
|
80 |
1 |
0 |
A |
Kod för gällandedatum |
NO |
J = code used to indicate from which date the prices or discount groups apply. |
Layout post type P (Price record)
|
Pos |
Len |
Dec |
Type |
Description |
Mandatory |
Remarks / Explanation / Example |
|
1 |
1 |
- |
A |
"P" |
YES |
Price record, always written as P. |
|
2 |
20 |
- |
A |
Avtals-id |
YES |
The supplier’s ID for the agreement. Same as in the Agreement record. |
|
22 |
18 |
- |
A |
Artikelnr |
YES |
The supplier’s article number. |
|
40 |
15 |
8 |
N |
Pris |
YES |
Net price or list price per base price unit as stated in the general article file. Agreement type N = net price, C = list price, as specified in the A record. |
|
55 |
8 |
0 |
N |
Distributions-datum |
YES |
The date when the agreement should be sent to the customer. The date should be at least 2 weeks earlier than the effective date to ensure timely delivery to the subscriber. If the same date as stated in the Agreement record applies, or if the changes should take effect immediately, write 00000000. |
|
63 |
8 |
0 |
N |
Gällandedatum |
NO |
The date when the price becomes effective. Written as YYYYMMDD. Mandatory if the code for effective date in the A record = J. |
Layout post type R (Discount record)
|
Pos |
Len |
Dec |
Type |
Description |
Mandatory |
Remarks / Explanation / Example |
|
1 |
1 |
- |
A |
"R" |
YES |
Discount record, always written as R. |
|
2 |
20 |
- |
A |
Avtals-id |
YES |
The supplier’s ID for the agreement. Same as in the Agreement record. |
|
22 |
5 |
- |
A |
Rabattgrupp |
YES |
The discount group to which the discount rate applies. The discount group must exist on the articles in the general article file in order for the subscriber’s net prices to be calculated. |
|
27 |
4 |
2 |
N |
Rabattsats |
YES |
Used to calculate the net price, based on the base price. Example: a discount of 2% is written as 0200. |
|
31 |
8 |
0 |
N |
Distributionsdatum |
YES |
The date when the agreement should be sent to the customer. The date should be at least 2 weeks earlier than the effective date to ensure timely delivery to the subscriber. If the same date as stated in the Agreement record applies, or if the changes should take effect immediately, write 00000000. |
Layout post type F (Package record)
|
Pos |
Len |
Dec |
Type |
Description |
Mandatory |
Remarks / Explanation / Example |
|
1 |
1 |
- |
A |
"F" |
YES |
Package price record, always written as F. |
|
2 |
20 |
- |
A |
Avtals-id |
YES |
The supplier’s ID for the agreement. Same as in the Agreement record. |
|
22 |
18 |
- |
A |
Artikelnr |
YES |
The supplier’s article number. |
|
40 |
15 |
8 |
N |
Pris |
YES |
Net price for the packaging unit. |
|
55 |
8 |
0 |
N |
Distributionsdatum |
YES |
The date when the agreement should be sent to the customer. The date should be at least 2 weeks earlier than the effective date to ensure timely delivery to the subscriber. If the same date as stated in the Agreement record applies, or if the changes should take effect immediately, write 00000000. |
|
63 |
8 |
0 |
N |
Gällandedatum |
NO |
The date when the price becomes effective. Written as YYYYMMDD. Mandatory if the code for effective date in the A record = J. |
|
71 |
14 |
- |
N |
GTIN |
YES |
The GTIN of the packaging unit to which the price applies. |
Layout post type T (Text record for messages)
|
Pos |
Len |
Dec |
Type |
Description |
Mandatory |
Remarks / Explanation / Example |
|
1 |
1 |
- |
A |
"T" |
YES |
Text record, always written as T. |
|
2 |
20 |
- |
A |
Avtals-id |
YES |
The supplier’s ID for the agreement. Same as in the Agreement record. |
|
22 |
8 |
0 |
N |
Distributionsdatum |
YES |
If the same date as stated in the Agreement record applies, write 00000000; otherwise, enter the desired activation date for the text record. This date should correspond with the other dates to ensure that the text record is distributed at the same time as the other records. |
|
30 |
2 |
0 |
N |
Radnr |
YES |
Sequence number within the same date: 01, 02, etc. |
|
32 |
45 |
- |
A |
Text |
YES |
Free text that the supplier controls and is responsible for. It is sent as a separate paragraph in the price notification from Finfo. |