From the sale to the invoice
A customer pays at the register, and the invoice is issued in a different program. Instead of an employee on shift re-entering every sale into accounting, the invoice goes out on its own and its number is saved on the sale.
Systems involved: The register and the accounting software
The full story
Where the day starts
A customer buys in the shop or pays for a job. The register records the sale: who the customer is, which items, and the amount. For the customer, this is the moment the transaction is done.
Where it gets stuck
The invoice is a separate document, and it is issued in the accounting software. An employee on shift opens that program, re-types the customer, the items, and the amount, and issues the invoice. At month end the accountant finds sales without an invoice and invoices whose amount differs from the register.
What Flow Vector connects
Flow Vector connects the register to accounting. Closing the sale issues the invoice with exactly the same details, and the invoice number is saved on the sale. The books match the register without month-end cleanup.
What stays with a person
An employee still approves a sale when the price agreed with the customer differs from the price list, when a special discount was given, or when a business customer has no tax ID on file. Without that decision the invoice does not go out, and the system waits for approval instead of issuing a wrong document.