Here’s a detailed Business Process Model for the Trade Finance Management System,

tailored for a bank's trade finance operations. This model illustrates the workflows for key
processes in the system, including user roles and actions.

Business Process Modeling Notation (BPMN)

1. Document Registration Workflow

Actors: Maker, Checker, Supervisor

Description: Handles the collection and verification of applicant documents and generates
unique IDs.

Start --> Maker Inputs Applicant Data --> Submit for Review --> Checker
Reviews and Verifies -->
Approved? --> [Yes: Document Registered] --> [No: Sent Back for Corrections]
--> End

Process Steps:

1. Maker: Inputs applicant details (Name, TIN, License Number, etc.) and uploads required
documents.
2. Checker: Verifies the correctness of data and supporting documents.
3. Decision Point:
o If approved, the document is registered with a unique ID.
o If rejected, the document is sent back to the Maker for corrections.

2. Purchase Order (PO) Processing Workflow

Actors: Maker, Checker, Supervisor

Description: Captures and verifies purchase order details, including supplier and goods
information.

Start --> Maker Enters PO Details --> Link PO to LC or IMP --> Submit for
Review --> Checker Verifies -->
Approved? --> [Yes: PO Processed] --> [No: Sent Back for Corrections] --> End

Process Steps:

1. Maker: Inputs PO details such as supplier, invoice, and goods description, then links the
PO to an LC or IMP.
2. Checker: Ensures PO details match trade finance requirements and associated
transactions.
3. Supervisor (optional): Handles escalated or high-value POs.
3. Letter of Credit (LC) Opening Workflow

Actors: Maker, Checker, Supervisor

Description: Manages LC issuance requests and links them to POs or IMPs.

Start --> Maker Records LC Details --> Link LC to PO/IMP --> Submit for Review
--> Checker Verifies -->
Approved? --> [Yes: LC Issued] --> [No: Sent Back for Corrections] --> End

Process Steps:

1. Maker: Inputs LC details such as supplier, terms of payment, and validity period.
2. Checker: Verifies LC details against associated POs and trade finance guidelines.
3. Supervisor: Monitors high-value LC requests or exceptions.

4. Import Permit (IMP) Processing Workflow

Actors: Maker, Checker, Supervisor

Description: Processes import permits by validating details and linking them to LCs or POs.

Start --> Maker Inputs IMP Details --> Link IMP to PO/LC --> Submit for Review
--> Checker Verifies -->
Approved? --> [Yes: IMP Issued] --> [No: Sent Back for Corrections] --> End

Process Steps:

1. Maker: Enters HS codes, invoice numbers, and transport details for the import permit.
2. Checker: Reviews and approves IMP requests, ensuring compliance with trade policies.

5. Export Permit (EXP) Processing Workflow

Actors: Maker, Checker, Supervisor

Description: Processes export permits and links them to export repatriations or LCs.

Start --> Maker Inputs Export Details --> Link to LC/Repatriation --> Submit
for Review --> Checker Verifies -->
Approved? --> [Yes: Export Permit Issued] --> [No: Sent Back for Corrections]
--> End

Process Steps:

1. Maker: Records goods description, payment terms, and destination for export permits.
 2. Checker: Validates data against export regulations and client agreements.

6. Inward Bill Collection (IBC) Workflow

Actors: Maker, Checker, Supervisor

Description: Tracks inward bills by linking them to LCs or IMPs.

Start --> Maker Records Document Arrival --> Link to LC/IMP --> Submit for
Review --> Checker Verifies -->
Status Updated --> End

Process Steps:

1. Maker: Records remitting bank details and links IBC to associated transactions.
2. Checker: Verifies the data and updates the payment status (Paid/Unpaid).

7. LC Settlement Workflow

Actors: Maker, Checker, Supervisor, Inspector

Description: Tracks LC settlements, including shipment and payment statuses.

Start --> Maker Records Settlement Data --> Submit for Review --> Checker
Verifies -->
Approved? --> [Yes: Settlement Recorded] --> [No: Sent Back for Corrections]
--> End

Process Steps:

1. Maker: Records settlement details, including document reference and shipment status.
2. Checker: Validates settlement data and ensures all conditions are met.
3. Inspector: Periodically audits settlements for compliance.

8. Foreign Currency (FCY) Utilization Workflow

Actors: Maker, Checker, Supervisor, Inspector

Description: Tracks and validates foreign currency utilization for trade finance requests.

Start --> Maker Records FCY Utilization --> Link to LC/PO/IMP --> Submit for
Review --> Checker Verifies -->
Approved? --> [Yes: FCY Updated] --> [No: Sent Back for Corrections] --> End

Process Steps:
 1. Maker: Enters FCY utilization data and links it to related trade instruments.
2. Checker: Ensures FX usage complies with regulations and policies.

9. Export Repatriation Workflow

Actors: Maker, Checker, Supervisor, Inspector

Description: Tracks export proceeds and links them to export permits or LC repatriations.

Start --> Maker Records Export Proceeds --> Link to Export Permit/LC -->
Submit for Review --> Checker Verifies -->
Approved? --> [Yes: Repatriation Recorded] --> [No: Sent Back for Corrections]
--> End

Process Steps:

1. Maker: Records ticket references and proceeds linked to export permits.

2. Checker: Verifies and approves repatriation records.

Workflow Integration and Monitoring

1. Dashboards:
o Supervisors have access to real-time dashboards showing workflow progress,
pending approvals, and escalations.
o Inspectors can view audit logs and compliance statuses.
2. Escalation Rules:
o Requests pending beyond predefined SLAs are automatically escalated to
Supervisors.
3. Notifications:
o Role-based email/SMS notifications for approval requests, escalations, or
rejections.
4. Audit Trail:
o Every workflow step is logged for traceability.

Visual Representation

If needed, I can generate visual BPMN diagrams for these workflows to enhance clarity. Let me
know if you'd like to see them!

Detailed Business Process Model (BPM) for Trade Finance System

The Trade Finance Management System for the bank is a complex environment, and the
business processes must be clearly defined to ensure seamless operations. Below is an in-depth
and comprehensive Business Process Model using BPMN that covers the core workflows in the
system, specifying the roles, interactions, tasks, and decision points involved in each process.

1. Document Registration Workflow

Actors:

 Maker: Data entry, document registration, and unique ID generation.

 Checker: Validation of the registration details, approval/rejection of documents.
 Supervisor: Oversees document registration, handles exceptions and escalations.
 Inspector: Audits document registrations for compliance with policies.
 Viewer: Accesses registered documents for information purposes.

Description:
This process involves collecting applicant details such as Name, TIN, License Number, etc.,
generating unique transaction IDs for each document, and verifying their correctness.

Steps:

1. Maker:
o Inputs the applicant details and uploads supporting documents (e.g., company
registration, identification, license).
o Submits the document for review.
2. Checker:
o Verifies the document and applicant details for correctness and completeness.
o Checks for missing documents or any inconsistencies.
o Approves or rejects the registration request.
3. Supervisor:
o Reviews escalated or flagged documents.
o Resolves issues or discrepancies raised by the Checker.
4. Inspector:
o Periodically audits document registrations to ensure compliance with regulatory
standards.
5. Viewer:
o Views the registered documents and details as per access permissions (read-only).

Decision Points:

 If the document is validated correctly, it is registered and assigned a unique ID.

 If rejected, it is sent back for correction, and the Maker is notified.

Workflow Diagram:
Start --> Maker Inputs Applicant Data --> Submit for Review --> Checker
Reviews and Verifies --> [Approved?] --> [Yes: Document Registered with Unique
ID] --> [No: Return for Correction] --> End

2. Purchase Order (PO) Processing Workflow

Actors:

 Maker: Data entry for PO details, link PO to relevant documents.

 Checker: Validation of PO details, ensuring compliance with trade regulations.
 Supervisor: Handling escalated PO requests, especially high-value or complex cases.
 Viewer: Views PO details for information.

Description:
This process involves entering and validating purchase order details, such as supplier
information, invoice details, goods description, and terms of delivery. The PO is then linked to
Letters of Credit (LCs) or Import Permits (IMPs).

Steps:

1. Maker:
o Enters PO details (Supplier, Invoice, Goods Description, Delivery Terms).
o Links PO to related LC or IMP if necessary.
o Submits PO for review and approval.
2. Checker:
o Verifies the PO details, checking compliance with the bank's policies, including
the relationship with LCs or IMPs.
o Approves or rejects the PO based on the validation.
3. Supervisor:
o Handles any escalated issues or complex POs, particularly those requiring manual
intervention or high-value transactions.
4. Viewer:
o Views the processed PO details and its associated statuses.

Decision Points:

 If the PO passes the validation checks, it is approved and linked to the relevant
documents.
 If rejected, it is sent back to the Maker for correction.

Workflow Diagram:

Start --> Maker Enters PO Details --> Link to LC/IMP --> Submit for Review -->
Checker Verifies PO Details --> [Approved?] --> [Yes: PO Processed] --> [No:
Return for Correction] --> End
3. Letter of Credit (LC) Opening Workflow

Actors:

 Maker: Inputs LC details, links to PO or IMP, and submits for review.

 Checker: Verifies LC details, ensuring they align with bank policies and trade
regulations.
 Supervisor: Reviews escalated cases for high-value transactions.
 Inspector: Audits the opening of LCs to ensure compliance with regulatory standards.
 Viewer: Views LC details and associated trade instruments.

Description:
This workflow ensures that LCs are opened according to client requirements, and all details are
validated before issuance.

Steps:

1. Maker:
o Inputs LC details such as terms of payment, supplier details, validity period, and
the relevant trade instrument (PO or IMP).
o Submits the LC opening request for review.
2. Checker:
o Reviews the LC details and validates them against the trade instrument (PO or
IMP).
o Verifies that the terms align with the client’s request and regulatory compliance.
3. Supervisor:
o Handles escalated or high-value LC opening requests.
o Provides final approval for exceptional cases.
4. Inspector:
o Conducts periodic audits to verify that the opening of LCs adheres to the bank's
policies and regulatory requirements.

Decision Points:

 If the LC details pass validation, the LC is issued.

 If there are discrepancies, the request is returned to the Maker for corrections.

Workflow Diagram:

Start --> Maker Records LC Details --> Link to PO/IMP --> Submit for Review --
> Checker Verifies LC Details --> [Approved?] --> [Yes: LC Issued] --> [No:
Return for Correction] --> End

4. Import Permit (IMP) Processing Workflow

Actors:

 Maker: Inputs IMP details, links it to LC/PO.

 Checker: Validates the IMP data and compliance.
 Supervisor: Handles high-value or complex IMP cases.
 Viewer: Views IMP details for reference.

Description:
This workflow manages the processing of import permits (IMP), linking them to LCs or POs,
and validating the relevant import data.

Steps:

1. Maker:
o Inputs import permit details such as HS Code, invoice, and transport information.
o Links the IMP to the relevant PO or LC.
o Submits the IMP request for validation.
2. Checker:
o Verifies the correctness of the IMP details against the bank's regulatory
requirements.
o Checks if the permit aligns with the terms of the related PO or LC.
3. Supervisor:
o Reviews escalated or high-value IMP requests.
o Provides final approval for special cases.

Decision Points:

 If the IMP passes validation, it is processed and issued.

 If rejected, the IMP is sent back for corrections.

Workflow Diagram:

Start --> Maker Inputs IMP Details --> Link to PO/LC --> Submit for Review -->
Checker Verifies IMP Details --> [Approved?] --> [Yes: IMP Issued] --> [No:
Return for Correction] --> End

5. Inward Bill Collection (IBC) Workflow

Actors:

 Maker: Records IBC details, links to related LCs or IMPs.

 Checker: Verifies IBC data and updates payment status.
 Supervisor: Monitors the IBC process, handles exceptions.
 Viewer: Views IBC data for informational purposes.
Description:
The IBC workflow tracks the arrival of bills and the payment process. It links incoming bills to
LCs or IMPs and tracks payment status.

Steps:

1. Maker:
o Records document arrival and invoice details.
o Links IBC to the relevant LC or IMP.
o Submits IBC data for review.
2. Checker:
o Verifies the accuracy of the IBC details, ensuring compliance with contractual
agreements.
o Updates the payment status (Paid/Unpaid) for the IBC.
3. Supervisor:
o Monitors the IBC process, resolving any exceptions or discrepancies.

Decision Points:

 If the IBC data is accurate, the status is updated accordingly.

 If discrepancies are found, the IBC is returned for correction.

Workflow Diagram:

Start --> Maker Records IBC Details --> Link to LC/IMP --> Submit for Review
--> Checker Verifies IBC Details --> [Payment Status Updated?] --> [Yes: IBC
Processed] --> [No: Return for Correction] --> End

6. Letter of Credit (LC) Settlement Workflow

Actors:

 Maker: Records settlement details, links to related documents.

 Checker: Verifies settlement data.
 Supervisor: Monitors high-value settlements.
 Inspector: Conducts audits to ensure compliance.

Description:
This process tracks LC settlements, ensuring payment and shipment statuses are correctly
recorded and managed.

Steps:

1. Maker:
o Records LC settlement details, including shipment status and payment status.
 oSubmits settlement data for validation.
2. Checker:
o Verifies the settlement details, ensuring accuracy and compliance with the
original LC terms.
o Updates the settlement status.
3. Supervisor:
o Oversees LC settlements, especially for high-value transactions.

Decision Points:

 If the settlement data is validated, the settlement is completed and recorded.

 If issues are identified, the settlement is returned for correction.

Workflow Diagram:

Start --> Maker Records Settlement Data --> Submit for Review --> Checker
Verifies Settlement Data --> [Approved?] --> [Yes: Settlement Recorded] -->
[No: Return for Correction] --> End

Key BPMN Concepts Used:

 Start/End Events: Denote the beginning and conclusion of processes.

 Tasks: Represent actions performed by the actors.
 Gateways (Decision Points): Represent conditions that direct the flow based on a
decision.
 Sequence Flows: Indicate the order of process steps.
 Subprocesses: Represent complex tasks that can be broken down into smaller processes.

Conclusion

The Business Process Model described here ensures that all critical processes in the Trade
Finance Management System are handled with transparency, accuracy, and compliance. Each
workflow is carefully designed to involve the right actors at the appropriate stages, ensuring
efficient operations, minimizing risks, and enabling smooth interactions within the system. The
detailed BPMN diagrams ensure clear documentation of process flow, and the comprehensive
nature of this model guarantees that all aspects of trade finance operations are effectively
captured.

In the context of the Trade Finance Department, the roles of Maker, Checker, Supervisor,
Inspector, and Viewer are assigned as follows, with responsibilities and duties allocated based
on the nature of trade finance operations.
1. Document Registration Workflow

 Maker:
o Responsible for entering applicant details (Name, TIN, License Number, etc.),
uploading supporting documents, and generating unique transaction IDs (e.g., for
PO, LC, IMP, EXP).
o Submits the registration request to the Checker for validation.
 Checker:
o Validates the accuracy of the documents entered by the Maker and checks for any
missing or inconsistent data.
o Approves or rejects the document registration request.
 Supervisor:
o Reviews any escalated or exceptional document registrations, especially for high-
value clients or complex cases.
o Resolves any issues or discrepancies flagged by the Checker.
 Inspector:
o Periodically audits document registration for compliance with regulatory policies
and internal standards.
o Conducts audits for quality assurance and ensures regulatory compliance in
documentation.
 Viewer:
o Views registered documents and associated details without the ability to modify
them.
o Primarily for internal staff who need to reference documents for reporting or other
purposes.

2. Purchase Order (PO) Processing Workflow

 Maker:
o Responsible for inputting PO details such as supplier information, invoice data,
goods description, and delivery terms.
o Links the PO to related documents like LC or IMP (if applicable).
o Submits the PO for review and validation by the Checker.
 Checker:
o Validates the PO data entered by the Maker, ensuring all details are correct and
comply with trade finance policies and regulatory requirements.
o Approves or rejects the PO based on compliance and accuracy.
 Supervisor:
o Oversees the entire PO processing workflow, particularly for high-value
transactions or cases that need special attention.
o Handles escalations and ensures that the PO approval process aligns with trade
finance protocols.
 Inspector:
 o Conducts audits on processed POs to ensure compliance with internal policies and
regulatory standards.
o Reviews POs to identify any irregularities or issues.
 Viewer:
o Views PO details for informational purposes only, such as for internal reporting
or audits.

3. Letter of Credit (LC) Opening Workflow

 Maker:
o Inputs LC details, including payment terms, supplier information, and validity
period.
o Links the LC to relevant documents such as POs or IMPs.
o Submits the LC opening request to the Checker for review and approval.
 Checker:
o Validates LC details to ensure they align with the terms of the related PO or IMP.
o Verifies compliance with trade regulations and approves/rejects the LC opening
request.
 Supervisor:
o Reviews escalated LC opening cases, especially those involving high-value
transactions or complex terms.
o Ensures that the overall LC opening process is compliant with bank policies.
 Inspector:
o Periodically audits the LC opening process to ensure compliance with internal
procedures and regulatory requirements.
o Conducts audits to verify the accuracy and legality of the opened LCs.
 Viewer:
o Views LC details and associated transactions, mainly for internal use or reporting.

4. Import Permit (IMP) Processing Workflow

 Maker:
o Inputs import permit details (HS Codes, transport information, invoice data, etc.)
and links it to relevant PO or LC.
o Submits the IMP request for verification by the Checker.
 Checker:
o Validates IMP details to ensure they align with trade regulations, including
checking the connection to the PO or LC.
o Approves or rejects the IMP request based on compliance with regulations.
 Supervisor:
o Monitors the IMP processing workflow and handles escalations for any high-
value or complex cases.
 o Ensures overall compliance with trade finance regulations and oversees the
resolution of any issues that may arise.
 Inspector:
o Audits IMP processing to ensure compliance with regulatory standards,
conducting regular checks and reviews.
 Viewer:
o Views processed IMPs and their related trade documents for informational
purposes.

5. Inward Bill Collection (IBC) Management Workflow

 Maker:
o Records the arrival of inward bills, including invoice and remitting bank details,
and links IBC to relevant LC or IMP.
o Submits the IBC data for review by the Checker.
 Checker:
o Verifies the IBC details, including validating the payment status (paid/unpaid).
o Approves or rejects the IBC based on accuracy and completeness of data.
 Supervisor:
o Monitors the IBC processing workflow, particularly high-value or complex
transactions.
o Resolves any escalations or discrepancies flagged during processing.
 Inspector:
o Audits inward bill collections to ensure compliance with internal trade finance
policies and regulatory requirements.
 Viewer:
o Views IBC details for informational purposes only.

6. Letter of Credit (LC) Settlement Workflow

 Maker:
o Records LC settlement details, including shipment and payment statuses.
o Submits the settlement data for validation by the Checker.
 Checker:
o Reviews and validates the LC settlement details.
o Ensures the settlement is in accordance with the terms of the original LC and
updates the settlement status.
 Supervisor:
o Oversees LC settlements, especially high-value settlements, and monitors
compliance with internal policies.
o Provides final approvals for any exceptions or special cases.
 Inspector:
 o Conducts audits of LC settlements to ensure adherence to trade finance policies
and compliance with regulations.
 Viewer:
o Views the LC settlement details for reporting and informational purposes.

7. Foreign Currency (FCY) Utilization Workflow

 Maker:
o Inputs and tracks foreign currency (FCY) utilization against approved amounts,
linking FCY usage to PO, LC, or IMP.
o Submits FCY data for review by the Checker.
 Checker:
o Validates FCY utilization data to ensure compliance with foreign exchange
regulations and trade agreements.
o Approves or rejects FCY usage requests.
 Supervisor:
o Monitors FCY utilization for compliance and ensures regulatory adherence in
currency transactions.
o Reviews high-value or complex FCY transactions.
 Inspector:
o Audits FCY utilization transactions to ensure accurate reporting and compliance
with internal and external policies.
 Viewer:
o Views FCY utilization data for reporting, analysis, or audit purposes.

8. Export Repatriation Workflow

 Maker:
o Records export repatriation data and links it to relevant export permits or LC
repatriation documents.
o Submits the data for review by the Checker.
 Checker:
o Validates export repatriation data, ensuring that the details align with the original
trade agreements and export regulations.
o Approves or rejects the repatriation request.
 Supervisor:
o Monitors export repatriation processes and ensures that all transactions comply
with trade finance guidelines and regulatory requirements.
o Reviews complex or high-value export repatriation cases.
 Inspector:
o Audits export repatriation records to ensure compliance with trade regulations,
internal policies, and international trade agreements.
  Viewer:
o Views export repatriation records and related transactions for informational
purposes.

Role Overview Summary

Role Responsibilities
Data entry, initial submission of requests for document registration, PO, LC, IMP,
Maker Export, IBC, and FCY utilization. Links documents, initiates workflows, and
submits them for validation.
Validates submitted data for correctness, compliance, and completeness. Approves
Checker
or rejects requests based on thorough review and internal policy.
Monitors overall workflow processes, handles escalated cases, especially high-value
Supervisor transactions, ensures compliance, and resolves discrepancies or exceptions flagged
by Checkers.
Audits processed data to ensure regulatory and internal policy compliance. Regular
Inspector audits of document registration, LC opening, settlement, export repatriation, and
FCY usage.
Views information without modifying it. Used for internal reporting, audits, or
Viewer
monitoring purposes. Does not have permissions to approve or reject requests.

This structure ensures that responsibilities are clearly defined and that checks and balances are in
place for each step of the trade finance process.

### Entity-Relationship Diagram (ERD) for Enhanced User Interface System

The following ERD represents the entities and relationships for the enhanced
user interface system that manages various functions related to document
registration, purchase orders, letters of credit, import/export permits, and
more.

#### **Entities and Attributes**

1. **User**
- **UserID** (Primary Key)
- Username
- Password
- Email
- Role (Admin, User, Manager)

2. **Document**
- **DocumentID** (Primary Key)
- DocumentType (PO, LC, IMP, EXP, IBC)
 - CreatedDate
- Status (Draft, Approved, Rejected)
- UserID (Foreign Key)

3. **PurchaseOrder**
- **PurchaseOrderID** (Primary Key)
- OrderNumber (Format: DSB/DMB/PO-00000/24)
- DocumentID (Foreign Key)
- SupplierID (Foreign Key)
- OrderDate
- TotalAmount
- Status (Pending, Completed)

4. **LetterOfCredit**
- **LetterOfCreditID** (Primary Key)
- LCNumber (Format: DSB/LC/0001/24)
- DocumentID (Foreign Key)
- Amount
- OpeningDate
- Status (Open, Settled)

5. **ImportPermit**
- **ImportPermitID** (Primary Key)
- PermitNumber (Format: DSB/DMB/01-00000/24)
- DocumentID (Foreign Key)
- ApprovalDate
- Status (Pending, Approved)

6. **ExportPermit**
- **ExportPermitID** (Primary Key)
- PermitNumber (Format: DSB/DMB/02-00000/24)
- DocumentID (Foreign Key)
- ApprovalDate
- Status (Pending, Approved)

7. **InwardBillCollection**
- **IBCID** (Primary Key)
- DocumentID (Foreign Key)
- Amount
- PaymentStatus (Paid, Unpaid)
- CollectionDate

8. **ForeignCurrencyUtilization**
- **FCYID** (Primary Key)
- DocumentID (Foreign Key)
- AmountUtilized
 - CurrencyType
- UtilizationDate

9. **ExportRepatriation**
- **RepatriationID** (Primary Key)
- DocumentID (Foreign Key)
- AmountRepatriated
- RepatriationDate

10. **AuditLog**
- **LogID** (Primary Key)
- Action
- Timestamp
- UserID (Foreign Key)
- DocumentID (Foreign Key)

#### **Relationships**

- **User to Document**: One-to-Many

- A user can create multiple documents, but each document is created by
one user.

- **Document to PurchaseOrder**: One-to-One

- Each document can be associated with one purchase order.

- **Document to LetterOfCredit**: One-to-One

- Each document can be associated with one letter of credit.

- **Document to ImportPermit**: One-to-One

- Each document can be associated with one import permit.

- **Document to ExportPermit**: One-to-One

- Each document can be associated with one export permit.

- **Document to InwardBillCollection**: One-to-One

- Each document can be associated with one inward bill collection.

- **Document to ForeignCurrencyUtilization**: One-to-One

- Each document can be associated with one foreign currency utilization
record.

- **Document to ExportRepatriation**: One-to-One

- Each document can be associated with one export repatriation record.

- **User to AuditLog**: One-to-Many

 - A user can perform multiple actions that are logged, but each log entry is
associated with one user.

- **Document to AuditLog**: One-to-Many

- A document can have multiple actions logged, but each log entry is
associated with one document.

#### **ERD Diagram Representation**

```plaintext
+----------------+ +----------------+ +----------------+
| User | | Document | | PurchaseOrder |
|----------------| |----------------| |-----------------|
| UserID (PK) |<-------1| DocumentID (PK)|<-------1 | PurchaseOrderID (PK)|
| Username | | DocumentType | | OrderNumber |
| Password | | CreatedDate | | DocumentID (FK) |
| Email | | Status | | SupplierID (FK) |
| Role | | UserID (FK) | | OrderDate |
+----------------+ +----------------+ | TotalAmount |
| Status |
+-----------------+
|
|1
|
|1
+----------------+
| LetterOfCredit |
|-----------------|
| LCID (PK) |
| LCNumber |
| DocumentID (FK)|
| Amount |
| OpeningDate |
| Status |
+----------------+
|
|1
|
|1
+----------------+
| ImportPermit |
|-----------------|
| ImportPermitID (PK)|
| PermitNumber |
| DocumentID (FK) |
| ApprovalDate |
| Status |
+----------------+
|
|1
|
|1
+----------------+
| ExportPermit |
|-----------------|
| ExportPermitID (PK)|
| PermitNumber |
| DocumentID (FK) |
| ApprovalDate |
| Status |
+----------------+
|
|1
|
|1
+----------------+
| InwardBillCollection |
|-----------------|
| IBCID (PK) |
| DocumentID (FK) |
| Amount |
| PaymentStatus |
| CollectionDate |
+----------------+
|
|1
|
|1
+----------------+
| ForeignCurrencyUtilization |
|-----------------|
| FCYID (PK) |
| DocumentID (FK) |
| AmountUtilized |
| CurrencyType |
| UtilizationDate |
+----------------+
|
|1
|
|1
+----------------+
 | ExportRepatriation |
|-----------------|
| RepatriationID (PK)|
| DocumentID (FK) |
| AmountRepatriated|
| RepatriationDate |
+----------------+
|
|1
|
|M
+----------------+
| AuditLog |
|-----------------|
| LogID (PK) |
| Action |
| Timestamp |
| UserID (FK) |
| DocumentID (FK) |
+------------------+
```

### Conclusion

This ERD provides a structured overview of the entities, their attributes, and
the relationships between them for the enhanced user interface system. It
captures the essential functions related to document registration, purchase
orders, letters of credit, import/export permits, and more, ensuring a
comprehensive representation of the system's data architecture.