Skip to main content
What you’ll learn in this lesson:
  • Understand the three categories of batch types: input, production, and output
  • Map each batch type to its corresponding ledger
  • Configure multiple batch types in Mangrove
  • See how batch types work together to create end-to-end traceability
In Module 3, you worked with a single batch type — typically a delivery batch that credited one ledger. Now that you’re tracking material across multiple stages with multiple ledgers, you need different batch types for each stage.

​
The three batch type categories

Each stage in your process has its own batch type. These fall into three categories:
Not every project needs all three categories. A project with two ledgers might only need input and output batch types. The number of batch types should match the number of ledgers — each batch type feeds exactly one ledger.

​
How batch types map to ledgers

Each batch type credits exactly one ledger. When a batch is created, it adds to that ledger’s balance. Material then flows to the next ledger through allocations. The key relationship: batch type → credits ledger → allocation → next ledger. This chain creates the mass balance tracking from input to output.

​
Configuring multiple batch types in Mangrove

To set up multiple batch types, go to the Production Accounting section of your project and create a batch type for each stage. For each batch type, you’ll configure:
1

Name and description

Give the batch type a clear name that identifies the stage (e.g., “Feedstock Receipt”, “Biochar Produced”, “Carbon Delivered”).
2

Target ledger

Select which ledger this batch type credits. Each batch type feeds exactly one ledger.
3

Partition strategy

Choose how batches are created — per-event (each delivery = one batch), time-based (daily, monthly), or manual. This is the same partitioning you configured in Module 3.
4

Output datapoints

Define what each batch calculates. Input batches might track mass received; output batches might track tCO2e delivered.
5

Source event types

Link the batch type to the event types that provide its data. Feedstock Receipt batches pull from feedstock delivery events; Production batches pull from production run events.

​
Example: Mangrove Biochar multi-stage batch types

Here’s what the three batch types look like for the Mangrove Biochar project:
Credits: Feedstock Inventory ledger (dry tonnes)Each feedstock delivery creates a batch that adds to the Feedstock Inventory ledger.

​
End-to-end traceability

With multiple batch types feeding multiple ledgers, you get full traceability from input to output: A verifier can trace any credit claim back through the chain: Report → Carbon Delivered batch → Biochar Produced batch → Feedstock Receipt batch → source event data. At every step, the ledger balances confirm that outputs don’t exceed inputs.

​
Check your understanding

Each batch type credits exactly one ledger. This is a 1:1 relationship — a Feedstock Receipt batch type credits the Feedstock Inventory ledger, a Production batch type credits the Production ledger, and so on.
The chain is: batch type → credits ledger → allocation → next ledger. Each batch type creates batches that credit one ledger, and allocations move material between ledgers. A verifier can trace any output claim back through this chain to the original source events.
You’re now ready to put it all together. Head to the Module 4 Exercise: Design & Build Mass Balance with Ledgers to build a multi-ledger project in Mangrove.