Skip to main content

Integration

Integration is the Reports area for the connection between ITS and the customs systems that call it. It answers three questions: what ITS refused and why, whether the declarations ITS announced to other countries were accepted, and how far organisations have got with onboarding.

It counts calls made by connected systems only. Refusals of your own portal session, such as a page you may not open, are not counted here.

It is the page a technical contact opens after a complaint that "ITS is rejecting our declarations".

Before you start​

  • You need a role that reads the integration area (Secretariat admin or Organisation admin). See What each role can do.
  • Have the correlation ID of a refused call to hand if you are chasing one particular refusal. Your customs system receives it in every answer from ITS.

Open it​

  1. Select Reports, then the Integration tab.
  2. Check the Period and the sentence You are reading ….

Integration as the Secretariat: the Rejections, Distinct reasons, Deliveries and Acceptance figures; Why we refused, with reasons in words; Whose calls are refused, each caller by name; Rejections over time, one point per day; Did the endpoint accept it; Were our declarations delivered; Onboarding

On the page​

On the pageWhat it is for
RejectionsCalls from connected systems that ITS refused in the period.
Distinct reasonsHow many different reasons those refusals had.
DeliveriesAnnouncements ITS sent to other countries' systems (a new declaration, a stamp, an amendment).
AcceptanceThe share of deliveries the receiving system acknowledged, to one decimal. The line under it says how many are still awaiting an answer; those are not counted as accepted.
Why we refusedRefusals by reason, in words, largest first. See The refusal reasons.
Whose calls are refusedRefusals by the organisation that made the call, by name: a State Party by its country's name (Kenya), and a REC by its name when the Secretariat is reading. A State Party or a REC sees a REC as its code (AMU). No identified caller is a call that arrived with no organisation attached.
Rejections over timeRefusals through the period, at the period's own grain: one point per day for a day, a week or a month, one per month for a year or a longer span. It follows the period exactly, so it carries no "Covering …" line. Open full report opens the Rejections over time report.
Did the endpoint accept itAnnouncements ITS delivered to you, by result: Acknowledged, Sent, not yet acknowledged, Failed, retrying, Queued (waiting to be sent) or Undeliverable, gave up.
Were our declarations deliveredAnnouncements of the declarations you lodged, delivered to the other countries on their route, by the same results.
OnboardingOrganisations by how far they have got with connecting to ITS. Its View as table and the full Onboarding report name each organisation: a State Party by its name, and a REC by its name when the Secretariat is reading. A State Party or a REC sees a REC as its code (AMU), because the name is read from Governance.

The refusal reasons​

Reason as shownWhat it usually means
Not entitled to do thisThe caller may not do this, or may not see this declaration.
Not foundThe declaration or office asked for does not exist, or is outside the caller's scope.
Fields failed validation, The request could not be read, A value is not in the registerThe request was badly formed or used a value ITS does not know.
A business rule refused itThe request was well formed but broke a transit rule, for example a stamp out of order.
Out of date — another change came firstAnother change to the declaration arrived first. Read it again and resend.
Too many requestsThe caller sent too many requests too quickly.
Error inside ITSA fault on ITS's side. Report it with the correlation ID.

The full Rejections report has an Error code column beside the Reason. For every error code, see the error catalogue.

What you see depends on who you are
SecretariatState Party (Uganda)REC (AMU)
Refusals countedEvery organisation'sCalls made by Uganda's systemCalls made by AMU's system
Whose calls are refusedEvery country and organisation (Kenya, Uganda, Zimbabwe, No identified caller …)Uganda onlyAMU
Did the endpoint accept itEvery announcement ITS sentAnnouncements to UgandaAnnouncements to the members
Were our declarations deliveredEvery announcement ITS sentAnnouncements of what Uganda lodgedAnnouncements of what AMU's members lodged
OnboardingEvery organisationUgandaAMU and the members it administers
SecretariatState PartyREC
Integration as the Secretariat: every organisation's refusals, with the reasons in wordsIntegration as Uganda: "You are reading Uganda." under the period, the Rejections, Distinct reasons, Deliveries and Acceptance figures, and the refusals of calls made by Uganda's system in Why we refused, with the reasons in words, and Whose calls are refusedIntegration as AMU, reading every member it administers (no Scope field on this area), for a REC with no refusals and no deliveries in the period: Rejections, Distinct reasons and Deliveries read zero, Acceptance shows a dash, the Why we refused and Whose calls are refused tiles are empty, and Rejections over time says there are no movements in this period

Find out what your system is sending wrong​

  1. Read Why we refused. Reasons other than Not entitled to do this and Not found are the ones your system can usually fix.
  2. Open the tile's ⋮ menu and select Open full report. Rejections lists every refused call: when, which request, the reason, the reference and the caller.
  3. Narrow it to the period and reason you are chasing, and export it for your developers. See Export a report.
  4. For a single refusal, look it up by correlation ID on Failed transmissions (in All areas).
The Onboarding tile and System integration count differently

The Onboarding tile counts organisations by their state in ITS's reports. The System integration workspace can list a different number. A member that a REC files for, and that has no connection of its own, reads Through and the REC's code (for example Through AMU) in the State column of the full Participation report, not Not connected. The report's Through column gives the REC's code by itself (AMU).

  • Reports
  • All reports: Rejections, Rejections by reason, Rejections over time, Outbound deliveries, Delivery outcomes, Deliveries of what we lodged, Onboarding.