Reimbursement application process/Submitting one by one,Receipt image up-loading,Superior approval

This sample process is for reimbursement application. The receipt is digitally managed

Summary

 * In a corporate organization, the constituent member adjusts payments in place of others.
 * The receipt is converted to an image file and contributed. (taking a picture with PC camera, and scanning, etc.)
 * When there is no receipt, such as the case of credit-card transactions or small sum for transportation, etc., are applied for by "Circumstances explanation" and "Put of the confirmation e-mail text", etc.

Possible risks

 * Unfair billings:Unfair billings to the organization are generated by the falsification of the receipt image etc.

Advantage

 * "Submitting is forgotten[Forgetting to submit]" decreases by applying one by one when generated. (It is treatable while the matter circumstances are remembered well. )
 * The expense total can be understood in real time by applying one by one when generated. (The daily budget balance can be understood. )
 * Keeping documents can be reduced by converting the receipt into a digital image.

Disadvantage

 * One-by-one processing requires frequent approval compared with the monthly batch application.

Process owner

 * Director of Accounting Department

Participant

 * Member：　any-section@company.com
 * Leader：　any-section-leader@company.com
 * Accountant：　accounting@company.com

Process diagram and process data
digraph TMPG { graph [size="10,5", rankdir=LR]; node [shape=box, style=rounded]; edge [labelfloat=true];

subgraph clusterS { labeljust=l; label="any-section@company.com"; SS [label="", shape=circle, width="0.3"]; SE [label="", shape=circle, width="0.3", style=bold]; S1 [label="S1:Reimbursent \n Input of information\n (The receipt image is contained)"]; S2 [label="S2:Payment\n Confirmation of schedule"]; Se [label="Se:Rejected\n Confirmation of content"];

SS -> S1; S1 -> Se [dir=back,arrowhead=rcrowlvee, arrowtail=normal, weight=10]; Se -> S2 [style=invis,weight=10]; S2 -> SE [weight=10]; Se -> SE [tailport=n,headport=n,arrowtail=odiamond,label="Permission of rejection\n(Withdrawal of application)"]; }

subgraph clusterL { labeljust=l; label="any-section-leader@company.com"; L1 [label="L1:Application\nApproval of"]; }

subgraph clusterA { labeljust=l; label="accounting@company.com"; A1 [label="A1:\nApproval content confirmation\n(It is possible to correct it minutely. )\nPayment schedule input"]; }

S1 -> L1 ; L1 -> Se [arrowtail=odiamond, label="Rejected"]; L1 -> A1 [arrowtail=rcrowlvee, minlen=2, weight=10]; Se -> A1 [dir=back, arrowhead=odiamond, arrowtail=normal, label="Correction necessary"]; A1 -> S2 [arrowtail=rcrowlvee];

}


 * (R)：　The thing acquired in a standard function of BPMS is assumed.
 * [R]：　Depneding on routes, there exists no value.