Create an expected-benefit object at shipment and follow it through eligibility, claim, processing, exception and credit.
The key question is not whether a CHA filed something; it is whether the exporter received the expected ₹ outcome.
| Stage | EXIMYug check | Failure detected |
|---|---|---|
| Eligibility | Scheme/product/shipment applicability | Missed entitlement |
| Declaration | Required shipping-bill fields | Incorrect/missing claim setup |
| Expected amount | Compute expected benefit | No benchmark for leakage |
| Processing | Status + exception | Stuck WIP |
| Credit | Expected vs received | Short/missing benefit |
Use when drawback, RoDTEP/RoSCTL, IGST refund or another export benefit is delayed or unclear.
Use when drawback, RoDTEP/RoSCTL, IGST refund or another export benefit is delayed or unclear.
Shipping bills, scheme eligibility data, claim/status records, bank/Customs/DGFT evidence.
Eligibility → claim → processing → exception → amount due → missing action.
Benefit register + ₹ due + blocker + evidence/action pack.
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.
Resolve exceptions, escalate where needed, then add preventive declaration/readiness checks.
Identify benefits that are eligible, delayed, unmatched or unresolved.
Share only what is needed to assess the workflow.