Core Concepts
Data Integrity and Issues
Understand structured issues and layers of accounting validation
VRPlatform continuously checks configuration and calculated output. A successful read can include issues even when the resource remains usable.
| Layer | Purpose |
|---|---|
| Schema | Required fields, formats, and basic values |
| Business rules | Conditional validity across related fields |
| Accounting | Balance, dates, ownership, accounts, and assignments |
| Historical state | Books closing, statements, and reconciliation |
| Concurrency | State that changed between read, preflight, and write |
Issues use stable machine-readable codes plus severity, category, message, affected count, and contextual identifiers. Use code and context for program behavior; the message is display text.
Repair the condition: configure a mapping, select an eligible account, use an open posting date, settle a balance, or correct source data. Do not suppress an issue because a previous operation happened to succeed.
See the generated Issue Catalog, Portfolio health, and Requests, Locks & Issues.