Changelog

​

Data Rules

• Run a rule only on demand. Turn on Run only on demand for a rule that should run when you decide a period is complete, rather than on every data point as it arrives. Saving it evaluates nothing, and it runs over a period you start with Evaluate a period. A substitute rule set this way can read the capture rate of a data point other than the one it corrects. See Rules that run on demand.
• Fill a gap from the whole month. A calendar window’s new Covers setting offers Whole month, which reads the whole period, including data points after the one being corrected, so a month’s gap can be filled from the month’s full average. Whole month is available on rules that run on demand.
• The method that copies another data point type’s value, Another data point in the same event, is now called Cross fill in the rule builder and in correction history.
• On a proposal waiting for approval, the buttons read Use proposed and Keep current.
• Rule runs and data feed runs say Revert throughout, so Undo run reads Revert run.

​

Production Accounting

• Edit assets in bulk. Export the asset list, edit the file, and import it back, with a preview of every change before anything is saved. Import history lists past imports, and Revert import puts an import’s edits back. Enabled per account. See Editing assets in bulk.

​

API

• Every filter is applied or refused. An unknown filter field, a comparator the field does not support, or a malformed filter parameter returns 400 naming the problem. A filter value that cannot be read returns 400 rather than 422. Batch lists no longer take filter[state], event data points no longer take filter[value], and methodologies no longer take filter[report_type]. See Filtering.
• Project data points take filter[slug][eq] and filter[start_time] and filter[end_time] with geq or leq, alongside the plain slug, start_time and end_time parameters. Sending a time bound both ways, or two different slugs, returns 400.
• page_size is capped at 200, and defaults to 20.
• Rules carry evaluation, automatic or on_demand, and a calendar window takes extent, to_date or whole_period. backfill_enqueued on a rule update says whether a re-evaluation started, so it reads false on an on-demand rule.
• A model run carries is_deletable and deletion_blockers, and a refused delete returns each blocker with a code and the records in the way.
• Breaking: a batch’s input_data rows carry a fixed set of fields, which adds the data point’s substituted, imputed, raw_value and substitution and the event’s project_id. Evidence, rule results and the full event record are no longer on the row; read them from their own endpoints, using the row’s event.project_id and event.id.
• ui_url on ledgers, models and batches uses friendly IDs, and a report’s ui_url opens it inside its project.

​

Data Rules

• Catch a sensor stuck on one value. A new WITHIN TRAILING window reaches back from the data point being evaluated and never forward, so a rule can test that the lowest and highest values over the last hour are the same. A windowed rule can now act on the whole window, or on the whole run of repeats, rather than only on the most recent data point: turn on Flag the whole run or Correct the whole run on the Then step. See Catching a stuck sensor.
• Spot an outlier against its own history. ZSCORE returns how many standard deviations a value sits from the average of its window, so a rule can flag a value that is inside its permitted range but out of character for that stream. See Spotting an outlier.
• Hold corrections for approval. A substitute rule can propose each correction instead of writing it. The data point keeps its measured value until someone approves or rejects the proposal in the Event Detail drawer, and each decision is recorded with who made it. A data point with a proposal waiting cannot go into a new batch. Approve and reject over the API too. See Approve corrections.
• Substitute with a percentile. A new Percentile method replaces a value with a chosen percentile, such as the 90th or the median, of the valid values in a window.
• Calendar windows in the rule builder. A substitution method’s window can be set to a calendar period, with a number of periods back and a span of several consecutive periods, directly in the rule wizard. Last month’s average, or the previous two complete years, no longer needs the API.
• Test a computed value with a Batch Calculation rule: calculated data point types no longer appear in a Data Points rule’s autocomplete, and a condition naming one is rejected when you save.
• Compare two data points with RATIO. A rule can divide one measurement by another and test the result, so two meters that should agree, or a week’s average against the year’s, becomes one condition. Each side is a data point or an aggregate over one, and the two sides can carry different windows. See Catching drift between two data points with RATIO.
• The rules list carries a Rule ID column, switched on from Columns, and the search box matches a rule’s name or its ID.
• Undo run puts corrected values back. Undoing a substitute rule’s run restores each value it corrected, except a value in a reported batch or one somebody has corrected since.
• A substitute rule that has written corrections can now be deleted. The corrected values stay, and each keeps the rule’s name and ID in its history.
• Alert cards name the rule that raised them, with its ID and effective period.
• A value covering a span of time counts toward a window only if it overlaps it, so a calendar bucket no longer takes in a data point that ended exactly as the bucket began. Corrections drawn from such windows can change as a result. See What to know before you use one.
• Duplicate Project copies the project’s data rules, each with a new rule ID and no run history.

​

Data Collection

• Needs attention replaces the Health Check button on the Events table. It lists the values waiting on a person, with a count against each queue: Alerts, and, where substitutions are enabled, Data points to review. Pick a queue to filter the table to it.
• Restore to original now puts a corrected value back to the original in one step, however many corrections stand on it. It previously undid only the most recent correction.
• The capture rate’s Substituted count carries its own share of what was expected, and breaks down by what wrote each correction, with Show matching data points on each line to filter the Events table to that set. Substitution detail needs a date range of 92 days or less. See Data capture rate.
• Reverse on a bulk job is refused once its data points have fed a model run, so a reversal cannot pull values out from under a calculated result. The job names the reason.
• A data feed run breaks down what it created by event type and data point type, with counts of alerts and substitutions that open the matching values. See Bulk import.
• Where substitutions are enabled, the correction history in Event Detail reads as one trace from the value recorded to the value in force, including proposals and the decisions on them.
• Where substitutions are enabled, the Analytics chart marks the periods that hold substituted values.
• The Events export carries an Alert Reason column, and, where substitutions are enabled, Original Value, Substitution Rule ID and Substitution Reason. Its Origin column reads Reverted for a restored value. See Exporting.
• Charts no longer count a batch or data point that ends exactly on a period boundary toward the next period as well.

​

API

• Reverting a data point value restores the original value, clearing every correction on it, rather than stepping back one correction. The endpoint keeps its shape and status codes.
• Rules carry window_member_scope and requires_approval. Rule results carry approval_state, proposed_correction and the rejected_* fields, and two new operations approve and reject a proposed correction.
• A substitution method’s window accepts kind: trailing as a spelling of rolling, a calendar window takes a value counting consecutive periods, and percentile joins the method list. The grammar endpoint serves the method catalog alongside the expression grammar.
• Creating a ledger or a report accepts the project’s friendly ID (prj_...) as well as its numeric ID. An unknown project now returns “Project not found”.
• Updating a data point or an event records a value change as a correction, so the value as captured stays available as raw_value beside the current value, and the change appears in the correction history. Submitting the value already held records nothing. Clearing a value with null or a blank string is rejected.
• An asset custom field label that matches a standard column of the Assets spreadsheet is rejected with a 422, since the export would otherwise write two columns under one heading.
• Undo all of a rule’s corrections puts back every value a rule corrected, and reversing a rule run removes the corrections that run wrote. Deleting a rule is no longer refused because it has written corrections.
• Bulk approve and bulk reject decide up to 100 proposed corrections in one call. A rule’s results filter by approval_state, and rules and rule stats carry pending_count.
• Projects, event types, ledgers, batches, models, reports and rules carry ui_url, a link that opens the resource in the app.
• Sending cadence_amount or cadence_unit on an account without the data capture rate feature returns 422 instead of being ignored.
• GET /feature_flags returns every flag that affects the API, with false for the ones that are off.

​

Production Accounting

• The Generate Score drawer lists the operational inputs the selected batches supply, with each one’s Value and Source Batch. See Generate scores.

​

Reporting

• Audit Hub gives the auditor reviewing your report their own way into Mangrove. Invite them by email from the report’s Auditors card, and they get read-only access to that report’s batches, documents, and evidence, with everything previewable in place and downloadable as one package. Remove access at any time, and re-invite the same auditor later. Enabled per account; talk to your Mangrove account team to switch it on. See Share a report with an auditor.
• Reports assemble a package of their own: a calculation workbook per batch, the source workbooks behind each model, a CSV per event type, and the evidence and documents attached to the report. It rebuilds when you add something the report includes.
• Batch workbooks now open on the quantification model sheet and carry the source-data correction columns, so a reviewer can see the value as captured, what replaced it, and which value the calculation used.
• Batch workbooks carry a Substitutions Summary tab, with counts and totals split by whether a value was substituted, and a link through to each source sheet. Source rows now carry a start and an end time instead of a single timestamp, each naming its timezone.

​

Data Rules

• A rule’s action can now be Substitute rather than Alert, so it corrects the values it matches. Add substitution methods in the rule wizard and Mangrove works down them in order until one produces a value: a fixed constant, another data point on the same event, the nearest earlier or later data point, or the average, lowest or highest across a trailing window. Where nothing produces one, the rule raises an alert instead. Enabled per account.
• Every rule keeps a run history on a Runs tab. Re-run a date range with Evaluate a period, and take back what a run wrote with Undo run.
• Filter the rules list by rule type.
• Substitute rules can also be written over the API. See Correcting many values at once.
• The rule preview evaluates windowed aggregates, so a WITHIN condition previews the result it will produce once saved. It previously read them against an empty set. Preview also applies the same validation as saving.
• A substitution window takes an offset, which steps it back whole periods so a method can draw on the previous month rather than this one so far.

​

Data Collection

• Declare how often an event type is expected to report, and Mangrove tracks how much of that data actually arrived. The capture rate sits on the Data Points toolbar, breaks a shortfall into substituted and missing, and a rule can alert on it with DATA_CAPTURE_RATE. Leave a stream on Irregular where it has no schedule. Enabled per account. See Data capture rate.
• Filter the Data Points table by Value is missing to find gaps directly, with no data point type filter needed first.
• The Origin column filter is simpler: a gap that has since been filled now sorts under Substituted with every other changed value, rather than needing its own option. Exports still label the two separately.

​

Account Admin

• Sign in with Microsoft Entra ID. The sign-in page now asks for an email address first and sends a connected domain on to Microsoft. Configured by your Mangrove account team. See Single sign-on.

​

API

• Breaking: deleting a batch returns 202 and a task, not 204 and an empty body. Poll the returned task at GET /async_tasks/{task_id}, which is now documented. Deletion blockers are still checked before anything is queued.
• Breaking: event type endpoints no longer accept a numeric ID. Use the friendly ID, for example et_AbCd1234567890Ef.
• Filter events by event type friendly ID, event type slug, or location. filter[event_type_id], filter[slug] and filter[location_id] are new and accept only the eq comparator. filter[nexus_event_type_id] still takes the numeric ID for callers that already have it. An unrecognised filter key is dropped rather than rejected, so a misspelled filter returns unfiltered results with a 200.
• Rule runs over the API. List a rule’s runs, re-evaluate a period, read a run back, and reverse one. See Rule Runs.
• Event types carry cadence_amount and cadence_unit.
• Assets accept a flat filter[project_id]=prj_... as well as the bracketed form.
• Report map endpoints accept prj_ friendly IDs.
• The batch CSV export on a ledger is now scoped to that ledger. It previously exported every batch on the account.
• API tokens now expire. New tokens default to 90 days, with 30, 60, 180 days, 1 year, and no expiration also available. Expiry cannot be changed after creation, and the Expires column flags a token in its last 14 days. Tokens created before this change keep working. See Authentication.

​

Data Collection

• The Events table now lists your data one data point at a time, so each measured value carries its own status, alerts, and provenance. A data point recorded without a value shows as Missing. Available on every account.
• Filter and sort at the value level: quick filters for event type and data point type, numeric filtering and sorting on a single data point type, and Filter by AI for plain-language requests like “anomalous data points from the last month”.
• Export the Events table to CSV or Excel, flat and one row per value, honouring whatever filters you have applied.
• Deleting data points now shows what it will affect before you commit. Choose whether to remove the whole event or only the selected values, see the counts for each choice, and have locked values skipped rather than silently dropped.

​

Data Rules

• Substitute a data point’s value without editing the original record. Replace a wrong value or fill a gap where no value exists, and the original stays readable with the method, source, and author recorded against the change. The most recent substitution can be restored with Restore to original, and the whole history stays on the data point. Substitutions are enabled per account; talk to your Mangrove account team to switch them on.
• Substitutions are written through the API or from a data feed transformation. Filter the Events table by Substituted to find every changed value, or by Value was missing to isolate the filled-in ones.
• Alerts now land on the data point they are about. A rule that reads several values can name which of them can be flagged, so triage goes to the value that actually breached.
• Bulk alert dismissal now accepts at most 1000 results per request. See Dismissing many rule alerts at once for how to split a larger triage.

​

Production Accounting

• Two new batch partition strategies combine dimensions: Tracking ID + Feedstock and Tracking ID + Asset.
• Batch generation allocation is more predictable. An amount drawn from a source batch is the total for the generation, divided evenly across the partitions that run, so allocating one source batch across several partitions no longer draws it once per partition.
• Generating batches on a ledger no longer generates its concurrent ledgers as well. Pass generate_concurrent_ledgers to opt back in. See Generating batches.

​

Data Rules

• Windowed aggregates let a rule ask questions across events. Use WITHIN ROLLING for a sliding window (“a cluster of data points within seven days either side”) or WITHIN CALENDAR for a reporting period (“more than one delivery in a calendar month”). See Rule Expressions.

​

Production Accounting

• Track the physical equipment behind your production data as Assets: chargers, meters, wells, kilns, vehicles. Manage them in each project’s Settings → Assets page, with per-asset coordinates and an exportable asset list.
• Attach events directly to the asset that produced them. Event types can require an asset so per-equipment data never loses its linkage during ingestion.
• Partition batches by asset: one batch per piece of equipment in the generation window, a natural fit for programs that report per-unit.

​

Admin

• Custom Fields are now available on Assets. Define typed per-equipment attributes (text, number, boolean, date, select, URL) in Account Admin → Custom Fields → Assets (serial numbers, registration statuses, registry-assigned IDs) and set values per asset.

​

Data Rules

• Configure project Data Rules in Project Settings → Data Rules to automatically validate event data at ingestion or model outputs after batch calculation. Write expressions that flag out-of-range measurements, missing values, and methodology violations.
• Scope each rule’s evaluation window with Effective from / Effective to dates: rules auto-evaluate every matching record in range, with no separate backfill step.
• Triage rule alerts directly in event drawers, batch detail pages, and reports. Dismiss alerts with a reason to preserve audit history.

​

Production Accounting

• Maintain multiple versions of a model with drafts and active versions. Edit a model and save it as a labeled draft without affecting live calculations, or set it as the new active version on save to pin it for batch generation. Override the version at batch generation time to preview how a draft will calculate before activating it.

​

Data Collection

• Connect a SQL database with your credentials to pull data daily into Mangrove and transform it into accounting-ready events. Mangrove initially supports MSFT SQL Server, Snowflake (Direct and Secure Share.)
• Auto-generate transformations on data feed creation using an example import CSV file. Edit and test transformations in the editor before you run bulk data ingestion.

​

Production Accounting

• Generate Carbon Intensity scores using your project’s ongoing production accounting. Use different score models (e.g. CA-GREET, ISCC GHG Add-on) to simultaneously generate various scores using the same production data.
• Mangrove calculations backed by industry-standard Excel workbooks (e.g. CA-GREET, OR-GREET, GHGenius) can be generated, with the populated workbooks saved down as proof for auditability.

​

Data Collection

• Set up new Data Feeds directly in the Input Settings to receive and transform bulk data.
• Using the POST data feeds endpoint, send bulk CSV files from your various frontline systems directly to your Mangrove Project through the Mangrove API. See API documentation for latest.
• Filter for the set of events that was generated from a bulk import or bulk file in the project’s Bulk Jobs table.
• Evidence files can now be associated with individual datapoints within your project’s Event data. Attach different evidence for different datapoints (e.g. weigh tickets for transport mass vs route maps for transport distance).
• Preview XLS/XLSX evidence files to compare the raw ingested data to event data synced in Mangrove. Use Mangrove’s AI scanning to scan Excel evidence files and auto-generate event data.

​

Production Accounting

• Use your favorite AI tool to connect to your Mangrove data through the Mangrove MCP Server. Ask questions about your project, collected data, production batches and reports and get answers quickly.

​

Admin

• Manage Custom Fields for projects. Admins can create Custom Fields and define their type, visibility on project overview pages and order.

​

Projects

• Add Custom Fields to a project and enter their values.

​

Data Collection

• See audit trails of past edits to event data, for visibility into how the data has changed over time.

​

Production Accounting

• Auto-generate route maps with distances as evidence for transport emissions calculations.
• The Mangrove API has been updated with many new endpoints. Retrieve feedstocks, ledgers, production batches, model calculations, reports and make changes directly through the API. See API documentation for latest.

​

Production Accounting

• Evidence files can be uploaded when generating batches which allocate mass from one ledger to another. Manage evidence files from allocated batches from the calculations table.

​

Projects

• Project details are now shown in the overview. Use the edit link or navigate to Settings to update project details.
• Manage your project information and configuration in Settings.
• Add a registry and edit registry settings in the Registry section of Settings.

​

Production Accounting

• On the Project Overview, current and cumulative ledger balances are now shown for each ledger.

​

Inventory Management

• On the Project Overview, a credit inventory summary added with an interactive chart for credits issued and delivered.

​

Admin

• Assign the user role “Member - Read Only” to new or existing users. Users with this role can view core features, but cannot add, edit or delete data.

​

Production Accounting

• Filter production accounting batches by multiple paramaters, such as output values, net carbon removal, and locations. Use Filter By AI to filter for batches simply by describing the filter criteria.

​

Reporting

• Include the associated location names and latlongs on reported batches in Mangrove’s auto-generated statements.
• Regenerate any auto-generated statements to capture updates to the batch calculations within a draft Report.

​

Data Collection

• Filter the feed of operational data collected in Mangrove by multiple paramaters, such as locations of events, evidence, tracking ID, and data source.
• Use Filter By AI to filter the events feed simply by describing the filter criteria. Let AI help filter, sort, and show simple aggregate calculations.

​

Production Accounting

• Track inventories of renewable instruments (RECs, book and claim units) within a project, and allocate them to be used in production accounting.

​

Reporting

• See which parts of calculations in Mangrove are reported to a registry through API, through a registry label alongside the calculations.
• Registry submissions through API generates an audit log for easy review of the submission activity.
• Mangrove’s updated integration with Isometric’s Certify API enables projects to package up their MRV data and report removals to the Isometric registry.

​

Production Accounting

• Track a list of embodied emissions within the project, and set corresponding amortization rules for each embodied emission.
• Generate batches easily by reviewing inputs required by category, syncing existing project data, and adding new data and evidence.
• Skip inputs that aren’t relevant to a specific batch - Mangrove automatically assumes a 0 value for calculations.

​

Data Collection

• Mangrove has overhauled delivery tracking. Collect data during every truck delivery with an improved tracking experience. Drivers scan a QR code per delivery, and record information at every step of the way (tank fill, start delivery, end delivery, end use), along with photos or files as evidence.

​

Reporting

• Auto-generate monitoring reports and GHG statements from reported accounting data, with embedded lists of evidence and verification views. Package and submit a Report, and track submission statuses.
• Auto-update a project’s forecasted credit inventory based on submitted reporting, generating an updated estimate of credit quantity and issuance time. Replace existing credit forecasts for the same production period.

​

Admin

• Manage a portfolio of project owners, each with access to their own Mangrove Managed Accounts where they can submit data, review production accounting, and reporting for each of their projects. Summarize the credit inventory and customer orders across all your managed partners’ projects, all in a central Portfolio account.

​

Data Ingestion

• Track an audit log of changes on a Data Request to see when and where submissions were made by your data partners.
• Add a new data source to a project using example spreadsheet data, for ongoing bulk imports. Attach transformations to the import data to normalize the import into events.

​

Production Accounting

• Directly add and build new acccounting models within each project.
• Organize your production accounting summary into various project stages.
• Partially allocate production batches to downstream production ledgers.
• Download an Excel version of your projects’ quantification models, and the calculations backing up a production batch, for flexible validation and analysis.

​

Credit Inventory

• Select all projects, or all projects of a particular methodology, to see the credit inventory summary.

​

Data Ingestion

• Switch between map style layers to view location data in the context of terrain or satellite imagery.

​

Production Accounting

• Admins can run a test on every node calculated in a model to ensure accuracy of models. See errors and missing inputs in context of the model itself to understand where to adjust the calculations.

​

Reporting

• Users with Admin privileges can initiate a new Report from production data. View all Reports across various statuses within the Reporting section of the project. Assign Reports to specific Account Admins to own the submission and completion.
• Sync the Report directly as a GHG Statement to the Isometric registry.

​

Credit Inventory

• The vintage year of a credit issuance is auto-assigned as the end date of the production period. Users can now update the vintage year for issued spot credits if the actual vintage differs from this auto-assigned year.

​

Data Ingestion

• Directly create delivery events with origin and destination in Mangrove, and auto-calculate road transport driving distances for emissions accounting.
• Attach URLs as evidence to events and static inputs, to support data with web-available documentation or deep links to large-format evidence such as 3D models hosted in other systems.

​

Production Accounting

• Track mass flows and balances across many stages of the project, including emissions and carbon intensity calculations of individual units of material. Get a quick a summary overview across balances.
• View an aggregated list of associated evidences within the detail view of each batch of production.

​

Data Ingestion

• Send data requests to custom email recipients to request one-off data submissions from external parties. CC yourself to ensure they’ve received the requests.
• Upload new files to your project and auto-detect data from the file to be saved as operational events.
• Preview a range of evidence file types and CSV files within the Mangrove Platform, to cross-check the accuracy of the collected data against the attached files.

​

Production Accounting

• Account for the ongoing generation of multiple co-products and environmental attributes/credits from a single project, across parallel accounting ledgers.

​

Credit Inventory

• Transfer and retire Puro CORCs directly from within Mangrove to your customers’ registry accounts, synced to the Puro registry.
• View credit inventory schedule by issuance period, alongside cumulative inventory availability and upcoming deliveries.

​

Reporting

• Directly report MRV data to CSI using the EBC-Sink and Global C-Sink Standards

​

Data Ingestion

• Mangrove integrates data directly from your SQL databases like Snowflake. Provision access credentials to your Snowflake database for continuous data fetching, or use Snowflake’s Secure Data Sharing to share data with Mangrove.
• Track all metadata of unique deliveries with Mangrove-generated Tracking Units - embed QR codes into delivery workflows and auto-calculate emissions for transport legs of the journey.
• Categorize the data being collected from your partners by naming the Data Request
• Cancel, retry, or reverse your Bulk Imports, to ensure you’re bringing the right project data into Mangrove.

​

Production Accounting

• Analyze detailed gross-to-net carbon accounting on every batch of production

​

Credit Inventory

• Mangrove integrates directly with your Salesforce account, allowing credit inventory and deliveries in Mangrove to be synced with your contacts and opportunities in Salesforce.

​

Data Ingestion

• Mangrove integrates data directly from Endress + Hauser’s sensor hardware, including through E+H’s Netilion SCADA.
• Integrate with the Mangrove API to push project data, events, and evidence directly into your project in Mangrove.

​

Data Analysis

• Run a data Health Check on your feed of operational events, and filter for incomplete or anomalous events.
• View an updated home dashboard, including a map of all project production, and a feed of latest notifications that need your attention.

​

Production Accounting

• View the chain of custody for every batch, with locations of key operational activity marked on a map.
• Drill into the source events and evidence for calculations within each production batch.

​

Reporting

• Generate PDF reports alongside spreadsheet statements for registry reporting
• Skip manually generating PDF and Excel statements, and push reporting directly from your Mangrove account to Carbon Standards International for fast verification.

​

Credit Inventory

• Within the Customer Portal, credit buyers can easily review past and upcoming credit deliveries, and see location information within the MRV calculations of each delivery

​

Data Ingestion

• Send a test Data Request to yourself, before sending it to data partners
• Auto-calculate driving distance and routes based on start and end latlongs of ingested transport trips for transport emission quantification, using Mapbox’s Directions API within your transformations

​

Reporting

• Generate Puro-compliant CORC Output reports with data from a reporting period of your project.

​

Data Ingestion

• Data partners can add notes to the files that they submit to provide more context
• See a map of locations and asset hierarchy of each project in the Project Boundary section.
• In the Project Boundary section, add and manage locations and their child assets to build a full location graph of each project.

​

Data Analysis

• View a dashboard of key ingested time-series data for every project - see trends, catch outliers, view gaps in the data.
• Filter for specific time ranges on each dashboard chart, and zoom into the specific event data on the feed.

​

Production Accounting

• Admin users can test calculations in project models to be sure that calculations are properly modeled.
• Simulate a run of the model by entering a series of inputs and viewing the calculated results.

​

Credit Inventory

• Export all credit deliveries in a project, and across projects, into a CSV or Excel file for easy analysis.
• Certain registries such as Puro charge a flat per unit fee per credit. Besides %-based fees, users can now set a registry flat fee per project, and adjust it per credit delivery, to accurately capture the revenue breakdown of each order.

​

Admin

• Scale your Mangrove MRV implementation as you scale to new deployed projects.
• Duplicate an existing project’s configuration to set up a new project.
• Copy over the project type, methodology, models, and data sources all at one go.

​

Data Ingestion

• View and edit how files imported through specific Data Sources are transformed into events using a Python-based transformations editor.

​

Production Accounting

• Write equations as complex expressions in the model builder.
• Analyze production trends over time and the breakdown of allocatable production batches with a user-friendly Production Accounting dashboard.
• Filter production batches to view and manage the accounting within a particular production period.

​

Reporting

• Skip manually generating PDF and Excel statements, and push reporting directly from your Mangrove account to Isometric for fast verification.

​

Data Ingestion

• Request data and documentation from your data partners for individual data inputs, and review submissions.
• Include detailed descriptions and links to help your partners understand what to submit.
• Transform data into rich events with a set of associated datapoints.

​

Production Accounting

• Admin users can edit calculations within your project’s production models using the built-in script-based model editor.
• Add and edit nodes, check the model, and save it to update calculations.
• View all the project’s models in one place in the Project’s “Models” section, including production and quantification models under the project’s accounting data flow.
• See details, inputs, and settings for models.

​

Credit Inventory

• Preview delivery details as credit deliveries are created, including estimated revenue.
• Fulfill a delivery by manually allocating credits from specific issuances on a project.
• Save documents such as contracts and agreements with each customer order to centralize all information about the credit order in one place.

​

Data Ingestion

• Send email requests or share a request link to collect data and documentation from your data partners, and track the progress of submissions.

​

Customer Management

• Add your customers to a branded Customer Portal where they can view the credits that have been delivered to them, as well as upcoming scheduled deliveries.
• For each credit delivery, customers can see in-depth MRV calculations, evidence documentation, as well as general information about the project and methodology.

​

Production Accounting

• Before running a dataflow to perform production accounting, users can validate the completeness of data inputs from a reporting period in real-time.

​

Data Ingestion

• Bulk import production data exported from various systems within your project environment into Mangrove in various file formats, including XLS, XLSX, and CSV files.

​

Credit Inventory

• The Orders section has been enhanced. Users can search for orders by order ID, and review the delivery schedule on each Order with deeper levels of detail on each delivery, including delivery dates and payment statuses.

​

Customer Management

• Allow your credit buyers to integrate APIs from Mangrove to pull information about their orders, upcoming credit deliveries, and underlying MRV calculations for delivered credits.

​

Production Accounting

• Production accounting within each project can be done through a data flow that is structures calculations sequentially across different production models.
• Calculated data points that are generated from models are saved onto the project’s events feed as a growing stream of production data.
• In the Value Streams section, see a list of value streams that are active across your projects.
• View the quantification model of each value stream, as well as the static inputs used for net carbon quantification.

​

Credit Inventory

• Browse your inventory across all projects in one consolidated schedule view - add multiple projects to compare your credits on hand.
• See all issuances within the same Inventory section.
• Add recurring forecasts (monthly, quarterly, or annually) to the credit inventory of each project to project out your expected inventory.

​

Data Ingestion

• Ingest string and boolean-type inputs, to represent descriptive data or yes/no events
• See the configured bulk import data sources within each project’s Input Settings.
• Bulk import events using the default event schema, or work with Mangrove to configure new data sources per project.
• Track the status of past and ongoing bulk imports.

​

Production Accounting

• Ingest event data with tracking IDs. Generate one batch per tracking ID, to track the accounting and chain of custody data under each physical SKU.
• Filter and search the events feed - by input type, date range, and event status.
• See events with evidences attached.

​

Credit Inventory

• Issuances that are Pending Issuance represent credits that are no longer just Active Forecasts but are in the process of being issued.
• When production data is allocated to a forecast, the issuance automatically switches to Pending Issuance.
• The user will need to Issue the credits to be able to complete deliveries.
• The Customers section has been updated with improved search and filtering.
• Better search and filtering within the Orders and Customers sections.
• Use quick filters to easily narrow the list of relevant Orders to Open Orders or Fully Delivered.

​

Admin

• Configure account brand settings for external interfaces such as portals and verification views.
• Set brand colors and logos.