IX. The Stable Contract

Every source collapses into one canonical MINT schema.

Receivables do not enter the engine in a stable form. An ERP extract and an investor pool tape describe the same asset class in different languages. Phase 2 collapses that variation into one internal contract. Raw accounts receivable from any source, ERP export, scheduled file, pool tape, or API payload, is mapped into a canonical MINT invoice schema, validated, and tagged with every derivation or assumption. Eligibility and concentration rules run only after the record shape is fixed. The output is a clean validated pool tape. Aging, concentration, structuring, pricing, and surveillance all run against the same stable contract.

The ingestion layer is the only part of the engine that knows anything about source level variation. Everything downstream sees one structure.

Assumption transparency is part of the product. If a field is derived, defaulted, or rejected, that record travels with the output package.

Next post in series:

X. Pool Fixity

VIII. Resolve the Receivable