Declarations as received
Keep the facts from the source in analysis and casework — not silently replaced by re-typed values.
Customs · Workflow
From declarations to outcome
Munire Customs helps you find the right work, understand why it was flagged, and take a supported finding through to reclaim — without turning the system into an automatic decision-maker.
01 / Source and client
First: whose declarations are these?
Bring in structured declaration data and keep its source clear. Analysis stays blocked until the population is matched to an authorised client and the right importer identity.
Authorised importer context
Records without a matched importer stay visibly unmatched and cannot enter controlled analysis.
Know where each fact came from
Separate imported declaration facts from manually entered claim information so validation stays appropriate.
One importer or thousands of lines
Work populations at scale while keeping a clear path back to the individual declaration and line.
02 / Analysis and triage
Prioritise attention — not automated answers.
Rules surface declarations that need a look, rate relative significance, and explain the signals behind each result.
Surface potential issues
Repeatable checks on classification, origin and preference, valuation, duty, import VAT, procedure use and related facts.
Decide what to review first
Focus professional time on the most significant or promising items — not every line equally.
Show why it was flagged
Expose the rules and facts behind the rating so you can evaluate the output, not trust a black-box score.
03 / Investigation
Turn a flag into an evidenced professional finding — or close it.
The investigator reviews the declaration, source record, commercial documents and applicable customs position. The system records the reasoning and supports a positive, negative or unresolved conclusion without assuming every flag is an error.
Work from the actual declaration facts
Keep the MRN, line, commodity, customs value, origin, procedure, duty and import VAT context attached to the investigation.
Record the reasoning, not only the status
Capture what was considered, what rule or treatment applies, where judgement was exercised and what remains uncertain.
Define what would support the conclusion
Set evidence requirements by issue type and show which documents have been received, matched, rejected or remain outstanding.
Make ownership explicit
A human user reviews and signs the conclusion. Automated and AI-assisted results remain decision-support outputs throughout.
04 / Controlled outcome
One finding. Several legitimate routes.
An error may require recovery, correction, voluntary disclosure, monitoring, client advice, broker feedback or no further action. The application preserves the chosen route and the reasons for it.
- 01CorrectRecord the change required and connect it to the affected declaration, client and evidence.
- 02RecoverWhere a paid amount exists and authority is in place, progress a controlled duty or import VAT recovery route.
- 03DiscloseStructure the facts, evidence and correspondence needed where an underpayment or compliance exposure must be addressed.
- 04LearnIdentify repeated broker, supplier, code, origin or process failures across the declaration population.