Receipts will present all details of the purchase performed.

1 Receipts

1.1 Registration

Menu path:
Point of sales (POS) / Tickets / Registry
Mobile / Point of sales / Tickets / Registry
Point of sales / Tickets / Registry

This form is used to view all completed receipts along with their details: form of payment, total price, date, name, etc.

apps_pos_ticketh_close
Label Description
Hardware ID Hardware identification
Terminal ID Terminal identification
Series
Number
Invoice number
User code User login code
Customer Customer code
Warehouse
Source document
Document type
Start date
End date
Status Receipt status

  • Default: 0
  • Values:
    • 0: Correct.
    • 1: Canceled.
Processed Indicates if the receipt has already been processed

  • Default: 0
  • Values:
    • 1: Processed.
    • 0: Pending.
Hash key Hash key generated for the document
Total
Actions
Button Title Notes
BUT_PROCESA_TICKET en.BUT_PROCESA_TICKET Processes the receipt record originating from a POS terminal and generates a corresponding Axional receipt.

1.2 Type

Menu path:
Point of sales (POS) / Tickets / Type Documents
Mobile / Point of sales / Tickets / Type Documents
Point of sales / Tickets / Type Documents

To create documents through the device, the document type must be configured. Document types possess a series of attributes and parameters.

To set the document type as multi-language, the header description field must be left empty. Further below, in the "Document Description" tab, each language must be selected and its field filled in.

apps_pos_ticketd
Label Description
Code Document type code
Description Description of document type
Order Display order

  • Default: 0
Type
Document Document to generate

  • Default: gtpv_ticketh
  • Values:
    • gtpv_ticketh: Tickets.
    • geanmovh: EAN movements.
    • glog_recuenth: Counts.
    • gman_parteser: Service sheet.
    • gvenpedh: Sales order.
    • null: Nothing.
Type Type of document to be generated
Document series

  • Case: Upshift
Ask for payment Flag indicating whether to ask for payment

  • Default: 0
  • Values:
    • 1: Yes.
    • 0: No.
Refund Refund document

  • Default: 0
  • Values:
    • 1: Yes.
    • 0: No.
Request Flag indicating whether a document closing request exists

  • Default: 0
  • Values:
    • 1: Yes.
    • 0: No.
SAF-T request Request SAF-T certification

  • Default: 0
  • Values:
    • 1: Yes.
    • 0: No.
Stock control

  • Default: 1
  • Values:
    • 1: Yes.
    • 0: No.
Invoice series
Customer report required Flag indicating whether the customer must be reported

  • Default: 0
  • Values:
    • 1: Yes.
    • 0: No.
Warehouse report required Flag indicating whether the warehouse must be reported

  • Default: 0
  • Values:
    • 1: Yes.
    • 0: No.
Source report required Flag indicating whether the source document must be reported

  • Default: 0
  • Values:
    • 1: Yes.
    • 0: No.
Print copies

  • Default: 1
Background color

Text color

default_code

  • Default: 0
  • Values:
    • 1: Yes.
    • 0: No.
Status

  • Default: A
  • Values:
    • A: Active.
    • B: Drop.
comment
User created User who first added the record

  • Default: USER
Registration date Log entry date

  • Default: CURRENT
Update user User who last updated the record

  • Default: USER
Update date Date of last record modification

  • Default: CURRENT
Document Type Document Description
(Button) Select document type. List of document types authorized for the user.

The device prepares transactions using the most recent document type selected in past transactions.

To modify this default document type, the Document Type button must be pressed to bring up a list of options. Once an item is introduced into a document, the document type cannot be modified without pausing, canceling, or finalizing the operation.

1.3 Charges

Menu path:
Point of sales (POS) / Tickets / Type of collection
Mobile / Point of sales / Tickets / Type of collection
Point of sales / Tickets / Type of collection

Forms of payment consist of the different payment methods which can be related to documents.

When a document type has the label "Payment", it means that one or more forms of payment must be indicated for that transaction.

The system initializes, by default, with three forms of payment (CASH, CARD or CHECK). As many forms of payment can be added as a company requires.

To set the payment type as multi-language, the header description field must be left empty. Further below, in the "Payment Description" tab, each desired language must be selected and its field filled in.