Factsheets: 📈 Markets 🎯 Mandates 📋 Case Studies 📘 SOPs 🏛 Trade Bodies 🏙 Cities 🌍 Countries 🇮🇳 Indian States ⚓ Ports 🏛️ SEZs 🤝 Blocs 📜 FTAs 🛤 Corridors ⚙ Verticals 📦 Commodities 🧮 Tools ⚖️ Compare 🌐 Bilateral Hubs 📚 Library 🎓 Academy ✍️ Essays 📰 Blog 🔤 Lexicon ❓ FAQ 📡 Authority Sources ⚡ Daily Pulse 📰 Topic Briefs 📡 Google Signals 🧭 Scope Scape cron-refreshed
Live factsheets · cron-refreshed

All factsheets at a glance

Command center →
📈 Markets
554
global + India · commodities + indices + shares + crypto + FX
minute
🎯 Mandates
69
sell + buy · live
daily
📋 Case Studies
37
closed · anonymised
weekly
📘 SOPs
42
step-by-step playbooks
weekly
🏛 Trade Bodies
1,350
291 baseline + 1059 hand-curated
monthly
🏙 Cities
1,584
global atlas
daily
🌍 Countries
184
multilateral
weekly
🇮🇳 Indian States
37
state trade profiles
monthly
⚓ Ports
52
global maritime gateways
monthly
🏛️ SEZs
31
global SEZ profiles
monthly
🤝 Blocs
28
tracked
monthly
📜 FTAs
526
active or signed
monthly
🛤 Corridors
37
tracked
monthly
⚙ Verticals
50
sectoral
weekly
📦 Commodities
51
HS-coded intelligence
monthly
🧮 Tools
105
free utilities
monthly
⚖️ Compare
pairwise combinations
monthly
🌐 Bilateral Hubs
184
India × every country
weekly
📚 Library
140
interconnected
monthly
🎓 Academy
25
trade education
monthly
✍️ Essays
30
long-form analysis
monthly
📰 Blog
34
editorial
weekly
🔤 Lexicon
312
glossary terms
monthly
❓ FAQ
155
curated Q&A
monthly
📡 Authority Sources
140
curated · vetted
hourly
⚡ Daily Pulse
145
rolling 5,000 cap
hourly
📰 Topic Briefs
29
permanent archive
hourly
📡 Google Signals
Trends·News·Alerts
hourly
🧭 Scope Scape
61
11 scopes
hourly

Frequently Asked Questions

Answers to 1205 questions about India-EU trade, FTAs, customs, CE marking, trade finance, regulatory compliance, pharma, logistics, and the AJG mandate process.

Clear

14 questions found

💰

Trade Finance & Payment

14 questions
What payment method should I use for new EU buyers? +

For new EU buyers, AJG recommends: (1) Irrevocable Confirmed Letter of Credit (LC) for orders above USD 100K, (2) Documents against Payment (D/P) for orders of USD 25K-100K, (3) 30% advance + 70% before shipment for orders below USD 25K. Avoid open account with new buyers.

How does a Letter of Credit work? +

A Letter of Credit (LC) is a bank' written undertaking to pay the Indian exporter a specified amount upon presentation of complying shipping documents within a stipulated time. Process: (1) EU buyer instructs their bank (issuing bank) to open an LC, (2) LC is transmitted via SWIFT MT700 to an Indian advising bank, (3) Indian exporter ships goods and presents documents to the advising/negotiating bank, (4) if documents comply, the bank pays the exporter. The LC is the most secure payment method for India-EU trade.

What is the difference between a confirmed and unconfirmed LC? +

An unconfirmed LC is a payment undertaking by the issuing bank (EU buyer' bank) only. A confirmed LC adds a payment undertaking from an Indian bank (confirming bank). Confirmation eliminates the risk that the EU issuing bank defaults or the EU country imposes foreign exchange restrictions. For first transactions or buyers from higher-risk countries, always request a confirmed LC.

What documents are required for a typical India-EU LC? +

Standard documents for India-EU LC: (1) Commercial invoice, (2) Packing list, (3) Bill of Lading (negotiable, full set 3/3), (4) Certificate of Origin (from EEPC/FIEO/EIC/Chambers), (5) Packing certificate, (6) Insurance certificate (if CIF), (7) Inspection certificate (if required), (8) Phytosanitary/sanitary certificate (for agro-food). Additional documents vary by product and buyer requirements.

What are the most common LC discrepancies? +

Common discrepancies that cause LC rejection: (1) Late presentation (documents presented after LC expiry or after 21 days of shipment date), (2) Description of goods does not match exactly, (3) Short shipment (quantity less than LC amount), (4) Missing endorsement on B/L, (5) Insurance cover insufficient or incorrect currency, (6) Inconsistency across documents (invoice and packing list amounts differ). Always use an experienced customs house agent to prepare documents.

What is ECGC and how does it protect Indian exporters? +

ECGC (Export Credit Guarantee Corporation of India) is the government-owned export credit insurer. ECGC provides: (1) Buyer exposure limits — ECGC assesses your EU buyer and issues a credit limit, (2) Export credit insurance — if buyer defaults, ECGC pays 60-90% of the loss, (3) Bank guarantees — allowing Indian banks to provide pre/post-shipment credit. AJG recommends ECGC cover for all new EU buyer relationships.

What is pre-shipment finance and how do I access it? +

Pre-shipment finance (packing credit) is a loan from an Indian bank to fund the procurement, production, and packaging of goods before shipment. Two types: (1) PCFC (Pre-Shipment Credit in Foreign Currency) — in USD/EUR at SOFR/EURIBOR-based rates, typically lower than INR credit; (2) Packing Credit in INR — at concessional rates for confirmed export orders. Apply with your confirmed purchase order or LC.

What is factoring and is it available for India-EU trade? +

Export factoring allows Indian exporters to sell their export invoices (accounts receivable) to a factor at a discount, receiving immediate cash instead of waiting for the EU buyer to pay. Two-factor system: Indian export factor purchases the invoice and bears the buyer credit risk; EU import factor collects payment from the EU buyer. Available via FCI (Factors Chain International) member institutions in India and EU.

What is the role of SWIFT in India-EU trade payments? +

SWIFT (Society for Worldwide Interbank Financial Telecommunication) is the global messaging network banks use for international payment instructions and LC communications. Key SWIFT messages in India-EU trade: MT700 (LC issuance), MT710 (LC advice by bank), MT103 (international wire transfer), MT202 (bank-to-bank transfer). All India-EU international payments are routed through SWIFT.

Can India trade in Rupees with EU? +

India is promoting INR settlement for bilateral trade. An INR settlement mechanism requires: (1) EU importer opens a special INR Vostro account at an Indian bank, (2) EU importer pays in INR; Indian exporter receives INR. As of 2026, INR settlement with EU is limited — most India-EU trade remains in USD or EUR. RBI has approved INR trade with UAE, Russia, Malaysia, and several other countries.

What is supply chain finance and how can it help? +

Supply chain finance (SCF) is a set of financial solutions allowing large EU buyers to extend payment terms while enabling Indian suppliers to receive early payment at a lower cost. Example: EU retailer (Buyer) has 90-day payment terms; SCF platform allows Indian exporter (Supplier) to receive payment in 2-5 days at a small discount — using the EU buyer' credit rating. Programmes offered by Santander, BNP Paribas, HSBC, and others in EU.

What payment terms should I offer EU buyers? +

Standard EU buyer payment terms by product type: Consumer goods/FMCG: 30-60 day open account (for established buyers). Industrial/engineering: D/P or 30 day usance LC. Pharma/medical devices: D/P or LC, 60-90 day usance. Capital equipment: LC, 90-180 day usance or forfaiting. Always use ECGC cover for open account trade.

What is forfaiting and when is it appropriate? +

Forfaiting is the purchase of an Indian exporter' medium-term export receivables (bills of exchange or promissory notes) by a forfaiter at a fixed discount rate, without recourse to the exporter. Suitable for: capital goods exports with credit periods of 1-7 years. Indian machinery, power equipment, and turnkey project exporters use forfaiting to offer EU buyers extended payment terms while receiving immediate cash.

How do I hedge INR/EUR exchange rate risk? +

Indian exporters can hedge EUR/INR exposure using: (1) Forward contracts with Indian banks — lock in the EUR/INR rate for a future delivery date; (2) Cross-currency swap — exchange EUR receivables for INR at a fixed rate; (3) Options — buy the right (not obligation) to exchange at a fixed rate. Under FEMA, Indian exporters can hedge up to 100% of contracted foreign currency exposures with RBI-authorised banks.

Can't find your answer? Ask our principals directly.

Ask the Principals Contact Form

Totality lens · 32 points to ponder · 16 user POV + 16 developer POV · this institutional hub

User POV — for the practitioner navigating the Faqs institutional hub

Eight dimensions

1 · Possibility

A FAQ atlas that consolidates the recurring questions from across all entity types — country, vertical, FTA, corridor, tool — into searchable answers replaces the per-page micro-FAQ scatter with a single navigable surface. The possibility is to make the platform answerable to questions even when the user does not know which page would have hosted the answer. The atlas is also the highest-density SEO surface because each Q+A is naturally a target keyword.

2 · Plausibility

Plausibility tracks question-currency. FAQs go stale when underlying answers change; a FAQ that says "the FTA covers up to 90 percent of HS lines" is wrong if the coverage changed. We attach last-verified per FAQ + cron-driven detection of question-answer drift. The plausibility floor is the verification cadence.

3 · Probability

On a six-month horizon, FAQ-led search is dominated by long-tail question queries that aggregator sites do not answer well. The probability that the atlas wins these queries is high because it is structured + sourced + searchable. Aggregate FAQ traffic typically grows compounding with the atlas size; doubling the atlas roughly doubles the inbound.

4 · What works

What works is one-question-one-answer-one-screen format. The reader arrived for an answer; they get it in two paragraphs and a sourced reference. Cross-references to deeper content live below the fold for readers who want depth. What works less well is questions answered with another question; we reject those at intake.

5 · What doesn't work

What does not work is over-stuffing answers. A two-paragraph answer with a sourced reference outperforms an eight-paragraph essay every time on FAQ pages because the user came for an answer not an article. Editorial discipline keeps answers tight.

6 · Common pitfall

A common pitfall is duplicating per-page FAQs into the atlas without context. A FAQ that is meaningful on a city page may be context-dependent in a way the atlas page cannot replicate. We tag context-dependent FAQs and surface their context-anchor explicitly in the atlas-version answer.

7 · Counter-intuitive insight

Counter-intuitively, the FAQs that drive the most cross-page traffic are not the most-searched questions but the questions that most often have follow-up questions. A user asking "what is rules of origin?" is at the start of a multi-question journey; a user asking "what is the Singapore postal code?" is at the end of a one-question journey. We weight follow-up-likelihood when prioritising FAQ deepening.

8 · Highest-leverage move

The highest-leverage move is the question-cluster surface: groups of related questions arranged in a rough learning order. A user reading "what is rules of origin?" sees a cluster including "how do I prove rules of origin compliance?", "what documents are needed?", "who issues the certificate?" — moving them from one question to a procedural understanding in five clicks. The cluster compute is graph-walk over the question-relation taxonomy.

Eight user intents

9 · Who gains most

For curious readers without deep platform-knowledge — first-time visitors arriving via long-tail search, students researching trade-related topics for coursework, professionals fact-checking specific points mid-work, and the question-driven sub-group of any of the above who reach for FAQ pages by reflex. The schema serves all four because a good FAQ answer is universally useful regardless of audience.

10 · Irreducible essence

They want a direct answer in two paragraphs, with a sourced reference, and a path-forward to deeper content if they want to keep going. The schema delivers all three: the answer is the headline, the reference is in-line, the deeper-content link is below.

11 · Optimal timing

When they have a specific question. FAQ traffic peaks during workdays + weekday evenings (curious learners). Editorial freshness matters because question-answer drift is most-likely to surface on FAQs that read confidently — a confident wrong answer is worse than no answer.

12 · Where (sub-areas)

Where they read it: 60 percent mobile because question-search is opportunistic. The mobile design surfaces the answer above the fold with the source-reference inline. Desktop readers consume the question-cluster surface more.

13 · Why misunderstood

Because FAQ content is the cheapest SEO win in trade-content publishing — every Q+A is a natural keyword target, and aggregator sites do not answer well. The why for the atlas is fundamentally about claiming the long-tail SERP for trade questions before competitors do.

14 · Highest-leverage sub-paths

Which FAQ-cluster dominates per audience: terminology FAQs ("what is X?") for new visitors, procedural FAQs ("how do I do X?") for execution-mode visitors, comparison FAQs ("X vs Y?") for diligence-mode visitors, edge-case FAQs ("what if X happens?") for problem-solving-mode visitors.

15 · Whose advice to trust

Whose perspective answers the question: the schema labels each answer with the actor-perspective (principal, broker, banker, regulator, lawyer) where it matters. A "what documents are needed for an LC?" answer differs depending on whether the asker is the importer, exporter, or bank.

16 · How to proceed differently

How they engage: arrive via search, read the answer, click through to deeper content if interested, exit the platform satisfied. Conversion to deeper engagement is moderate; conversion to repeat visit is high because FAQs build name-recognition. The atlas is a top-of-funnel surface that pays off in long-term recurrence.

Developer POV — for the architect, maintainer, future contributor to this hub

Eight dev dimensions

17 · Data architecture

Data architecture: per-FAQ record with question + answer + actor-perspective + source-reference + last-verified-date + question-cluster-tags + cross-references. The cluster-graph is hand-curated; the per-FAQ data is editorial. Search index is text-indexed across question + answer + cluster-tags.

18 · Schema markup

Schema markup: each FAQ page emits as FAQPage with mainEntity Question children. Each Question has acceptedAnswer + dateModified + sameAs (the source-reference). The hub itself emits a parent FAQPage aggregating high-priority Q+A. JSON-LD identifier "ajg:faq::{slug}".

19 · Internal linking

Internal linking: FAQs hub → individual FAQ URLs (one per question) + cluster-pages (groups of related FAQs). Each individual FAQ links to relevant deep-content (entity hubs, methodology essays, SOPs). Cross-content injector surfaces relevant FAQs throughout the platform — a city page mentions "rules of origin" and gets a FAQ link for that term.

20 · Page-speed posture

Page-speed posture: FAQ pages are tiny (under 25 KB compressed). The hub is the heavier surface because it surfaces the question-cluster index (typically 200+ questions across clusters); we virtualise rendering with intersection-observer.

21 · Mobile UX

Mobile UX: FAQ page is question-as-headline + answer-as-body + source-reference-as-footer. Cluster pages are vertical-scroll lists of question-headers (tap-to-expand). Search input is sticky-top. All tap targets 48 px.

22 · Accessibility

Accessibility: FAQ pages use proper heading + section semantics. Cluster pages have role=region per cluster with aria-labelledby. Tap-to-expand questions are role=button with aria-expanded. Screen readers traverse cluster pages cluster-by-cluster.

23 · SEO saturation

SEO saturation: each FAQ page has unique H1 (the question), meta-description (the answer summary), FAQPage schema for the single Q+A, BreadcrumbList. Cluster pages emit FAQPage with the full cluster set. Speakable on the answer text. The hub gets ItemList plus the high-priority FAQPage extract.

24 · Extensibility

Extensibility: question-cluster taxonomy grows organically as the atlas widens. Adding new actor-perspectives requires schema-bump but is rare. New cross-references between FAQs are continuously curated; the cluster-graph densifies as the atlas grows.

Eight dev intents

25 · Maintainer audience

For the developer maintaining this atlas, the question-cluster graph is the most editorially-influenced data structure. Algorithmic clustering misses the pedagogical sequencing that makes clusters useful. We maintain the graph by hand at data/faq-clusters.php with cluster-master + question-to-cluster mappings.

26 · Architectural commitment

What changes when FAQs update: data/faqs-data.php gains records or updates existing ones with verification-bumps. The cluster-graph picks up new questions on next-cron rebuild. The text-search index reindexes nightly to pick up new questions.

27 · Refresh cadence

When the cron runs: nightly at 06:00 UTC for the search-index rebuild + cluster-graph cache refresh + verification-cadence sweep. Stagger from other crons.

28 · File map

Where files live: data/faqs-data.php (the registry), data/faq-clusters.php (the cluster graph), includes/faq-template.php (renderer). Hub at /faqs.php; individual FAQs at /faqs/{slug}/; cluster pages at /faqs/cluster/{slug}/.

29 · Existence rationale

Why hand-curated cluster graph: because pedagogical sequencing requires editorial judgement. "What is X?" sequences differently into deeper questions depending on the reader's expected next step, and that depends on context that algorithmic clustering does not capture.

30 · Highest-leverage extension

Which renderer: includes/faq-template.php emits the question + answer + actor-perspective badge + source-reference + cluster-rail + cross-references rail. Accepts $faq_slug. Echoes directly. Idempotent.

31 · Authoritative sources

Whose responsibility: FAQ authoring is editorial. Question-cluster curation is editorial-with-data-assist (we surface candidate cluster memberships from search-co-occurrence, editorial decides). Schema validity enforced by pre-flight.

32 · Maintenance procedure

How to add a new FAQ: (1) author question + answer + actor-perspective + source-reference; (2) submit through admin/faq-intake.php; (3) editorial review checks for over-stuffing + actor-perspective accuracy; (4) on approval, faq-publish.php writes to data/faqs-data.php; (5) editorial assigns to clusters. Total: about 30-60 minutes per FAQ.

PhiloJain Music
Loading…

Explore

Explore the AJG knowledge graph

Every page in the AJG platform cross-links to these primary entities. Click any pill to explore that branch of the knowledge graph.

All hubs · 80 surfaces · click to expand ↓