EXIMYug / EXIM SAMADHAN
EXIM SAMADHAN

Something went wrong. Determine what can actually be fixed or recovered.

Samadhan diagnoses the root cause, validates entitlement and evidence, tests deadlines and economics, then executes the appropriate FIX / CLAIM / CHALLENGE / RECOVER route—or tells the exporter when escalation or further spend does not make sense.

Samadhan case flow

A resolution workflow, not a blanket recovery promise.

1. DIAGNOSEWhat failed and why?
2. VALIDATEIs there a legitimate basis?
3. VIABILITYFixable, recoverable, negotiable or low-value?
4. ROUTEWhich mechanism and decision-maker?
5. EXECUTEFix, claim, challenge, negotiate or escalate.
6. TRACKEvidence, action, response and outcome.
7. LEARNTurn root cause into a Prevent control.

Six resolution outcomes

EXIMYug controls diagnosis, evidence and execution workflow. It does not pretend to control a bank, buyer, insurer, ECGC, carrier, Customs, DGFT, arbitrator or court.

01

FIX

Correct & close

Repair procedural, data and documentary exceptions where correction is permitted.

EDPMS • e-BRC • DOCUMENTS • BENEFITS
02

CLAIM

Claim protected loss

Map policy/contract entitlement, quantify loss, assemble evidence and manage the claim workflow.

ECGC • MARINE • CARRIER
03

CHALLENGE

Challenge a rejection or charge

Test a decision against applicable rules, policy wording, documents and transaction facts; build the representation/rebuttal.

BANK • INSURER • ECGC • CARRIER
04

RECOVER

Negotiate & recover

Evidence-led demand, acknowledgement, settlement, payment plan and collection escalation.

BUYER • COUNTERPARTY
05

ROUTE

Escalate intelligently

Prepare the case and route it to the institution, authority, mediator, collection specialist or lawyer that can decide or enforce it.

RIGHT ROUTE • RIGHT PACK • RIGHT DEADLINE
06

STOP

Do not chase bad cases

Compare amount at stake, entitlement, evidence, limitation/deadline, counterparty and likely cost before spending more.

SAVE FURTHER LOSS

What “how we solve it” actually means

Representative workflows. Final outcomes remain subject to the relevant counterparty, institution or authority.

ProblemEXIMYug diagnosisExecution mechanismExternal decision / dependency
Buyer unpaidDebt acknowledgement, invoice, delivery/acceptance, payment terms, dispute statusDemand sequence → acknowledgement → settlement/payment plan → collection escalation → legal pack if justifiedBuyer / collection / court or arbitration where needed
Buyer deduction / short payInvoice vs received amount; acceptance/QC; contractual deduction rights; bank/FX/commission effectsQuantify unexplained deduction → evidence pack → formal dispute → negotiate/recoverBuyer / contractual dispute forum
Quality disputePO/spec ↔ inspection/test/QC ↔ shipment evidence ↔ buyer complaintLiability matrix → causation/evidence gaps → rebuttal or commercial settlement → claim where cover/liability existsBuyer / surveyor / insurer / dispute forum
LC discrepancyLC/UCP/ISBP requirements vs presented documents and timelinesClassify curable/not → corrected document / amendment / waiver request / resubmission packIssuing/nominated bank and applicant where waiver required
Bank refuses documentsRefusal notice, LC terms, UCP/ISBP and document setStructured discrepancy analysis → rebuttal/representation → bank escalation → expert/DOCDEX route where suitableBank; external expert process is not court enforcement
ECGC claim rejectedPolicy clause ↔ rejection reason ↔ declarations/overdue/limit/recovery obligations ↔ event factsIdentify evidence or interpretation gap → representation → grievance/escalation packECGC / appropriate dispute route
Marine claim rejectedPolicy/exclusions, survey, causation, notice and evidenceCoverage/cause matrix → missing evidence → rebuttal/representation → grievance/dispute packInsurer / ombudsman or dispute forum where applicable
EDPMS / e-BRC stuckShipping bill ↔ invoice ↔ IRM/payment ↔ AD-bank data ↔ exception reasonReconcile → identify mismatch → correction/closure evidence pack → bank workflow → track to updated statusAD bank / relevant system
Incentive / refund stuckEligibility, shipping-bill declaration, claim/process status, exception and amountReconstruct entitlement → identify missing/incorrect field or evidence → amendment/representation/action packCustoms / DGFT / GST or other scheme authority
Freight / demurrage disputeQuote, booking, B/L, tariff/surcharges, event timeline, free days and invoicesRecalculate amount → allocate responsibility → challenge unsupported days/rates/charges → refund/dispute packCarrier / forwarder / terminal / contractual forum
Fraud / diverted paymentPayment instructions, communications, bank trail and change-of-account evidencePreserve evidence → urgent bank recall/freeze requests → counterparty-bank/insurer notification → authority/legal packBanks, authorities, insurer, legal process; recovery may be impossible
Evidence missingTransaction chronology across ERP/email/bank/CHA/forwarder/carrier/insurerEvidence graph → source requests → version/timeline reconstruction → explicit missing-proof listAvailability of original records and third-party cooperation

Case viability before spend

Every case gets a pursue / negotiate / route / stop recommendation based on evidence—not a promise of success.

ENTITLEMENTBasis?Contract / policy / rule / obligation
EVIDENCEProvable?Completeness + contradictions + gaps
DEADLINEOpen?Remedy, notice, claim or limitation clock
ECONOMICSWorth it?₹ at stake vs time, cost and dependency
Open Case Viability →
SAMADHAN → PREVENT

Every resolved or failed case becomes a future control.

Root cause is translated into a rule, document check, data dependency, deadline or evidence requirement and attached to the relevant transaction stage.

CASE

Failure

What actually happened?

ROOT CAUSE

Why

Rule, document, data, deadline or external event?

CONTROL

Prevent

Can it be stopped, protected or proved?

BEFORE SHIP

Clear to Ship

GO / FIX / HOLD / PROTECT.

AFTER SHIP

Clear to Close

Watch until financial/regulatory closure.

See EXIM Prevent →
SAMADHAN CASE SIMULATOR

See what “solve” means for different failures.

Select a case. The route changes according to evidence, economics and who has authority to decide.

SERVICE JOURNEY

Something went wrong. Determine what can actually be fixed or recovered.

Use for buyer non-payment, deductions, LC/bank issues, ECGC/marine rejection, freight disputes, compliance or evidence failures.

01 · WHEN

Start with the problem

Use for buyer non-payment, deductions, LC/bank issues, ECGC/marine rejection, freight disputes, compliance or evidence failures.

02 · INPUTS

Bring the transaction evidence

Case facts, amount, documents, correspondence, rejection/reason, deadlines and actions already attempted.

03 · ANALYZE

What EXIMYug actually checks

Diagnose → validate → viability → choose FIX / CLAIM / CHALLENGE / RECOVER / ROUTE / STOP.

04 · OUTPUT

What you receive

Case route + evidence pack + action plan + ownership + tracked outcome.

05 · OWNERSHIP

Who acts next

Every finding is assigned an owner, action, deadline/dependency and ₹ exposure. EXIMYug does not imply authority where a bank, buyer, insurer, carrier, Customs/DGFT, ECGC or legal forum must decide.

HOOK→QUALIFY→INPUTS→CHECK→₹ IMPACT→ACTION→OWNER→OUTCOME
Confidential case intakeDocument-led analysisHuman review where judgment is requiredYou control what you submit

Check My Case

Tell us what is stuck, rejected, disputed or unpaid.

Talk to EXIMYug