What this category's data looks like
This page addresses research funding budget adjustment and reimbursement scenarios, covering three types of materials: budget adjustment applications, reimbursement forms, and contract invoices. Budget adjustment applications carry inter-account amount changes and the approval chain; reimbursement forms record actual expenditures and invoice details; contract invoices provide the basis for transaction amounts and invoicing dates. The material sources are the research management system and the financial shared services platform, and the update cadence follows approval flow and invoice receipt. Field characteristics include account name, amount, date, signature, and receipt number. When the materials enter the HTTP interface, each assumes the role of a request body field or path parameter: budget adjustment applications provide the amounts before and after adjustment, reimbursement forms provide expense details and the associated contract number, and contract invoices provide the invoice code and amount verification value. Version maintenance requires that the current version be unique, old versions be traceable, and references be synchronized, with ledger updates driven by the response body and status code returned by the interface.
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 "version ledger and change records" are parsed from the response by subsequent nodes, or handled by an external system according to the agreement to complete the process. Variables can be used as placeholders in all three places: the request URL, request headers, and request body. Variables come from global variables, system variables, or the output of preceding nodes.
| Object | Check | Verification action |
|---|---|---|
| Budget adjustment application | The account name, adjustment amount, effective date, and approval signature are consistent between the application form and the budget ledger | In the request preview, check the rendered path parameters and request body fields, and compare the signature field with the receipt number |
| Reimbursement form | The name, quantity, date, and associated contract number of the expense details correspond between the reimbursement form and the contract invoice | Use a sample request to compare the returned fields, and check whether the amount and invoice number in responseData are synchronized |
| Contract invoice | The invoice code, invoiced amount, and contract amount match between the invoice and the contract materials | Check the source of the Authorization value in the request header, and confirm that the authentication information is passed in according to the external system's requirements |
| Variable source | Each placeholder variable can be traced to a global variable, system variable, or the output of a preceding node | In the variables panel, check the origin of each placeholder in variables, and confirm that there are no empty fields |
Three common errors
- Symptom: The amount and date of the same reimbursement form do not match between the budget ledger and the contract invoice. Cause: The two materials were entered separately, and field mapping was not performed based on the same record.
- Symptom: The budget adjustment application has been updated, but the reimbursement form still references the old account name. Cause: The versions were not synchronized, and the reference relationship was not refreshed with the change records.
- Symptom: The contract invoice lacks a signature or receipt number. Cause: The material circulation step did not return the receipt voucher, so the interface's returned fields are incomplete.
How to verify the setup
Preview the rendered request, check the status code and returned fields, then compare the result against a sample to confirm that the version number and reference identifier in responseData are updated synchronously.
Business test: change one piece of content and see whether the version number and references are updated synchronously.
- In the request preview, view the rendered complete URL and request body, and check the
Authorizationrequest header name and the source of its value. - In the variables panel, check the origin of each placeholder in
variables, and confirm that the variables in all three places—path parameters, request body, and request headers—can be resolved into actual values.