Export Formats
AlchemOS Positive supports multiple export formats across reports, emission entries, offsets and certificates. Use this page as a reference for what each format contains and when to use it.
When to use
- Sharing with stakeholders who do not have a platform account
- Submitting to regulators or auditors
- Archiving a point-in-time snapshot of your sustainability position
- Annual reports and boardroom presentations
Contents
- Full visual layout matching the on-screen report
- Charts rendered as vector graphics
- Embedded fonts for consistent rendering
- Digital signature block (optional) for audit submissions
- AlchemOS Positive watermark and generation timestamp
Limitations
- Not machine-readable; not suitable for importing into other systems
- Charts cannot be edited post-export
Excel (.xlsx)
When to use
- Further analysis in Excel or Google Sheets
- Sharing with finance teams for budget integration
- Pivot tables and custom charts from raw data
Contents
Multi-sheet workbook:
| Sheet name | Contents |
|---|---|
| Summary | Key metrics matching the report summary table |
| Emissions | Grain-level emission entries (one row per entry) |
| Factors | Emission factors used, with source and vintage |
| Offsets | Credits purchased and retired |
| Targets | Active targets and milestone progress |
| Charts | Static chart images embedded in sheet |
| Metadata | Generation date, period, org name, currency |
Limitations
- Charts are static images (not linked to data cells)
- Protected column headers cannot be deleted
CSV (comma-separated values)
When to use
- Importing into data warehouses or BI tools (Power BI, Tableau, Looker)
- Feeding into custom scripts or ETL pipelines
- Sharing raw data with third-party auditors
Contents
For reports with multiple sections, each section is exported as a separate .csv file, bundled into a .zip archive.
For entry-list exports, each row is one emission entry:
| Column | Description |
|---|---|
entry_id |
Unique entry identifier |
scope |
1, 2, or 3 |
category |
Activity category code |
subcategory |
Activity subcategory code |
quantity |
Measured activity amount |
unit |
Activity unit |
tco2e |
Calculated emission (tCO₂e) |
factor_code |
Emission factor code used |
factor_source |
Source of factor (DEFRA, EPA, etc.) |
factor_vintage |
Year the factor was published |
period_start |
Entry period start (ISO 8601) |
period_end |
Entry period end (ISO 8601) |
location |
Site / cost centre |
state |
Draft / Approved / Locked |
created_at |
Timestamp (UTC, ISO 8601) |
Limitations
- No visual formatting (no charts)
- Columns are fixed; use the JSON export for schema flexibility
JSON
When to use
- API-driven consumption by internal tools or dashboards
- Embedding sustainability data in ERP or finance systems
- Custom integrations not covered by the REST API webhooks
Contents
Structured JSON matching the REST API response schema. Includes nested objects for related data (e.g., entry.factor, target.milestones).
{
"exported_at": "2024-11-01T09:00:00Z",
"period": { "start": "2024-01-01", "end": "2024-12-31" },
"organisation": { "id": "...", "name": "..." },
"emissions": [
{
"id": "em_abc123",
"scope": 1,
"tco2e": 12.4,
"factor": { "code": "...", "source": "DEFRA", "vintage": 2023 }
}
]
}
Limitations
- Largest file size of all formats for full datasets
- Requires a developer or BI tool to consume
XBRL (eXtensible Business Reporting Language)
Availability: Professional and Enterprise plans only.
When to use
- Filing structured climate and sustainability data with regulators (e.g., ESMA, SEC)
- Submitting to digital disclosure platforms that accept XBRL-tagged data
- Machine-readable exchange with auditors using XBRL-enabled tools
Contents
A standards-compliant XBRL instance document using the AlchemOS GHG taxonomy (http://alchemos.io/xbrl/ghg/1.0):
| Element | Description |
|---|---|
ghg:Scope1Emissions |
Direct GHG emissions (Scope 1), metric tonnes CO₂e |
ghg:Scope2Emissions |
Indirect energy GHG emissions (Scope 2), metric tonnes CO₂e |
ghg:Scope3Emissions |
Other indirect GHG emissions (Scope 3), metric tonnes CO₂e |
ghg:TotalEmissions |
Total GHG emissions, metric tonnes CO₂e |
ghg:OffsetsRetired |
Carbon offsets retired in the period, metric tonnes CO₂e |
ghg:NetEmissions |
Net GHG emissions after offsets, metric tonnes CO₂e |
Context and unit elements follow XBRL 2.1 specification. The unit is ghg:MetricTonsCO2Equivalent.
File format
- Extension:
.xbrl - MIME type:
application/xbrl+xml - Encoding: UTF-8
Limitations
- Single-period reporting only; multi-period comparison uses separate files
- Taxonomy coverage is currently limited to GHG emissions metrics
XBRL-JSON (OIM)
Availability: Professional and Enterprise plans only.
When to use
- API-driven consumption by RegTech platforms and compliance tools
- Modern digital reporting workflows that prefer JSON over XML
- Integration with platforms implementing the XBRL Open Information Model (OIM)
Contents
A JSON document following the XBRL OIM specification (xbrl.org/2021/xbrl-json):
{
"documentType": "https://xbrl.org/2021/xbrl-json",
"prefixes": { "ghg": "http://alchemos.io/xbrl/ghg/1.0" },
"facts": {
"id1": {
"dimensions": { "concept": "ghg:Scope1Emissions", "entity": "...", "period": "..." },
"value": "120.50"
}
}
}
File format
- Extension:
.xbrl.json - MIME type:
application/xbrl+json - Encoding: UTF-8
Limitations
- Same taxonomy coverage as XBRL-XML (GHG emissions metrics)
- OIM JSON format is less widely supported than XBRL-XML in legacy regulatory systems
Choosing the right format
| Need | Recommended format |
|---|---|
| Audit submission | |
| Board presentation | |
| Finance team analysis | Excel |
| BI / data warehouse | CSV or JSON |
| API integration | JSON |
| Regulatory filing (structured) | Excel or CSV |
| Regulatory filing (XBRL-tagged) | XBRL |
| RegTech / digital reporting platform | XBRL-JSON (OIM) |