Schema design
- Use names that describe the source and record type.
- Keep field names stable across runs.
- Represent identifiers as strings unless arithmetic is required.
- Represent money and quantities consistently.
- Document fields that are derived or normalized.
Schema lifecycle
Change control
Changing a schema can change future run output. When a schema change affects comparison behavior, record why it changed and which reconciliation runs use the revised schema.To create a schema in Darpan, see Create a schema.