FEMA (Foreign Exchange)

FEMA (Foreign Exchange) Module - User Guide

FEMA Index Page

1. Introduction πŸ“

The FEMA (Foreign Exchange Management Act) module is designed to track the regulatory lifecycle of foreign exchange transactions. It monitors the progression of an international paymentβ€”from purchase intent and outward remittance to the final proof of import and bank reconciliation.

ℹ️

Business Purpose:

  1. Tracks compliance milestones required by banking and exchange control regulations.
  2. Ensures Outward Remittances (ORM) are paired with physical import documentation (BOE).
  3. Monitors the status of document submissions to authorized dealers (banks).

2. Transaction Lifecycle 🌏

The FEMA module follows a structured progression to ensure regulatory data integrity:

πŸ“„ Pro-Forma Invoice (PFI)

The initial purchase agreement. Records the PFI Number, PFI Date, and PFI Amount in foreign currency.

πŸ’Έ Outward Remittance (ORM)

The actual foreign payment. Tracks the ORM Number and ORM Date of the fund transfer.

πŸ“¦ Invoicing & Shipping

The final receipt of goods. Records the Commercial Invoice (No/Date/Amount), AWB/Bill of Lading Number, and the Bill of Entry (BOE) details.

🏦 Bank Submission & AD Code

The close-out step. Tracks the Authorized Dealer (AD) Code of the transacting bank branch, the Bank Submission Date, and the corresponding Debit Advice Numbers for transaction pairing.


3. Features ✨

πŸ›‘οΈ Sequential Milestone Enforcement

To maintain audit integrity, the system enforces a strict date-logic sequence when a FEMA record is finalized:

  • PFI -> ORM: Outward Remittance date cannot precede the Pro-Forma Invoice date.
  • ORM -> CI: Commercial Invoice date must follow the Remittance date.
  • ORM -> BOE: Bill of Entry must be dated after the Outward Remittance.
  • CI -> Bank Submission: The bank submission date must be on or after the Commercial Invoice date.

πŸ“‹ Checkpoint Invariants

The system provides conditional mandatory checks:

  • If an ORM Date is entered, the ORM No becomes mandatory.
  • If an Invoice Date is entered, the Invoice No becomes mandatory.
  • If a BOE Date is entered, the BOE No becomes mandatory.
  • Bank AD Code must be mapped against the corporate banking profile.

4. Validations and Logic ⚠️

Date Selection Guardrails

  • Financial Year: Reporting and record creation default to the active fiscal year’s start date and today’s date.
  • Range Limitation: In the FEMA Report option screen, a maximum date span of 2 years is permitted to ensure consistent query performance.
  • Future Dates: Strictly prohibited for both ORM and Submission dates.

5. Complete Workflow πŸ”„

Record Initial Transaction

  • Create a FEMA record with the Pro-Forma Invoice details.
  • The system assigns a unique 6-digit FEMA Number (e.g., 000215).

Record Remittance

  • Update the record when the Outward Remittance (ORM) occurs.
  • Enter the ORM No, Date, and select the AD Bank.

FEMA Record Details

Finalize Lifecycle & Reconcile

  • Upon receipt of goods, enter the Commercial Invoice and BOE details.
  • Set the FEMA Status to “Completed”.
  • The system validates the entire date sequence before allowing the status update.

Generate FEMA Report

  • From the FEMA Index, click the dedicated “FEMA Report” button (femareportoption).
  • Select the desired date range to export the statutory compliance schedule.

6. Reports πŸ“Š

  • πŸ“Š FEMA Compliance Report: An exhaustive 19-column report (PFI, ORM, CI, BOE, AWB, Debit Advice, Status, Notes) generated via the “FEMA Report” button on the FEMA index screen for bank reconciliation and regulatory monitoring.
  • πŸ“Š Pending Submission Report: Highlights remittances for which the final customs import proof (BOE) has not yet been submitted to the bank.

7. Best Practices / Tips πŸ’‘

  • Launch FEMA Report from Index: To run the FEMA compliance analysis, click the “FEMA Report” action button located directly on the FEMA transaction index screen.
  • Debit Advice Check: Always cross-reference the DebitAdviceNo field with your bank statement to ensure no transaction gaps.
  • Submission Timing: Aim to fill the SubmissionDate as soon as physical documents are delivered to the bank to avoid statutory compliance notices.