Episode 502: "Master Reference" is for Eliminating the Fluctuation!

"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]

Episode 500: Manual Input is A Must for Transfer Slip?

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]

Automatic Posting to a Blog System (OAuth 2.0 Connection)

"Official Blog Site" of an enterprise is no longer unusual.
Or rather, it is getting to be 'for granted' as well as 'Website'. Needless to mention, it is very convenient for publicity of latest business information. It also could be a tool for communication with customers.

This article has taken the form of a blog of "Workflow sample", as well...
Questetra Inc., is running a blog called "Questetra Blog"...
(Whoops, the official blog of Google's, well well, how many would be there?)

The following Workflow definition, "Official Blog Publishing flow" is (obvious to look into the Process diagram, though) a mechanism that a draft which have reviewed will be automatically posted to blog system. I wish to ensure the readability and accuracy of the article through various devices such as "mechanical automatic cooperation" or "human reviewing process" as in this example.

[Official Blog Publishing flow]

Cloud-based Workflow and Google Calendar (OAuth 2.0 federation)

For Outsourcing Software companies or Business Process Outsourcing companies, the "Delivery Date" that promised to the customer is absolutely unmistakable. Once they delayed, their credibility would fall to the ground. However, you can't be sure that the "delivery date" is shared to be recognized thoroughly.

Team members would rather continue to recognize the deadline for the "processing of their own". In other words, they barely have chances to recognize the "Delivery Date" that is the deadline of entire steps. Watching the screens of the Workflow system, even though the deadline of 'underwritten processing of their own' is obvious, the "Delivery Date" which should be important for the team is hardly to be recognized.

Furthermore, "cross-project information" such as 'a lot of Delivery Dates are concentrated in this month', there will be no chance to grasp them.

In the following Workflow, "Data of Delivery Date" is arranged to be synchronized to a [Calendar system]. Specifically, "Delivery Date data" in the 'order information' will be automatically written to the Google Calendar, using the secure communication of OAuth. Looking at the calendar, "distribution of Delivery dates" is obvious at anytime. This information will be a very important source not only for the team members, but also for directors and auditors.

[Contract-Delivery flow]