Skip to content
Get a diagnostic
Our services

Two ways to unblock your invoicing flows

A fixed-scope, fixed-price audit that establishes exactly what is failing. Technical oversight so your own team can fix it inside your existing tools. Either way, your systems stay yours.

Written for : IT directors, finance directors and IT/TMS leads at freight forwarders, customs brokers and transport organisers.

At a glance

What is sold
Two consulting engagements: a fixed-scope, fixed-price audit of the failure points in your flows, and technical guidance for your teams on your existing tooling.
Who it is for
Freight forwarders, customs brokers and transport organisers — IT directors, finance directors and TMS owners.
Division of roles
Anumerik analyses, specifies and validates. Your teams build and operate. You keep control of your system.
What we do not do
Anumerik does not host, operate or warrant the compliance of any production system, and gives no legal or tax advice.
Pricing
Not published. Scope and price are fixed before work begins, after a first conversation.
Service A · Fixed-scope audit

Know exactly why your invoices are being refused

Your invoices go out and some come back refused. The reason given is short, technical, and does not say what to change. Your teams rework the documents one by one, sometimes for weeks, without knowing whether the problem is one customer, one type of service, or the tool itself.

This audit answers one question: what exactly is making your flows fail, and in what order should it be fixed. Scope agreed in advance, fixed price, result delivered in ten working days.

What you get is a working document your IT team or TMS integrator can apply directly. We do not touch your systems: we tell you where to look and what to change.

Format
Fixed-scope audit, agreed before we start
Duration
10 working days
Price
On quotation — fixed, known before signature
Execution
By your teams, from our specification
Request this audit

This audit is for you if

  • Some of your invoices are refused and the reason returned means nothing to your teams.
  • You rebill costs advanced on behalf of your customers and those lines cause trouble.
  • Some service types go through and others do not, with no apparent logic.
  • Your TMS produces an export the receiving platform refuses.
  • A deadline is approaching and nobody can say what gap is left to close.
  • You have to budget a compliance project without knowing what is in it.

What the audit examines

We compare what your systems actually produce against the rules the receiving platform applies, field by field.

EDIFACT messages (D96A / D01B)

Analysis of the messages actually transmitted: expected segments and qualifiers, conditional elements that become mandatory depending on transaction type, gaps against the recipient’s specification in force.

TMS exports against the validation rules

Your exports run against the Schematron rules derived from your country's tax platform specification: what is structurally valid but invalid against the business rules, and therefore refused despite being well-formed.

Customs disbursements (débours)

Handling of sums advanced in the customer’s name and on their behalf. This is the line item that most often fails at a customs broker: it exists, but it is not qualified in a way the platform recognises.

Ancillary charge codes

Demurrage (surestaries), BAF and other surcharges: how the items are coded, their consistency with the main service, and correct attachment to the taxable base.

VAT exemption categories

Verification of the exemption categories used and their consistency with the reason carried on the invoice — a missing or miscoded reason is enough to have an otherwise correct document refused.

Rounding and amount consistency

Gaps between line totals and header totals, the rounding rules your tools apply, units and currencies. A frequent cause of serial rejections on otherwise simple documents.

What you receive

  • A Technical Gap Specification: every gap found, each tied to the field, the message and the rule that fails.
  • A RAG audit report — Red, Amber, Green — ranking each control point by criticality, so you can separate what blocks a flow from what can wait.
  • The recommended fix order, with the dependencies between fixes.
  • What belongs to your tooling, what belongs to your data, and what belongs to platform-side configuration.

Who does what

Us
We analyse, qualify every gap and write the remediation specification.
You
Your teams apply the fixes in your tools, at their own pace and under their own control.

How the ten days run

  1. 01

    Scoping

    Written, fixed scope: which flows, recipients and service types are covered.

  2. 02

    Collection

    Transmitted messages, rejection responses, TMS exports and applicable specifications.

  3. 03

    Analysis

    Rule-by-rule comparison and qualification of every gap.

  4. 04

    Write-up

    Technical Gap Specification and RAG ranking of the control points.

  5. 05

    Handover

    A working session with your IT team or your integrator.

Service B · Technical oversight

Make the fixes in your own tools, with someone who knows them

You know what needs fixing — sometimes because the audit has just said so — but your team has not done this kind of transformation before, and the stakes are too high to learn in production.

We work alongside your teams on the tooling you already own. No new platform to buy, no extra subscription, no migration: we work inside your existing chain.

In practice we specify the transformation logic, define the checks to apply, and validate that the connection genuinely works end to end. Your teams build and run it.

Format
Time-and-materials or milestone-based, depending on scope
Price
On quotation — day rate or fixed price per milestone
Duration
Scope-dependent, framed milestone by milestone
Execution
By your teams, with our technical oversight
Discuss my scope

This engagement is for you if

  • You already own a mapping tool and nobody on the team has handled this case.
  • Your developers are making progress, but every business rule raises a question of interpretation.
  • Your connection passes the tests and nothing actually flows in production.
  • You want to build the capability in-house rather than depend on a supplier for every change.
  • Your TMS integrator is waiting for a specification nobody has written yet.
  • You have to choose between several technical approaches with no basis for comparison.

What we oversee

We work on design and validation. Development and operation stay with you.

Transformation logic specification

Rule by rule: which source field feeds which target field, under what conditions, with what handling of edge cases and missing values.

Schematron assertion rules

The checks to run before transmission, so what would be refused externally is caught internally — with an error message your finance team can act on.

Invoicing-platform connectivity validation

Verifying that the electronic identifier is correctly registered and routed, that the content profile is honoured, and that both directions — sending and receiving — genuinely work.

Choosing between approaches

Where a rule belongs: in the mapping, the ERP, the TMS or the integration layer. That choice determines who maintains the rule three years from now.

Review of your developments

Reading the transformations your teams produce before go-live, on nominal cases and on edge cases alike.

Knowledge transfer

Documentation of the rules and the decisions, so your team can evolve the flow without calling us on every specification change.

The tools we work in

  • Mapping and integration tools: Altova MapForce, Talend, Boomi, MuleSoft.
  • Native TMS mapping: CargoWise, SAP TM, Akanea.
  • Whatever your existing chain happens to be — we adapt to the tooling in place, not the other way round.

Who does what

Us
We specify, arbitrate and validate. We answer design questions throughout the project.
You
Your teams build, test and operate. The infrastructure and the code stay with you.

How an engagement runs

  1. 01

    Scoping

    Scope, milestones and respective roles, written before we start.

  2. 02

    Design

    Specification of the transformation logic and the control rules.

  3. 03

    Oversight

    Your teams build; we answer the design questions as they arise.

  4. 04

    Validation

    Review of the developments and end-to-end testing, edge cases included.

  5. 05

    Handover

    Documentation of the rules and decisions, for your autonomy afterwards.

Your infrastructure stays yours

We host nothing, we operate nothing, and we sell you no platform. That is not a caveat: it is what keeps our engagements short and your costs predictable.

No dependency created
Your flows run on your tools. If you stop working with us, nothing stops and nothing needs migrating.
No additional subscription
No licence to take out, no recurring cost added to what you already pay. You buy an engagement, not an ongoing service.
The capability stays in-house
Every engagement ends with the rules and decisions documented. The goal is that your team can evolve the flow without us.
You keep control of the schedule
Fixes are applied by your teams, on your priorities and in your release windows.

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.

Other sectors hit the same mechanics

Rebilling advanced costs, multiple line items attached to one main service, and exemption categories produce the same rejections well outside transport.

Construction

Remediation of construction e-invoices: VAT on subcontracting, progress claims, retention and price revision.

Temporary staffing

Remediation of temporary staffing e-invoices: timesheets, charge-out coefficients, expense rebilling and multi-site invoicing.

Describe my situation

Frequently asked questions about these two offerings

Do we have to start with the audit before the advisory engagement?

No, but it is the most frequent and most economical sequence. The audit produces the specification the advisory engagement implements; without it, part of the advisory time goes on establishing the same findings, at the time-and-materials rate.

What if the audit finds nothing significant?

That is a result in itself, and it is delivered as such: the RAG report says so explicitly. It happens that a flow is technically correct and that a value entered upstream, or a business rule, is the real cause. We report that rather than hunting for a technical problem that does not exist.

Do you work directly inside our systems?

No. We analyse, specify, arbitrate and validate; your teams build and operate. For the audit, read access to the messages and exports is enough in the large majority of cases.

Do you work with our TMS integrator or instead of them?

With them. The Technical Gap Specification is written to be handed straight to an integrator or an internal team. We coordinate with them when a change falls within their scope.

Do you guarantee that our flows are compliant?

We stand behind the rigour of the technical analysis and the precision of the gaps identified against the rules applicable at a given point in time. Whether a production system is compliant depends on how it is operated, which remains yours — and interpreting the rules is a matter for your legal or tax advisers.

Can the audit scope change partway through?

The scope is fixed at scoping, which is what makes the price and the timeline holdable. If the analysis surfaces something outside scope, it is flagged in the report and quoted separately — never absorbed silently.

The rest of what we do

These two offerings cover the most frequent case. The detail by technical area is here.

E-invoicingEDI / EDIFACTERP integrationRevenue recoveryOperational automation
See how we work

Describe what is blocking, and we will tell you which offering applies

A short conversation is usually enough to know whether your situation calls for the audit, the advisory engagement, or neither.

Describe the problem — 30 minGet the cause established

Fix the flow. Remove the friction. Recover the value.