What this category's data looks like
This category's data involves three types of materials: budget adjustment applications, reimbursement forms, and contract invoices. Budget adjustment applications come from the project team and are submitted according to the project cycle; their fields include adjustment subject, amount, reason, approval signature, and date. Reimbursement forms come from the handler and are submitted according to reimbursement batches; their fields include expense details, quantity, unit price, total amount, signature, and receipt. Contract invoices come from suppliers or partners and are updated according to contract milestones; their fields include contract name, invoice number, invoice date, amount, and seal. After the three types of materials enter the workflow, the budget adjustment application serves as the basis for adjustment, the reimbursement form serves as the expenditure voucher, and the contract invoice serves as the original supporting document, together forming the reconciliation working papers for exception tracing and manual review.
Configuration and implementation checks
This step is executed by workflow nodes (user selection and branching), outputting branch directions and interaction status records. The exception list and review conclusions are completed by subsequent nodes continuing execution according to the branches. When the user selection node is triggered, the conversation enters an interactive state and records the workflow status; after the user completes the selection, execution continues along the branch corresponding to the selected option.
| Object | Check | Verification action |
|---|---|---|
| Budget adjustment application | Whether the adjustment subject, amount, reason, approval signature, and date correspond consistently with the reimbursement form and contract invoice | Compare the subject name, amount, and date of the adjustment application and the reimbursement form item by item, check whether the approval signature and receipt are complete, and verify the options and branch connections in the node |
| Reimbursement form | Whether the expense details, quantity, unit price, total amount, signature, and receipt match the contract invoice | Trace the name, quantity, and date of the contract invoice item by item according to the reimbursement form, check whether the versions are synchronized, reference the selection result variable in subsequent nodes, and run a trial once |
| Contract invoice | Whether the contract name, invoice number, invoice date, amount, and seal support the reimbursement form and adjustment application | Using the contract invoice as the source material, trace back the name, quantity, and date of the reimbursement form and adjustment application, check the seal and receipt, and trigger one view of the node status in the run records |
| Exception record | Whether the exception is supported by original records and the reviewer's signature | Create an exception record, trace it along the branch direction to the source material, and check variables, nodeId, and the interaction status records |
Three common errors
- Symptom: The name, quantity, and date of the same expenditure do not match between the reimbursement form and the contract invoice. Cause: The two materials were entered separately, were not compared field by field against the same record, and the discrepancy was not flagged.
- Symptom: The budget adjustment application has been updated, but the reimbursement form still references the old version. Cause: The versions were not synchronized, the node branch did not follow the latest material, and subsequent nodes used outdated fields when continuing execution.
- Symptom: The review conclusion lacks a signature or receipt, and the exception cannot be handed to the person in charge for handling. Cause: The process stopped after the interaction was completed, the selection result variable was not recorded, and the reviewer did not complete confirmation in the node.
How to verify the setup
Feature acceptance: run trials option by option, check the branch directions and interaction status in the run records, confirm that options and branches correspond one-to-one, that the selection result variable has been passed to subsequent nodes, and run a trial once referencing variables and nodeId in a subsequent node.
Business test: create an exception record, see whether it can be traced to the source material, check that the exception is supported by original records and the reviewer's signature, and then hand it to the person in charge for handling.
- Check the options and branch connections one by one in the node, and trigger one view of the node status in the run records
- Reference the selection result variable in a subsequent node and run a trial once to confirm that selecting a certain option will not still follow the default branch