Customs pre-clearance without the re-keying.
We ingest customs documents as they arrive, reconcile them field by field against your order data, then push a validated payload into CargoWise. Nobody re-keys anything.
Test it on 100 files you have already cleared
Your CargoWise stays in place — nothing is replaced
In French and English, across the UEMOA zone
Customs documents into CargoWise, with no re-keying
This is the service we lead with: a customs file is ingested as it arrives, reconciled field by field, then pushed into CargoWise as a validated payload.
- 01
Ingest the document as it arrives
Scans, faxes, native PDFs and photographs of paper documents all enter the same pipeline, whatever the language and whatever the layout.
- 02
Reconcile field by field
Container numbers, gross weights, HS tariff codes and IncoTerms are reconciled against your purchase-order data. Any discrepancy is flagged the moment it appears, not once the entry has been filed.
- 03
Push a validated payload
The validated record maps to native eAdaptor XML and is pushed straight into CargoWise. Your team reviews only what was flagged.
Start with 100 files you have already cleared
Send us 100 shipments you have already cleared. We run them through the same pipeline and return the parsed output with every discrepancy we found. Historical files only, so no live shipment is at stake, and there is no integration to stand up first.
See customs pre-clearanceCargoWise stays your system of record: nothing is replaced, no schema is modified.
At a glance
- Who we are
- Anumerik is a technical provider specialising in e-invoicing, EDI and business-system integration.
- What we do
- We ingest customs documents into CargoWise with no re-keying, and we diagnose and repair failing flows: EDIFACT mappings, data transformations, invoicing-platform connectivity, ERP, TMS and WMS integration, invoice validation.
- Who for
- Companies whose trading exchanges are standardised and high-volume: transport and logistics, distribution, manufacturing, food and beverage.
- Where
- Francophone West Africa — Benin, Burkina Faso, Côte d'Ivoire, Mali, Niger, Senegal and Togo — plus cross-border flows within the UEMOA zone. In French and English.
- How it starts
- With a diagnostic that establishes the real cause of the failure, never with a software proposal. For customs pre-clearance, with a test on 100 files you have already cleared. No published pricing: engagements are quoted after the diagnostic.
- What we are not
- Not a legal or tax advisory firm, not a marketing agency, not a software vendor. We take no commission on the platforms in use.
Is this what you are dealing with right now?
These symptoms almost always share one cause: data that does not reach the next system in the shape that system expects.
- Your operators retype customs document data into your TMS by hand.
- An EDIFACT mapping started failing after a customer-side update.
- Your invoices are being rejected and nobody can say exactly why.
- Your ERP and your EDI platform no longer agree with each other.
- Your connection to the invoicing platform is incomplete or stuck in testing.
- Your normalised invoice does not pass validation.
- Invoices are being re-keyed by hand to "unblock" the flow.
- The same data exists in three different versions across systems.
- A compliance deadline is approaching and nobody knows where you stand.
- Several systems communicate badly, and your teams compensate every day.
If two or more of these look familiar, the real cause is rarely where people look first — and it does not cost what you think. The processing time is not the expense. The expense is that every manual fix pushes a payment back, occupies someone you pay, and leaves the same error free to return next month.
A diagnostic, not a software quote
We do not start by selling you a platform. We start by establishing precisely why your flow fails, where it fails, and what has to be fixed first — whether that is a customs document being retyped by hand or an invoice coming back rejected.
- 01Current architecture
- Which systems are involved — ERP, TMS (CargoWise included), WMS, accounting, EDI platform, invoicing platform — and how they are connected today.
- 02Data flow
- The actual path an invoice, a message or a customs document takes, from issue to acceptance, step by step.
- 03Failure points
- Exactly where data is lost, distorted, rejected — or sent back for manual re-keying: in the mapping, the transformation, the transport or the validation.
- 04Applicable requirements
- The formats and rules your flows must satisfy for your customers, your markets and your transmission channels.
- 05Manual interventions
- The workarounds your teams built to make it work anyway — and what they cost.
- 06Business impact
- What the failure actually causes: late payments, rework, disputes, lost time.
- 07Remediation order
- What to fix first, what can wait, and what is not worth fixing at all.
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.
What we actually fix
Once the cause is identified, we work directly on your existing systems. No imposed rebuild: we repair what needs repairing.
EDI mapping remediation
Failing EDIFACT or X12 mappings, missing segments, wrong qualifiers, partner rules not honoured: we rework the mapping until the message goes through.
Data transformation
Conversions between formats and structures — EDIFACT, XML, UBL, CII, Factur-X, CSV, JSON — with the business rules that come with them.
Platform connectivity
Onboarding, configuration, end-to-end testing and go-live, through to exchanges actually validating.
ERP / TMS / WMS integration
Making your business applications talk to your invoicing flows, in both directions, without re-keying.
Invoice validation
Checks before transmission, so what would be rejected externally is caught internally — with a message a human can act on.
Error handling & monitoring
Automatic retries, alerts worth reading, and visibility on what was sent, what is stuck and what failed.
What we work with every day
Every technology below answers one question: what it does for your problem.
Formats & standards
- Normalised invoice
- The format and marking your country's tax authority expects on an invoice.
- EDIFACT
- The language of your trading exchanges: orders, despatch advices, invoices.
- UBL / CII
- The XML structures most invoicing platforms expect to receive.
- Factur-X / EN 16931
- The European hybrid format and semantic standard: what your partners in Europe expect.
- ANSI X12
- EDIFACT's North American counterpart, for partners in that market.
Transport & connectivity
- AS2 / OFTP2 / SFTP
- The long-standing channels your large customers still run on.
- REST APIs
- The modern way to connect one system to another in real time.
Business systems
- ERP
- Where your orders, invoices and master data live.
- TMS / WMS
- Transport and warehouse: the systems that feed your despatch advices.
- SYDONIA World
- The region's customs system: the data it requires governs what can clear.
- Accounting
- The destination: reconciliation, matching, close.
- Middleware
- The layer orchestrating exchanges between all of the above.
From an urgent problem to a lasting relationship
We come in through the problem keeping you awake. We stay because, once inside, we see what nobody was looking at.
- 01
Diagnose
Establish precisely what is broken, where, and what it costs.
- 02
Fix
Remediate the urgent problem on your existing systems, through to production.
- 03
Discover
While fixing it, we map how your flows actually run — and what that reveals.
- 04
Expand
We report what we found, with evidence. You decide what happens next.
- 05
Partner
A technical partner who keeps finding and removing operational friction.
Fixing one broken process almost always reveals another
To repair an invoicing flow you have to follow it end to end. That is when the everyday becomes visible: the workarounds, the re-keying, the data that exists twice, the enquiries nobody answered.
Revenue leakage
Opportunities you already generated, disappearing before they close.
- Unanswered enquiries
- Follow-ups never made
- Quotes with no tracking
Operational leakage
Human time spent on work no human should be doing.
- Invoice re-keying
- Manual reconciliation
- Repetitive checks
Data leakage
The same information, several versions, none of them authoritative.
- Divergent master data
- Duplicate customers
- Systems out of sync
Process friction
Teams permanently compensating for poorly connected systems.
- Backup spreadsheets
- Copy-paste between applications
- Double-checking
We do not sell an upsell — we report what we found
Every recommendation starts from something observed in your environment, with evidence. If we find nothing, we propose nothing.
- Invoices reconciled by hand every morningreconciliation automation
- Customer messages handled one at a timeresponse and qualification automation
- Incoming enquiries with no follow-upautomatic capture and follow-up
- The same data entered in two systemssystem integration
- The same checks repeated every dayautomated checks and validation
What we can tackle next
These offers only make sense afterwards. They answer problems we observed, not a catalogue.
Revenue recovery
You are already generating opportunities. We make sure they don't disappear on the way.
- Incoming enquiries left unprocessed
- Conversations and messages with no reply
- Follow-up that is too slow, or missing
- Lead qualification still done by hand
Operational automation
Once the flow is repaired, the repetitive work around it remains. Reconciliation done by hand, the same checks repeated daily, data re-entered from one system to the next: paid time that produces nothing.
- Automatic invoice processing
- Reconciliation and matching
- Automated replies and qualification
- Data verification without human intervention
Where these flows break most often
The more standardised and high-volume your exchanges, the more a mapping error costs.
EDI- and invoicing-intensive sectors
What your rejections actually cost
A rejection is never free: someone reprocesses it, and the invoice is paid later. Set the sliders to your reality — this is your number, not ours.
Rejections, blocks and reprocessing combined.
Identifying, correcting, resending, following up.
Days of slippage before you get paid.
Reprocessing hours per year
600
per year
- Cumulative days of payment delay per year
- 17,280
This uses only your values and stops at hours: the loaded hourly cost is a figure only you know. It does not replace a measurement on your real data: establishing the exact figure, flow by flow, is precisely what the diagnostic does. But if the order of magnitude surprises you, it is worth verifying.
Frequently asked questions
What people ask before handing us a flow.
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.
What exactly is the pre-clearance you offer?
Preparing the file before it enters your TMS. We ingest customs documents as they arrive, reconcile container numbers, gross weights, HS tariff codes and IncoTerms field by field against your order data, then push a validated payload into CargoWise. It is not a customs brokerage service: we file no entry on your behalf.
Which documents can you ingest?
Scans, faxes, native PDFs and photographs of paper documents, in any language and any layout. The file enters the pipeline as it arrives: there is no per-shipper template to define and no format to impose on your partners. An unreadable document is flagged as an exception rather than pushed through with doubtful data.
Where do the 45 minutes per file and the 3-second processing time come from?
They are order-of-magnitude estimates meant to frame the problem, not measurements taken in your operation — the pre-clearance page says so next to the figures. The 100-shipment benchmark exists for exactly that reason: it replaces our estimate with your own durations, on your own files.
What does the first step actually look like?
Describing your problem, in a few lines. We come back with a first reading and, if the subject is in our field, we scope a diagnostic. We never start with a software proposal.
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 an estimate after the first conversation, before starting.
Are we committed to continuing after the diagnostic?
No. The map and the remediation plan are yours, including if you choose to have the fixes carried out in-house or by another team.
Do we need to change software or platform to fix the problem?
Usually not. Most failures come from the mapping, the transformation or the upstream data, not the tool. If replacement genuinely becomes the best option, we say so after the diagnostic — not before.
Is Anumerik a legal or tax advisory firm?
No. We work on the technical implementation: mappings, data transformations, connectivity, integration. On interpreting the rules and your own obligations, your legal or tax advisers remain the reference.
Which areas do you operate in?
Mainly Francophone West Africa, plus cross-border flows within the UEMOA zone. We work in French and English.
Why is no pricing shown on this site?
Because a price published before a diagnostic would be invented. What an engagement costs depends on the number of systems involved, the number of partners affected and the state of the existing documentation — three things nobody knows before looking. We quote after the diagnostic, against a written scope.
What data do we need to send you?
The minimum necessary. For the first conversation, the symptom and one rejected message are almost always enough. For the analysis, read access to the messages and exchange logs covers most cases. We state exactly what we need, and why.
Do we become dependent on you to maintain the flow?
That is precisely what we try to avoid. Every delivery is documented, and a knowledge transfer is offered so your team can read a rejection, fix the common cases and know when to escalate.
What are your tool recommendations based on?
On the constraints we observe, and on nothing else. We sell no platform and take no commission on the ones you use or that we might mention. When we say a replacement is unnecessary — which is usually the case — we lose nothing by saying it.
Why talk about automation on an e-invoicing site?
Because fixing a flow means following it end to end, and that traversal almost always reveals manual work that no longer needs to exist: re-keying, reconciliation, double-checking. We report it; you decide whether it is worth addressing.
Describe the problem. We will tell you what is happening.
A short conversation is often enough to locate the origin of the failure. We will tell you what we think is happening, what you can handle in-house, and whether the subject is outside our field. Would it be unreasonable to look at where the flow actually breaks before deciding whether anything needs fixing?
Fix the flow. Remove the friction. Recover the value.