BloomSpec
Entities

Source file

An ingested file from a bank, processor, POS or ERP, with its structural fingerprint, record count and control totals.

Volume

Tens to thousands per day

Retention

Audit period — it is the evidence behind every match

Entity attributes8
  • Journal entry generation and posting must be idempotent, with deduplication keyed on the originating match or reconciliation record.
  • Source format changes must be detected at ingestion and fail loudly rather than producing a partial or misaligned parse.
  • Input files must be validated at ingestion for completeness, record count and expected structure before any matching runs.
  • source_file_id
  • source_system
  • Store instants in UTC, but never derive an accounting period from them.
  • Accounting date and system timestamp must be separate fields. The period an entry belongs to cannot be derived from when it was recorded.
  • Input files must be validated at ingestion for completeness, record count and expected structure before any matching runs.
Entity relationships1
Capability entities1
Entity lifecycle

Not yet researched

Only the control-bearing entities were modelled for lifecycle. Defensible as a starting point, but it does leave the entity model uneven, and this is incompleteness rather than a finding.

Capability operations7