Passmark
Home › Guides › Conflict Minerals Compliance: A Practical Guide for Buyers Sourcing from West Africa
Product GuidesExporters Reviewed against official sources as of 06.11.2026

Conflict Minerals Compliance: A Practical Guide for Buyers Sourcing from West Africa

A practical guide to conflict minerals compliance for buyers and exporters working across West African mineral supply chains.

On this page
  1. Why conflict minerals compliance comes up in West African sourcing
  2. Building a traceable supply chain, step by step
  3. What a buyer actually checks before paying
  4. Worked example: a tin and tantalum trader in the Upper West Region
  5. Weak file vs strong file: a side-by-side comparison
  6. FAQ

Conflict minerals compliance is the set of checks a buyer runs to confirm that tin, tantalum, tungsten, gold, or other minerals in a shipment did not come from a mine or trading route tied to armed conflict or serious human rights abuse. For exporters in Ghana, Burkina Faso, Mali, and neighboring countries, this isn't a one-off form. It's a working habit: knowing which pit or depot a parcel of ore came from, who handled it between the mine and the port, and being able to produce that chain on request.

This guide walks through what a buyer's compliance team is actually trying to confirm, how to build a traceable chain from mine site to export, and what separates a shipment that clears quickly from one that gets held up for weeks of back-and-forth emails.

Why conflict minerals compliance comes up in West African sourcing

Several West African countries sit inside or near regions where mineral trading routes have historically overlapped with conflict financing — some gold and tin supply chains run through areas with limited state control over mine sites. That history is why buyers in electronics, jewelry, and industrial manufacturing run extra checks on minerals from the region, even when a specific mine has no connection to any conflict at all.

Rules differ depending on where the buyer is based and what the mineral is. A US electronics manufacturer sourcing tantalum answers to different reporting obligations than an EU jewelry brand sourcing gold, and both differ again from a buyer supplying a domestic market with no cross-border reporting duty. Rather than guess at which regime applies, treat the underlying ask as constant: show where the mineral came from and who touched it on the way out.

For exporters, this means the paperwork habit matters more than knowing every regulation by name. A trader who can produce a mine-site ID, a transport permit, and a buyer receipt for every lot will satisfy most reporting regimes without ever needing to cite a specific law.

Building a traceable supply chain, step by step

Traceability breaks down into four links. Miss one, and the chain stops being a chain — it becomes a set of documents that don't connect to each other.

  1. Tag the mine site or depot. Every lot needs a site identifier — a name, a permit or license reference, and a date range for when it was dug or bought. If ore from three different pits gets mixed in one sack, the lot can only be traced back to the loosest of the three.
  2. Record the first purchase. Whoever buys from the miner or small-scale digger writes down the date, the quantity, the price, and who they bought it from. This is the weakest link in most informal supply chains because it's the point furthest from any buyer's paperwork, and the easiest step to skip under time pressure.
  3. Track every handoff. Each time the lot changes hands — digger to local buyer, local buyer to regional aggregator, aggregator to exporter — note the date and the parties. A lot that passes through four hands needs four dated handoff records, not one summary line.
  4. Keep the export documents matched to the lot, not the shipment. A shipment often bundles several lots together. If the export paperwork only describes the shipment as a whole, there's no way to trace a problem back to a single lot without retracing the entire consignment. Keep a lot-level reference on the export file so each parcel inside a container can still be identified on its own.

Software built for this — sometimes marketed as compliance tracking software or part of a broader third party risk management setup — mainly automates step four: it keeps lot references, handoff dates, and supporting documents linked together so a buyer can pull the full chain for one lot instead of being handed a shipment-wide file and told to search it.

What a buyer actually checks before paying

A buyer's compliance reviewer is running a vendor risk assessment, and for minerals specifically that assessment has a narrow focus: does the paper trail match physical reality, lot by lot. Four things get checked in roughly this order:

  • Site reference matches a real, named location — not a region or district, a specific site with a permit or license number attached.
  • Dates run forward, not backward. A purchase date before the mine permit was issued, or an export date before the first handoff, is the single fastest way to get a file sent back.
  • Quantities reconcile. If 400kg was bought across three handoffs but the export declaration says 500kg, that gap needs an explanation before anything else gets reviewed.
  • Each handoff has a named counterparty.

A missing name at any handoff forces the reviewer to treat everything downstream of that gap as unverified, even if the rest of the file is clean.

Exporters who keep this file updated per lot, rather than reconstructing it when a buyer asks, are the ones who get paid on the first review cycle instead of the third.

Worked example: a tin and tantalum trader in the Upper West Region

Kwame runs a small trading post in the Upper West Region, buying tin ore from four licensed small-scale sites and selling consolidated lots to an exporter in Tema who ships to a smelter in Europe. His buyer's compliance officer, Priya, asks for a lot-level trace before she'll release payment on a 12-tonne shipment.

Kwame's first file is a single typed summary: total tonnes bought that month, the names of the four sites, and a signed statement that none of the material came from an unlicensed pit. Priya sends it back. She can't match the summary to the shipment because there's no way to tell which tonnes came from which site, or when.

Kwame rebuilds the file lot by lot. For the 12 tonnes in this shipment, he lists: 3.2 tonnes from Site A, bought on four separate dates with the digger's name and a copy of Site A's permit; 4.1 tonnes from Site B with the same detail; and so on for Sites C and D. Each lot shows the date it left Kwame's depot and the date it arrived at the exporter's warehouse in Tema, with a signed handoff note from the truck driver.

Priya approves the shipment in four days instead of the three weeks the first file would have taken to untangle. Kwame tells his sites going forward that every sack needs a tag with the site name and purchase date written on it before it leaves the pit — not after, when someone has to reconstruct it from memory.

Weak file vs strong file: a side-by-side comparison

ElementWeak fileStrong file
Site identificationRegion or district name onlyNamed site with permit or license reference
Purchase recordMonthly total, no per-lot datesDated purchase per lot, digger named
HandoffsSingle summary line covering the whole chainDated, named record for each handoff
Export matchShipment-level description onlyLot-level reference tied to the export declaration
Review timeWeeks of back-and-forth to reconstruct gapsDays, because nothing needs reconstructing

Frequently asked questions

Does conflict minerals compliance only apply to tin, tantalum, tungsten, and gold?

Those four get the most attention because of how widely they're used in electronics and jewelry, but the same tracing logic applies to other minerals a buyer flags as higher-risk. If a buyer asks for a traceable chain on a mineral not usually covered by conflict minerals rules, it's often because of that buyer's own internal policy rather than a specific external requirement — ask what triggered the request before assuming it's optional.

What if a mine site doesn't have formal licensing paperwork?

Document what does exist — a community agreement, a local government acknowledgment, a tax receipt — and be upfront with the buyer about what's missing. A gap that's disclosed and explained is easier for a compliance reviewer to work with than a gap that surfaces during their own check.

How does this connect to broader due diligence buyers ask for?

Conflict minerals traceability is usually one section inside a wider buyer due diligence file that also covers ownership, labor practices, and environmental questions. Building the mineral trace as a standing file rather than a one-time answer means it's ready to slot into that wider file each time a new buyer asks.

Is a digital audit trail actually necessary, or will a spreadsheet do?

A well-kept spreadsheet with consistent lot references can work for a small trading operation. The problem shows up at scale, when dozens of lots move through multiple handoffs a week — at that point a spreadsheet becomes hard to search and easy to edit after the fact, which is exactly what audit trail software is built to prevent.

Where to go from here

If origin documentation is part of what a buyer is asking for alongside conflict minerals traceability, check how your product qualifies under AfCFTA rules of origin as well — the two files often get requested in the same due diligence round, and keeping both lot-referenced from the start saves a second scramble later.

The Passmark Brief · Monthly

Rule changes for your markets, before they hit your shipments