Automatize billing

In the previous article, we created a workflow in which "PayPal Invoice" is automatically sent, by placing two automatic Steps "PayPal Create" and "PayPal Send".

That is, "billing data" which has been checked and approved in the human Step is automatically POSTed to PayPal side and then "PayPal invoice" is generated. And at the specified time (send command is delivered), it will be sent by email. After all, since it can be defined with only "Addon Service Task" ("Script Task" is not used), it is attractive to be able to build an "automatic billing system" according to your business even if you had no programming knowledge.

However, it was "out of scope" for "work of checking whether 'PayPal invoice' was settled".

Automatize throughout deposit confirmation

In the following Business Process, an automatic Step called "PayPal Check" (Addon Service Task) has been added furthermore. In other words, this Workflow system is set to continuously check the settlement status for "PayPal invoice" that has been sent, periodically and automatically.

Specifically, an Issue which is staying at "(3. Unpaid retention)" will arrive at "PayPal Check", each time when
  • the accounting staff proceeds the Issue, or
  • retention time of 12 hours passes.
So, the settlement status is inquired via secure communication (OAuth 2 communication / PayPal Invoicing API). If the status is "settled (PAID)", it will store "Settled time" and "Settled amount", and the entire process end, without returning to "(3. Unpaid retention)".

[PayPal Invoice Issuance-PayPal Check]

Invoice directly connected to settlement

"PayPal Invoice" is an electronic invoice in the format of "Email".

From the viewpoint of the person who received the mail, it is very simple since you can click on the "View and Pay Invoice" button and immediately complete the settlement processing (card payment / PayPal account settlement). Of course, even when "in-house transfer to accounting personnel" is required, it is very easy to do, just a transfer operation on email client.

Also, viewing from person who issued the invoice, it is very easy since its procedures are only
  1. Login to PayPal and enter billing data
  2. (receive Settlement completion notification)
comparing to conventional "Business Process of invoicing in paper" took
  1. Create Excel data of invoice
  2. Printout the invoice
  3. Mail the invoice
  4. Confirm remittance in specified bank account

Moreover, we do not receive credit card information, so there is no "information leakage risk".

In recent years, it has also gained much attention on the aspects of "productivity improvement" and "teleworking environment improvement". (PayPal Invoice)

[Example of received email]

API connection to Workflow

"PayPal invoice" does not require introduction of particular system.

However, this ease of "you can send an invoice by logging in to PayPal" also brings new challenges such as "ambiguous approval by supervisor" and "difficult to make mistake checks by multiple people". Especially if a company emphasizes "Business Process", there is a possibility of being discussed as a problem on governance.

In the following Business Process definition example, we have realized the policy that

"to utilize PayPal invoice without logging in to PayPal"

by implementing API control from the Workflow system. That is, the data which have been approved and checked in the workflow system is automatically linked to PayPal side through the API, and the "command to send the invoice email" is also delivered from the Workflow system via the API. And all work records of "When and who did what" are all recorded on the Workflow system side.

* If it is a Cloud-based workflow "Questetra BPM Suite", it can be realized for free. (By importing the Business Process definition, you can build it in a few hours.)

[PayPal Invoice Issuance]

Passive Step of "Receiving acceptance report"

Illustration production, Website production, Interior construction... "Acceptance inspection" is accompaniment to these outsourced businesses.

Issues based on contract is, not simply 1)"to deliver" the deliverable, but through 2) the step of "Receiving an acceptance report" from the client, and finally you can 3)"Claim the commission fee".

(Although there are cases in special business relationship where "Acceptance inspection step' is omitted and "immediate billing on delivery" is allowed...)

Pathetically sincere efforts and ingenuity have been performed all over the world, such as
  • attaching a sample of "Acceptance report" for clients, or
  • titling the slip as "Acceptance report request (cum-Deliverly note)" instead of "Delivery note".

Not yet decided what the Step is for to do?

However, "Receiving of Acceptance report" in the reality, there are not only cases that
  • A) They give "Acceptance report" on the delivery day.

There occurs various cases such as
  • B) they will send "Acceptance report" to the inspection deadline limit, or
  • C) the client presupposes the application of the "provision on deemed inspection passed" without submitting the acceptance report.

Moreover, there could be
  • D) cases where it is judged that "the deliverable do not meet the specifications" and forced to extend the acceptance period, or
  • E) cases where it is judged that "the deliverable do not meet the specifications" and forced to re-deliver.

So what kind of Business Process diagram should you draw for such cases? In particular, for cases of C) which is "doing nothing until the deadline, then ends", it is difficult how to express it.

[Acceptance inspection corresponding flow]

Measuring working time on certain process

For example, when you want to measure the "time required for translation" in the translation process, you can consider a method that having "reporting (inputting)" actual working time" together with the"translation result".

However, in that method, it requires to have the workers to measure the actual work time in the means such as;
Such an act of "self-measuring and reporting working hours" must be a major effort.

* However, there are still advantages that it is possible to respond flexibly, such as temporarily stopping the measurement, when time to be excluded such as "coffee break" or "corresponding to interrupt work " occurs halfway.

The accuracy of the reported value

Also, "Inaccurate actual work time" may be reported as a result.

For example, the "work time" would be entered a little differently from the fact, if it is a system in which some incentive affects to make the "translation time" looks shorter (or longer) in terms of personnel evaluation and ability assessment.

Alternatively, if there are workers who are proud of their outcome of the work itself and have no interest in such as "translation time", we have to assume that 'perfunctory data' will be entered.

[Translation flow]