Showing posts with label Payments. Show all posts
Showing posts with label Payments. Show all posts
To continuously improve business processes is to polish corporate competitiveness. In particular, the financial, information communication and distribution industries are already beginning to have established BPM practices. More vendors who offer BPM systems have a variety of workflow templates.

The primary areas for BPM application include complaint management, loan approvals, management of accounts payable in resource management and procurement, reimbursement management and asset management. Corporations with a long history of BPM activities tend to apply BPM to difficult business processes, such as management of accounts payable and budget planning.

The below workflow is a very simple form of accounts payable management. There is no Swimlane representing the accounting department, but if they refer to the list of approved invoices, they can pay them at once at the end of the month.

<Tasks>
1. Receive Invoice, 2. Approve Payment, 3. Inquiries


[Management_Supervisor : "2. Approve Payment" screen]

<Process Data Items>
  • title <<Payee and use (ex: Japan Printing/50000 leaflets)>>
  • Payment to (string)
  • Amount (numeric)
  • Ordered on (date)
  • Payment deadline (date)
  • Summary of invoice (string: text box 3 lines)
  • Scanned invoice (file)
<<Control>>
  • Supervisor approval (select:OK/No)
  • Correspondence (discussion)

Of course, it would not be bad to define the role of accounting. That way, the upstream purchasing employee can see whether the downstream accounting made the payment or not. Of course, the deadline of [4. Make Payment] corresponds to the process data item "payment deadline."

<Tasks>
1. Receive Invoice, 2. Approve Payment, 3. Inquiries, 4. Make Payment


Processing salaries is an important job. The person in charge of this has to collect each employee's total work time and calculate overtime compensation, compensation for working on holidays, and late night compensation.

Today's workflow sample assumes all employees report their attendance records in their own attendance file (Excel). They have to submit this every month, but they can use the same file over the course of one year, with 12 separate sheets within the file. Basic information (Process Data) can be copied from the previous month.


<Tasks>
1. Request Attendance Log, 2. Input Attendance Log, 3. Supervisor Confirmation, 4. Revise, 5. Accounting Confirmation


[Attendance Report <Bypass Input>: "2. Input Attendance Log" screen]