Showing posts with label Addon-XML. Show all posts
Showing posts with label Addon-XML. Show all posts

Season for reviewing Processes

April...

In Japan, it is a month when a new fiscal year starts.

Not only the accounting of the nation, accounting of local governments, new grades at school, etc. start, but also the ceremony for new entrants are conducted simultaneously in April. (About 20% of Japanese companies start their fiscal year in April)

It can be said that in Japan, April is 'the month when motivation for improving business processes increases' or 'perfect month for improving business process'.

Also in Questetra, Inc., which operates this blog, the amount of updating on Business Processes (number of version upgrades of Workflow Apps) will increase in April.

Dare to extend the time required

The business process introducing this time is a slightly strange improvement example that is "extending the time required at all Steps".

As a usual business improvement, it is normal to consider about improvement on "flows" or "data input screens" upon "dissatisfaction" and "challenges" that you are feeling during your daily work.
  • Automation of Steps
  • Addition of double-checking Step
  • Addition of guidance sentences
  • Implementation of handy button

And, in many cases, we will seek "a direction for a measure to shorten the total duration of work as much as possible".

However, in April, which is a break of the fiscal year, you might become wanting to deal with "inefficiencies you felt throughout the total counting work". In this business process (Workflow-App), it has been revised to stay in the middle of the way. (Addition of Human Process: "x. Retaining Rework")
Business process before improvement: Episode 511: Automatically Generate Transfer Slip File (Excel-CSV)

[Invoice Issuance-Retention]

Measurement of error rate

The invoice issuance process is one of the tasks in which mistakes are not allowed.

"Accounts receivable / sales" is recorded based on accurate billing data, and "savings accounts / accounts receivable" should be recorded upon collection afterword.

However, "redoing" occurs on the actual work site. For example, even in the same human process in Questetra, "Redo" occurred with a 2.8% chance as a result of last year.
  • Correction on "customer address and name"
  • Correction on "quantity and amount"
  • Correction on "issue date and due date"

Of course, the causes are various, including "unavoidable redoing".
  • Information was changed between order acceptance and billing (change of person in charge of customer)
  • The sales representative made a mistake in transcribing the contents of the order form
  • In the first place 'order data' was wrong

However, in any case, if the invoice (billing data) is "redoing the entire process again" when the customer receives it, in addition to the effort of redoing the bill approval processing, the data of the accounting system must also be manually corrected.

I must say such a "Redoing process from scratch" is "big loss".

Reworking and Sending back

In this business process improvement, the retaining Step of "x. Retain Sending back" of the Accounting manager is added, and progress toward the downstream process (data cooperation with the accounting system) is restrained.

That is, it will retain in the state that can be sent back to the most upstream, for a while (e.g. until the end of the month). (Reduce the risk of occurrence of "big loss" rather than increasing overall speed.)

Certainly, data such as 'sales' would like to be incorporated into the accounting system as soon as possible. I agree that it is a wonderful direction as a business management to further "accelerate monthly settlement of accounts" aiming for "daily settlement of accounts."

However, as in this example, "Business process that can absorb some extent of data modification by slowly flowing business Issues" can be another direction of business process improvement.

[Invoice Issuance-Retention:"1. Bill info entry" screen]

[Data Items list]


[Free Download]
<Similar Models>
<<Related Articles>>

[Japanese Entry (ε’Œζ–‡θ¨˜δΊ‹)]
In the last three articles of

I mentioned the difference and respective implementation method of
  • A) Automatically advance to the "next Step" in the Business Process
  • B) Make "certain Step" within a Business Processes to be processed unattended
regarding automation within a "Business Process".

In this (final) article, I am going to organize about the automation between Business Processes.


Connection between Business Processes

Positions of Business Processes

Until now, we discussed focusing on "individual Business Processes" such as "Estimate Approval process" and "Order Receipt process". However, in order to promote automation (improvement of productivity) in the company-wide, we must consider about "connectivity between Business Processes".

On such a stage, it is a shortcut for improvement discussion that enumerating the internal "Business Processes" as much as possible in advance.

That is, the overall viewing would reveal the position and dependency of each Business Process, and the way it should be of the "inputs" and "outputs" of each Business Process would become clear. Along with, it would also clarify the operation method and direction of improvement that the responsible person (Process Owner) of the Business Process should aim for.

Enumerating Business Processes

So, what kind of "Business Processes" are there inside the company?

It goes without saying that it varies greatly depending on the business contents and organization size. At the same time, you should suppose that there is no one who can grasp all the business details in the company. In other words, regardless of who is in charge of "enumerating Business Processes", on-site hearings in certain extent will be required.

And when enumerating the survey results, it is important to enumerate by categories so as to make it easy to see the whole.

As a methodology in practice, it is necessary to map in-house Business Processes utilizing the cost categorization upon calculating the profit and loss of the compan such as "manufacturing cost", "selling expenses" and "general administrative expenses", in addition to the Process classification method of the research institution.

[APQC Process Classification Framework]
  1. Develop Vision and Strategy
  2. Develop and Manage Products and Services
  3. Market and Sell Products and Services
  4. Deliver Products and Services
  5. Manage Customer Service
  6. Develop and Manage Human Capital
  7. Manage Information Technology
  8. Manage Financial Resources
  9. Acquire, Construct, and Manage Assets
  10. Manage Enterprise Risk, Compliance, and Resiliency
  11. Manage External Relationships
  12. Develop and Manage Business Capabilities

[Quote Creation and Approval-Order Report launcher]

[Order Report-Launched by Quote flow]
In the article before the last, "Episode 518: What is Automation of Business Process (Part 1)", I mentioned about two aspects regarding automation of Business Process, such as;
  • [A] Automation of handing over of Issue information between Processes
  • [B] Automation of processing in certain Step

Also, in the last article, "Episode 519: What is Automation of Business Process (Part 2)", I mentioned about the scope and implementation method of "[A] Automation of handing over".

In this article, I would like to organize the range to which "[B] Automation of processing" can be applied and the implementation method.



What kind of "processing" can be automated

Complete automation (Auto-Step)

Likewise the idea of "[A] Automation of handing over" is that leaving the delivery of Issue information from a certain Step to the next one to a computer, it leaves the "work inside certain Step" to the computer in "[B] Automation of processing".

Even in "Quote Creation and Approval" which is a Business Process with a high degree of human dependence, for example, it is possible to leave processing in Steps to the computer, such as
  • creating Quote PDF file,
  • sending email with file attachment,
  • posting summary of the Quote to Enterprise social network.

* Incidentally, it may be easy to understand with an expression that (instead of using the term of 'automation') "part of Step of Business Process to be unmanned", as long as it is not necessary to contrast with "[A] Automation of handing over."


Partial automation

On the other hand, there are some Steps that not to be automated completely.

For example, in the Step of "Creating a Quotation" in "Quote Creation and Approval" Business Process, supporting function such as
  • Calculate total amount
  • Calculate consumption tax amount
would contribute to labor saving of work. However, in this case, the Step of "Creating the Quote" is not unmanned, as some human input (human interface) is necessary. Therefore, it can be said that such Steps should be classified as "human Step".

[Quote Creation and Approval]

Start workflow by external trigger

In the previous article "Episode 516: Method of Starting Workflow by "Email", I wrote about Workflow triggered by" Incoming mail ". Surely, I will be asked the question that "Is there any other way to start Workflow besides email?" (I have not been asked it yet, though...)

Yes, there are!

In the case of the Cloud based Workflow "Questetra BPM Suite", the APIs are provided as follows. "B1. Start Process" among them corresponds to all of HTTP / WebForm / Email. That is, it is possible to design a Workflow triggered not only by "Incoming mail" but also by "Web form input" or "Reception of HTTP request".
  • A. "Developer APIs" which Workflow system always provides (OAuth 2 / Basic)
    • A1. Operation by User (Workflow APIs)
    • A2. Operation by System administrator (System Setting APIs)
  • B. "Process Model connection API" which each business application provides
    • B1. Process start (Message Start Event) (HTTP / WebForm / Email)
    • B2. Standby in the middle of Process (Catching Message Intermediate Event) (HTTP)
    • B3. External transmission (Throwing Message Intermediate Event / Auto-step) (HTTP / Email)

Workflow to start Workflow

Even though it becomes a little "beyond the basics"... Since it has a function of "B3. External calling in the middle of Process", If you set it as follows
  1. X-Process as to "transmit HTTP request", and
  2. Y-Process as to be started by "Receiving of HTTP request",
so that connection between XY Workflows is also possible.


That is, you can realize the followings.

Well, now, In this article, I would like to think further about a method of"start multiple Issues at once" using CSV data.

[Batch starting of Telephone survey Process (Parent Process)]

[Telephone survey Process (Child Process)]

Happy New Year

New Year 's Days in Japan are "almost like holidays" from January 1 to 3, and will gradually return to "normal" from the 4th.

"Stock exchange", for example, it is decided to start trading (unless Saturdays and Sundays) on January 4th. (December 31 to January 3 are all closed holidays) Also, in the "Act on Holidays of Administrative Organs", December 29th to January 3rd is stipulated as "administrative organs holidays".

So, today (January 2), many workers in Japan are spending a lot of time doing nothing.

Whereas, if you are working as (*) a planner, you might want to put "inspired idea" on workflow even if you are on such a holiday.
* Reporter, Composer, New product planner, etc.

Business Process that can also be started by email

In the following Workflow, you can separately start [1x. Idea registration] by emailing, besides starting a Process" from [1. Idea registration] like other general application Workflow.

The point is where the person in charge of handling of the first processing Step (person in charge of Swimlane in which the first Step is) is decided by using the "From address" of the email.

Even though somebody might say 'if it is 'inspired idea', it is enough to just email to oneself'... If you understand this mechanism, for example, it can be applied to "Email linkage with other systems" etc. Taking advantage of consecutive holidays, you ought to try out "Business modeling" with the free version of Cloud based Workflow.

[Email Starting]

"Cannot see the Business Process in the Field"?


In autumn 2016, "Plagiaristic act" by "curated media" is reported sensationally in Japan.

Originally, "content curation" is worthwhile, so as "curation tools / platforms" which enables anyone to post their curated contents. However, a site management company (listed company) mass-produces contents curation articles through cloud-sourcing, and the fact that plagiarism has been instructed during the outsourcing of article writing is brought to the light.

Process of Curated Article Production

There indeed was a Disclaimer note, i.e.
We are completely not responsible for the accuracy, completeness, benefits, conformity to specific purposes, or anything else regarding the information in this article and the user's judgment for using this information.
However, since the particular site was curation concerning "wellness", "Moral" was questioned rather than "copyright infringement". And, as a result, the CEO apologized as "there was a problem in the process of article creation".

DeNA press releass: Statement by CEO
some parts of our manual and directions to writers could be interpreted as suggesting plagiarizing other websites. I cannot view this as being morally correct ... I promise to fundamentally change our operations of these media and create a process which I can completely place my faith in.

I do not know whether it is truth or not, but probably "he did not really see the business process". (I want to believe so.) Then, what kind of business process should he have build if the operating company needs to write articles responsible for?

[Article Creation process]

"I want to try business flow designing..."

In the world of "programming" it is said that "the only way to learn it is to write a program". In fact, everyone writes a program that displays a string "Hello World" at start learning programming. Similarly to this, "try to draw a Business Process" is very important even in the world of "modeling".

The following Business Process is started by "receive mail", and it ends with "chat post".

In the commonplace, a Business Process begins with some sort of "trigger", and several "Steps" follow after it. Whereas, there is only one processing step of "Post to chat" in this example. And, that is a "processing by computer" (automatic processing), so there is no "handling by human" at all. (What a heck!)

[Chat Post flow]
"It's so troublesome to enter billing data..."

Logs such as bank deposits and withdrawals and card payments have become "automatic journalizing", and "accounting input work" became quite easier compared to before.

However, in terms of "sales" in particular, it is too late to wait for the timing of "deposit". After all, it is desirable to record it as "sales as accounts receivable" at the time of "invoice" issuance... Rather, it's a must.
  • 2016 - 11 - 22: Accounts receivable 120,000 / Sales 120,000 = Website creation (for company A)
  • 2016 - 12 - 31: Saving deposit 120,000 / Accounts receivable 120,000 = Website creation (for company A)

Incidentally, on the contrary, there are cases where cannot include in "sales" at the time of issuing "Invoice" (even at the time of "deposit").
  • 2016 - 12 - 31: Saving deposit 120,000 / Advance received 120,000 = Maintenance 2017 - 01 - 2017 - 12 (for Company A)
  • 2017-01-01: Advance received 10,000 / sales 10,000 = 2017-01 of Maintenance 2017-01 to 2017-12 (for company A)
  • 2017-02-01: Advance received 10,000 / sales 10,000 = 2017-02 of Maintenance 2017-01 to 2017-12 (for company A)
  • 2017-03-01: Advance received 10,000 / sales 10,000 = 2017-03 of Maintenance 2017-01 to 2017-12 (for company A)
  • 2017-04-01: Advance received 10,000 / sales 10,000 = 2017-04 of Maintenance 2017-01 to 2017-12 (for company A)
  • 2017-05-01: Advance received 10,000 / sales 10,000 = 2017-05 of Maintenance 2017-01 to 2017-12 (for company A)
  • 2017-06-01: Advance received 10,000 / sales 10,000 = 2017-06 of Maintenance 2017-01 to 2017-12 (for company A)
  • 2017-07-01: Advance received 10,000 / sales 10,000 = 2017-07 of Maintenance 2017-01 to 2017-12 (for company A)
  • 2017-08-01: Advance received 10,000 / sales 10,000 = 2017-08 of Maintenance 2017-01 to 2017-12 (for company A)
  • 2017-09-01: Advance received 10,000 / sales 10,000 = 2017-09 of Maintenance 2017-01 to 2017-12 (for company A)
  • 2017-10-01: Advance received 10,000 / sales 10,000 = 2017-10 of Maintenance 2017-01 to 2017-12 (for company A)
  • 2017-11-01: Advance received 10,000 / sales 10,000 = 2017-11 of Maintenance 2017-01 to 2017-12 (for company A)
  • 2017-12-01: Advance received 10,000 / sales 10,000 = 2017-12 of Maintenance 2017-01 to 2017-12 (for company A)

The creation method and creation timing of so-called "transfer slips" (transfer records) varies depending not only on the type of industry but also on company policy. Even so, the work itself should certainly be "automated".

In the following Workflow, at the moment when the "Invoice" is approved by the supervisor,
  • Receipt PDF will be emailed to he customer,
  • Multiple line "transfer records" are automatically calculated
  • The import file is automatically generated.

Accounting staff can finish "input work" by only uploading the automatically generated Excel-CSV file to the accounting system.

[Invoice Issuance flow]
"Because of the corporate card, it is difficult to grasp the entire expenses"

Business process improvement will reduce "wasteful work" and "time-consuming procedures". However, along with that, "checking by human" tends to be inadequate.

It sure will be a problem if "a loophole (fraud method) has been created as a result of promoting work efficiency" in high occurrence work of "Four major apps" which are;
  • Expense reimbursement flow
  • Procurement purchasing flow
  • Attendance report flow
  • Request for decision flow
However, there is often a trade-off relationship between "labor saving and unmanning" and "strengthening the check system." After all, must seek "compromise to suit each company".


The Expense reimbursement flow below is a monthly application type business flow that mainly aiming "reimbursing out-of-pocket expense".

In this example, it is devised so that approval can be obtained for expenses which do not require settlement as reimbursable out-of-pocket costs at the same time. This is an idea that it will eliminate advance approval about "payment with credit card" and "travel expenses receiving temporary payment".

The applicant himself will have the effect of not only "saving labor" in one application, but also "becoming aware of how much company expenses is using each month".

[Expense and Out-of-pocket costs report]
'What a cumbersome it is to fill in year-end adjustment paper!'

In Japan, workers in every enterprise are instructed submission of "two sheets of document" at the end of year. Looking at that annual paper, a salary earner would think to oneself 'Ah, this year is going to end soon...' And once starts filling in the paper, he or she would be irritated for its cumbersomeness. (And then later, administrative staff would deeply sigh for too many omissions of entry...)

=[EDEIE] Acceptance and confirmation of Application for (Change in) Exemption for Dependents of Employment Income Earner
'Is it OK to write "Same as above" in the column of Address of Family member?'
'Do I write "Same as submitted number" into the column for Personal number?'
'I am not sure about the date of birth of all of my family...'

= [DIPEIE] Acceptance and confirmation of Application for Deduction for Insurance Premiums for Employment Income Earner and Application for Special Exemption for Spouse of Employment Income Earner
'Life insurance with Term insurance rider... wordy...'
'Medical payments and personal injury protection ...wordier...'
'Management Organization for Postal Savings and Postal Life Insurance... too wordy!

It sure is an once-a-year "seasonal event", but it won't be a fun. Suppose 50 million workers nationwide would be irritated for 30 minutes, how much of GDP would be lost? (Need to break away from "handwriting" at least...)

* Incidentally, when it comes to wasting of "100 million sheets of paper" and "storage for it", it will be ended up with "Approval for provision by electronic or magnetic means". In short, it requires submission of "Application for approval on the provision of descriptions concerning withholding by electronic or magnetic means" (Japanese description only), which I would like to mention about at other chances...

The following two Workflows are schemes that an applicant makes application, and administrative accepts and confirms. Everything will be completed online.

And for the next year, applicants will be able to "Start a new Process with these data". Everyone who makes application through this Workflow will be required only to rewrite "HEISEI 28" (Japanese calender year) to "HEISEI 29" at [EDEIE], and "HEISEI 27" to "HEISEI 28" at [DIPEIE]. (Unless change in family member or in insurance policy.)

[Dependent Exemption Application / Insurance Premium Deduction]
"Enter the official company name!"

You should manage suppliers or customers in "Master file". However, even if you keep saying "Register the official company name!" there will be differences such as
  • Upper case or lower case letter
  • Double byte or single byte character
  • Space in between or not

Since October 2015, Japanese government (National Tax Agency) has allocated "Corporate Number" to each and every enterprise in Japan. There, "official company names" (trade names), etc. are strictly managed. And Web-API that can be used free of charge has also been operating. That is almost an "infrastructure", so you have no choice not to use it.

The following Workflow is a scheme of automatic appending of "Customer code" and "Customer name" to SpreadSheet, by entering new customer information. Although it takes a little labor, "official company names" are secured by entering "Corporate number". It has a very significant meaning that it will relieve you from "name-based aggregation" and "data cleaning".

Yes, it will keep "big data" from being ended up in being "big noise-data".

[Customer Master Appending]

"Oh, I did it again... double-booked..."

From Business meeting by visit and face-to-face, I have shifted my work style to "Online negotiation" using 'Google Hangout', etc. I used to feel "My schedule is full!" for having three meetings in a day. But now, even if I have six appointments that is twice as much than before, I still have leeway. However, even though I have achieved so-called "Improvement of productivity" in the aspect of the number of meetings, new challenges are becoming conspicuous which is "Schedule adjustment has become complicated"...


The following Workflow is a Business flow of 'Product demo'.

The basic flow is, capable sales rep to undertake corresponding of "product demo requests" (desired date and time) from the customer voluntarily. For actual 'schedule adjustment', it is done on the phone or by emails. Then when the schedule is fixed, you input it into [2. Demo Date], the second Step.

Its excellent point (seemingly, even though it seems sober) is that "the fixed schedule will be automatically appended to Google Calendar". It is very easy-to-understand to see schedules info on the calendar. (Or, it is very hard-to-understand if it was data list like CSV.) This will reduce the occurrence of 'Double-booking' significantly.

Moreover, *direct links to "Issue details page of Questetra" are embedded in the calendar so that you can smoothly move to the Step of [3. Demo Implementation Report].
* ${var[applicationRoot]}OR/ProcessInstance/listView?processInstanceId=#{processInstanceId}

[Product Demo flow]
"Please share the presentation materials in PPT format with me, instead of PDF."

In-house sharing of files... Companies of nowadays would use "Cloud storage". (Besides, there used to be "File servers"...)

However, in cases where file sharing "with an associated company or an agency" or "in collaborative project", there will be troubles since the other party is not "In-house". Suppose if you share by "email attachment", there will be problems like, not being shared until demanded, or annoyed with unnecessary files, or hesitate to share for not being requested. (In the first place, there are anxieties in terms of security in email protocol.)

For those cases, you ought utilizing accounts of Google, which one billion people use.

Create a folder for the project in "Google Drive", and add "Google Accounts" of all the members of the project team in Share setting of the folder.
(And make a wish that every member has got an account...)


The following is a mechanism to upload files that have been approved through team Workflow, to "Google Drive" automatically.

If some members of the team were users of "G Suite" (Google Apps) and "external sharing' was permitted, you would simply use Questetra standard [Service Task (Google Drive)] (M229). Whereas, in this case here, it is assumed to be operated with common accounts of gmail.com / googlemail.com.

[File Approval flow]

"Monthly settlement confirmation, oh, bother..."

Trouble concerning settlement would never end. Even though 'Online banking' has become convenient, still it takes some sort of effort.

Furthermore, work of "dunning" occurs if "unpaid" occurred. This is not just 'laborious'(increase of steps), it will be a burden to mental health for both the debtor and the creditor. Why can't it be "electronic settlement" furthermore?


The following Business Process Definition is a Workflow of credit card settlement on "monthly tuition for piano lesson".

In this example, 'fee according to the number of lessons' (instead of 'fixed monthly tuition') will be charged at the end of months. It is like, for example, 2000JPY for the month in which two lessons have given, 5000 JPY for five lessons. (We use "Stripe" for online settlement.)

When you realize electronic settlement for lesson fees with this Workflow, you will no longer have to hand-deliver the "invoice" to your students. For the parents of the student, they will not need to go to the bank to make a remittance of the lesson fee every month.

By the way, "Questetra BPM Suite", a Cloud-based Workflow, is free of charge for a use by 'less than ten staffs'. However, you should be careful that the service will be stopped if an interval of logins exceeds 15 days. But that won't be a problem, as long as you login after each lesson to write "date of lesson" (information for charging).

[Lesson Fee Credit Charge]

"What a cumbersome it is to submit documents to the audit firm!"

Even though staff of a business company may think so, it is tough for auditors as well. They are worrying endlessly that if there is any way to ease this 'battle against a mountain of documents'...
  • "Necessary documents are missing" or,
  • "Unnecessary documents are mixed"
If such situations occur frequently, it will crack their minds...

In the Workflow below, quotations that resulted in a contract will be shared in real time. It's nothing so special, just a scheme that digital file to be uploaded successively to a folder in Dropbox which is managed by the audit firm. This is so-called "Unmanning".

In addition, there won't be mistakes, since no human being to select "necessary documents" to put into copying machine. And searching for files is also easy.

Therefore, it increases matters that they can invest in advance, and occasions of visiting auditees would be reduced.

Isn't it wonderful?


* This example is almost the same as "Episode 499: Why am I Unsure about General Situation of Submitted Quotations?". (Just one auto-step has been added)
* To add this Step to existing Process Model, you obtain [Add-on XML], and import it into a Model as function addition file (Process Model file) in advance.

[Quotation Creation flow-Dropbox]

"Want to manage the Customer Master in kintone!"

"kintone" is a Cloud-based Database that is popular in Japan. Comparing to the "Google Spreadsheet" which is likewise a simple Cloud-based database, it is easy to use for beginners of the Cloud computing even though it has some functional limitation.

And "Customer management" is one of the most common kintone use applications.


The following Workflow is a synchronization process for updating "Customer Master on the Workflow platform" in referencing "Customer Master on kintone". It is exactly the same flow of the previous article "Episode 502: "Master Reference" is for Eliminating the Fluctuation!". Automatically runs at five o'clock in every morning.

The only difference is that it refers to "the Master on kintone", instead of "the Master on Google SpreadSheet".

[Customer Master Synchronization-kintone]
"Fluctuation" occurs frequently to corporate name!

Destination data in a Quotation or an Invoice differs like "Nippon Telegraph and Telephone Corporation" or "Nippon Telegraph and Telephone Corp." or "NTT Corporation" ... Yet, the SELECT method must be adopted for an input form in Quote creation flow or Billing flow (instead of TEXT form). Otherwise, data that are not worthy to be aggregated would be accumulated, on and on.

Even though we manage so-called "Customer Master" in a Spreadsheet...


In the following Workflow, it is devised that a "Customer Master for Workflow platform" to be updated automatically with data in a Google Spreadsheet. The "Customer Master" will be maintained to be always up-to-date.

* The Auto-step (Service Task) referred to [Sheet reference] which is utilized here, will become available by feature expansion with [Addon XML] beforehand. (v11.1: 2016-09-05)

[Customer Master Synchronization]
"How much money did we spend on Entertainment expense, this period?"

Serving as a Sales Manager, one should precisely know "Current total amount of external expenses that have approved". If possible, a Manager should recognize "Spending that not needed to be approved" as well. (In plain words, to keep tracking on "pocket money book" of Sales Department diligently... Formally speaking, it is "Budget management".)

In the following Workflow, "Total expenditure until then" will be indicated on the side at the time Approval request coming around. Specifically, spendings recorded in "Budget consumption logs", which is a Google Sheet (commonly called Pocket Money book), will be summed automatically. Moreover, at the moment of approving newly on a spending, the approved expenditure will be appended automatically to "Budget consumption log".


If you want the Budget consumption log to be more accurate, you will be required operational devising such as,
  • to remove the approval log that has not been consumed actually
  • to append manually for irregular small expenses
or improvement of Business Process such as
  • to create a mechanism of automatic appending from "Advertising flow" which approval is not required
  • to create a mechanism of automatic appending the items of expenditure corresponding to the budget consumption from Expense reimbursement flow

However, it is a great progress that knowing just the approximation of the total amount.

Incidentally, you will be able to build "dedicated Cloud-approval" in half a day, using this sample. You may use that system at your own home, assigning the husband as the applicant and the wife as the approver.

[Approval Request flow]
A Wave of Cloud computing is surging over Accounting systems, last few years.

In Japan, the start out of "Cloud service" by a long-established software company was a major impact. Specifically, "Yayoi online" entered into a marketplace formed by "MF Cloud" and "freee" in July, 2015. In these systems, functions that are oriented to medium or large enterprises have been enhanced, and these are tools not only for "Startup companies" or for "Sole proprietorship".

The most advantage of these systems is their capability of retrieving "detail data" of "bank statement" and "credit card" collectively. That is, All of the detail records are automatically fetched as sales slip and payment slip. Moreover, accounting titles that should have been entered manually by accounting staffs have been set beforehand by "automatic journal entry function". (Improvement on performance of automatic Journal entry is discernibly.)


However, it will not be so easy for such Cloud accounting systems to automate generating slips which according to human judgment.

* Indeed, regarding "not allocate to sales deeming as advance received" or "allocate to sales as account receivable", who made the judgment and when should be recorded precisely. (Deterrence of accounting fraud, internal control)

The following Business Process is an accounting Workflow related to advance received. It is a mechanism that automatically generates twelve "transfer slip data", for example, upon receiving "service fee of twelve months" in advance.

It is a flow of;
  1. Accounting staff determines as "advance received"
  2. Supervisor approves on it
  3. Bookkeeping staff registers "transfer slip data"

[Advance-received Registration]
"How much is the total of Quotations that have been submitted currently?"

Sales budget, which all the Sales managers care about. Even not being a Sales manager, there are many people who care about company's sales progress.
  • How many Quotations have been submitted?
  • How much is the total of those Quotations?
  • How many Orders will be reported among them?

As a matter of course, if you would like to forecast the "Sales", "Quotation tracking" is essential.

"How many of what Issues in which Step?" will be obvious if the progress of series of Quoting operations, such as "Drafting", "Approval" and "Win-loss Report", have been managed (in a Workflow). Even "Order rate" can be calculated easily by aggregating of past Issues that flowed through the Workflow. (Or rather, "Productivity of the Sales Department" should be questioned if they don't know the total price of submitted Quotations...)

The following Workflow is a "Quotation Creation flow" that begins with "1. Drafting Quotation" and ends at "4. Win-loss Report". (Want to connect to "Billing Process" in the future...)

Once a Quotation operation has started, things that must be done at the moment ("to approve on a draft of Quotation", "to submit the Quotation to the customer", etc.) will be clarified for both of Sales manager and salesperson. There will never be "Useless waiting time". And of course, never be omissions or oversights.

And the directors on board would make check for "Quotations that have been submitted and waiting for Win-loss report" (Quotations that staying at the 4th Step) in every quarterly results.

[Quotation Creation flow]