From the flare meter to the annual report

Calculation engine built for oil & gas

Generic carbon tools mostly model Scope 1 as fuel × factor. Oil & gas emissions do not work like that. EmitLedger calculates each source with a method written for it, gas by gas, and keeps the inputs behind every result.

• Composition-based combustion and flaring. Carbon mass balance on the actual gas analysis, with combustion efficiency for flares.
• Venting and fugitives. Whole-gas volumes, blowdown events from pressure, temperature and isolated volume, count-based factors for pneumatics and seals, and measured leak rates from LDAR surveys.
• Scope 2, both ways. Location-based and market-based results side by side, with energy attribute certificates and residual mix.
• Explicit reference conditions. Standard (15 °C) and normal (0 °C) cubic metres differ by about 5.5%. Every meter carries its reference conditions and the engine converts them explicitly.
• Gas by gas. Results are stored as tonnes of CO₂, CH₄, N₂O and other gases. CO₂e is derived when you report, with the GWP set you choose.
• Your own emission factors. Add a fuel analysis, a supplier’s factor or a national grid factor the reference library lacks, for a source, an asset, a country or the whole organisation. Each one cites its reference and licence, is marked verified by your team, and can be previewed: a dry run shows the change in CO₂e per asset before you save. Months already locked are never changed. Included in the Professional and Enterprise plans.
• Calculation runs you can see. Every calculation is listed with its findings, and you can recalculate an asset or the whole organisation for a range of months yourself.

Excel-first onboarding

Most operators run their inventory in spreadsheets today. EmitLedger meets them there.

1. Set up assets from templates. Pick a template such as a spread-moored FPSO, a fixed platform or an onshore gas plant. It fills in typical systems and emission sources, which you then tailor.
2. Download generated workbooks. Templates are generated from your source register, per asset and year, with a locked structure, unit dropdowns and validated cells.
3. Upload and review. The import checks structure, units, ranges, gas compositions that do not sum to 100 mol%, duplicates and month-on-month jumps, then previews what will change before anything is saved.
4. Fix with a marked-up file. When something is wrong, you download your own workbook back with the problem cells highlighted and commented.

Small corrections go straight into a paste grid: paste a block from Excel, move with the arrow keys, fill a selected block with one value. A value a colleague changed in the meantime is never overwritten, and “38,5” reads as 38.5 wherever you type a number. The onboarding wizard ends with a checklist of what is still missing before your first complete inventory.

Blank means “no data” and zero means zero activity, a distinction the platform keeps everywhere. Macros are never executed, and uploads are parsed in an isolated background worker.

Dashboards

Executive overview, by country, by asset, asset drill-down to system and equipment, source categories, flaring and venting, methane, energy, data quality and targets. Filter by period, scope, category, gas, consolidation approach, GWP set and Scope 2 method. Intensity KPIs include GHG intensity per barrel of oil equivalent, methane intensity and flaring intensity, and the overview ranks emissions by country. Save the filters you use every month as your own views, and open the overview on a Waiting for you list: the months you can submit, review, approve or lock, the questions a verifier assigned to you, and any import or calculation that failed.

Governance & verification

• Calculation provenance: applicable activity data, gas analysis where used, emission factor and reference, method version and library release.
• Reporting period workflow: open, submitted, reviewed, approved, locked, month by month or for a whole year of assets in one action. Changes to locked periods go through a restatement.
• Append-only audit log and evidence attachments.
• Library pinning: a reported year stays on the factor library it was reported with. When a new release arrives, you see the impact before you choose to upgrade.
• Verifier access: invite an external verifier with read-only, time-limited access, and run the engagement in the verification workspace below.
• Roles: client admin, methodology owner, data provider, reviewer, country manager, executive viewer and external verifier.
• Self-service sign-in recovery: two-step verification for everyone, recovery codes, and client administrators can reset a member’s authenticator after confirming who is asking.

Verification workspace

Run a third-party verification engagement inside EmitLedger, next to the inventory data it is about, instead of in emails and spreadsheets. The same pages serve the verifier and your team.

• Engagements. Name the verification body, the months being verified and the scope (the whole organisation or selected assets), and move the engagement from planning to fieldwork, findings and closed. Assign external verifiers: each one sees only the engagements it is assigned to, and its access ends when its membership expires. Verifier seats are free on every plan.
• Sampling. The verifier draws a seeded random sample, or the largest contributors covering a percentage the verifier enters, from the emission results in scope. Each sample is stored with its seed, parameters and a fingerprint of the population, so it can be reproduced and a later change of the data is detectable.
• Requests for information (RFIs). Raised against a result, a source, a reporting month, an import, an evidence file or the engagement as a whole. Your team answers in a thread and attaches evidence; the verifier accepts, reopens or closes. Assignees and verifiers get email notifications.
• Findings. Misstatements and non-conformities with the severity labels the engagement defines, your response, and a link to the restatement that corrects the data. Closing a finding never changes data: corrections go through the restatement workflow.
• Review trail export. The engagement, samples, RFIs with their threads and evidence references, findings and the linked audit events, as Excel, CSV or JSON.

EmitLedger records the engagement; it does not form a verification opinion. Materiality, sample sizes, coverage percentages and severity scales are the verifier’s professional judgement, not built-in defaults.

Integrations: data-ingestion API and webhooks

With the API access included in the Enterprise plan, your own systems and your vendors (SCADA historians, sensor and aerial-survey providers, data platforms) can exchange data with EmitLedger without a browser. The developer page has the details.

• Scoped API keys. Client administrators create keys with the scopes they need: read (assets, sources, reporting periods, aggregated results, current activity values and per-source result lines with the factors used), and separately writing activity data, events, site-level methane measurements or Excel imports. The secret is shown once, keys can expire and be rotated in place, and requests are rate-limited per key.
• The same checks as the web app. Pushed meter readings, production, gas compositions, energy certificates, component counts, LDAR findings, flaring, venting and blowdown events, site measurements and whole Excel workbooks go through the validation of the Excel import and the web forms: units stored as sent and checked against the data stream, locked months refused, recalculation queued. Each item carries your own id, so a retry never creates a duplicate. Writes act with the authority of the administrator who created the key and are recorded in the audit log under that key.
• Signed webhooks. Register HTTPS endpoints for events such as a month submitted, approved, rejected or locked, results recalculated, an import committed or failed, a report ready, a verifier’s question raised or answered, a restatement approved, a reconciliation decided or overdue LDAR items. Every delivery is signed (HMAC-SHA256 over a timestamp and the body) with a secret shown once and rotatable. Payloads carry identifiers and states only, never emissions values.
• Protected delivery. Webhook addresses must be public HTTPS: addresses that resolve to private, loopback, link-local or cloud-metadata networks are refused when the endpoint is registered and checked again before every delivery, and redirects are not followed. Failed deliveries are retried with backoff, and an endpoint that keeps failing is disabled until an administrator re-enables it.

Methane: LDAR programme and measurement reconciliation

• LDAR programme management. Survey plans per asset with the survey method, frequency and repair window your organisation sets. Next-due dates, surveys completed on time, open leaks with repair deadlines, delay-of-repair records with a reason, and weekly overdue reminders by email and in the app. EmitLedger ships no regulatory survey frequencies: you configure the ones that apply to you.
• Site-level measurement reconciliation (OGMP 2.0 Level 5 framework). Record aerial, drone, satellite or continuous-monitor results from your measurement provider, with their uncertainty and evidence. EmitLedger compares each one with the source-level inventory for the same asset and period, including both uncertainty ranges, and keeps a decision log. Adjusting the inventory always goes through a restatement, never silently. Reconciliation thresholds and reporting rules are yours or your pack’s, not built-in defaults.

Decarbonisation planning

• Emissions budgets: annual budgets for the company, a region or an asset, tracked against actuals year to date.
• Carbon price exposure: enter the schemes and prices that apply to you and the assets they cover, and see exposure for past and projected years, net of any free allocation.
• Abatement projects and MACC: record projects with abatement, capex, opex and lifetime; EmitLedger ranks them on a marginal abatement cost curve using your discount rate.
• Forecasts: trend or flat projections, with and without planned projects, against your targets and budgets. Forecasts are labelled as projections, never as inventory values.

All planning inputs (prices, costs, discount rates) are entered by you; EmitLedger ships no default prices.

Data quality and anomaly checks

Completeness heatmaps and data-quality tiers show where inputs are missing or estimated. Anomaly checks flag month-on-month jumps above your threshold and values out of line with the previous twelve months, on the Data quality page and as warnings during import.

Reports & exports

ISO 14064-1 inventory report (PDF and Excel) with your logo, GHG Protocol summary tables and a full calculation audit export for verifiers. Schedule any of them to arrive by email every month, quarter or reporting year; each member chooses which notification emails they receive. OGMP 2.0 reporting-level coverage is shown on the methane dashboard. You can export your full tenant dataset at any time.

Mobile field app

Dashboards, offline field entry (meter readings, flaring and blowdown events, LDAR findings with photo and GPS), approvals and notifications, in one app for all clients. The mobile app is rolling out.