View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Show collection (0 pages)
Collections help

Search

Retail:InvoiceSequence

Contents

Invoice Sequence

Bulbgraph.png   This feature is available starting from 20Q3.

Introduction

Invoice Sequence project implements a clear way to distinguish "full", "simplified" and "aggregated" invoices created in any touchpoint, in terms of document type, numbering and printing.

A full invoice is also known as a full or complete VAT invoice. A complete invoice requires both seller and buyer identification, that is buyer’s name, address and tax id; therefore it allows a proper VAT deduction for the buyer.

A simplified invoice is commonly known as a ticket in some countries. A simplified invoice does not require identifying the customer to who products are being sold, by indicating his/her name, address or tax id. Regardless of what simplified invoices can include any of that data if provided.

An aggregated invoice is an invoice that gathers as many tickets issued to the same buyer as required. This invoice type is created at the time of cash up, not at the time of sale.


Bulbgraph.png   As part of this project, the way document number is generated in Web POS has changed

Draft tickets will not have a document number assigned any more. Once a ticket is completed using Web POS, a new document number will be generated using the corresponding document sequence and the ticket will be synchronized to back office using this document number. Thus, duplicated document number generation will be avoided when having several opened draft tickets.

Draft Ticket

Configuration

Touchpoint Type

Simplified and aggregated invoices can be enabled at Touchpoint Type level.

Both types of invoicing are incompatible. In case Generate Simplified Invoices is enabled, a simplified invoice will be created at sale time and for each ticket created in the touchpoint.

In case Generate Aggregated Invoices is enabled, aggregated invoices will be created at cash up time and gathering tickets created for the same customer in the touchpoint.

Touchpoint Type

Document Type

New document types should be created for simplified and aggregated invoices, related to order and return document types defined in each Organization.

Organization Document Type
Order Document Type
Return Document Type

In case invoice document types are not defined for current store, an error will be shown when loading Web POS.

Document Type Error

Touchpoint

New sequence prefixes must be defined for full and simplified invoices at Touchpoint level. Thus, each invoice type will follow a different document number sequence.

In case a different sequence needs to be used for full or simplified return invoices, the corresponding prefix needs to be defined as well.

Changing a sequence prefix will reset the sequence last number, starting next document number from zero.

Touchpoint

In case full invoice sequence prefix is not defined for current touchpoint, an error will be shown when trying to issue a full invoice.

Full Invoice Sequence Error

In case simplified invoice sequence prefix is not defined for current touchpoint, an error will be shown when trying to issue simplified invoices.

Simplified Invoice Sequence Error

Organization

Finally, new print templates can be defined for new invoice types in Organization window.

Organization Template

Invoicing

Full Invoice

Full invoices can be issued on demand for identified customers and based on invoice terms:

Full invoices will be generated using full invoice document sequence defined at Touchpoint level, will be printed using full invoice template defined at Organization level and will be synchronized to back office using full invoice document type defined at Document Type level.

Full Invoice Print
Full Invoice ERP

In order to generate a full invoice, customer must be identified by a commercial or fiscal name, an invoice location and a valid tax ID. In case tax ID is not defined for the customer, the invoice will not be generated and an error will be shown in Web POS.

Tax ID Error

Simplified Invoice

In case Generate Simplified Invoices is enabled at Touchpoint Type level, a simplified invoice will be created at sale time and for each ticket created in the touchpoint with Immediate invoice terms.

Simplified invoices will be generated using simplified invoice document sequence defined at Touchpoint level, will be printed using simplified invoice template defined at Organization level and will be synchronized to back office using simplified invoice document type defined at Document Type level.

Simplified Invoice Print
Simplified Invoice ERP

Aggregated Invoice

In case Generate Aggregated Invoices is enabled at Touchpoint Type level, aggregated invoices will be created at cash up time and gathering tickets with Immediate invoice terms created for the same customer in the touchpoint.

Aggregated invoices will be generated using aggregated invoice document type and sequence defined at Document Type level.

Aggregated Invoice ERP

Retrieved from "http://wiki.openbravo.com/wiki/Retail:InvoiceSequence"

This page has been accessed 3,345 times. This page was last modified on 15 May 2020, at 08:06. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.