What this category's data looks like
This page handles exception tracing and manual review of research funding budget adjustments and reimbursements. The materials include three categories: budget adjustment applications, reimbursement forms, and contract invoices. Budget adjustment applications record the account, amount, adjustment reason, and approval chain; reimbursement forms carry expense details, the handler, date, and signature; contract invoices provide the counterparty, amount, invoice date, and receipt. When the three categories of materials enter this function, the HTTP node in the workflow first initiates a request to the external system to retrieve the original records and version information, for subsequent nodes to compare fields, dates, and signatures. The update rhythm is generated transaction by transaction along with the reimbursement and adjustment processes, and the field characteristics are concentrated in the name, quantity, date, version number, and signature field.
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 exception list and review conclusions are obtained by subsequent nodes parsing the response, or the external system completes them next according to the agreement. The request URL, path parameters, request headers, and request body can all reference variables via {{}}, and authentication information is placed in Authorization according to the external system's requirements.
| Object | Check | Verification action |
|---|---|---|
| Budget adjustment application | Whether the account, amount, adjustment reason, and approval chain are consistent with the contract invoice | Retrieve the original record, compare the account name, amount, and date, and check the approval signature and version number |
| Reimbursement form | Whether the expense details, handler, date, and signature correspond to the budget adjustment application | Parse responseData, compare the name, quantity, and date item by item, and check the signature and receipt |
| Contract invoice | Whether the counterparty, amount, invoice date, and receipt match the reimbursement form | Check the request header Authorization and the request body fields, and confirm that the invoice receipt and version are synchronized |
| Exception list and review conclusions | Whether each exception is supported by an original record and signed by the reviewer | Check each placeholder source in the variables panel, and confirm that the exception can be traced back to the source material |
Three common errors
- Symptom: The name, quantity, and date of the same record do not match between the budget adjustment application and the reimbursement form. Cause: The two materials are entered separately, without field-level comparison and version synchronization.
- Symptom: The contract invoice has been updated, but the reimbursement form still references the old version, and the review conclusion and receipt are missing. Cause: The version is not synchronized, and the signature or receipt field is empty.
- Symptom: The request returns 401, and the external system receives empty fields. Cause: The source of the
Authorizationvalue and the request body fields are not passed in according to the external interface agreement.
How to verify the setup
Preview the rendered request, check the status code and returned fields, and then compare the result against one sample.
Business test: create one exception record and see whether it can be traced back to the source material.
- In the request preview, view the complete rendered URL and check whether the path parameter placeholders are parsed into actual values.
- In the variables panel, check the source of each placeholder, and confirm that the request header names and value sources meet the external system's requirements.