Mining ERP in the DRC: What the System Must Record to Trace Copper and Cobalt from Pit to Export

# Mining ERP in the DRC: What the System Must Record to Trace Copper and Cobalt from Pit to Export

TL;DR — A mining ERP for the DRC and the Zambian Copperbelt is not accounting software with a "stock" module bolted on: it is a system whose base unit is the lot (bag, big-bag, truck or wagon), which carries origin, grade, certificate of analysis and chain of custody through to export, works offline on sites with no network coverage, and turns the mine-to-plant-to-shipment reconciliation gap into an accounting entry instead of a disputed spreadsheet.

Why the spreadsheet stops working

On a copper-cobalt operation in Lualaba, Haut-Katanga or the Zambian Copperbelt, the question at every month-end close isn't "how much did we produce?" — it's "how many tonnes of payable copper and cobalt can we prove, lot by lot, between the pit and the export bill of lading?" As long as that proof lives across separate spreadsheets held by the lab, the weighbridge and accounting, it will not survive an audit, a regulatory control, or a due-diligence request from an international offtaker. This is a data-model problem before it is a reporting problem.

Building custom software for this use case follows the same discipline as any custom web and mobile application built for operations in the DRC: it starts from the real constraints of the field, not a generic requirements list copied from a Western ERP template.

The lot as the unit of truth

The data model has to be built around the lot: a bag of artisanal ore weighed at a buying point, a big-bag of concentrate, a truck loaded at the stockpile, a railcar at the border. Every lot carries a unique identifier and fields that do not change once sealed.

Field	Type	Why it exists
`lotId`	Unique identifier (QR/barcode)	Physically ties the bag or truck to every downstream digital record.
`originSiteId` / `panelId`	Reference to Site/Shaft/Panel	Traces a lot back to a specific pit or buying point — the baseline of any due-diligence file.
`wetMassKg` / `moisturePct`	Decimal	Gross weight and moisture: the basis for dry-mass and payable-grade calculations.
`gradeCuPct` / `gradeCoPct`	Decimal, with `analysisMethod` and `labId`	Declared grade and lab-measured grade almost never match; without a field keyed to method and lab, the gap stays invisible.
`sealNumber`	String	Proof that a sealed lot was not opened or blended in transit — the core of chain-of-custody evidence.
`chainOfCustodyLog`	Linked table (timestamp, agent, location, action)	Records every transfer of responsibility with a verifiable timestamp.
`weighInKg` / `weighOutKg`	Decimal, with `scaleId`	Reconciles declared weight against confirmed weight; feeds the reconciliation-gap calculation.
`coaId`	Reference to Certificate of Analysis	A lot without a linked COA should not be invoiceable (see below).
`reconciliationStatus`	Enum (pending / confirmed / disputed)	Stops a lot with an unexplained gap from disappearing into aggregate stock.

Each field maps to a real friction point between a mine and its buyer: the grade a truck arrives claiming is never exactly the grade the lab confirms, and that gap is what the ERP has to surface, not smooth away in an average.

The reconciliation gap: an accounting entry, not a spreadsheet

Between the pit, the concentrator, intermediate stock and export, every step generates a gap: handling losses, residual moisture, weighing imprecision, dilution from blending lots. The common habit — calculating it once a month in a spreadsheet and adjusting stock at period-end — prevents anyone from knowing, on a given day, whether an abnormal gap comes from a weighbridge error, theft, or genuine process drift.

In a properly designed model, every lot transfer between two stages automatically generates a gap entry: expected mass and grade against confirmed mass and grade at the next stage, posted to the stock ledger with an offsetting account for normal process losses and a "to investigate" status beyond a per-site threshold. That is what lets finance distinguish a structural loss from a one-off anomaly, and answer an auditor within minutes on the delta between reported extracted tonnage and invoiced shipped tonnage.

The certificate of analysis as an entity, not a PDF

The certificate of analysis (COA) — copper and cobalt grade, moisture, penalty elements such as arsenic or manganese depending on the contract — is usually a PDF signed by the lab and filed in a shared folder. The problem isn't the format: a PDF has no structured relationship to the lot it describes. It can't trigger a price calculation, can't be queried for a lab's drift history, and drops off the radar the moment a file gets renamed.

The COA needs to be a database entity linked to lotId by a foreign key, with its own structured fields (grade per element, method, date, technician, lab, validation status), the original PDF kept only as an attachment — not the source of truth. That structure enables the capability that matters commercially: automatically comparing, lot by lot, the grade declared at purchase against the payable grade confirmed on arrival, surfacing the gap in both percentage and value — instead of discovering it at quarter-end.

Artisanal ore purchasing and due diligence

Congolese artisanal cobalt doesn't follow the linear industrial-mine → concentrator → export flow: it moves through traders and buying points before entering a formal chain. The Entreprise Générale du Cobalt (EGC), a Gécamines subsidiary created in 2019, holds the state mandate over purchase, processing and marketing of artisanally mined cobalt. It announced, in late 2025, the rollout of more than fifty Artisanal Exploitation Zones (ZEA) and launched its first batch of traceable artisanal cobalt in Kolwezi, a 1,000-tonne run (EGC; Magazine Le Temps). That rollout is still in progress — not yet nationwide coverage — and an ERP built today has to work in both a formalized ZEA and a conventional buying circuit.

For a buying point or trader, the ERP has to record at minimum: seller identity (including affiliation to a recognized cooperative, if any), collection point, weight and estimated grade at purchase, the grade-based price actually paid (not a flat per-bag price), any advance paid and its balance, and the resulting lot reference. This is exactly the data set the OECD Due Diligence Guidance for Responsible Supply Chains of Minerals from Conflict-Affected and High-Risk Areas expects a company to be able to produce (OECD). Without these fields captured at the point of transaction, reconstructing a due-diligence file afterward is, in practice, not achievable.

The Congolese regulatory framework: what's confirmed, what's still moving

The mining fiscal regime stems from Law No. 007/2002 of 11 July 2002, as amended by Law No. 18/001 of 9 March 2018 (Leganet). Its article 241, as rewritten by article 9 of that law, sets the full royalty schedule: 0% for common construction materials, 1% for industrial minerals and iron, 3.5% for non-ferrous and/or base metals — copper, raised from 2% by the 2018 reform — 3.5% for precious metals, 6% for precious and coloured stones, and 10% for strategic substances, the category into which Decree No. 18/042 of 24 November 2018 placed cobalt, germanium and coltan (NRGI; Ebuteli). An ERP calculating royalties needs to carry that rate at the lot or product level, not as a single global parameter.

The DRC's cobalt export regime has changed substantially since 2025. ARECOMS — the Authority for the Regulation and Control of Strategic Mineral Substance Markets, created by Decree No. 19/16 of 5 November 2019 and headquartered in Lubumbashi — extended the export suspension until 15 October 2025, then replaced it with a quota system effective 16 October 2025. For 2026, the annual quota is 96,600 tonnes of contained cobalt — 87,000 tonnes allocated pro rata among producers (roughly a 7,250-tonne monthly cap) and 9,600 tonnes under ARECOMS' discretionary control — with the regulator indicating it plans to maintain the regime through 2026–2027 while reserving the right to adjust it (Benchmark Mineral Intelligence; Fastmarkets). An ERP therefore needs to reconcile, lot by lot and month by month, cobalt tonnage shipped against remaining quota balance — a check still largely manual at most sites.

On revenue transparency, EITI-DRC made public, in 2025, data warehouses for the mining and hydrocarbon sectors — the mining one is publicly browsable and publishes extractions, royalties and contracts operator by operator (Mining Data Warehouse, CTCPM; EITI) — a move that pushes operators toward structured production and sales data rather than aggregated annual reports.

What is not yet settled: how far EGC's zone coverage will actually extend, and how ARECOMS will handle in-year quota adjustments if the market turns. ARECOMS' own remit is moving too — on 10 April 2026 the government adopted a decree creating a national strategic mineral reserve entrusted to ARECOMS, plus a second decree adapting the authority's operation to that new mandate (Actualite.cd). A system built today should treat these parameters (rates, quotas, eligible zones) as editable configuration, not hard-coded constants.

Downstream due diligence: the EU and the OECD

The EU Battery Regulation (EU) 2023/1542 requires battery manufacturers placing products on the EU market (above a turnover threshold) to adopt a due-diligence policy covering cobalt, lithium, nickel and natural graphite. Those obligations, originally due 18 August 2025, were postponed to 18 August 2027 by Regulation (EU) 2025/1561 of 30 July 2025, after the European Commission concluded the original timeline was too tight (EUR-Lex; GreenSoft Technology). That postponement doesn't remove the need to prepare: buyers who will require this documentation in 2027 are negotiating supply contracts today, and a supplier able to produce a structured lot history now has an obvious negotiating advantage.

The OECD Due Diligence Guidance remains the de facto reference for documenting the origin of copper and cobalt, including outside the strict "conflict-affected area" scope — since 2023 the London Metal Exchange has required every listed brand to implement it, with cobalt brands automatically treated as "higher-focus" and subject to an external alignment assessment and audit (OECD; LME Responsible Sourcing).

The real physical constraints of the field

None of this holds up if the system assumes a permanent network connection. A significant share of sites in Lualaba and Haut-Katanga operate without reliable coverage, with frequent SNEL power outages that make even keeping a data-entry terminal powered uncertain. The ERP has to run offline in the field — weight, grade and seal capture stored locally, synced when a connection returns — a constraint that shapes the architecture, not just the interface. This is a topic covered directly in our guide to digital transformation in Kinshasa and Lubumbashi, where the gap between office connectivity and field connectivity is a defining factor for any software project in the country.

Concretely: an app built for an entry-level Android phone, with a minimal number of screens and minimal network dependency per transaction; explicit conflict resolution for synchronization (what happens if two agents seal the same lot number during an outage?); and a visible local queue so the field agent knows whether an entry has actually been transmitted. A system that silently loses a weighing record during a three-hour SNEL outage is not a mining ERP — it's an additional reconciliation risk.

At the border, trucks sometimes wait hours at the Kasumbalesa crossing, which carries roughly a third of the DRC's copper cathode exports. That corridor is not an abstraction: overnight on 28 February 2026 the Kakoso bridge at km 15 of the T3 road between Chingola and Chililabombwe, on the Zambian side, collapsed after heavy rain and severed the route, forcing shipments to reroute via Sakania and Mokambo (News24 / Bloomberg). On the Zambian side, a $110 million concession signed on 20 November 2024 with the ZMart Group covers a one-stop border post and a 2,000-truck park, with no published completion date (Copperbelt Katanga Mining). As long as that bottleneck exists, the ERP needs to track a lot "in border transit" as its own status — queue-entry timestamp, wait duration, customs reference — rather than letting it vanish from stock until it reappears on arrival.

Interfaces: weighbridges, lab, GPS and accounting

A mining ERP that doesn't interface with existing instrumentation recreates the problem it was meant to solve: manual re-keying, and a new source of gaps.

Weighbridges: automatic capture of inbound/outbound weight, timestamped and tied to lotId, instead of transcribed from a paper ticket.
Laboratory (LIMS): structured exchange of results, so the COA is created as a linked entity as soon as a result is validated, with no re-keying.
GPS / truck telematics: position and status of the vehicle carrying a given lot — useful for chain-of-custody and for anticipating border delays.
Accounting: reconciliation-gap entries and per-substance royalty calculations flowing into the general ledger without re-keying.

This kind of multi-system integration is precisely what distinguishes custom software built for mining operations from a generic ERP with modules bolted on afterward.

Most of the physical flows described here — transport, weighing, sometimes extraction itself — run through subcontractors. Law No. 17/001 of 8 February 2017 sets the rules for subcontracting in the private sector, and the Autorité de Régulation de la Sous-traitance dans le Secteur Privé (ARSP), a public body created by Decree No. 18/019 of 24 May 2018 as amended by Decree No. 20/025 of 12 October 2020, enforces it (Daldewolf; ARMP-RDC). A mining ERP should tie every transporter and handling contractor to a registered subcontracting agreement, for the same reason an audit expects ore traceability.

The production context

The orders of magnitude explain the stakes. Per the US Geological Survey's Mineral Commodity Summaries 2026, the DRC produced 230,000 tonnes of cobalt in 2025 out of a 310,000-tonne world total — about 73% of world output, well ahead of Indonesia at 14% — and 3.2 million tonnes of copper, second worldwide behind Chile (5.3 Mt) and ahead of Peru (2.7 Mt) (USGS cobalt; USGS copper). Zambia produced 890,346 tonnes of copper in 2025 according to its Ministry of Mines, up 8% from 825,513 tonnes in 2024 (MINING.COM / Reuters). At that scale, a reconciliation gap that looks negligible at a single lot's level becomes, aggregated across a year, a multi-million-dollar question.

FAQ

Can a well-maintained spreadsheet replace an ERP for mining traceability?

It can record the same fields, but it can't stop a lot being invoiced without a linked COA, generate a gap entry automatically at every transfer, or survive a file getting renamed. Traceability rarely fails from a lack of data — it fails because that data lives in three files that don't talk to each other.

Does a mining ERP need constant internet access on site?

No — a system that requires it isn't fit for most sites in Lualaba or Haut-Katanga. Field capture needs to work offline, syncing whenever a connection returns.

Is the mining royalty rate the same for copper and cobalt in the DRC?

No. Copper is at 3.5% (Law No. 18/001, 2018); cobalt, classified as a "strategic mineral substance" under Decree No. 18/042 of 24 November 2018, is at 10%.

Does the EU battery due-diligence requirement already apply?

The specific obligations of Regulation (EU) 2023/1542 were postponed from 18 August 2025 to 18 August 2027 by Regulation (EU) 2025/1561 — which doesn't stop many European buyers from already requiring this documentation contractually.