Skip to main content

Oversee the continent as the Secretariat

Who this is for: the AfCFTA Secretariat.

What you will achieve: a picture of how transit is working across Africa this month: how much is moving, how much is completed, where the borders are slow, what is overdue, and which administrations are having trouble with their systems.

1. Open the continent's figures​

  1. Sign in. The Secretariat opens on System integration; select Overview in the header.
  2. Leave Scope on Africa and Period on This month.

The Overview for the Secretariat: Scope Africa, This month, and the Registered, Discharged, Completion rate, Median border crossing and Overdue now figures with their comparisons

Read the five figures. This month is the month so far, compared with the same days of last month, as the caption on the right says (1 – 29 Sep 2026, against 1 – 29 Aug 2026). See Overview.

2. Find where the borders are slow​

Scroll to Time at the border. Each crossing is named by the posts on its two sides, such as Malaba (KE) → Malaba (UG). A post the customs office register does not hold keeps its code. The crossings are listed worst first by their 90th-percentile time: the time within which nine crossings in ten are completed. A crossing with a long bar between median and 90th percentile is unpredictable, not only slow.

For the full picture by crossing and country, open the tile's menu and select Open full report, or open Reports, then Time & delays. See Time & delays.

3. Look at what is overdue​

Overdue now is the number of declarations still open after their transit window closed and the grace ran out. The grace is yours to set: Grace before a transit counts overdue, under Transit rules on Settings. Select Overdue now to open the Overdue transits report: each row names the declaration, how many days overdue it is and where it was last seen. Reports, then Register, has the same list as its Overdue worklist, and Lost handovers: declarations that left one country and never entered another before their deadline. See Register. Open a few, and look at Held by on each: the country holding an overdue declaration is the one to ask.

4. See who is having trouble​

  1. On Overview, select the Failed transmissions tab.

    Failed transmissions as the Secretariat: the Correlation ID search, the organisation filter on All organisations and the other filters, and one row per refusal with the columns Received, Organisation, Request, Urgency, Refusal and Status

  2. Leave the organisation filter on All organisations, or choose one.

  3. Leave Received on this month, or set its From and To dates.

  4. Narrow the list if you need to, with Serial number, Error code or Outcome. Clear filters puts everything back.

  5. Read the Urgent rows first: they have a red edge, and Urgent in the Urgency column. Urgent marks a refusal that can hold up cargo; Needs attention marks the rest.

  6. Select a row to open its panel, which gives the reason, the request and the correlation ID to quote to the administration's technical team.

Every row is a refusal of an administration's system; the Organisation column says whose. A pattern of the same refusal from one administration is worth raising with its technical team. While you read, a bar above the filters announces refusals that have arrived since, for example 3 new failures — show them: select it to bring them in. See Failed transmissions.

The Integration report shows refusals by reason, by caller and over time. See Integration.

5. Read the notifications​

Select the bell, then View all notifications. The bell's number counts the notices needing attention; it is red when at least one of them is Urgent.

The Secretariat receives notices about declarations anywhere on the continent, and its own organisation's notices. Among them:

  • When an organisation's system meets a refusal that can hold up cargo, an Urgent notice naming that organisation, one for each kind of refusal each day. Selecting it opens Failed transmissions narrowed to those refusals. Refusals that are not urgent are told to the organisation alone: step 4 is where you read those.
  • ITS cannot deliver announcements to …, naming a country whose receiving endpoint has stopped accepting announcements. The country is told too. If several countries are named at once, look for a cause they share.
  • Under Adoption, … is on a corridor but not on ITS: a declaration named a country that is not connected. There is one a month per country.

See Notifications.

6. Answer a query about one declaration​

When an administration or a trader raises a specific consignment, find it in Declarations; the Secretariat's register holds every declaration on the continent. The Held by and Station filters answer "who holds it" and "what is at this office" without opening each declaration. See Find a consignment and Follow a declaration to discharge.

7. Check the rules and limits in force​

  1. Select All areas, then Settings under Administration.
  2. Read Declarations (the limits on what one declaration may carry), Transit rules and Operations. Each shows the value in force and any change already scheduled.

Only the Secretariat changes these. The administrators of every LIVE State Party and REC are e-mailed and notified of a change to a limit or a transit rule; a change under Operations is announced to the Secretariat only. A change starts at a UTC day and time you choose, at least one minute ahead. If the refusals in step 4 show declarations over a limit, or step 3 shows more overdue transits than the corridors justify, this is where the rule is reviewed. See Settings and Change a setting.

What "done" looks like​

  • You know this month's volume, completion rate and median border time, against a fair comparison.
  • You know the three slowest crossings.
  • You know which administrations hold the most overdue declarations.
  • You know which administrations' systems are being refused, and why, starting with the urgent ones.
  • You know which rules and limits are in force.