Showing posts with label Contract management. Show all posts
Showing posts with label Contract management. Show all posts
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]

"Contract flow" and "Decision making Flow" are popular in 2016 as well

This is the last post of this year. We were able to deliver Business Templates every week in 2016 as well. This is also thanks to the "support message" and "Like" from the readers.

Yes. We will try harder next year (2017) as well.

Well, this blog has disclosed over 500 articles (and nearly 800 templates) over the past seven years so far, what kind of articles were read well in this year of 2016? I immediately examined the access log of this year.

<Top 5 Articles>

Again, online approval (paperless) on "Contracts" and "Decision-making request" seems to be a popular agenda. (Note: This is the result of the Japanese version)


How do I write it at the present time? "Contract approval flow"

However, this article was written already six years ago.

As being in a position of a person who draws Business Processes every day, I cannot stop thinking that "I would recommend a different Process now". (Though it cannot be helped to be "often read", because it comes at the top when searching for "contract workflow" in Google search in Japanese, currently...)


So, in the last article of this year, I would like to rework the "Contract approval Process" in a simple way.

[Contract approval Process (2010-11-12)]
"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]

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]

Arranging a button for downloading CSV for MS Excel. (previous post)

From the aspect of a person who has to input data into an Accounting system, the "Download button" is very helpful. It allows to add so-called "Journal slip" data snappy to an Excel file. The business efficiency differs greatly depending on "there is" or "isn't" a button. The difference is to take only five minutes for inputting daily accounts receivable, or one whole hour.

However, it is yet a closed to personal process since it is an operation that "to append to an Excel file". The know-hows, which should be associated to the Step, such as "Where is the latest file?" or "Tips and knacks for the work" or "Technique for the case where minor modifications are required", these are tend to be individualism. (As well as anxieties for omission, or miss-copying or fraud.)

The following Workflow is a mechanism of auto-appending of multiple Journal slip data, which have been generated automatically, to Google SpreadSheet. (Either "MF Cloud-accounting" or "Freee",) throwing data to any of Cloud based accounting software, it is very convenient if "Journal slip" was managed uniformly on the Cloud.

By the way, in the first place, it should be the job for the Workflow system that to aggregate the issues which flowed on the Workflow. "List of Issues", for example, total and average of each property are aggregated. However,in a case where each Issue generates "uncertain number of slips", it is difficult to correspond the needs of demanding an aggregation on the "slips". Another table of "List of slips" should be prepared separately in such a case.

Here, we use the "Sheets API v4", which appeared in May 2016.

[Sales Report-SpreadSheet cooperation]
How do I make "Slip data" federated?

In the Latest post, we succeeded to auto-generate some sheets of "Transfer slip" upon reporting orders. Yet, it doesn't mean a thing if they are not entered to "Accounting software".

Well, should I rather say "Cloud-based accounting software" than "Accounting software", for the coming age?

However, unfortunately there are only few Cloud-based accounting software which allows "API access from external" as of 2016. Therefore, I would like to consider to utilize "File import" feature which is supported in every software efficiently.

(Though, REST API over OAuth will be supported in any software service after a year or two.)

Incidentally, although this Business Process is almost the same as the one in the latest post, it has been added a Step of "Superior's approval" for the sake of more practical use.

[Sales Report-CSV Download]

"Debits? Credits? ... What is that? Tastes good?"


Indeed, there are some programmers who show "Allergic reaction" against "Finance and accounting terminology".

However, these are words which working adults should know. Even in the "Information Technology Engineers Examination", which certifies basic IT skills, these terms appear frequently.

Incidentally, there will be nothing wrong if you call them as "Left column, right column" in practice. Both of the column are merely a "breakdown table of assets". If you consist to describe concretely, it will be sufficient to consider that "Left column: Breakdown of cash and cash-like assets", "Right column: Breakdown of assets which must be paid (debt) and which are not needed to be paid."


So... How each of "Breakdown table of assets" (Balance sheet) will be transitioning, in a case that a Cloud service providing company
  • sold service provisioning for twelve months
  • agreed on April 1st, for 120,000 JPY
  • paid on May 30th

For example...

In April, it can be regarded as "increasing of asset for one month of service worth (10.000 JPY)" since they have already provided their service (not yet paid, though.) It is so-called "Selling on credit". (Account receivable) And it will keep on changing on and after May...

[Sales Reporting]

"Reminder notification of Maintenance service contract renewal on the same date in 12 months later."

When I design, for example, a Contract Process, I would want an Email alert (Email reminder). That is, I want to arrange an Event to transmit an email at the most downstream of the business flow. That is referred to as [Throwing Message Event (Email)] in the terminology of "Process Modeling" (BPMN terminology).

However, the Process will take one year for all the Steps to be completed, if you have setup naturally.
(Even though any other Steps have been completed up to Conclusion of contract...)

Although this may depend on personal preference, I feel uncomfortable that the status of the Issue remains in "Running" just for not yet sending the "Reminder email". If the "Time until all the Steps to be completed" is measured as KPI in your organization, it will truly be an "annoying presence".

The following Workflow is a Business Process of Email reminder part that is independent. (It is too simple to refer to as a Business Process, though.) In short, it is a mechanism that just to accept "messages" from various Business Processes, and to transmit them at "Reminding date and time".

[Remind Notification]

The last time, I published a case of cooperation with "Corporate Identification Number System" (Web-API).

◇2015-12-07: Brush-up on Customer Master Data by "Corporate Identification Number System Web-API"

This Business Process is a mechanism to automatically check if "the Names of Businesses in connection have changed" or not every week. It is automatically started at six o'clock in every Sunday morning. Human beings can detect naturally something to be corrected has occurred in "Customer Master (XML)".

However, it is on the assumption that "all the company has a Corporate Number". That is, it makes inquiry about all the companies listed one by one toward the "Web-API system". In reality, there exist trade partners who do not have Corporate Number. (Sole traders, foreign companies, etc.)

In the following Business Process Definition, it tolerate the presence of dummy number of "9999999999999" (13-digit 9) in the "Customer Master".

That is, it is the rule that to register "13-digit 9" for the business partners like overseas clients that do not have a Corporate Number. In addition, it is devised to make request for 10 instances at one time, toward "Web-API system".

[Automatic check of Trade-name Registration in Customer Master #2]

"Company name (trade name) will be changed."
"Transaction company will be changed for a group restructuring."

You may have often received "Name change notification letters" from suppliers. However, it is really insecure to carry out maintenance on"Customer Master data", only relying on such a letter.

Since December 1st, 2015, the Japanese government has started running a "Web-API function" for the "Corporate Number system".

If the application side has obtained the "Corporate Number of business partners" (13-digit number), it is possible to refer the registration information such as the business name and location of the customer, at any time. In addition, it is now able to detect change information (processing segment), such as the "Name Change", "Merger", "Company dissolution".

The following workflow definition is a mechanism to automatically detect "Name changes", utilizing this "Web-API function".

Here, we assume that the "Business Partner Master" (Business-Connection. xml) is present on the Workflow platform. In other words, trade names that are registered in the "Business Partner Master" will be confirmed if it is as the same as the information registered in government. It is set to be automatically run every Sunday morning.

[Automatic check of Trade-name Registration in Customer Master]

"Workflow systems" of nowadays have responded very well to the needs of Quote creation.
  • A. Requirement of "Approval" by the supervisor who is in the headquarter
  • B. Requirement of "Paper" document for submitting to "Client" 
That is, not only responding to work on Smartphones, many of Workflow systems are capable of so-called "Document output function". However, furthermore devising will be needed for even such Workflow systems if you want;
  • X. to aggregate by "Salespersons"
  • Y. to aggregate by "Customers"
In short, you cannot expect smooth aggregation if, for example, a site where "fluctuation" would frequently occur upon inputting customer's name. Thus, the following three viewpoints shall be pre-considered.
  • o. Group management on "Quote"
  • x. Group management and ID management on "Salespersons"
  • y. Group management and ID management on "Clients"
In the following workflow, "Customer Master Interlocking Form" is utilized for inputting customer's name. (Search combo-box)

[Quote Creation flow]

In this example, a "Sales activity that begins with Lead handling" is divided into three stages.

  • 1st stage: [Sales Lead] - Confirmation if it goes Progress - [Submission of Estimate]
  • 2nd stage: - Progress extension (Estimate resubmission) - [Quote]
  • 3rd stage: - Negotiation - (Quote resubmission) - [Contract / Lost-contract]

That is, an Issue in which "Estimate PDF" has been registered is the Issue that has finished the 1st stage, and an Issue in which "Quote PDF" has been registered is the Issue that has finished the 2nd stage.

In addition, the information of the customer is specified by referring to "Customer Master data". Please refer to previous articles about Maintenance Operations on Customer Master.
Note that here, it has not been defined jobs of "Indirect departments", such as print-out, signature and mailing. You would be better to connect to these Workflows if they have been defined separately. (Process model connection API)

[Quote Creation flow:"1. Issue Registration - Provisional Quote" screen]


[Data Items list]

[Free Download]
<Similar Models>


<<Related Articles>>



[Japanese Entry (和文記事)]
A supplier changed their "Name" (trade name). It is a common story.

You changed the priority of your customer. It is as well.

The following is a Business flow to maintain "Customer Master data" collectively. "Monthly Reviewing" of regular basis and "Extraordinary Reviewing" will be performed by the Sales administrative assistant team.

By updating "Customer Master data" on this special Workflow, you can switch "List of Customers" which is shown on many of Workflows on your Workflow platform (Drop-down list of Options, list in a combo-box, etc.) all together. In other words, each Process-owner who is designing and operating respective Business Processes such as "Quote Approval flow" or "Billing Process" or "Repair Request Response" Process, will be freed from maintaining data of "Customer list".

* Please see the previous article for "Separative addition" to Customer Master data.

[Customer Master Data Maintenance]

If the Workflow platform possesses "Customer Master data", it will be convenient in various ways.

However, if everybody enters in "text form of free input", the names will be ambiguous such as;
  • "NTT", or "Nippon Telephone and Telegraph", or "enu-ti-ti (in Japanese characters)"
  • "Apple Inc." or "Apple, Inc." or even "Apple computer, Inc."
Anyway, input of corporate name would diverge... The work so called "Name identification" is so worthless to do.


The following is a "Trade Account Opening" Workflow.

At first glance, It's almost the same flow as the previous article (Credit Management flow), but it also has a mechanism which automatically updating "Customer Master data" (Business-Connections.xml), at the time of registering a new customer.

You can call this "Customer Master" into "Drop down list" or "Combo box which filters the list as you type" on other Workflows. That is, in any of the Workflow of "Quote approval flow", or "Invoicing flow", or "Inquiry correspondence flow", the corporate names to be input will always be "formal name" for it is selected from the "Customer Master data".

[Trade Account Opening]

"Goods and cash are exchanged at the same time"... it is not always. After all, in the business-to-business transactions, either one is required to "trust" the other party.
  1. To pass the goods and invoices, and get remittance by the end of next month (Accounts receivable)
  2. Transfer cash, and get the Goods shipped later (Advance payment)
So many companies, to set the "credit limit" for all the counter-parties. The procedure when setting for the first time is also especially referred to as "procedure for trading account opening". (Incidentally, to decide which side will be the creditor, it depends on whether "products first" or "cash first". It is the same structure as the "ransom exchange scene" you see in the dramas and movies.)


The following Workflow is a very simple Business flow of "Credit management". It is to set the "credit limit" for a particular customer. Specifically, a supervisor determines it with information such as "financial statements that obtained directly from the customer" or "information from a credit research company", or "past trading performance" or "priority on the business strategy". Eventually, CFO will grant an approval to it. (And day-to-day "accounts receivable" will be controlled within the limit that has been set there.)

The notable point of this Workflow definition is the utilization of "Corporation Number" which Japanese government is going to begin operation since October 2015. You will be possible to prevent failure in the "name identification" (the multiple setting of limits)...

[Credit Management flow]

There, it will come one more month later...

The Individual Number system will start also here in Japan. (2015-10-05) In this blog as well, I have exemplified several Workflows (Business Process) about "Process of Individual Number collection".

And I am going to introduce examples of utilizing "Corporation Number" also in the following weeks. Also,I am planning to publish utilization examples of "Web-API function" of Corporate Number system sequentially as soon as I confirm operation on "Pre-verification environment".

In this article, I will summarize on "Error detection" which is indispensable in the business that deal with "Individual Number".

The Workflow definition below is a sample which allows you to experience 'accuracy check' on input data. It is set both of [1] the mechanism of automatic data checking during input (JavaScript in input screen), and [2] the mechanism of data checking on the server computer (JavaScript in Script Step)

By the way, "Check Digit" means a character for inspection. It is used widely for such as "Credit card number", "Product code"(EAN / JAN barcode), "International Standard Book Number" (ISBN), etc. In the case of "Individual Number" in Japan,
  • Corporation Number (13 digits): The leftmost digit
  • Individual Number (12 digits): The rightmost digit
are calculated by the "specific formula", and is added.

[Check Digit sample:"Test form" screen]

In the previous article, I introduced Japanese "Civil Procedure" and a Process Diagram of it.

The following represents trial process of "Criminal Procedure" in Japan.

This Process Diagram will be helpful for understanding the outline of Criminal Procedure, its "Three-trial system" and the "positioning of the Summary Court". Also, it will help to aware of the "difference between Civil Procedure and Criminal Procedure" by comparing with trial process of Civil Procedure.

For instance, it has not generally been recognized that an appellate against the "first instance in Summary Court" moves to "High Court in a Criminal procedure, whereas it is brought in District Court in Civil Procedure. Or else, recognition by the Flow chart will promote understanding the difference which "submission of Indictment" by prosecutor will trigger a Criminal Procedure, whereas "Filing of Complaint" by plaintiff will do a Civil Procedure.

"Process Diagram" is indispensable in understanding the "rules" whatever it is the law statement or the company regulations.

<Reference>

[Criminal Procedure flow]
Most of what is called "rule" are described in "text".
  • Law
  • Administrative Procedures
  • Company regulations
  • School regulations
And therein, the "flow of the procedure " is also described.

Needless to say, the costs for "understanding the entire rule" would be significantly reduced if there was a"Process Diagram". The Process Diagram, "Deliberation Process on the Bill" which I have introduced in the last article, is also very useful for understanding the Japanese legislative rules.

The following Process Diagram, which I am going to introduce this time, is "Court Process for Civil Litigation."

The "judicial rules" in Japan has been drawn there, and it can be said that is an effective figure for understanding the "Three-trial system" or "positioning of the summary court". For example, if they have embedded this diagram onto their website, it would surely contribute to the understanding of site visitors.

Incidentally, please be noted that the following business Process Diagram is described as being limited to "ordinary suit" (legal disputes between individuals) within the "Civil Suits". (Not includes Criminal procedure, Administrative litigation, Patent litigation, Domestic Relations Cases or Juvenile Cases)

[Civil Suits flow]
'I see, In Japan, Laws are established through the deliberations by both of "the house of Representatives" and "the House of Councillors".'

If you want to let someone to understand this basic framework (only), the Business Process Diagram (Workflow Chart) which I introduced before contains too many information. I can hardly say that it is easy to browse / to understand. That is because it describes a variety of details of Flows that may happen.

Indeed, even though it has been described focusing on "pathways which may realistically chosen", I cannot hardly say that it is easily to understand (e.g.) the notable "Flow of 60 days rule", which is a measure for the conclusion by re-vote in the House of Representatives when deliberations in the House of Councillors were prolonged. Further consideration will be needed if it is used for "Civics textbook" or for "newspaper article".

The following Business Process Diagram is a simplified version of previous Business Process Diagram.

This also can be said that a flow chart for explaining the "backbone" of the Business Process. Although some part of "procedures actually possibly occur" has been omitted, there is no inconvenience in understanding the mechanism or to check the status of deliberations. (Cases that the succeeding House passed the bill with alteration, etc.)

[Bill Deliberation in the National Diet-2]