Feature Requests

Create Packing List along with invoice. Packing List - Shipping by sea/air, number of boxes, dimensions and weight. For reference: incodocs.com

No Complete Video Training Series There is no sufficiently complete, structured video series explaining how the Refrens Accounting System works from beginning to end. Individual explanations or isolated demonstrations are not enough for users trying to manage actual business accounts. Expected result: Provide a complete training series covering: Company setup and financial year configuration. Chart of accounts and ledger creation. Sales invoices and purchase bills. Receipts and payments. Advance payments and TDS. Journal entries and invoice settlement. Credit notes and debit notes. Discounts and mutual account adjustments. Employee expenses and salary payable. Bank reconciliation and AI statement imports. GST accounting and reports. Opening balances, closing balances, and year-end procedures. Each video should use practical examples and explain the complete accounting workflow.

Uploading a bank statement should do more than import transaction data. It should help create the appropriate accounting entries automatically. Expected result: Recognize customers, vendors, employees, and other parties. Suggest the appropriate ledger and voucher type. Identify transfers, receipts, payments, bank charges, and other common transactions. Detect possible duplicate transactions. Ask the user for clarification when a transaction cannot be confidently classified. Allow review and approval before posting entries to the books.

The AI bank statement upload feature should be capable of handling statements downloaded from different banks without requiring users to convert them manually into a particular format. Expected result: Allow users to upload common bank statement formats and automatically identify transaction dates, descriptions, debit amounts, credit amounts, and balances.

The document scanning feature currently appears limited to Invoice and Expenditure sections. Purchase documents are not adequately supported in the same workflow. Expected result: Extend document scanning to purchase bills and supplier invoices, extracting the vendor, invoice number, date, taxable amount, GST, total amount, and relevant ledger details.

No Proper Salary Payable Workflow We need to record monthly salary expenses at the end of the month without making a bank entry at that time. The required accounting workflow is: At month-end: Debit: Salary Expense / Employee Cost Credit: Salary Payable When salary is actually paid: Debit: Salary Payable Credit: Bank

Employee Payments Are Incorrectly Handled Through Banking Employees have been created in the Employee section and assigned to the Employee Cost/Salaries Account. However, employee payment workflows appear to be linked to banking transactions, causing problems when creating receipts and payouts. Expected result: Employee salary accounting should be separate from bank transactions until the actual salary payment is recorded.

Financial year selection and control during accounting entries and invoice creation are not sufficiently clear. This can lead to transactions being entered or billed in the wrong financial year. Expected result: Provide clear financial year controls, transaction-date validation, and proper separation of opening balances, current-year transactions, and previous-year records.

When the same customer or vendor has been created more than once, there is no sufficiently clear process to merge the accounts without losing transaction history or creating ledger discrepancies. Expected result: Provide a safe account-merging facility that consolidates ledger balances and preserves all historical transactions and references.

Adjusting credit notes and debit notes against existing invoices or outstanding balances is not straightforward. Expected result: Allow users to select the relevant invoice, adjust the credit/debit note, view the remaining balance, and maintain a complete adjustment history.

When a discount is agreed upon after an invoice has already been issued, it is unclear how to record the discount and adjust the outstanding balance correctly. Expected result: Provide a clear workflow using the appropriate discount entry or credit note, with automatic adjustment of the invoice balance and correct tax treatment.

Transactions displayed in the ledger cannot be opened directly to view their underlying vouchers or source entries. Expected result: Each ledger transaction should be clickable and open its original invoice, receipt, payment, journal voucher, credit note, or debit note.

A single customer receipt may cover several invoices, advance payments, TDS deductions, and other adjustments. Managing these through separate entries is complicated. Expected result: Provide a consolidated receipt allocation screen that supports: Multiple invoices against one receipt. Partial and advance payments. TDS deductions. Invoice-wise allocation of the net payment. Automatic calculation of the remaining outstanding balance.

Sometimes, the payment has already been credited to the bank account, but it has not been correctly allocated against the invoice. There is no clear workflow to adjust the existing receipt without recording the bank transaction again. Expected result: Allow users to allocate an existing receipt to the correct customer, invoice, or outstanding balance without duplicating the bank entry.

Unable to Settle Invoices When Both Companies Bill Each Other In business transactions, a customer may raise a bill against us while we also raise an invoice against the same customer. There is no clear and convenient workflow to adjust the mutual balances and mark the invoices as settled. Expected result: Provide a proper invoice-to-bill adjustment or set-off facility, with the necessary accounting entries and audit trail.