Skip to content

Allow Purchase Invoice Payment by Employee Cash Custody (Retail Purchases) #52194

@rizwan100mu

Description

@rizwan100mu

@DipenFrappe @mihir-kandoi
ERPNext does not support recording Purchase Invoices paid by an employee from their cash custody, which is a very common scenario for retail shop purchases.
In retail purchases, an employee often goes to a shop, pays cash from their assigned custody, and brings the invoice back. The Purchase Invoice should reflect that the supplier was paid by the employee using company cash custody.
Currently, ERPNext does not provide a way to select:
• Party Type = Employee
• Party = Employee
within the Purchase Invoice payment section.


Current Behavior
• Purchase Invoice cannot be marked as paid by an employee
• Cash custody held by employee cannot be linked to Purchase Invoice
• Employee-paid retail purchases must be recorded using:
o Expense Claims, or
o Employee Advances, or
o Manual Journal Entries
• These options do not accurately represent a supplier payment


Expected Behavior
Purchase Invoice should support payments made by employees from their cash custody.
When enabled:
• User can select Party Type = Employee
• User can select the Employee who paid
• Cash custody balance of that employee is reduced
• Supplier payable is settled
• Purchase Invoice is marked as Paid
• Clear audit trail is maintained


Why This Is Important
• Retail purchases are frequently paid in cash by employees
• Cash custody accountability is required for internal control
• Avoids misuse of advances and expense claims
• Improves accuracy of Accounts Payable
• Reduces need for custom development


Additional Notes
This use case is different from Employee Advance or Expense Claim.
It represents a direct retail supplier payment made by an employee using company cash custody.

Feature Idea in Screenshot as marked

Image

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions