Technical guide

Sending the invoice interface file — File 100

To send data to Segment in File 100 format, the file contains 4 record types. Below are the structure of each record, field positions and sizes, and an example file.

Guidelines for sending the invoice file (File 100)

To send data to Segment in File 100 format, the file contains data in 4 record types:

RecordContentOccursRequired
0Invoice detailsOnce per invoiceYes
1Delivery note details within the invoiceAfter record 0 — one per delivery noteYes
2Delivery note linesAfter record 1 — one per lineYes
3Israel Invoices allocation numberA single summary record per invoicePer Tax Authority instructions and the customer’s guidelines — mandatory for invoices over ₪5,000

Record types explained

RecordMust be followed byTotals that must match
0 — InvoiceType 1 record(s) belonging to the same invoiceTotal of the delivery note lines (record 1) = invoice total (record 0)
1 — Delivery noteType 2 record(s) belonging to the same delivery note, in the same invoiceTotal of the lines (record 2) = delivery note total (record 1)
3 — SummaryA single record per invoiceThe invoice’s summary record

Record type 0 (invoice details)

PositionSizeField nameDescriptionRequired
1-11Record typeConstant “0”Yes
2-65FILLERFILLER, constant zerosYes
7-1610Vendor numberThe vendor’s number at the customerYes
17-226Invoice dateFormat YYMMDDYes
23-3210Invoice no.The invoice number the delivery notes are attributed toYes
33-4410.2Gross amountInvoice gross total – excluding VAT and discounts.Yes
45-5610.2Regular discountInvoice total regular discount – excluding VATNo
57-6810.2Promotional discountInvoice total promotional discount – excluding VATNo
69-722.2Total rounding (incl. VAT)Example: 52.19 is written 5219
Example: 1.5 is written 0150
No
73-808FILLERFILLER, constant zerosYes
81-9210.2VAT amountVAT amountYes
93-953CurrencyILS, USD, EUR. Default 000 = ILSNo
96-1004FILLERFILLER, constant zerosYes
201-23030Long invoice numberIf the invoice number is longer than 10 charactersNo
231-2362.4Exchange rateOptional. Example: 3.7612 is sent as 037612No
237-26630Transaction numberOptionalNo
267-28112.3Index-linkage amountOptionalNo

Record type 1 (delivery note details)

PositionSizeField nameDescriptionRequired
1-11Constant “1”Record typeYes
2-1110Store numberThe customer’s store / branch / project numberYes
12-2110Delivery note numberThe number shown on the delivery note sent by the vendor. For return notes, enter the chain’s return note numberYes
22-221Document type0 = return. 1 = regular receipt.Yes
23-286Document dateThe date on the document, format YYMMDDYes
29-3810Receipt (“Bul”) numberThe chain’s receipt (“Bul”) number – the branch’s goods-receipt document numberYes
39-7133FILLERFILLER, constant zeroYes
72-8615Additional referenceOptionalNo
87-9711Purchase order numberPad with leading zeros to the left of the order number if space remains. Example: order 998121 is written 00000998121No
98-1003FILLERFILLER, constant zeroYes
101-11515Tax invoice / transaction invoice numberFor cases where the settlement document is a tax invoice or transaction invoice. In that case, send zeros in fields 12-21 and 29-38No

Notes

FieldNote
Store numberthe branch number in the chain. If you use “branch code conversion”, make sure the conversion is up to date in Segment.
You can always check this in the Segment portal under “Update branch details”, manually or from an Excel file. Make sure the branch number matches the branch number on the delivery / receipt note.
Delivery note no.make sure a receipt exists for the delivery note. The receipt must reach Segment and appear in the portal under “Deliveries”.
You can omit this value and rely only on the “Receipt (Bul) no.” – fill the field with “0” values instead. In that case a valid receipt number matching the data received from the chain is required.
Receipt (Bul) no.you can omit this value and rely only on the “Delivery note number” – fill the field with “0” values instead. In that case a valid delivery note number is required.
If the chain allows an invoice to settle more than one delivery note – define a new type “1” record for each delivery note.

(!) Also check each chain’s own conditions – for example, if the chain allows an invoice to contain more than one delivery note but only for the same branch / store number, all delivery notes in the invoice must have the same store number.

Record type 2 (delivery note lines)

PositionSizeField nameDescriptionRequired
1-11Constant “2”Record typeYes
2-1413Customer item no.The item number in the customer’s catalog.Yes
15-2713Vendor item no.The item number at the vendorYes
28-281Sales unit type0 = units 1 = packagesYes
29-355.2Unit quantityIf this field contains data, it overrides the value in field 201-211Yes
36-383Quantity per packageRequired when the sales unit type = 1Yes
39-413Number of packagesRequired when the sales unit type = 1Yes
42-527.4Unit priceUnit price excluding VATYes
53-615.4Item discountItem discount amountNo
62-7918Long customer catalog item no.For long item codes. In that case, send zeros in field 2-14No
80-845Order line numberConstant zeros if none. Pad with leading zeros to the left of the number. Example: 00005No
85-895Delivery note line numberConstant zeros if none. Pad with leading zeros to the left of the number. Example: 00005No
90-10011Purchase order numberPad with leading zeros to the left of the order number if space remains. Example: order 998121 is written 00000998121No
201-2117.4Long unit quantityFor quantities with 4 digits after the decimal point. In that case, send zeros in field 29-35No
212-22110Order sub-line numberOptionalNo
222-23612.3Index-linkage amountOptionalNo

Notes

FieldNote
Customer item numberthe chain’s item code as it appears in its catalog. If you use the “Vendor item code” instead, make sure the “Customer item code” is filled with “0” values.
Vendor item numberthe vendor item code as defined by the vendor in “Vendor item conversion”. Make sure the data is up to date – you can always check this in the Segment portal under Catalog -> “Update item details”, manually or from an Excel file. If you don’t use this field, fill it with “0” values.
Make sure the customer item code and vendor item code fields are in the correct positions. Mixing up or swapping their positions will cause an error.
The comparison is made against the chain’s receipt document -> so if there is an error, compare your data with the chain’s receipt data.

Make sure the items, prices and quantities in the receipt documents match the data in File 100 – otherwise an error will be returned.

Record type 3 (Israel Invoices allocation number)

PositionSizeField nameDescriptionRequired
1-11Constant “3”Record typeYes
2-2625Sender licensed dealer no.The vendor’s licensed dealer (VAT) number – the invoice senderNo
27-5125Recipient licensed dealer no.The customer’s licensed dealer (VAT) number – the invoice recipientNo
52-8635Invoice allocation numberThe allocation number received from the Tax Authority for this invoiceYes
87-10014FILLERFILLER, constant zerosYes

Notes

This record type is mandatory for invoices over ₪5,000, in line with Tax Authority requirements. Invoices above this amount that do not contain this record type will fail validation.

Handling negative values

Below is the translation table for the minus sign “-” in negative values. Replace the last digit in the field with the corresponding letter:

Digit to replace0123456789
Replace with letter{JKLMNOPQR

Need help connecting?

Our support team will guide you through setting up the interface.

Contact support