Docs
ERP Crystal
MFG
Sales
Transactions
Sales Rejection

Sales Rejection

Sales Rejection Module - User Guide

1. Introduction 📝

The Sales Rejection module (also referred to as Sales Return or SRN) is designed to manage the process of receiving goods back from customers. Whether due to quality issues, incorrect shipments, or warranty claims, this module ensures that every return is documented, inspected by QA, and correctly accounted for in both inventory and financial records.

ℹī¸

In the overall business flow:

  1. It handles customer returns after a Sales Invoice or Challan has been issued.
  2. It integrates with Quality Assurance (QA) to validate the reason for return.
  3. It tracks Warranty Status (In-Warranty vs. Out-of-Warranty) for repair processing.

Typically, this module is used by Warehouse Personnel, QA Teams, and Sales Coordinators.

2. Getting Started with Sales Rejections 🚀

Accessing the Module

Navigate to the Sales Rejection Index from the main menu.

The Index Page

The index page displays a list of all rejections with their current status:

  • No. / Date: Unique SRN reference and reception date.
  • Party Branch Name: The customer location returning the goods.
  • QA Report No/Date: References the inspection document.
  • Status: Indicates if the rejection is Pending (P) or Closed (C).

Creating a New Rejection

The process is split into three main phases:

  1. Header Creation: Basic customer and QA reference info.
  2. Item Entry: Selecting specific items and linking them to original sale documents.
  3. Warranty Update: (Optional) Detailing the repair/warranty status of the returned units.

3. Features ✨

The Sales Rejection module offers several specialized features:

  • 🛡ī¸ Warranty Metric Tracking: A dedicated system to track In-Warranty (IW) and Out-of-Warranty (OW) quantities, further categorized by OK, Not OK, Repaired, and Scrapped.
  • 🔄 Flexible Transaction Types: Supports multiple return scenarios (e.g., Replacement, Repair & Return, Credit Note Only) through the Transaction Type system.
  • 🔗 Document Linkage: Validates returns against original Invoices, Challans, or Debit/Credit Notes to prevent unauthorized returns.
  • 📍 Store & Rack Management: Specify the exact Store Location and Rack Info where the returned goods are kept during inspection.
  • 🔐 Locked Closure: Prevents closing a rejection unless the “Customer In/Out” quantities are balanced, ensuring no items are unaccounted for.
  • 📝 Compliance Logging: Requires a mandatory reason (10-250 characters) for any deletion, which is permanently logged for audit trails.

4. Complete Flow 🔄

Follow these steps to process a sales rejection:

Create Rejection Header

  • Click “Create New” on the Sales Rejection Index.
  • Select the Date and the Party/Branch.
  • Enter the QA Report No and QA Report Date from the inspection team.
  • Provide Rack Info for storage location.

Add Items and Link Documents

  • After saving the header, move to the Sales Rejection Line Details page.
  • Select the Item, Brand, and Store Location.
  • Enter the Challan Qty (customer’s claim) and Actual Qty (manually verified).
  • Select the Transaction Type (e.g., Replacement).
  • Link the entry to a Customer Document (Invoice/Challan) by providing the document number and date.

Update Warranty Info

  • If applicable, click on “Update Warranty Info” from the line details.
  • Break down the Actual Qty into IW/OW categories.
  • Specify how many units were repaired or scrapped.

Close the Rejection

  • Once all items are processed and quantities are balanced, modify the header status to Closed.
  • This finalizes the transaction and prevents further edits.

5. Validations and Error Handling ⚠ī¸

The system enforces strict data integrity rules:

Validation TypeWhat is checked?Error Message / Action
QA DateQA Report Date vs SRN Date.“QA Report Date cannot be before SRN Date.”
Doc LinkageExistence of original Invoice/Challan.“Document No… for this party does not exist.”
Warranty TallySum of OK/Not OK units.“Addition of Ok and Not Ok Qty should be equal to Total Qty.”
Status ClosureIn/Out quantity balance.“Customer In / Out is not balanced.”
Delete RulesDeleting a Closed record.“You may not delete… status is Closed.”
QuantitiesActual vs Challan Qty range.“Qty must be between 0.001 - 9,999,999.999.”

6. Tools / Smart Features 🔧

  • 🛠ī¸ Warranty Wizard: A specialized interface for breaking down large return quantities into repair categories without manual math.

7. Related Reports 📊

  • 📈 Sales Analysis Report: Track return trends and reasons (select ‘Sales Rejection’ transaction type).
  • 📕 Inventory Ledger: Audit real-time stock movements for returned goods.

8. Configuration Requirements ⚙ī¸

Before processing rejections, ensure:

  • đŸĒ Store Masters: Designated stores for “Rejection” or “RMA” are configured.
  • 🏷ī¸ Srn Transaction Types: Return/Replacement codes are set up.
  • đŸ“Ļ Item & Brand Masters: Items must be correctly linked to their brands for warranty tracking.

9. Best Practices / Tips 💡

ℹī¸
  • Link Correct Documents: Always link the rejection to the original Invoice whenever possible to ensure correct financial credit.
  • Detailed QA Notes: Use the Notes field in the line items to describe specific defects found during inspection.
  • Prompt Closure: Close rejections as soon as the physical movement of goods is complete to keep inventory counts accurate.

10. Technical Observations 🔍

⚠ī¸
  • Status (Closed): This is permanent. Once a rejection is closed, you cannot add or remove line items.
  • Audit Trail: Every edit and deletion is tracked via the MFGLog, including the mandatory deletion reasons provided by the user.
Sales InvoiceShort Close Order