Invoice Storage Process 2023<\/div>
A process for electronic storage of received invoices and receipts. This workflow is designed to adapt to the “Revision of the Electronic Book Law 2022” and “Start of Invoice 2023”. The recipient of the invoice registers the PDF invoice and the invoice amount in the received transaction data. The supervisor approves the registered invoices. The workflow platform saves the invoice file as digital data in various types of storage.<\/div><\/div>\n\n\n
<\/span>Workers (Number of swimlanes: 6)<\/div>
\n\n\n\n
- \n
- Operator’s supervisor<\/strong>\n
- \n
- Supervisor of the Procurement Officer. Approves the contents of the invoice (including electronic invoice).<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Accounting Dept.<\/strong>\n
- \n
- Accounting Department. Finalize invoices (including electronic invoices). Waiting for acceptance each time.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Operator (processor of step 1x)<\/strong>\n
- \n
- Procurement Officer. The person who received the invoice or receipt or registered the invoice data. (The user specified in the User-type data “Operator”)<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Operator<\/strong>\n
- \n
- Procurement Officer. The person who received the invoice or receipt.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Electronic Transactions (Sales Department)<\/strong>\n
- \n
- Procurement Officer. The person who verifies and registers the contents of the electronic invoice.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Electronic Transactions Processor (Development Department)<\/strong>\n
- \n
- Procurement Officer. The person who verifies and registers the contents of the electronic invoice.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n<\/div><\/div>\n\n\n<\/span>Workflow (Complexity of workflow diagram: 33)<\/div>\n\n\n\n
- \n
- 1a. Attachment + input date, amount, etc.<\/strong>\n
- \n
- The procurement manager registers the contents of the invoice PDF (including other receipts, etc.)<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- 1b. Enter date, amount, etc.<\/strong>\n
- \n
- The procurement officer (after forwarding the email with the invoice PDF attached) registers the contents of the invoice PDF.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- 1c. \nConfirmation posting of dates, amounts, etc.<\/strong> <\/li>\n\n\n\n
- <\/i>18<\/span><\/span><\/span> 1c. Confirmation posting of dates, amounts, etc.<\/strong> <\/li>\n\n\n\n
- 2. Recognition by supervisor<\/strong>\n
- \n
- The procurement manager’s supervisor approves the request.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- 3. Accounting Approval<\/strong>\n
- \n
- The Accounting Department will perform a final review of the invoices (including other receipts, etc.) to be kept.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- 4. Remittance Processing<\/strong>\n
- \n
- The Accounting Department handles invoices that require transfer processing.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- 9. Call-back<\/strong>\n
- \n
- The procurement manager will re-register the contents of the invoice PDF (including other receipts, etc.)<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- From to Quser<\/strong>\n
- \n
- The workflow platform references the string type “From” and sets the Quser type person in charge.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Backup to G-Drive<\/strong>\n
- \n
- The workflow platform saves files to Google Drive.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- parse Peppol<\/strong>\n
- \n
- The workflow platform parses the incoming Peppol and sets the date\/transaction amount\/party name, etc.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- parse Peppol<\/strong>\n
- \n
- The workflow platform parses the incoming Peppol and sets the date\/transaction amount\/party name, etc.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- <\/i>31<\/span><\/span><\/span>Rename a file<\/strong>\n
- \n
- The workflow platform adds “PID-Date-” to the Prefix of the file name.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Enter title to non-deletable area<\/strong>\n
- \n
- The workflow platform writes the case title to the log (non-deletable area).<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Automatically set receipt title<\/strong>\n
- \n
- The workflow platform sets the Date\/Transaction Amount\/Franchisee Name as the title of the case.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n<\/div><\/div>\n\n\n<\/span>Workflow Diagram (click to open)<\/div>\n\n\n\n
![\"\"](\"https:\/\/i0.wp.com\/support.questetra.com\/wp-content\/uploads\/2023\/03\/eye-catch-e-invoice-storage-2023-en-1024x513.jpg?resize=1024%2C513&ssl=1\")
<\/a><\/figure>\n\n\n\n- \n
- BPMN Icons\n\n\n\n\n
- \n
- Start Event<\/li>\n\n\n\n
- End Event<\/li>\n\n\n\n
- Merge Gateway (XOR)<\/li>\n\n\n\n
- Message Start Event (email)<\/a><\/li>\n\n\n\n
- Message Start Event (HTTP)<\/a><\/li>\n\n\n\n
- Message Start Event (Webhook)<\/a><\/li>\n\n\n\n
- Exclusive Gateway\n(XOR)<\/a><\/li>\n<\/ul>\n\n\n\n
- \n
- Human Task<\/a><\/li>\n\n\n\n
- Update Data<\/a><\/li>\n\n\n\n
- Google Drive: Upload File<\/a><\/li>\n\n\n\n
- Script Task<\/a><\/li>\n\n\n\n
- Service Task (Add-on): Converter: Email-Str to Quser<\/a><\/li>\n\n\n\n
- Serevice Task (Add-on): Files, Duplicate<\/a><\/li>\n\n\n\n
- Service Task (Add-on): any data-type, Output to Log<\/a><\/li>\n\n\n\n
- Intermediate Error Catch Event (Boundary Type)<\/a><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n<\/div><\/div>\n\n\n
- Update Data<\/a><\/li>\n\n\n\n
- Message Start Event (HTTP)<\/a><\/li>\n\n\n\n
- BPMN Icons\n\n\n\n\n
- The workflow platform sets the Date\/Transaction Amount\/Franchisee Name as the title of the case.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n<\/div><\/div>\n\n\n
- <\/i>18<\/span><\/span><\/span> 1c. Confirmation posting of dates, amounts, etc.<\/strong> <\/li>\n\n\n\n
- 1a. Attachment + input date, amount, etc.<\/strong>\n
- Procurement Officer. The person who verifies and registers the contents of the electronic invoice.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n<\/div><\/div>\n\n\n
![\"\"](\"https:\/\/i0.wp.com\/support.questetra.com\/wp-content\/uploads\/2023\/03\/eye-catch-e-invoice-storage-2023-en.jpg?ssl=1\")
<\/a><\/figure>\n\n\n\n