Showing posts with label Invoice. Show all posts
Showing posts with label Invoice. Show all posts
I'm afraid to say that there are only few companies that have visualized the issuance of their 'Quotes' and 'Invoices'. There are not so many of the personnel in charge who can answer immediately to the question about
  • How many Quotes have been issued now?
  • How many Invoices have been issued now?


In most of the companies, personnels of Sales or Accounting create each quote and invoice manually in Excel, print them out, get approved by manager, copy them for backup, enclose them and finally post them... With all their effort they created them with the computer, but eventually they are handled in an analog way. And they are hard to be aggregated.

The 'Invoice Issuance flow' below is so to speak a "Billing system".
The 'Billing Data' that has been entered into Workflow will be approved through Workflow. Using the data, the Invoice PDF is generated. In other words, Invoice PDF will not be created except from this system. You can centralize management of issuance of invoice PDF. When you could develop a Business Process this far, for example you can download business data of 'Issued date', 'Billing company name', 'Billing amount' in CSV format. That means you can create a 'Real-time Billing Ledger' anytime.

By the way, the excellence of this Workflow is to throw backup of 'Invoice file' automatically to a specific folder in "Google Drive", the Online Storage.

[Invoice Issuance - Auto Backup flow]

What we're doing with BPM is, setup work flows and check out tokens labeled on them.
It looks like, laying railroad track and run a train car on it. Sometimes, one wants to run a car on somebody else's track switching from his own track. (What say???)

For example, Office A gets a lead, then passes office B to carry on the business.
Today we expand "lead-negotiation-order"process,in "Building an SFA System INSIDE a BPM System" sample model, to enable to pass particular case between offices. Each offices (office A,B,C in this model) must apply workflow down here. (detail can be altered by offices)

<Tasks>
1. Input Lead Info, 2. 1st Contact, 3. Initial Proposal, 4. Proposals to Decision-Maker, 5. Final Negotiations


[Lead-Negotiation-Order-Trans-Office Connection Flow:
"setup for Message Throwing Intermediate Event"]

Sales section always maintain information of customer, their demands, their problems, solutions they dream.

The sales section's maintenance of customer information using "process data" was introduced in "Building an SFA System INSIDE a BPM System." Today we will offer a smaller process using these data.


<Tasks>
1. Estimate Data, 2. Request Print & Signature, 3. Advice, 4. Receive Estimate, 5. Send


[Estimate Creation <Notify Sales Staff>: "1. Estimate Data" screen]

We stick to the principle of starting small and growing bigger, especially with BPM activities. Of course, the assumption is on growing bigger. This means once you get a grasp on the items and flow necessary in a business process, you'll want to increase the range to include up or downstream processes.

The below business model is a holistic "lead—negotiation—order" process that includes marketing and sales. It helps to visualize the status of internal projects. Enabling eternal loops in the middle of the process allows concerned parties to add detailed info on customer profiles. This is, in effect, a Sales Force Automation (SFA) system.


<Tasks>
1. Input Lead Info, 2. 1st Contact, 3. Initial Proposal, 4. Proposals to Decision-Maker, 5. Final Negotiations


[Lead-Negotiation-Order Flow: "1. Input Lead Info" screen]