What this category's data looks like
This page centers on research funding budget adjustments and reimbursements, bringing three types of materials—budget adjustment applications, reimbursement forms, and contract invoices—into a single set of progress records and statistical verification. Budget adjustment applications provide the adjustment reason, amount, and approval chain; reimbursement forms carry the actual expenditure, handler, and date; contract invoices are used to compare names, quantities, dates, and signed receipts. The materials come from submissions by handlers, financial ledgers, and external system callbacks, updated weekly and aggregated monthly. Field characteristics center on amounts, dates, signatures, version numbers, and external document numbers. If the name, quantity, or date of the same record does not match across the two types of materials, the progress table and the statistical basis will diverge.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, outputting the response body, status code, and returned fields. The "progress table and statistical basis description" is parsed from the response by subsequent nodes, or handled by the external system according to the agreement to complete the rest. The request URL, path parameters, request headers, and request body can all use variable placeholders, and the variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Budget adjustment application | The application amount, adjustment date, and approval signature must match the ledger, and the version number must be traceable | Check the placeholder sources in the variable panel, render the request with variables, and compare the returned fields |
| Reimbursement form | The reimbursement amount, handling date, and receipt must be aligned line by line with the contract invoice | Use one sample request to compare the response, and check the name, quantity, and date in responseData |
| Contract invoice | The contract name, invoice quantity, invoice date, and signed receipt must mutually corroborate with the reimbursement form | Check the source of the Authorization value in the request header, then compare the fields of the two materials |
| External system callback | The external document number must correspond one-to-one with the internal record, and missing signatures or receipts must be flagged | View the fully rendered URL in the request preview, and check whether the returned fields contain the receipt flag |
Three common errors
- Symptom: The name, quantity, or date of the same reimbursement does not match between the reimbursement form and the contract invoice. Cause: The two materials are entered separately and are not cross-checked against the same record.
- Symptom: The budget adjustment application has been updated, but the progress table still shows the old version. Cause: The version is not synchronized, and the HTTP node retrieves a cached or old variable value.
- Symptom: The reimbursement form lacks a signature or receipt, but the statistics still include it in the total. Cause: The basis does not list signatures and receipts as mandatory verification items, and exceptions are not listed separately.
How to verify the setup
This feature's acceptance: preview the rendered request, check the status code and returned fields, then compare the result against one sample to confirm that the name, quantity, and date in responseData are consistent with the variables values.
Business test: use one week of records to verify the total, see whether the basis and exceptions are clearly stated, and confirm that the record count and statistical count match and that the basis is written into the table header.
- In the variable panel, check the source of each placeholder, and confirm that the placeholders in the request URL, path parameters, request headers, and request body can all be traced to global variables, system variables, or the output of preceding nodes.
- Use one sample request to compare the response, check
AuthorizationandresponseData, and record the exceptions for name, quantity, date, signature, and receipt one by one in the progress table header.