10 docs tagged with "Data Structures"

Field reference for ReceiptRequest, cbCustomer, ReceiptResponse, ChargeItem, PayItem and SignatureItem used with fiskaltrust.Middleware.

Austria-specific behaviour of the receipt request, receipt response, ftState and ftStateData, charge items, pay items and signature entries in the Middleware data structures, including the RKSV machine-readable code (QR code).

Placeholder for Belgium-specific data structures that links to the general Middleware data structures chapter.

German-specific fields of the receipt request — single fields, cbCustomer, ftReceiptCaseData, charge items and pay items.

Spanish rules for cbCustomer — required fields for invoices, NIF validation and TicketBAI foreign customer identification.

French fields of the receipt request and response — bills and table changes, copies, training mode, charge items, pay items and signatures.

How cbCustomer fields are transmitted to myDATA as the document counterpart for Greece, how cbArea is transmitted as the table number of restaurant orders, how refunds and voids reference documents from other systems by their MARK, and how discounts are transmitted to myDATA.

Receipt request fields needing special handling in Italy, such as cbTerminalID, cbReceiptReference and cbCustomer customer data, and how refunds and voids reference the original receipt.

Data structure rules for Poland — mandatory PLN currency on every request, separating return positions from sales, and how discounts and extras are assigned to sale lines.

Placeholder chapter for Portugal-specific data structures, pointing to the Data Structures chapter of the General Part.