---
title: "How to print gift tickets in the POS?"
slug: "1602862798"
updated: 2026-07-30T07:48:51Z
published: 2026-07-30T07:57:22Z
canonical: "help.ila.cegid.com/1602862798"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.ila.cegid.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to print gift tickets in the POS?

- [x] PT
- [x] ES
- [x] AO
- [x] CV
- [x] MZ
- [x] ST
- [x] GW

- [x] Professional
- [x] Executive
- [ ] Public Sector
- [ ] Omnia
- [ ] Evolution

---

Printing gift tickets on the POS requires a **set of configurations and validations** on the reports created for this type of tickets.

---

## Create report for gift tickets

To print gift tickets, it is necessary a report created specifically for that.

To create a report for gift tickets, follow these steps:

**Step 1: Create report for gift tickets**

1. Access **Marketing & Sales | Sales | Resource 1. Access**s | Tools** | **Config. POS Documents;** 2. Select the **VD Template** (Cash sales for POS); 3. In the edition area, delete all fields with value; 4. If you wish the ticket to specify that it is a gift ticket, you must insert that information manually in the header; 5. Change the name of the template (for example, VD2); 6. Finally, click **Save**. After creating and saving a Cash Sale document, you can change it to print the gift ticket.**

**Step 2: Create cash sale document**

1. Select the desired document and click **Change Document**;
2. Click **Printing Config.**  and select the report created for gift tickets;
3. Click **Confirm**;
4. When selecting the option **Print**, a gift ticket with no price is printed.

**Note**: If the Gift Tickets configuration, you must use a **specific tag** that allows to ignore the mandatory fields as to make it possible to freely set up the ticket:

| **Field** | **Tag** | **Section** |
| --- | --- | --- |
| Gift Ticket | [] | Header |

---

## Change printer definitions

The definitions applied on the document printing will always be performed at the BackOffice level, but due to the point of sales nature, it is necessary to make a way of changing the printing template available to the operator.

To change the printer definitions, follow these steps:

1. Access **Documents** | **Printing Config.** ;
2. Change the definitions of the A4 or receipt template;
3. Click **Confirm**.

---

## Validate printing in receipts

The reports used to print financial and transport documents with fiscal interest, **are now the target of a****validation process** that ensures the compliance with the applicable fiscal requirements.

This validation is performed on the reports distributed by PRIMAVERA also on any other custom report that apply. In this last scenario, **the user is responsible for providing all changes to the** **custom** report, so that the ERP PRIMAVERA can validate the report and continue using it in place of the standard reports distributed by the app.

The **main rules and elements** that these reports should comply with must be ensured.

#### General Rules

The report validation is intended to ensure that the printing of the fiscal nature document contains all elements required by the Portuguese Tax Authority (Autoridade Tributária). As such, besides checking if the report contains a set of mandatory fields in its structure, the ERP will also check that:

- The fields are not suppressed;
- An adequate character font is used;
- The fields are not hidden or overlapped by graphic elements or other fields;
- The fields do not exceed the physical limits of the printing area;
- The formulas and expressions that feed these fields are the ones originally distributed by PRIMAVERA.

A given field is identified, not though his internal name/identifier, but through the formula that feeds it. In practice, and taking the requirement to print the tax ID of the issuing entity, the ERP will check, at the time of the invoice printing, if the report used contains a visible field fed by the Crystal formula originally distributed by ERP PRIMAVERA (in this case: @Contribuinte).

The following table summarizes the fields requires on the printing templates of POS receipts:

| **Field** | **Tag** | **Section** |
| --- | --- | --- |
| Issuer Name | [<^NomeEmp-XX] | Header |
| Issuer Tax ID | [<contribemp-xx]< td="> </contribemp-xx]<> | Cabeçalho</contribemp-xx]<> |
| Issuer Address | [<moradaemp-xx]< td="> </moradaemp-xx]<> | Cabeçalho</moradaemp-xx]<> |
| Issuer City | [<cpostalemp-xx]< td="> </cpostalemp-xx]<> | Cabeçalho</cpostalemp-xx]<> |
| Document type | [<tipodoc-xx]< td="> </tipodoc-xx]<> | Cabeçalho</tipodoc-xx]<> |
| Document no. | [<numerodoc-xx]< td="> </numerodoc-xx]<> | Cabeçalho</numerodoc-xx]<> |
| Document date | [<datadoc-xx]< td="> </datadoc-xx]<> | Cabeçalho</datadoc-xx]<> |
| AT Certification Text | [<textocertificacao-xx]< td="> </textocertificacao-xx]<> | Cabeçalho / Rodapé</textocertificacao-xx]<> |
| Entity Name | [<nomecli-xx]< td="> </nomecli-xx]<> | Cabeçalho</nomecli-xx]<> |
| Entity Address | [<moradacli-xx]< td="> </moradacli-xx]<> | Cabeçalho</moradacli-xx]<> |
| Entity Tax ID | [<contribcli-xx]< td="> </contribcli-xx]<> | Cabeçalho</contribcli-xx]<> |
| Item Code | [<codigoart-xx] [<codigoartdim-xx]<=" td="> </codigoart-xx]> | Detail |
| Item Description | [<descricaoart-xx] [<descricaoartdim-xx]<=" td="> </descricaoart-xx]> | Detail |
| Item Quantity | [<quantidadeart-xx]< td="> </quantidadeart-xx]<> | Detalhe</quantidadeart-xx]<> |
| Item Unitary Price | [<precoart-xx]< td="> </precoart-xx]<> | Detalhe</precoart-xx]<> |
| Item VAT | [<ivaart-xx]< td="> </ivaart-xx]<> | Detalhe</ivaart-xx]<> |
| Item Net Total | [<totallinhacomiva-xx]< td="> </totallinhacomiva-xx]<> | Detalhe</totallinhacomiva-xx]<> |
| VAT Rate | [<%TIva (TaxaIva,XX) >] | Footer |
| VAT Taxable Base | [<%TIva (Incidencia,XX) >] | Footer |
| VAT Value | [<%TIva (Valor,XX) >] | Footer |
| VAT Chart Title | [<nomeiva-xx]< td="> </nomeiva-xx]<> | Rodapé</nomeiva-xx]<> |
| Goods/Services Total | [<totalmercserv-xx]< td="> </totalmercserv-xx]<> | Rodapé</totalmercserv-xx]<> |
| Commercial Discounts Total | [<totaldescontos-xx]< td="> </totaldescontos-xx]<> | Rodapé</totaldescontos-xx]<> |
| IEC Total | [<totaliec-xx]< td="> </totaliec-xx]<> | Rodapé</totaliec-xx]<> |
| VAT Total | [<totaliva-xx]< td="> </totaliva-xx]<> | Rodapé</totaliva-xx]<> |
| Document Total | [<totaldoc-xx]< td="> </totaldoc-xx]<> | Rodapé</totaldoc-xx]<> |

 In the case of the **Gift Tickets** configuration, you must use a specific tag that allows to ignore the mandatory fields in order to freely set up the ticket: 

| **Field** | **Tag** | **Section** |
| --- | --- | --- |
| Gift Ticket | [] | Header |