How It Works
Outward Bank Payments - User Guide
This documentation explains how to create, manage, and track outward bank payments in the Lnder Banking system. It includes step-by-step instructions, workflow details, and role-based actions.
How To Use the Outward Bank Payment System
Step 1: Accessing the Outward Bank Payment Form
Navigate to the Outward Bank Payment module under Lnder Banking to create a new payment entry.
Step 2: Enter Basic Payment Information
- Company: Select your company.
- Company Bank Account: Choose the account from which payment will be made (mandatory).
- Transaction Type: Select IMPS, RTGS, NEFT, or Intra Bank Transfer.
- Payment Type: Choose Regular or Ad-Hoc.
Step 3: Specify Party Details
- Party Type: Employee, Supplier, Customer, or Ad-Hoc Party.
- Party: Select existing or enter details for Ad-Hoc Party.
- Party Bank Account: Select or add new bank details.
- Has PAN: Auto-filled if available.
- Party Name: Auto-filled from selection.
Step 4: Enter Payment Amount and Additional Info
- Amount: Enter a non-negative value.
- Remarks: Add notes if needed.
- Expense Level (Ad-Hoc only): Vehicle, Office, or General.
- Vehicle/Office (conditional): Select relevant details if applicable.
Step 5: References and Tracking
- References: Attach documents (Invoices, Expense Claims, POs).
- UTR Number: Auto-generated after processing.
- Processed & Completion Dates: Tracked by the system.
- Status: Shows payment state (Pending, Approved, Completed, etc.).
Step 6: Wallet Recharge Details (If Applicable)
- Recharge Type: Fastag, BPCL, IOCL, JIO BP, etc.
- Wallet ID & Balance: Managed by the system.
Step 7: Submitting and Processing
- Review entered information.
- Submit for approval.
- Payment progresses through workflow states (Pending → Approved → Completed).
- Authorized users can approve, reject, or reverse payments.
- If OTP is enabled, confirm via WhatsApp or Email OTP.
How It Works
- Create payments for Adhoc Party or Regular Party.
- Adhoc Party requires new/existing Party & Bank Account details.
- Regular Party links to existing party and stored bank details.
- Mandatory fields: company bank account, amount, transaction type, remarks.
- All payments are stored as Payment Entry records.
- Workflow manages approvals and processing securely.
- Bulk payments can be processed together with OTP confirmation.
- Bank account verification helps prevent failed transactions.
Alerts and Validations
- For Adhoc Parties, if you select No on the existing party prompt, you must verify bank account details. - Errors trigger alerts to guide corrections. - Mandatory fields and references are validated to avoid duplicate or incorrect payments.
Workflow States
| State | Description |
|---|---|
| Pending | Payment created, awaiting approval. |
| Approved | Approved by authorized user. |
| Transaction Initiated | Sent to bank for processing. |
| Transaction Pending | Bank is processing payment. |
| Transaction Completed | Successfully credited to beneficiary. |
| Transaction Failed | Processing error caused failure. |
| Rejected | Rejected by approver. |
| Cancelled | Cancelled before processing. |
| Transaction Reversed | Completed payment reversed successfully. |
Role-Based Actions
- Accounts Manager: Approve, Reject, Cancel, Reverse payments; initiate processing.
- Bank Maker: Create & submit payments.
- Bank Checker: Review, approve, or reject payments.
- Fleet Manager/User: View payment status & reports.