Purchase Return (Internal) Applet

Purpose and Overview

The Purchase Return (Internal) Applet is a specialized tool designed to manage the end-to-end process of returning goods to suppliers. It serves as the critical link between your warehouse operations (inventory) and financial accounts (payables), ensuring that every return is accurately recorded, tracked, and reconciled.

Key Features Overview

Who Benefits from This Applet?

Procurement & Warehouse Teams:

• Inventory Accuracy: Automatically deducts returned stock from inventory upon finalization.
• Traceability: Links returns directly to original Purchase Orders or GRNs.
• Efficiency: “Copy from Document” feature reduces data entry errors by 80%.

Finance Teams:

• AP Reconciliation: Automatically updates supplier aging and credit balances.
• Flexible Settlement: Supports Cash Refunds, Credit Notes, or Contra-offsets.
• Compliance: Generates necessary self-billed e-Invoices for tax purposes.

Management:

• Vendor Analysis: Identify poor-quality suppliers by tracking return frequency and reason codes.
• Audit Integrity: Maintains a permanent link between physical stock exit and financial credit.

What Problems Does This Solve?

The Manual Return Problem:

• Lost Credits: Finance isn’t notified of returns, so the company pays for goods it no longer has.
• Inventory “Ghost” Stock: Goods leave the warehouse but remain on the balance sheet.
• Tax Errors: Inconsistent handling of SST/GST adjustments without proper Debit Notes.

The Applet Solution:

• Unified Posting: One “Finalize” action updates Stock, GL, and Supplier Aging simultaneously.
• Linkage Validation: Prevents “over-returning” (returning more than was originally purchased).
• Settlement Tracking: Ensures every return is either paid back in cash or offset against an invoice.

Key Features at a Glance

Key Concepts

The “Golden Trio” of Returns

To effectively manage the system, it is crucial to understand how Physical Stock, Supplier Credit, and Document Linkage work together.

Document Hierarchy Structure

Think of the purchase return within the broader procurement flow:

Procurement Lifecycle
│
├── Purchase Order (PO) ──→ What we planned
│   │
│   └── Goods Received (GRN) ──→ What arrived
│       │
│       └── Purchase Invoice (PI) ──→ What we owe
│           │
│           └── PURCHASE RETURN (PR) ──→ What we sent back
│               │
│               ├── Contra ──→ Resets PI balance
│               └── Settlement ──→ Records cash refund

Document Status Lifecycle

Understanding the state transitions is essential for effective management.

CREATE → DRAFT
           │
           ├── FINAL ──→ Finalized (GL posted, stock deducted)
           │               │
           │               ├── VOID ──→ Reversed (GL and stock restored)
           │               │
           │               └── Settlement / Contra ──→ Financial closure
           │
           └── DISCARD ──→ Removed (draft deleted)

Quick Start Guide

For Procurement/Warehouse: Create a Return

Goal: Record a return for damaged goods and update inventory.

1. Navigate: Go to Purchase Return > "+" (Add).
2. Link Document: In the Search Document tab, click “Search Existing Document” and select the original GRN or PI.
3. Fill Header: In the Main Details tab, set the Branch, Location, and Transaction Date.
4. Select Supplier: In the Account tab, verify or select the supplier entity.
5. Pick Items: In the Line Items tab, select the items to return and specify the Return Quantity.
6. Review: Check the Delivery Details tab to confirm the Location (from where stock will be deducted).
7. Save: Click CREATE to save the return as a Draft.
8. Finalize: Click FINAL from the listing or edit screen. Inventory is now officially reduced.

For Finance: Process a Settlement

Goal: Close the return once the supplier provides a refund or credit.

1. Open Return: Locate the finalized PR document from the listing and click to edit.
2. Choose Path:
   • Contra: Go to the Contra tab → Select outstanding invoices from the same supplier → Apply the offset.
   • Settlement: Go to the Settlement tab → Enter the Bank/Cash account → Enter the refund amount → Save.
3. Verify: Check the ARAP tab to confirm the supplier balance has been updated correctly.

For Administrators: Initial Setup

Goal: Prepare the applet for the procurement team.

1. Default Selection: Set the default “Return Warehouse” in Settings > Default Selection.
2. Application Settings: Enable “Reason Code” as a mandatory field in Settings > Application Settings.
3. Perms: Assign the “Purchase Return Finalizer” permission set to relevant leads.
4. Print Format: Upload the company logo to Settings > Printable Format Settings.
5. Test: Perform a test return and verify the GL impact in Document Tracing.

Workflow Guide

Creating a Purchase Return

Method 1: Manual Entry Use this when returning goods without a specific source document reference (e.g., for goods received without invoice).

1. Click "+" (Add) from the main Purchase Return listing.
2. Account tab: Select the Supplier (Entity ID).
3. Main Details tab: Choose the Branch and Location (where the goods are physically stored). Set the Transaction Date.
4. Line Items tab: Click “Add Item” to add line items manually, specify Item codes and return quantities.
5. Main Details tab: Add a Reason Code or Remarks for audit purposes.
6. Click CREATE to save as Draft, then review before finalizing.

Method 2: Create from Existing Document (Recommended) Use this when returning against an original GRN or Purchase Invoice for accurate costing and linkage.

1. Click "+" (Add) from the main Purchase Return listing.
2. Search Document tab: Click “Search Existing Document” and search by original GRN or PI number.
3. Select the document — all item, price, and supplier details auto-populate into the Account and Line Items tabs.
4. Line Items tab: Adjust Return Quantity per line (cannot exceed original received quantity).
5. Click CREATE to save as Draft → Click FINAL after verification.

Management & Control

Handling Exceptions Sensitive actions (e.g., returning quantities above the original GRN, return date outside the purchase period) may require manager approval based on Workflow Settings.

Feature Deep Dive

Contra (Offsetting Invoices)

This is the most common settlement method. It allows you to “knock off” the value of a return against what you still owe the supplier on other invoices.

• Tab: Open the finalized PR document → go to the Contra tab.
• Workflow: Click Select Document to Contra With → choose outstanding invoices from the same supplier → set the contra amount → click Apply.
• Impact: Reduces your Accounts Payable (AP) without any bank transaction.
• Verification: Check the ARAP tab to confirm the updated Doc Open Amount and Balance.
• Use Case: You returned RM 500 of goods and have a RM 2,000 invoice outstanding. The contra offsets the return against the invoice, leaving only RM 1,500 payable.

Settlement (Recording Refunds)

Use this when a supplier physically returns money to you (e.g., a bank transfer).

• Tab: Open the finalized PR document → go to the Settlement tab.
• Workflow: Click Add Settlement → enter the Bank/Cash account → enter the refund amount and date → click Save.
• Impact: Reduces your AP balance and records a receipt in your bank/cash book.
• Verification: Check the ARAP tab to confirm the settlement has been recorded.
• Use Case: Supplier agrees to issue a refund and transfers the amount back to your company account.

e-Invoice Compliance

Automatically handles LHDN self-billed requirements for purchase returns.

• Self-Billed: Generates a self-billed debit note if required by tax regulations.
• Validation: Sends data to LHDN to receive a UUID for the return transaction.
• Applicability: Relevant for suppliers who are not registered for e-Invoicing, where you as the buyer are required to self-bill.

ARAP Impact

Every finalized Purchase Return creates an automatic accounting entry in the Accounts Payable (AP) ledger.

Document Tracing

Open a finalized PR document → go to the TraceDocument tab to access the complete forensic audit trail. You can also use the Posting tab to view the GL journal entries directly.

• Financials (Posting tab): Review the exact Journal Entries (e.g., Debit Inventory / Credit AP) generated.
• Inventory: Verify which Batch or Serial Number was removed from which Location.
• Upstream: See the original GRN and PI this return was derived from.
• Downstream: See any Contra or Settlement documents linked to this return.

Attachments

Open any PR document → go to the Attachment tab to store documentary evidence directly on the return record.

• Use Case: Attach supplier damage photos, quality reject certificates, or signed return authorization forms (RMA).
• Format: Supports PDF, JPG, PNG, and other common file types.
• Access: Attachments are visible to all users with read access to the document.
• Audit: Each attachment is logged with the uploader’s name and timestamp.

Line Reports

For deep analysis, the Line Reports view breaks down all purchase returns into individual row items. This allows for granular reporting, such as:

• “Total returns for Supplier X this quarter”
• “Most frequently returned item category”
• “Returns by reason code”
• “Return value as a % of purchases per branch”

Printable Format (Debit Note)

When finalizing a Purchase Return, the system can generate a Debit Note — a formal notice to the supplier that their account has been debited.

• Configuration: Customize the Debit Note layout in Settings > Printable Format Settings.
• Options: Add company logo, business registration numbers, custom footers.
• Use: Send directly to the supplier as formal documentation of the return.

Configuration & Settings

Customize the interface to match your workflow.

Personalization Menu

Access the Personalization menu to adapt the applet to your specific role.

• Default Settings: Set Default Branch and Location to avoid repetitive selection.
• View Layouts: Switch between Horizontal (Data-dense) or Vertical (Visual) orientation.

Admin Configuration

System Administrators can fine-tune behavior via the Settings panel.

• Default Selection: Set default branch, location, and other pre-fill values.
• Application Settings: Toggle visibility of fields like Reason Code, Permit No, etc.
• Printable Format Settings: Customize the Debit Note PDF layout with company branding.
• Webhooks: Set up event-driven notifications to external systems.

Applet Reference

This section provides a comprehensive reference of all menu items, settings, permissions, and configurable features.

Menu Items

Settings Sub-Menu Items

Settings Configuration Guide

This section provides detailed explanations of each settings option, including their purpose, use cases, and best practices.

Default Selection Settings

Purpose: Streamline data entry by pre-populating commonly used values, reducing repetitive selections and minimizing user error.

Best Practice: Configure Default Location to a dedicated “Returns/Reject” bin. This separates returned stock visually and physically from saleable inventory.

Application Settings

Purpose: Control which fields are visible, required, or hidden based on user roles and business requirements. This enforces data governance and simplifies the user interface.

Key Use Cases:

Enforcing Return Reasons

• Make Reason Code mandatory to ensure every return has a documented reason.
• Benefit: Enables downstream reporting on return reasons (e.g., “Defective Goods” vs “Over-Delivery”) for supplier performance reviews.
• Configuration: Define return reason codes in Settings > Return Reasons Settings.

Compliance Fields

• Show/hide Permit No for businesses with regulatory goods (e.g., controlled chemicals, pharmaceuticals).
• Make External Remarks mandatory for returns that require supplier acknowledgment notes.
• Benefit: Meets regulatory documentation requirements without cluttering the UI for unaffected flows.

Financial Sensitivity

• Hide Unit Cost from warehouse staff (only visible to finance team).
• Benefit: Prevents cost price disclosure to operational staff who don’t need it.

Printable Format Settings

Purpose: Customize the appearance and content of the Debit Note PDF to match company branding and meet supplier/legal requirements.

Debit Note

• Purpose: Official document sent to suppliers acknowledging the return and the corresponding credit owed.
• Customization Options:
  • Company logo and header branding
  • Business registration number and tax registration details
  • Custom footer text (e.g., bank account details for refund transfer)
  • Toggle visibility of Original Invoice No., Unit Cost, Return Reason
  • Approval signature lines

Best Practices:

• Include the Original Invoice Number in the printable format so suppliers can cross-reference the return against their records.
• Add bank account details in the footer to facilitate supplier cash refunds.
• Test printable formats before going live to ensure regulatory information is correct.

Email Template Settings

Purpose: Automate supplier communications with consistent, professional messaging at key transaction milestones.

Common Email Triggers:

Return Finalized

• Automatically send the Debit Note PDF to the supplier’s email.
• Include the original invoice reference and return reason.
• Benefit: Formal, immediate notification reduces supplier disputes.

Return Draft Created

• Alert the finance team or purchasing manager that a new return has been initiated.
• Benefit: Prevents returns from sitting in Draft status without review.

Webhook Settings

Purpose: Enable real-time integration with external systems by sending event notifications when key actions occur.

Common Webhook Use Cases:

ERP/Accounting Integration

• Trigger: Purchase Return finalized
• Action: Post debit entry to external accounting software
• Benefit: Eliminates double-entry, ensures real-time AP sync

Procurement System Alerts

• Trigger: Return quantity exceeds 10% of original PO line
• Action: Notify procurement manager for supplier review
• Benefit: Automates supplier quality management triggers

Feature Visibility Settings

Purpose: Control which applet features are accessible to users, allowing you to enable/disable functionality based on business needs.

Workflow Settings

Purpose: Define business rules and approval workflows to enforce governance.

Common Approval Workflows:

High-Value Returns

• Rule: Return value > configured threshold (e.g., RM 10,000)
• Action: Require manager approval before finalization
• Benefit: Additional scrutiny for large financial adjustments

Quantity Over-Return Prevention

• Rule: Return quantity exceeds 100% of original received quantity
• Action: System blocks submission; requires override approval
• Benefit: Prevents fraudulent or erroneous over-returns

Backdated Returns

• Rule: Transaction date < today - 7 days
• Action: Require approval from accounts manager
• Benefit: Prevents financial period manipulation

Permission Settings (Advanced)

The applet provides four layers of permission control for granular access management:

Permission Sets

• Purpose: Pre-configured bundles of permissions assigned in bulk.
• Example: “Purchase Return Viewer” has READ only; “Purchase Return Finalizer” has CREATE + FINALIZE.

User Permissions

• Purpose: Override or extend permissions for specific individuals.
• Example: Give one senior buyer DELETE permission while others cannot delete.

Team Permissions

• Purpose: Grant permissions based on team membership.
• Example: “Purchasing Team A” can only see returns for Branch A.

Role Permissions

• Purpose: Permissions tied to organizational roles.
• Example: “Warehouse Manager” role has FINALIZE authority.

Client-Side Permissions

• Purpose: UI-level feature visibility.
• Example: Hide the “Finalize” button from users who don’t have finalization rights.

Release Notes & Applet Log

Release Notes

• Purpose: Track applet version history and feature changes.
• Audience: Administrators and power users.

Applet Log

• Purpose: Forensic audit trail of system changes and administrative actions.
• Logged Actions: Settings changes (who changed what, when), permission modifications, feature enable/disable events.
• Use Case: Troubleshoot issues and demonstrate compliance to auditors.

Personalization Sub-Menu Items

Frequently Asked Questions (FAQ)

Q1: Can I return more than what was originally received in the GRN? A: No. If you link to a source document, the system prevents you from entering a return quantity higher than the available balance. This maintains audit integrity and prevents fraudulent over-returns.

Q2: What happens if I return an item that has different batches? A: You must select the specific batch number during the return process. This ensures the correct First-In-First-Out (FIFO) cost is deducted from the right inventory batch.

Q3: Is a Purchase Return the same as a Debit Note? A: In this applet, yes — conceptually. Finalizing a Purchase Return generates the financial equivalent of a Debit Note to the supplier, signifying that they owe you money (or that you owe them less on outstanding invoices).

Q4: Can I handle multi-currency returns? A: Yes. If you purchased in USD, the system will process the return in USD, maintaining the exchange rate used in the original transaction to avoid currency fluctuation errors in inventory valuation.

Q5: What if the supplier replaces the item instead of issuing a refund? A: Still process the Purchase Return to clear the defective stock from your inventory. Then process a new GRN or Purchase Invoice when the replacement goods arrive. Do not skip the return — it ensures your inventory count remains accurate.

Q6: What is the difference between Contra and Settlement? A:

• Contra is a paper-based offset. You use the credit from the return to reduce what you owe on another invoice. No cash changes hands.
• Settlement is a cash-based resolution. The supplier physically transfers money back to you, and you record it as a receipt in your bank or cash book.

Q7: If I finalize a Purchase Return by mistake, can I undo it? A: You cannot “un-finalize” directly. Use the VOID action to reverse the document — this nullifies all GL entries and restores stock, while preserving the audit trail. VOID requires appropriate permissions (typically restricted to Finance Managers). Always review the document carefully before clicking FINAL.

Q8: Do I need to create a separate Debit Note for the supplier? A: No. The finalized Purchase Return document is the Debit Note. You can print it directly using the Printable Format configured in Settings, and send it to your supplier as formal documentation.

Summary

The Purchase Return (Internal) Applet provides a structured, auditable environment for handling the complex logistics and financials of returning goods to suppliers. By strictly linking returns to original purchases and ensuring proper settlement (Contra or Cash Refund), organizations can prevent revenue leakage, maintain impeccable inventory records, and remain compliant with tax regulations (including LHDN e-Invoice requirements).

The key to success with this applet is:

1. Always link to source documents — this guarantees correct costing.
2. Finalize promptly — Draft returns don’t update inventory; delays create phantom stock discrepancies.
3. Close the loop with Contra or Settlement — An unsettled Purchase Return means a Credit Balance in your AP that isn’t being utilized.