Custom Tally Journal Voucher

Tally UDF & TDL Requirements I. Credit Dispatch Journal Voucher & Cash Dispatch Journal Voucher Hi, I need TDL-based customization in Tally Prime for creating structured Journal Vouchers for dispatch entries. Please review the requirement below and confirm feasibility, timeline, and cost. 1. VOUCHER TYPES TO BE CREATED Create 2 custom Journal Voucher Types: 1. Credit Dispatch Journal Voucher 2. Cash Dispatch Journal Voucher 2. COMMON FIELDS (FOR BOTH VOUCHERS) Each voucher should have structured input fields (not narration): Mandatory Fields: a. DCPI No. • Type: Numeric • Length: Exactly 9 digits • Validation: Only numbers allowed b. DCPI Date • Format: DD/MM/YYYY c. GST Invoice No. • Type: Numeric • Length: Exactly 13 characters d. Customer Name • Selection from existing ledger (Sundry Debtors) e. Grade (Dropdown) Options: • PP • PE • PVC • PP SEZ f. Quantity (MT) • Numeric • Up to 3 decimal places • Unit: Metric Tons g. Payment Terms • Auto-filled (non-editable based on voucher type): Voucher Type Payment Term Credit Dispatch E Z010 Cash Dispatch E ZCash h. Total Amount Payable • Amount field • Currency: ₹ • 2 decimal places 3. ACCOUNTING ENTRIES (AUTO POSTING) Based on the above inputs: ✅ For BOTH Cash & Credit Dispatch: Dr Customer Ledger Cr RIL Sales Ledger Notes: • Customer ledger = selected in field (d) • Credit ledger = fixed as “RIL Sales” • Amount = Total Amount Payable 4. DISPLAY REQUIREMENT (VERY IMPORTANT) All entered fields must be visible in Journal Voucher lines, including: • DCPI No • DCPI Date • GST Invoice No • Customer Name • Grade • Quantity • Payment Terms • Amount These should appear in column format within voucher entry and display mode (not only in narration). 5. VALIDATIONS REQUIRED • DCPI No must be exactly 9 digits • GST Invoice No must be 13 characters • Quantity must allow only numbers (3 decimals) • Amount must be > 0 • Customer must be selected 6. USER EXPERIENCE REQUIREMENTS • Clean, column-style entry (similar to structured grid) • Fast data entry (minimal manual typing) • Dropdown selection for Grade • Auto-fill Payment Terms • Error message if validation fails 7. DELIVERABLES • Working TDL file • Installation support • Testing with sample entries • Minor revisions if needed 8. PLEASE CONFIRM • Whether this can be done using UDF + custom voucher screen • Timeline for delivery • Fixed cost • Support after implementation This is a structured voucher customization requirement, not standard journal usage. Looking for someone experienced in TDL development and voucher customization. Please respond with details. II. RIL Discounts Journal Voucher 1. VOUCHER TYPE Create a custom voucher: “RIL Discount Journal Voucher” 2. HEADER FIELDS (TOP SECTION) The voucher should capture the following structured inputs: 1. Date • Format: DD/MM/YYYY • This date should apply to all accounting entries 2. Bank Received In • Dropdown: Select from Bank / CFA Ledgers 3. Amount Received • Numeric (₹) • 2 decimal places • Total amount received from RIL 4. Type of Discount • Dropdown: Select from predefined Discount Ledgers, such as: o Quantity Discounts o Performance Discounts o Trade Discounts o Regional Discounts o Locational Discounts o Quarterly Performance Discounts o Yearly Performance Discount o Rate Difference o Shortage Claims without GST 5. Period (Dropdown Selection) Options: • Month + Year (e.g., Apr 2026) • Quarter 1 (APR–JUN) + Year • Quarter 2 (JUL–SEP) + Year • Quarter 3 (OCT–DEC) + Year • Quarter 4 (JAN–MAR) + Year • Full Year (e.g., 2026–27) 3. GRID ENTRY (EXCEL-LIKE TABLE) Below the header, create a repeatable table (grid): Columns: 1. Customer Name o Dropdown from Customer Ledgers (Sundry Debtors) 2. Discount Amount o Numeric (₹) o 2 decimal places Behaviour: • User can add multiple rows • Press Enter → new row (Excel-like experience) • If customer not selected → allow moving to next field • Blank rows should be ignored 4. VALIDATION (CRITICAL) • Sum of all Customer Discount Amounts = Amount Received • If mismatch → Block saving with error message 5. ACCOUNTING ENTRIES (AUTO POSTING) All entries should be created automatically in a single voucher. ✅ Entry 1: Receipt from RIL Dr Bank / CFA Cr RIL Discounts Ledger • Amount = Total Amount Received ✅ Entry 2: Transfer to Discount Type Dr RIL Discounts Ledger Cr Selected Discount Ledger ✅ Entry 3: Customer-wise Allocation For each row in grid: Dr Selected Discount Ledger Cr Customer Ledger 6. DISPLAY REQUIREMENT All fields must be visible in voucher display: • Date • Bank • Amount • Discount Type • Period • Customer-wise split Grid data should be clearly visible in voucher drill-down 7. LEDGER REQUIREMENTS Pre-create: • RIL Discounts (Control Ledger) • Discount Type Ledgers (Quantity, Trade, etc.) • Customer Ledgers 8. USER EXPERIENCE • Clean layout (header + grid) • Minimal typing • Dropdown-based selection • Fast entry (optimized for bulk allocation) 9. DELIVERABLES • Fully working TDL • Installation support • Testing with sample data • Minor fixes post-delivery 10. PLEASE CONFIRM • Whether grid (repeat line) implementation is feasible • Validation logic approach • Timeline • Fixed cost • Support scope 11. LEDGER DISPLAY ENHANCEMENT (CUSTOMER VIEW) For all RIL Discount Journal Vouchers, the following additional fields must be visible in: Customer Ledger → Voucher Display / Ledger Drill Down Required Fields to Display: Along with existing: • Date • Amount Also display: 1. Discount Type o (e.g., Quantity, Trade, Performance, etc.) 2. Period o (e.g., Apr 2026, Q1 2026, FY 2026–27) Display Format Requirement: These fields should appear clearly in column or adjacent format, such as: Date Particulars Discount Type Period Amount ------------------------------------------------------------------ 01-04-26 RIL Discount Quantity Apr 2026 50,000 01-04-26 RIL Discount Trade Q1 2026 30,000 Technical Requirement: • Discount Type and Period should be stored as UDF fields at voucher level • These fields must be: o Accessible in voucher o Visible in ledger reports o Available for future reporting / Excel export Scope: • Only applicable for: “RIL Discount Journal Voucher” • Should not affect other voucher types Expected Outcome: • User can directly see: o Which discount has been passed. o For which period • Without opening voucher details Please confirm: • How these fields will be attached (Voucher UDF or Ledger Entry UDF) • Whether they can be shown in standard ledger view or require custom report This is a bulk allocation system, not standard journal entry.