CarbonAtoZ Logo
CarbonAtoZ Help PortalStandard Operating Procedures
EU CBAMGHG AccountingIndia CCTSFacility RegistersCompliance Deadlines
Academy Labs↗Launch Platform
On This Page (8 sections)
1. Overview & Architectural Context2. Prerequisites & Input Schema3. Step-by-Step Execution ProcedureStep 3.1: Navigate to the Data Ingestion ConsoleStep 3.2: Upload & Schema MappingStep 3.3: Pre-Ingestion Dry Run & Anomaly CheckStep 3.4: Finalize & Commit Ingestion4. Operational Note: Ingestion Error Resolution
⌘K
Configuring Custom Emission Factors & Laboratory Net Calorific Value (NCV) OverridesHow to Enter Monthly GHG Activity Data & Emission SourcesUpstream Supplier Carbon Passport Intake & Scope 3 Precursor ManagementAutomated Tally Prime XML & ERP CSV Batch Data Ingestion
Help Portal/Carbon Accounting/Automated Tally Prime XML & ERP CSV Batch Data Ingestion
GHG Accounting & IngestionVersion 2.5ISO 14064-1:2018 Clause 5.2 / GHG Protocol Scope 1 & 2

Automated Tally Prime XML & ERP CSV Batch Data Ingestion

Comprehensive guide for Carbon Accountants and Facility Managers to configure and execute batch imports of fuel, raw material weighbridge logs, and utility invoices from Tally Prime and enterprise ERP systems.

Last Reviewed: 2026-08-26
Owner: Data Ingestion Practice Lead

Prerequisites & Required Authorizations

  • Active Carbon Accountant or Facility Manager role.
  • Tally Prime ODBC/XML export enabled or standard UTF-8 CSV ledger extract.
  • Active facility and emission source stream mapping.

Expected Outcome

Clean ingestion of hundreds of transaction rows into preliminary activity ledger with zero schema reconciliation errors.

1. Overview & Architectural Context

Manual entry of hundreds of fuel purchase bills, coal weighbridge receipts, and utility electricity invoices is labor-intensive and error-prone. Carbonatoz provides a high-throughput, idempotent CSV and Tally Prime XML batch ingestion pipeline that reconciles financial ledger entries with physical greenhouse gas emission streams.

Note

All ingested transactions are assigned a cryptographic payload digest (sha256_hash) upon receipt to prevent duplicate reading insertions (Invariant INV-04).


2. Prerequisites & Input Schema

Before starting the batch import, verify that your CSV or XML export adheres to the canonical columns:

Column NameRequiredData TypePermitted Values / Description
transaction_dateYesISO Date (YYYY-MM-DD)Transaction or invoice date
facility_tagYesStringRegistered plant ID (e.g. FAC-JSR-01)
source_stream_idYesStringPhysical stream tag (e.g. BLR-02-NORTH)
fuel_or_material_typeYesStringcoking_coal, natural_gas, grid_electricity, diesel
quantityYesDecimal (> 0)Quantity in physical invoice units
unit_of_measureYesStringMT, Nm3, kWh, MWh, kL
invoice_referenceNoStringVendor invoice or weighbridge serial number
custom_ncv_gj_per_tNoDecimalNet Calorific Value from supplier lab test
Caution

Ensure dates are strictly in YYYY-MM-DD format. Non-standard date formats (e.g. DD/MM/YYYY) will trigger parser validation errors.


3. Step-by-Step Execution Procedure

Step 3.1: Navigate to the Data Ingestion Console

1
Log in to the Carbonatoz Workspace.
2
In the primary left navigation menu, expand GHG Accounting→select Batch Ingestion.
3
Select the target Facility and Reporting Period (e.g., April 2026).

Step 3.2: Upload & Schema Mapping

1
Click + New Batch Ingestion Job.
2
Select your file format: Tally Prime XML or Generic ERP CSV.
3
Drag and drop your file into the secure dropzone (max 25MB per batch).
4
Review the auto-detected column mappings on the preview screen. If custom ERP column names were used, select the appropriate target fields from the dropdown selectors.

Step 3.3: Pre-Ingestion Dry Run & Anomaly Check

1
Click Run Validation Dry Run.
2
The platform executes an in-memory test run checking for:
•Unknown source stream tags.
•Out-of-bounds quantity spikes (> 300% historical monthly rolling average).
•Incompatible units of measurement (e.g. attempting to import liters for electricity).
3
If errors are detected, click Download Error Log CSV to inspect and rectify row-level mismatches.

Step 3.4: Finalize & Commit Ingestion

1
Once the dry run reports 100% Validated, click Commit Ingestion Batch.
2
Records are written to the monthly activity ledger in pending_review status.
3
System triggers calculate preliminary Scope 1 and Scope 2 CO2e values automatically.

4. Operational Note: Ingestion Error Resolution

Important

Source Stream Not Found Discrepancy

- Root Cause: The source stream identifier in the CSV does not match any registered equipment in the Facility Source Register.

- Resolution: Navigate to Facilities→Source Register and verify that equipment tag spelling matches exactly (case-sensitive).

Previous Procedure
Upstream Supplier Carbon Passport Intake & Scope 3 Precursor Management
Next Procedure
Claiming Origin Carbon Price Deductions Under CBAM Article 9
Was this operational procedure helpful?

Your feedback helps our regulatory practice teams refine operational SOPs.

On This Page
1. Overview & Architectural Context2. Prerequisites & Input Schema3. Step-by-Step Execution ProcedureStep 3.1: Navigate to the Data Ingestion ConsoleStep 3.2: Upload & Schema MappingStep 3.3: Pre-Ingestion Dry Run & Anomaly CheckStep 3.4: Finalize & Commit Ingestion4. Operational Note: Ingestion Error Resolution
Hands-On Simulation Lab

Practice in Carbonatoz Academy

Test this procedure in a deterministic simulation sandbox with realistic precursor datasets.

Launch Academy Lab →
Carbonatoz Help Portal•Enterprise Standard Operating Procedures
(Statutory Reference: EU Reg 2025/2547 & 2025/2546 | BEE CCTS 2024)
Version 2.7 • Updated for EU CBAM 2025/2547 (Calculation), 2025/2546 (Verification) & India CCTS 2024
SOPs document live platform workflows; verify statutory requirements against official gazettes.