Skip to main content

Submitting Audit Packages

Overview​

An Audit Package is the final submission that bundles all your evidence, models, and frameworks for review by Puro.earth and verification bodies. Once submitted:

  1. Puro.earth reviews for errors and inconsistencies
  2. If approved, it's forwarded to the appointed verification body
  3. The auditor reviews and may request revisions
  4. Upon approval, credits can be issued

Pre-Submission Consistency Check​

Before submitting your audit package, perform a thorough consistency check to ensure all information is aligned and complete.

Critical Consistency Checks​

1. Cross-Document Consistency​

Verify information is consistent across all evidence:

  • ✅ Are financial additionality assumptions aligned with LCA assumptions?
  • ✅ Do facility design documents match feedstock details in the LCA model?
  • ✅ Is the monitoring plan consistent with the LCA model?
  • ✅ Is the project description aligned with all documentation?

2. Supporting Files for Deviations​

  • ✅ Have you uploaded supporting files to explain any deviations or missing documents?
  • ✅ Are there notes included if files are intentionally misplaced?

3. File Naming​

  • ✅ Have all files, especially templates, been clearly and consistently renamed?
  • ✅ Do file names reflect the facility name and document purpose?

4. Confidential Information​

  • ✅ Are all publicly published documents free of confidential information?
  • ✅ Have you verified that files for the Puro Registry exclude sensitive or proprietary content?

5. Completeness​

  • ✅ Are all required documents fully populated?
  • ✅ Have all Expected Field Values been submitted?
  • ✅ Are all Evidence Requests either completed or properly skipped with reasons?
Incomplete Submissions

Inconsistencies or missing information may result in delays or revision requests. A thorough pre-submission check saves time and reduces back-and-forth.

Creating an Audit Package​

To submit an audit package for a facility, use POST /v0/facilities/{id}/audit-packages:

Create audit package
curl -X 'POST' "/v0/facilities/{id}/audit-packages" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $BEARER" \
  -d '{ \
    "subjects": [ \
      { \
        "id": "framework-instance-uuid", \
        "type": "FRAMEWORK_INSTANCE" \
      }, \
      { \
        "id": "model-uuid", \
        "type": "MODEL" \
      } \
    ] \
  }'

Subject Types​

You can include multiple subjects in an audit package:

  • FRAMEWORK_INSTANCE - A framework instance you created for the monitoring period
  • MODEL - A model (like LCA & CORC Report) you configured
Auditor Assignment

The auditor for the submitted package is selected automatically based on its subjects. All acknowledgement fields for those subjects are also set to true automatically.

Listing Audit Packages​

To view audit packages for a facility:

Get audit packages
curl -X 'GET' "/v0/audit-packages" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $BEARER"

Response Schema​

required
object

The primary organization reviewing the Audit Package.

required
Array of objects or null (Organization)

The secondary organizations reviewing the Audit Package.

id
required
string
facilityId
required
string
startDate
required
string or null <date-time>
endDate
required
string or null <date-time>
required
Array of objects (Audit)
required
Array of objects (AuditPackageField)
createdAt
required
string <date-time>

Getting Audit Package Details​

To retrieve details about a specific audit package:

Get audit package
curl -X 'GET' "/v0/audit-packages/{id}" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $BEARER"

The response includes:

  • Package ID and metadata
  • Associated audits for each subject
  • Primary and secondary auditor organizations
  • Start and end dates
  • Custom fields

Creating Audit Export Jobs​

To export detailed audit data:

Create audit export job
curl -X 'POST' "/v0/audits/{id}/export" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $BEARER"

This creates an asynchronous export job. Currently, only Framework Audits are supported.

Checking Export Status​

Get audit export job
curl -X 'GET' "/v0/audits/export/{id}" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $BEARER"

The response includes:

  • id - Job ID
  • status - PENDING, COMPLETED, or FAILED
  • signedUrl - Download URL when completed

Monitoring Audit Status​

Once submitted, monitor your audit package in the MyPuro portal for:

  • Comments from Puro.earth reviewers
  • Revision requests
  • Status updates
  • Auditor feedback
In-Platform Notifications

Suppliers will receive in-platform notifications for comments or revision requests from Puro or the auditor. Check the portal regularly during the review period.

Understanding Audit Statuses​

Each audit in your package has a status:

StatusDescription
IN_PROGRESSAudit is being reviewed
APPROVEDAudit has been approved
REJECTEDAudit was rejected; revisions needed

Responding to Review Feedback​

When you receive feedback:

1. Review Comments​

Carefully read all comments from reviewers and auditors.

2. Make Necessary Changes​

Update your evidence, field values, or models as requested:

  • Upload corrected files
  • Update field values
  • Adjust model calculations

3. Document Changes​

Keep track of what changes you made in response to feedback.

4. Resubmit if Required​

Depending on the feedback, you may need to create a new audit package with the corrections.

Snapshot After Approval

Once the auditor approves or fails a framework/model, the full framework or model is snapshotted and no further edits are allowed. Make sure everything is correct before final approval.

Getting Audit Reports​

After the audit is complete, retrieve the final audit report:

Listing All Audit Reports​

Get audit reports
curl -X 'GET' "/v0/audit-reports" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $BEARER"

Getting a Specific Audit Report​

Get audit report
curl -X 'GET' "/v0/audit-reports/{id}" \
  -H "Accept: application/json" \
  -H "Authorization: Bearer $BEARER"

Response Schema​

id
required
string
packageId
required
string
publishedAt
required
string or null <date-time>
required
object or null
required
Array of objects (AuditReportConfirmation)
required
Array of objects (File)
required
Array of objects (AuditReportField)

The audit report includes:

  • id - Report ID
  • packageId - Associated package
  • publishedAt - When the report was published
  • publishedBy - Who published it
  • confirmations - Confirmation records
  • files - Downloadable report files
  • fields - Summary fields

Final Audit Outcome​

As the final step, the auditor will submit a Verification Outcome Report, available from the Audits tab within your facility.

This report will include:

  • Final audit outcome (approved/rejected)
  • Number of credits issued (if any)
  • Auditor's findings and recommendations
Credit Issuance

Once the audit is approved, credits can be issued to the Supplier's account.

Best Practices​

  1. Check everything twice - Use the consistency checklist before submitting
  2. Submit complete packages - Don't submit partial or incomplete audits
  3. Respond promptly - Address review feedback as soon as possible
  4. Keep records - Maintain documentation of all changes and communications
  5. Plan for iterations - Be prepared for revision requests
  6. Monitor notifications - Check the portal regularly for updates

Common Submission Issues​

Missing Evidence​

Problem: Required evidence files not uploaded Solution: Review all evidence requests and ensure all are completed or properly skipped

Inconsistent Data​

Problem: Values don't match across documents Solution: Cross-check all related fields and documents before submitting

Calculation Errors​

Problem: Model calculations produce unexpected results Solution: Verify all expressions, field references, and input values

Confidential Information​

Problem: Public documents contain sensitive data Solution: Review all files and redact confidential information

Complete Audit Workflow Summary​

  1. ✅ Set up monitoring periods and apply frameworks
  2. ✅ Create and configure models
  3. ✅ Set up documents and expected fields
  4. ✅ Create evidence requests
  5. ✅ Upload evidence and submit field values
  6. ✅ Perform consistency check
  7. ✅ Submit audit package
  8. ✅ Monitor for feedback
  9. ✅ Address any revision requests
  10. ✅ Receive final audit outcome

Next Steps​

Congratulations on completing the audit submission! Once your audit is approved:

  • Credits will be issued to the supplier's account
  • You can begin preparing for the next monitoring period
  • Use learnings from this audit to improve future submissions

For ongoing support, contact your Puro Account Director or refer to the dMRV Connect specification for detailed endpoint documentation.