![]() To reduce the number of unpaid invoices due to errors, this process starts with a Check invoice task: check the information on the invoice to see if it correct, perhaps by comparing it to a purchase order. A nice customer might immediately spot the errors and ask you to issue a new invoice, but some customers might wait until you complain about the unpaid invoice to tell you that there’s a problem and that it won’t be paid. Checking the invoice using an Effektif formĪ common reason for unpaid invoices is errors on the invoice. The form also captures the customer email address, which the process will use to send email to the customer. For this example, the process trigger is an Effektif form with a file upload for the invoice. ![]() The process starts with an invoice that is ready, perhaps as a PDF document. The key steps in this process are the Send Invoice task, an automatic task that emails the invoice to the customer, and a Check for payment task that involves someone in the finance department checking whether the customer has paid the invoice. When the invoice is ready, this process is triggered somehow. ![]() In this example, the invoice is produced by some other process. The customer invoice processĪs usual, the most concrete summary of this process is to describe the result that we want to achieve for each invoice - the process goal: ![]() ![]() This follow-up is usually necessary in practice, because customers cannot always be relied upon to pay on time. This article introduces a simple customer invoicing process, and how to use reminders to follow-up outstanding invoices. In any business, the most obvious example critical process is getting paid by customers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |