What you run
One program, five phases.
01EstablishBoundary, baseline, cap and trajectory.
02AllocateAllowances to participants, individually or pooled.
03Operate & measurePositions tracked against allowance.
04SettleExcess settled with validated carbon credits bought from Origin Ledgers, retired in the originating registry.
05RecordPVN validates; Origin Ledgers records.
Your boundary, stated plainly
Four responsibilities Origin Ledgers does not assume.
Origin Ledgers does not replace your operational role, your contractual responsibilities, or your regulatory obligations. It validates defined lifecycle conditions around the event you submit. The underlying activity remains within your own responsibility and control.
EnvironmentalWhether the underlying allowance activity is real, correctly measured, and supported by the required evidence remains your responsibility. Your MRV and applicable environmental records provide that basis.
OperationalImplementation, scheduling, measurement, and internal control of the activity within your operational boundary remain with you. We validate the lifecycle event you submit — not the process that produced it.
LegalContractual commitments to counterparties, representations you make, and obligations arising from your agreements remain with you. Validation does not transfer or reduce those responsibilities.
RegulatoryCompliance with applicable law and your program rules remains your responsibility. A validated record is not a legal, regulatory, or compliance opinion.
And the reverse holds: submission does not make an event valid or complete. An event must satisfy its defined conditions, reconcile against the expected state, and reach the required lifecycle state before it can proceed.
What Origin Ledgers provides
The infrastructure your program runs on.
The program record (LEDGERS)Boundary, allowances, positions, surrender and settlement in one record.LEDGERS
Participant accountsAn Origin Ledgers account, a register account and a designated virtual account for each participant. A designated virtual account is not a bank account in your name.Accounts & Payments
Validated carbon creditsBuy validated carbon credits from Origin Ledgers at a quoted price, or let participants buy them under your program rules. Set supply rules by tier: registry-verified or benchmark-assessed. Prepay by default. Approved program managers can have payment terms.ORIGIN
Independent validationPVN validates and reconciles every lifecycle event.Provenance
What gets validated
Six checks applied to every lifecycle event.
A validated result means the defined digital conditions have been satisfied. It does not certify the underlying emissions activity, establish environmental validity, or authorize a transaction. Validation is a technical determination about the submitted event. Environmental responsibility remains with the responsible party. Authorization and execution remain separate controls.
Asset class
Quantity & tolerance
Program & boundary references
Lifecycle-state consistency
Duplicate detection
Reconciliation status
When something doesn't reconcile
Held or escalated. Never treated as complete.
quantity variance
The event is heldIf the submitted quantity falls outside the tolerance defined in the validation profile, the event is held. It is not clipped to the quantity received, rounded into tolerance, or treated as complete.partial confirmation
It stays evidenceIf part of the expected quantity is confirmed, that confirmed amount remains recorded as reconciliation evidence. It does not turn the event into a partial completion, and it cannot be rounded up to a completed event.unresolved variance
A person decidesWhere a variance cannot be resolved through defined validation conditions, the event is escalated for operator or governance review. No timer, retry loop, or elapsed period resolves the exception automatically.A partial result is evidence of what happened — not evidence that the event completed.
Worked example · dummy data
A submission that gets rejected.
Next stage A rejected run stays rejected. A correction starts a new run. The fix is a corrected submission as a new event with its own run — not a retry of RUN-00907, and not an override. Your original submission stays in the record exactly as it arrived.
The control sequence
Nothing moves until every required control clears.
01Participant authorization
02Origin Ledgers policy checks
03PVN validation
04Registrar signing
05Execution
06Reconciliation and recording
Origin Ledgers operates the program register. Participants hold no keys. Register operations are signed with Origin Ledgers’ registrar keys, only after authorization, policy checks and PVN validation.
Validated is never the same as authorized.
Trust and reviewGetting started
From scope to live program in typically 30–90 days.
1Scope the boundary
2Establish the baseline
3Configure the cap and schedule
4Onboard and go live
Day 0
Typically 30–90 days
Live
Depends on scope, data readiness, participant population and configuration.
Invited to a program by a company you work with?
Join a Program
Reviewer questions