Skip to content
Get a diagnostic
The starting point

Find out exactly why your customs, e-invoicing or EDI workflow is failing

A focused diagnostic establishing what is broken, where, why, and what has to be fixed first. Whether the data comes back rejected by a partner or gets retyped by hand before it enters your TMS, the question asked is the same. Before any quote, before any software.

Here about customs pre-clearance? The diagnostic applies as it stands, but the shorter route is the test on 100 files you have already cleared: your own files, with no integration to stand up first.

See customs pre-clearance

What you receive

  • A map of your flows, systems and breaking points.
  • The identified cause of each observed failure — not a list of hypotheses.
  • An ordered, costed remediation plan stating what we do and what stays with you.
  • What you can handle in-house — we say so when that is the case.

Describe your problem

Two steps, under three minutes. We come back to you with a first reading.

Step 1 of 2
  1. 1Your context
  2. 2The problem

Fields marked * are required.

At a glance

What it is
A fixed-scope analysis of your flows — customs documents into CargoWise, e-invoicing, EDI — that establishes the cause of a failure before anything is corrected.
What you get
A written report: the cause identified, what it costs, the possible corrections and the order to do them in.
What it needs
A description of your problem to begin. For the analysis itself, read access to the messages and logs concerned — or, on a customs flow, a few files you have already handled.
What it is not
Neither a product demo nor a ballpark quote. No software is proposed at this stage.
Afterwards
You decide on the correction, with us or without us. The report is yours.

What the diagnostic establishes

We do not start by selling you software. We start by understanding what is broken.

01
Current architecture
The systems involved — ERP, TMS, platforms — and how they are connected today.
02
Data flow
The real path an invoice, a message or a customs document takes, step by step.
03
Failure points
Where data is lost, distorted, rejected — or sent back for manual re-keying.
04
Applicable requirements
The formats and rules your flows have to satisfy.
05
Manual interventions
The workarounds in place, and what they cost.
06
Business impact
Late payments, rework, disputes, lost time.
07
Remediation order
What to fix first — and what can wait.

How it runs

  1. 01

    You describe the problem

    The form below is enough. A few lines beat a full specification.

  2. 02

    First conversation

    A short call to locate the likely origin of the failure and confirm it is our field.

  3. 03

    Analysis

    We examine the flows, the rejected messages and the systems involved.

  4. 04

    Read-out

    You receive the map, the identified causes and the remediation plan.

What to know before writing to us

  • If the problem is outside our field, we say so — and point you elsewhere where we can.
  • If you can fix it yourself, we explain how rather than selling you an engagement.
  • We do not need access to your systems for the first conversation: the symptom and one rejected message are often enough.
  • The first conversation costs nothing. Beyond it, scope and price are written down and agreed before we start — nothing gets discovered on the invoice.
  • The diagnostic does not commit you to having us do the remediation.

Anumerik works on the technical implementation: mappings, data transformations, connectivity and integration. We do not provide legal or tax advice — your own advisers remain your reference on how the rules apply to you.

We don't start by selling you software. We start by understanding what is broken.

Describe the problem — 30 min

Frequently asked questions

We came here about customs pre-clearance — is this the right page?

Yes if the subject is a flow that does not work as intended — the diagnostic applies to customs documents like anything else. If the subject is the re-keying itself, start instead with the test on 100 files you have already cleared: it runs on your own files, needs no integration and no credentials, and shows you the result before any conversation about scope.

How long does a diagnostic take?

It depends how many systems are involved. A single failing flow is usually days, not weeks. A scope covering several partners and several applications takes longer. We give you an estimate after the first conversation, before starting.

Do we have to give you access to our systems?

Not for the first conversation. For the analysis, read access to the rejected messages and exchange logs is enough in most cases. We state exactly what we need, and why.

Are we then obliged to continue with you?

No. The diagnostic stands alone: the map and the remediation plan are yours, including if you choose to have the fixes carried out by another team or in-house.

What if the problem is not technical?

It happens: the flow works, but a business rule or an upstream piece of data is wrong. That is a useful result, and we say so plainly rather than hunting for a technical problem that does not exist.

How does this differ from the fixed-scope audit?

The diagnostic adapts to your situation: scope, duration and price are set after the first conversation. The fixed-scope audit is its productised variant, for freight forwarders and customs brokers: scope agreed in advance, ten working days, fixed price, standardised deliverable. The detail is on the services page.