2 min lesson
Producers, consumers and the data contract
Use "Producers, consumers and the data contract" to explain each part and the role it plays.
Step 1 of 2
Producers, consumers and the data contractwho owns correctness when data crosses teams
Ownership gets murky once data crosses team lines, because analytics, accounting and engineering all touch the same numbers. A clean mental model is producers vs. consumers. When finance runs its close on platform data, finance is the consumer; the partner teams emitting the upstream tables are the producers. The thing that makes the relationship work is an explicit data contract negotiated with those producers, covering three dimensions.
- Completeness
- Every row that should be there is there, with no silently dropped partitions feeding the close
- Accuracy
- The values are correct, not just present, and the producer asserts on content as well as on the job running
- Timeliness
- The data lands inside the window the consumer needs, and a close has a hard calendar deadline
Snapshot-and-diff backs the contract: take snapshots as data changes and run reconciliations against them, so a breach is caught against a known-good baseline rather than discovered at close.
Cursor's finance team describes governance for the close this way: finance is a data consumer, the partner teams are producers, and the two sides agree explicit contracts on completeness, accuracy and timeliness, with snapshot-and-diff as the data changes.
The takeaway for your answer is the shape of the arrangement: name the consumer, name the producers and write the contract down before the close, not after it breaks.