EUR.1 Movement Certificate: When African Exporters Need It and How to Get One

A EUR.1 Movement Certificate is issued by the customs authorities of an exporting African country and serves as proof of origin, unlocking preferential EU tariff rates under a bilateral trade agreement like an Economic Partnership Agreement.

But EUR.1 is only one of several possible answers to the same underlying question, and the EU has been actively steering exporters away from paper certificates toward digital self-certification for years now. Some African trade blocs have already made that shift complete.

Knowing exactly where a specific country sits on that spectrum, rather than assuming the paper-certificate era still applies everywhere, is the difference between smooth customs clearance and an unwelcome, expensive surprise.

Getting the wrong document — or assuming EUR.1 still applies when a specific agreement has already moved on — costs real money at customs, paid as full standard duty instead of the preferential rate an exporter's own trade agreement was supposed to guarantee.

That gap between the preferential rate and the full standard rate is rarely trivial, and it applies to every single shipment moved under the wrong assumption, not just one unlucky consignment. A pattern of paying full duty across an entire trading season, purely because the wrong proof-of-origin document was used from the outset, represents a genuinely avoidable cost with real, cumulative impact on margin.

What follows breaks down exactly which proof-of-origin document applies to which kind of African trade agreement, the specific errors that most commonly get a EUR.1 rejected, the threshold below which no certificate is even needed, and why two neighbouring African countries can legitimately use completely different systems for the exact same trade relationship with the EU.

Which Document Do You Actually Need?

Three distinct proof-of-origin document types exist within EU preferential trade, and which one applies depends entirely on the specific trade arrangement governing a given African country's relationship with the EU.

Treating these three as broadly interchangeable, or assuming any one of them will do in a pinch, is a genuine misunderstanding worth correcting immediately. Each document exists because it corresponds to a specific, legally distinct trade arrangement, and presenting the wrong one at an EU border, however carefully filled out, doesn't unlock preferential treatment under an agreement it was never designed to support.

Confirming which of these three categories a specific country's current agreement actually falls under is the necessary first step before any conversation about filling out paperwork correctly even begins. An exporter assuming their country uses EUR.1 simply because a neighbouring country does may be working from an entirely wrong starting assumption.

This confirmation step is worth treating as genuinely non-negotiable rather than a formality to skip past quickly. Trade agreement status isn't static — countries move between GSP eligibility tiers as their income classification changes, EPAs get signed and take effect at different times across a region, and least-developed country status carries its own specific eligibility criteria that can shift over time. Checking current status directly with a national trade promotion body or customs authority, rather than relying on what applied even a season or two earlier, avoids building an entire export operation around an assumption that may no longer hold.

The Five Most Common EUR.1 Errors

For African countries where EUR.1 genuinely is the correct document, a consistent, recurring set of errors accounts for most rejections at the EU border.

These five errors appear again and again across independent reviews of rejected certificates, which is precisely what makes them worth memorising as a fixed, standing list rather than treating each rejection as a novel, unrelated problem. Recognising the pattern across these recurring failure points is often more valuable than any single piece of specific guidance about one particular error in isolation.

Every one of these five errors is genuinely avoidable with a careful pre-submission review, and treating this list as a standing checklist before every single EUR.1 application is worth far more than learning it the hard way through a rejected certificate at an EU port.

Building this checklist into a formal, documented step in an exporter's own internal process, rather than relying on informal memory each time a certificate needs completing, is worth the modest upfront effort. A simple form matching each of these five points against the specific shipment before submission catches the overwhelming majority of avoidable errors, converting what could be a costly rejection into a routine, five-minute verification step completed well before a shipment ever reaches an EU border post.

The €6,000 Threshold Explained

Not every shipment needs a formal certificate at all, and understanding this specific value threshold can save smaller exporters considerable time and cost.

This is a genuinely welcome simplification worth knowing about early, rather than discovered only after already investing effort into a full certificate application that a smaller shipment never actually required.

For consignments of originating products valued at or below €6,000, based on the ex-works price, any exporter — regardless of REX registration or approved exporter status — can simply issue an invoice declaration directly on their own commercial documents, without needing a EUR.1, Form A, or any other formal certificate at all. Above this threshold, an invoice declaration is only accepted when issued by a registered or approved exporter specifically, otherwise a full certificate remains necessary.

This threshold is worth building directly into pricing and shipment-planning decisions for smaller African exporters and cooperatives. A shipment deliberately structured to stay within this value, where commercially sensible, can avoid the entire certificate application process, though this shouldn't come at the cost of artificially splitting genuinely larger orders purely to dodge the requirement, which carries its own compliance risk.

This threshold genuinely benefits the kind of smallholder-aggregation exporters already discussed elsewhere in our broader coverage, where a single, modest-value consignment might represent an entirely appropriate shipment size on its own merits, not an artificial construct designed purely to avoid paperwork. For an exporter whose typical shipment naturally falls within this range, understanding that no formal certificate is required at all removes an entire category of compliance work that would otherwise apply unnecessarily.

REX vs Approved Exporter

Two distinct authorisation systems allow exporters to self-certify origin without a physical certificate, and confusing the two is a genuinely common mistake worth avoiding directly.

The Registered Exporter, or REX, system applies specifically within the GSP framework, requiring registration with an exporter's own national competent authority before they can issue self-certified "statements on origin" directly on commercial invoices. Once registered, an exporter receives a specific REX number, verifiable by anyone through a public REX database, giving both the exporter and any EU customs authority a clear, checkable record.

Registration itself requires submitting a formal application to the relevant national authority, and this step is worth planning well in advance of any shipment that would rely on REX-based self-certification, since processing an application isn't instantaneous. Once granted, the resulting REX number remains valid for ongoing use across multiple future shipments, meaning this is a genuine one-time investment of effort that pays off across an entire trading relationship, rather than a per-shipment burden comparable to applying for a fresh EUR.1 certificate every time.

Approved Exporter status, by contrast, applies within EPA and other bilateral agreement contexts specifically, granted by an exporter's own customs authority after they demonstrate they can reliably prove the originating status of their products. This status can be withdrawn in cases of misuse, and unlike REX, it isn't tied to the GSP framework at all. Confirming which of these two systems actually applies to a specific country's trade agreement, rather than assuming they're interchangeable, avoids a genuinely easy source of confusion.

Both systems share a common underlying philosophy worth understanding clearly: the EU is deliberately moving away from paper-based certification toward exporter self-certification, backed by the exporter's own registered, verifiable status rather than a document issued and stamped for every individual shipment. This shift reduces administrative burden considerably once an exporter has secured either status, but it also shifts more of the compliance responsibility directly onto the exporter themselves, since a registered or approved exporter is personally accountable for the accuracy of every self-issued statement rather than relying on a third-party customs official's verification at the point of certificate issuance.

This trade-off between convenience and personal accountability is worth weighing honestly before pursuing either status. An exporter confident in their own internal record-keeping and origin documentation stands to gain considerably from the reduced friction self-certification offers across every future shipment. An exporter still building out that internal discipline, however, may find the more externally verified EUR.1 or Form A process, however slower on a per-shipment basis, offers a useful additional layer of built-in accuracy checking during the period their own systems are still maturing.

Validity: Four Months, or Ten

A EUR.1 certificate's validity period varies depending on the specific agreement it's issued under, and confirming the correct figure for a specific trade relationship matters directly for shipment timing.

The general default validity period is four months from the date of issuance, though certain specific agreements extend this to ten months instead. This isn't a detail worth guessing at or assuming based on a different country's experience — the specific agreement governing a shipment's origin determines which validity period actually applies, and using an expired certificate is treated identically to using no certificate at all.

This distinction matters enormously for exporters managing longer supply chains or working through intermediaries where a certificate might sit unused for some time before actually being presented at an EU border. A shipment routed through a longer logistics chain, perhaps involving transhipment through a hub port already covered in our Netherlands gateway guide, risks the certificate expiring in transit if the underlying validity period was assumed rather than confirmed. Building in a genuine buffer against the applicable validity period, rather than planning right up against the deadline, protects against this entirely avoidable failure mode.

A simple, practical safeguard worth adopting is calendaring the exact expiry date the moment a certificate is issued, treated with the same seriousness as any other hard shipping deadline. This small administrative habit removes any risk of a certificate quietly expiring somewhere in the middle of an otherwise well-managed shipment, discovered only when it's already too late to issue a replacement in time.

Building this validity check into standard export documentation review, alongside the CN code and goods description checks already covered, closes one more avoidable gap between a properly issued certificate and one that fails simply because too much time passed between issuance and actual use at the EU border.

Why Your Neighbour Uses a Different System

Central Africa offers a genuinely illustrative example of how differently neighbouring African countries can be treated under EU preferential trade, even within the same broad region.

Cameroon, having signed its own Economic Partnership Agreement, uses EUR.1 as its standard proof of origin. Congo Brazzaville, not yet party to that same agreement, instead trades under the EU's GSP scheme, using Form A. Gabon, classified as an upper-middle income country, lost GSP eligibility entirely once it crossed that income threshold. Meanwhile Chad, the Central African Republic, the Democratic Republic of Congo, São Tomé and Príncipe, and Equatorial Guinea, all classified as Least Developed Countries, receive duty-free, quota-free access under the Everything But Arms scheme without needing EUR.1 or Form A at all.

Five neighbouring countries, five genuinely different starting points for the exact same underlying question of how to prove origin to EU customs. This isn't an unusual or exceptional cluster — it's a representative snapshot of how EU preferential trade actually works across the African continent as a whole, shaped by each country's own specific history of agreement negotiation, income classification, and development status rather than by simple geography.

This variation extends well beyond Central Africa specifically — the same pattern of neighbouring countries sitting under genuinely different trade regimes repeats across West, East, and Southern Africa too, wherever EPA negotiations, GSP graduation, and least-developed country status have progressed at different speeds for different countries. No single regional generalisation substitutes for confirming a specific country's own current status directly.

This variation within a single geographic region is worth internalising as the genuine norm, not an unusual exception. Assuming a specific document applies based on regional proximity to another country, rather than confirming the exact current agreement covering one's own specific country, is exactly the kind of avoidable assumption that leads to using the wrong proof-of-origin document entirely.

Frequently Asked Questions

Getting proof of origin right isn't simply a matter of filling out a form correctly — it starts with confirming which specific document, if any, actually applies to a given country's current EU trade relationship. Between GSP's Form A, EPA's EUR.1, and the growing shift toward REX-based self-certification, the right answer varies by country and can change entirely with little warning. Checking a country's current status directly, rather than assuming continuity with what worked last season or what a neighbouring exporter uses, is what keeps preferential tariff access genuinely secure. The modest time it takes to confirm this status directly, well ahead of a shipment's departure, is a fraction of the cost of paying full standard duty because the wrong document, or no document at all, accompanied an otherwise perfectly compliant consignment.