What this category's data looks like
This page focuses on business basis queries for research funding budget adjustments and reimbursements. The materials include three types: budget adjustment applications, reimbursement forms, and contract invoices. Budget adjustment applications record the adjustment reason, amount, and approval nodes; reimbursement forms carry expense details, handler, and approval signatures; contract invoices provide transaction evidence and invoice dates. The material sources are research group and finance archives, and the update cadence advances with the approval process. Field characteristics are concentrated in name, quantity, date, and signature fields. When entering this feature, the budget adjustment application serves as the starting point for the adjustment basis, the reimbursement form serves as the direct evidence of expense occurrence, and the contract invoice serves as corroboration of transaction authenticity. Together, the three support back-referencing and version comparison of basis entries.
Configuration and implementation checks
This part is executed by application settings (response limit, etc.), which output the length of a single answer and the range of context that can be accommodated. "Basis entries that can back-reference the original text" are then completed by the model. The response limit uses a slider to control the length of a single answer. If set too low, the answer will be truncated; if set too high, consumption will increase.
| Object | Check | Verification action |
|---|---|---|
| Budget adjustment application | The adjustment reason, amount, and approval date must be consistent with the reimbursement form, and the signature field must be complete | Check the application number, amounts before and after adjustment, approval signature, and date, and confirm the version is current |
| Reimbursement form | The name, quantity, and date of expense details must correspond to the contract invoice, and the handler and approval signatures must be complete | Compare the name, quantity, and date of the reimbursement form and contract invoice item by item, and check signatures and receipts |
| Contract invoice | The invoice date, amount, and contract terms must match the reimbursement form; when the version is not synchronized, the current archive shall prevail | Check the contract number, invoice number, invoice date, and amount, and confirm there are no missing signatures or receipts |
| maxResponse, quoteMaxToken, maxContext | The response limit and context range are controlled by application settings and do not determine access authorization | In application settings, check the position of the response limit slider and see whether the end of a single answer is complete |
Three common errors
- Symptom: The same adjustment amount does not match between the budget adjustment application and the reimbursement form. Cause: The two materials were entered at different times and no cross-check was performed.
- Symptom: The date on the contract invoice is inconsistent with the date on the reimbursement form. Cause: The version is not synchronized, and the old invoice is still in the archive.
- Symptom: The reimbursement form lacks an approval signature or receipt. Cause: The approval process was not completed before archiving, and the signature field is empty.
How to verify the setup
Feature acceptance: Ask a question that requires a long answer, see whether the ending is complete, confirm that the response limit matches the answer length required by the page, and check the positions of maxResponse, quoteMaxToken, and maxContext in application settings.
Business test: Ask a basis question that spans materials, see whether the answer gives a back-referenceable source, and confirm that the basis comes from the institution’s materials, that the version is current, and that the entries match the original text.
- In application settings, check the response limit switch and slider position, and compare usage changes between two runs.
- Ask a question that requires a long answer, check whether the end of the answer is complete, and record the
quoteMaxTokenof the quoted text and the number of array entries.