Why two records

Where it connects

What you don’t have to change

Your ERP already is, and should remain, the system of record for the commodity — what you bought, from whom, in what quantity. Nset is the system of record for the performance that travels with it. Two records, two systems, deliberately.

The commodity and its environmental performance have different owners, different lifecycles, and different auditors. Forcing them into one system means one of them is served badly. Keeping them separate — but linked — lets each stay authoritative. Your procurement team keeps its workflow; the performance gets a workflow of its own.

This mirrors how other financial infrastructure works. Your bank does not replace your accounting system; it settles transactions your accounting system records. The rail settles performance your ERP never tracked in the first place.

None of these require a new source of truth for the commodity itself. They add a linked source of truth for the performance — which never had one.

Not your ERP, not your suppliers, not your procurement process. The rail is designed to snap into workflows buyers already run, because a reduction that requires reorganizing the company will not get bought. The point is to add a record, not replace one.