What this category's data looks like
The acceptance materials for research funding budget adjustment and reimbursement mainly come from three categories: budget adjustment applications, reimbursement forms, and contract invoices. Budget adjustment applications record fund transfers between accounts and the reasons for adjustment; reimbursement forms carry expenditure details, dates, and handler signatures; contract invoices provide the transaction basis, invoicing information, and receipts. When materials enter the Q&A acceptance and missing-item follow-up function, each plays a different role: budget adjustment applications are used to determine whether the adjustment is within the authorized scope, reimbursement forms are used to check the correspondence between expenditures and budget accounts, and contract invoices are used to verify transaction authenticity and amount consistency. Materials enter in batches, and the update rhythm is synchronized with the financial cycle. Field characteristics are concentrated in amounts, accounts, dates, handlers, and approval signatures. In the Q&A acceptance step, it first identifies whether the question lacks key material information, then decides whether to ask a follow-up question, ensuring that answers have a material basis.
Configuration and implementation checks
This step is executed by the HTTP node in the workflow, which outputs the response body, status code, and returned fields. The "acceptance records and items to be completed" are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the next step. The request URL, path parameters, request headers, and request body can all reference global variables, system variables, or outputs from preceding nodes through variables. Authentication information is placed in Authorization according to the external system's requirements, and the returned content is carried by responseData.
| Object | Check | Verification action |
|---|---|---|
| Budget adjustment application | Whether the account, amount, adjustment date, and signature are consistent with the reimbursement form | Compare the account name, amount, and date in the two materials field by field, and check whether the signature and receipt are complete |
| Reimbursement form | Whether the expenditure details, handling date, and the quantity and amount on the contract invoice match | Extract the quantity and amount from the reimbursement form, check them item by item against the contract invoice, and mark inconsistent items |
| Contract invoice | Whether the invoicing name, quantity, date, and version are synchronized with the budget adjustment application | Check the invoice title against the contract name, quantity, and date, and check whether the version is synchronized and whether the receipt is missing |
| HTTP node | Whether the placeholder variables in the request preview can be resolved into actual values | Check the source of each placeholder in the variables panel, and use a sample request to compare the returned fields and status code |
Three common errors
- Symptom: The name, quantity, or date of the same expenditure does not match between the reimbursement form and the contract invoice. Cause: The two materials were entered separately, and no cross-check was performed.
- Symptom: The budget adjustment application has been updated, but the reimbursement form still references the old version of the account and amount. Cause: The version was not synchronized, and there is no unified version identifier.
- Symptom: The acceptance record lacks the handler's signature or the external system receipt. Cause: The material circulation step did not return confirmation information, and the missing item was not identified.
How to verify the setup
Acceptance of this function: preview the rendered request, check the status code and returned fields, then compare the result against one sample to confirm that Authorization, variables, and responseData all appear as agreed.
Business test: submit a question that lacks key information, see whether it asks a follow-up question before answering, and check whether the answer references fields from the budget adjustment application, reimbursement form, or contract invoice.
- In the variables panel, check the source of each placeholder variable, and confirm that the placeholders in the request URL, path parameters, request headers, and request body can all be resolved into actual values.
- Use one sample request to compare the returned fields with the external interface agreement, and check whether the request header names and value sources meet the external system's requirements.