GS1 fields (GLN, GTIN)

How to carry the GS1 EDI data that retail and FMCG partners rely on (GLN, GTIN, delivery and receiving advice references, batch and expiry) in a Peppol BIS Billing 3.0 invoice sent through Unimaze.

Slovenská verzia: Polia GS1 (GLN, GTIN)

From 1 January 2027, invoices between Slovak companies must be Peppol BIS Billing 3.0 invoices. That replaces EDIFACT INVOIC, which many companies in fast-moving consumer goods (FMCG), retail and pharma exchange today through GS1 EDI. Those invoices carry data that the buyer's processes depend on, such as store GLNs, GTINs, receiving advice numbers and batch numbers.

GS1 Slovakia and GS1 Czech Republic have published a recommendation for where that data goes in a BIS 3.0 invoice. The Slovak Financial Administration has made Peppol providers aware of it. This page shows how to send and read those fields with Unimaze.

📘

What the recommendation is, and isn't

  • It is voluntary. It does not change what the law or the Slovak specification requires, and the invoice must still meet the Slovak requirements.
  • It uses only fields that already exist in BIS 3.0 and passes Peppol validation. There is no new customization or profile ID, so you send the invoice as usual.
  • Agree with your trading partner which fields you'll fill in. A buyer can only use what it expects.
  • The source is GS1's spreadsheet PEPPOL-BIS3.0_SK_FMCG.xlsx, published on gs1sk.org/e-faktura. This page follows version 1.11. If GS1 publishes a newer version, the spreadsheet takes precedence.

Sending and receiving

You send these invoices the same way as any other invoice in Slovakia (see Sending an invoice):

Transaction Services covers every field on this page except the supplier's order number (BT-14). If you need to send it, contact Unimaze support. Meanwhile, you can send it on each line in the supplier_order_number item property.

📘

Receiving these invoices

If your trading partners send you these fields, read the received invoice as UBL XML with GET /api/v1/messages/{messageId}/documents/core. The XML contains every field the sender filled in, including all cac:AdditionalItemProperty elements.

Document references

GS1 fieldBusiness termBIS 3.0 XPath (under Invoice/)Transaction Services property
Customer's order numberBT-13cac:OrderReference/cbc:IDorderReference.documentNo
Supplier's order numberBT-14cac:OrderReference/cbc:SalesOrderIDNone yet. Contact Unimaze support
Delivery note numberBT-16cac:DespatchDocumentReference/cbc:IDdocumentReferences.despatch.documentNo
Receiving advice number (RECADV)BT-15cac:ReceiptDocumentReference/cbc:IDdocumentReferences.receipt.documentNo
Contract numberBT-12cac:ContractDocumentReference/cbc:IDdocumentReferences.contract.documentNo
Preceding invoice number and dateBT-25, BT-26cac:BillingReference/cac:InvoiceDocumentReference/cbc:ID and cbc:IssueDatebillingReferences.invoices[0].documentNo and .issueDate
Invoicing period of a consolidated invoiceBT-73, BT-74cac:InvoicePeriod/cbc:StartDate and cbc:EndDatebillingPeriod.startDate and .endDate
Variable symbolBT-83cac:PaymentMeans/cbc:PaymentIDpaymentIdentifier of the payment means, for example paymentMeans[].sepaCreditTransfer.paymentIdentifier
  • If the invoice covers one order, put its number in BT-13. If it covers several orders, GS1 recommends the text Consolidated Invoice in BT-13, and the order number of each line in the buyer_order_number item property.
  • BIS 3.0 has one delivery note and one receiving advice per invoice, and no dates for them. For more than one, or for the dates, use the item properties delivery_note_number, delivery_note_date, receiving_advice_number and receiving_advice_date on each line.
  • GS1 recommends at most 10 characters for the variable symbol.

Parties and locations

Retail partners identify head offices, stores and warehouses by Global Location Number (GLN). In BIS 3.0 a GLN uses the scheme 0088. These are additional identifiers: the Peppol address is still the DIČ (0245), as described in Specific use for Slovakia. For the identifier schemes in general, see Business participant identifiers.

GS1 fieldBusiness termBIS 3.0 XPath (under Invoice/)Transaction Services property
Supplier GLNBT-29cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification/cbc:ID[@schemeID='0088']supplier.locationIdentifier, for example 0088:8589000100023
Buyer GLNBT-46cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID[@schemeID='0088']customer.locationIdentifier
Delivery place GLNBT-71cac:Delivery/cac:DeliveryLocation/cbc:ID[@schemeID='0088']delivery.locationIdentifier
Delivery place nameBT-70cac:Delivery/cac:DeliveryParty/cac:PartyName/cbc:Namedelivery.partyName
Delivery place addressBT-75 to BT-80cac:Delivery/cac:DeliveryLocation/cac:Addressdelivery.address
Supplier and buyer IČOBT-30, BT-47cac:PartyLegalEntity/cbc:CompanyID[@schemeID='0158']supplier.legalIdentifier, customer.legalIdentifier

Write locationIdentifier in the {scheme}:{identifier} format, as for the participant identifier. Unimaze then sets the schemeID attribute.

BIS 3.0 has no place for the ordering party, the final delivery place (store) or the ultimate customer. GS1 puts them on each line as the item properties ordered_by_gln, store_number_gln, ultimate_customer_gln and ultimate_customer_name.

Line items

GS1 fieldBusiness termBIS 3.0 XPath (under cac:InvoiceLine/)Transaction Services property (in invoiceLines[])
GTIN (EAN barcode)BT-157cac:Item/cac:StandardItemIdentification/cbc:ID[@schemeID='0160']standardItemNo
Supplier's article numberBT-155cac:Item/cac:SellersItemIdentification/cbc:IDitemNo
Buyer's article numberBT-156cac:Item/cac:BuyersItemIdentification/cbc:IDbuyersItemNo
Country of originBT-159cac:Item/cac:OriginCountry/cbc:IdentificationCodeoriginCountryCode
Order line numberBT-132cac:OrderLineReference/cbc:LineIDorderLineReference
Invoiced quantity and unitBT-129, BT-130cbc:InvoicedQuantity and @unitCodequantity and unitOfMeasure.code
Net unit priceBT-146cac:Price/cbc:PriceAmountunitPriceAmount
Additional item propertiesBG-32cac:Item/cac:AdditionalItemPropertyadditionalItemProperties[] with name and value

Unimaze writes standardItemNo with the scheme 0160 (GTIN). Peppol validates the GTIN check digit, so send the full 8, 12, 13 or 14 digits.

Line discounts and price discounts

GS1 separates two kinds of discount on a line. Use one or the other, not both.

KindBIS 3.0 XPath (under cac:InvoiceLine/)EffectTransaction Services discounts[].discountType
Price discountcac:Price/cac:AllowanceChargeExplains how the net unit price was reached from the list price (BaseAmount). It is already included in the price.LinePriceDiscount, with baseAmount and amount
Line discountcac:AllowanceChargeReduces the line amount.LineDiscount, with amount or percentage

Additional item properties

For everything EDIFACT INVOIC has on a line and BIS 3.0 does not, GS1 uses item properties (cac:Item/cac:AdditionalItemProperty) with fixed names. Rules:

  • Write the name exactly as listed: lower case, with underscores.
  • Every property needs both a name and a value.
  • Write dates as YYYY-MM-DD and numbers with a decimal point.
  • The properties are information for the buyer. Peppol does not validate or calculate with them. For example, vat_amount does not replace the VAT breakdown.
NameTypeMeaning
Item
item_typetextItem type: Z goods, O packaging, S service
units_per_cartonnumberNumber of consumer units in the invoiced unit
delivery_datedateDelivery date of the line
batch_numbertextBatch (lot) number
expiry_datedateExpiry (best before) date
serial_numbertextSerial number
article_number_manufacturertextManufacturer's article number
consumer_unit_pricenumberRetail selling price per unit
vat_amountnumberVAT amount of the line (informative)
free_text_lawtextText required by law
References
buyer_order_numbertextCustomer's order number
buyer_order_datedateOrder date
supplier_order_numbertextSupplier's order number
supplier_order_datedateDate the supplier received the order
delivery_note_numbertextDelivery note number
delivery_note_datedateDelivery note date
receiving_advice_numbertextReceiving advice (RECADV) number
receiving_advice_datedateReceiving advice (RECADV) date
invoice_reference_typetextWhat the invoice reference is: AAB proforma invoice, IV invoice
invoice_reference_numbertextReferenced invoice number, for example an advance invoice
invoice_reference_datedateDate of the referenced invoice
free_referencetextReference agreed between the partners
free_reference_datedateDate of that reference
Parties
ordered_by_glntextGLN of the ordering party
delivery_party_glntextGLN of the delivery place
store_number_glntextGLN of the final delivery place (store)
ultimate_customer_glntextGLN of the ultimate customer
ultimate_customer_nametextName of the ultimate customer
Fees and excise duty
excise_duty_category_codetextExcise duty category code
excise_duty_basisnumberExcise duty basis (quantity)
excise_duty_amountnumberExcise duty amount
recycling_fee_typetextRecycling fee type
recycling_fee_amountnumberRecycling fee for the line
recycling_fee_per_unitnumberRecycling fee per unit
recycling_fee_unittextUnit of measure of the recycling fee
copyright_fee_typetextCopyright fee type
copyright_fee_amountnumberCopyright fee for the line
copyright_fee_per_unitnumberCopyright fee per unit
copyright_fee_unittextUnit of measure of the copyright fee
Pharmaceuticals
sukl_idtextProduct code of the State Institute for Drug Control (ŠÚKL)
adc_codetextADC code (medicinal product identification code)
purchase_pricenumberPurchase price per unit (informative, for distributors)

Example

An invoice line for 10 pieces of a product with a GTIN, a batch and expiry date, delivered to a store, with a delivery note and a receiving advice. The example shows only the fields on this page; the rest of the invoice is as usual.

{
  "orderReference": { "documentNo": "ON-2026-1187" },
  "documentReferences": {
    "despatch": { "documentNo": "DL-55120" },
    "receipt": { "documentNo": "RA-900341" }
  },
  "supplier": { "locationIdentifier": "0088:8589000100023" },
  "customer": { "locationIdentifier": "0088:8589000100016" },
  "delivery": {
    "partyName": "Store 112 Žilina",
    "locationIdentifier": "0088:8589000200037",
    "actualDeliveryDate": "2027-01-14"
  },
  "invoiceLines": [
    {
      "itemNo": "A-1001",
      "buyersItemNo": "200345",
      "standardItemNo": "8586000123458",
      "name": "Mineral water 1.5 l",
      "quantity": 10,
      "unitOfMeasure": { "code": "H87" },
      "unitPriceAmount": 2.40,
      "taxableAmount": 24.00,
      "taxAmount": 5.52,
      "taxCategoryType": "StandardRated",
      "taxPercentage": 23,
      "originCountryCode": "SK",
      "orderLineReference": "1",
      "additionalItemProperties": [
        { "name": "item_type", "value": "Z" },
        { "name": "batch_number", "value": "L2701-07" },
        { "name": "expiry_date", "value": "2027-07-31" },
        { "name": "store_number_gln", "value": "8589000200037" }
      ]
    }
  ]
}

Codes when converting from EDIFACT

Some EDIFACT codes differ from the code lists that BIS 3.0 allows.

Payment means (BT-81, code list UNCL4461):

EDIFACT INVOICBIS 3.0
42 Payment to bank account30 Credit transfer, or 58 SEPA credit transfer
10 Cash10 Cash
21 Banker's draft21 Banker's draft
23 Bank cheque23 Bank cheque

Units of measure (BT-130, code list UN/ECE Rec 20). See also Unit of measure.

EDIFACT INVOICBIS 3.0
PCE pieceH87
CT cartonXCT, or EA or C62 if you invoice the carton as one unit
KGM kilogramKGM
LTR litreLTR

For VAT categories and rates, follow Specific use for Slovakia. Each VAT rate on the invoice gets its own entry in the VAT breakdown, so an invoice with goods at 5 %, 19 % and 23 % has three S entries with different percentages.


Did this page help you?