What this category's data looks like
This page addresses the category of research funding budget adjustments and reimbursements. The materials include three types: budget adjustment applications, reimbursement forms, and contract invoices. Budget adjustment applications record the account, amount, adjustment reason, and approval date; reimbursement forms record expense details, quantity, handler, and signature; contract invoices record the supplier, invoice date, amount, and receipt. The three types of materials enter in batches by business node, and the update cadence changes with the approval and invoicing progress. When entering the vector model and index feature, budget adjustment applications and contract invoices serve as basis sources, while reimbursement forms serve as the objects to be checked; each is stored by data row and generates a corresponding vector identifier. Field characteristics are concentrated in four types: name, quantity, date, and signature. Cross-material comparison requires referring back to the original text.
Configuration and implementation checks
This step is executed by the index service and vector database, outputting vectors and index status (whether recall is possible, whether data in the same group is merged). Basis entries that can refer back to the original text are then completed by subsequent AI nodes, code nodes, or manual work (retrieval and citation trimming only take supporting materials). The index model must be consistent with the vector model actually used by the knowledge base, and data rows record multiple vector identifiers in the index field.
| Object | Check | Verification action |
|---|---|---|
| Budget adjustment application | Whether the account name, adjustment amount, approval date, and signature correspond to the contract invoice | Open the data row to check the index field, confirm that multiple vector identifiers are complete, and run a retrieval once to see whether the same group is merged |
| Reimbursement form | Whether the expense name, quantity, handling date, and signature are consistent with the budget adjustment application | Compare the reimbursement form with the original text of the budget adjustment application, record differences in name, quantity, and date, and check the reference text budget of limit |
| Contract invoice | Whether the supplier name, invoiced amount, invoice date, and receipt correspond to the reimbursement form | Check the contract invoice receipt and signature, confirm that the version is current, and check that the number of references for limit is recorded separately |
| Data row index field | Whether multiple vector identifiers for one piece of data are complete, and whether the status is indexed | Open a data row to check the index field, and view the data range covered by the rebuild task record |
Three common errors
- Symptom: The name and quantity of the same record do not match between the budget adjustment application and the reimbursement form. Inspect the following: The two materials were entered separately, without referring back to the original text for verification.
- Symptom: The contract invoice version was not synchronized, and retrieval still recalls the old amount. Inspect the following: After changing the model, rebuild was triggered only for data that had already been indexed, and old data was not covered.
- Symptom: The reimbursement form lacks a signature or receipt, and duplicate entries appear in retrieval results. Inspect the following: The data row has content but cannot be retrieved, and data in the same group was not merged by identifier to take the highest score.
How to verify the setup
This feature's acceptance check: sample one data row to inspect the index field, confirm multiple vector identifiers and the indexed status, then run a retrieval once to see whether data in the same group is merged and the highest score is taken.
Business test: ask a cross-material basis question, see whether the answer provides a source that can be traced back to the original text, and check that the number of citations and the citation text tokens are recorded separately.
- In the knowledge base settings, check that the index model is consistent with the vector model actually used by the knowledge base, and view the data range covered by the rebuild task record.
- Open a data row to check the index field, confirm that multiple vector identifiers are complete, check after retrieval whether data in the same group is merged, and record the reference text budget of
limit.