Community mailing list archives
Re: POS receipt vs Invoice - Why the division?by
If you need to integrate POS with fiscal printers you need to create a driver such as this one;
which is the driver for the Epson printer in Argentina. That is the real block in using the POS module.
Later you can customize the POS to create invoices while tickets are created, but first you need to solve that
On Sat, Apr 29, 2017 at 1:20 PM, Gustavo Valverde <email@example.com> wrote:
Almost forgot another important difficulty that might be caused by the division: Fiscal Devices.There are 20+ countries around the globe that require a Fiscal Journal for the POS, and the sequence of this journal must be passed through to the receipt/invoice printed by the fiscal printer or even a normal printer; but the sequence is still needed.Regards,On Sat, Apr 29, 2017 at 11:19 AM, Gustavo Valverde <firstname.lastname@example.org> wrote:Hi Community,I've been recently working with the Point of Sale, and I'd like to know what caused the division and creation of two concepts: a receipt and an invoice.My curiosity comes from the difficulties that this commonly causes in most non-EU countries, and even so I can't understand why for the EU countries this needs a segregation, as I have not seen a legislation prohibiting the creation of an invoice for every sale that has been done.The most common difficulties I've seen in the community, caused by this segregation are:
- Anglo-saxon accounting can't be accomplished with the POS
- The invoice sequence can't be added to the POS receipt
- A paid invoice can't be printed through the posbox after payment has been received.I don't know if this has been discussed before, but maybe a "common" solution can be found for the previous difficulties that most non-continental accounting countries have to deal with.I'd like to know if a common solution has been thought, but from a functional view I see this as just having an option to use invoices globally (in the backend and in POS) or to have it segregate it (invoices and receipts); as receipts don't have much logic, this practically shouldn't be a problem in the future.Hopefully we can keep up with the discussion.Regards,--
Este mensaje y sus anexos pueden contener información confidencial y privilegiada con la intención de que sea utilizada por las personas u organizaciones a quienes esta dirigida, por lo que su uso es exclusivo para su destinatario. Si usted ha recibido este mensaje por error, favor de eliminarlo e informar al remitente del mensaje a través de un correo de respuesta. Si este es el caso, le notificamos que queda estrictamente prohibida la distribución o reproducción de este e-mail y/o sus anexos. iterativo no se hace responsable de las opiniones vertidas en esta comunicación que no estén acordes con su quehacer y fines, y que no se revistan de un carácter oficial.
This message and its enclosures may contain confidential and privileged information intended for the use of people and organizations to which it is directed and its use is thus limited to its addressee. If you have received this message by mistake, please eliminate it and inform the sender through a reply message. Should this be the case, you are advised that the distribution or reproduction of this e-mail and/or any attachments contained herein is strictly forbidden. iterativo is not liable for opinions expressed in this message which may not coincide with its responsibilities and purpose and which may not express official matters.