The Supplier Payment Request (SPR) feature enables the accounts or purchase team to initiate, track, and manage supplier payments in a structured and controlled workflow. This acts as a bridge between Purchase Invoices / Purchase Orders and actual Payment Entries.

Key Features

Multiple Payment Types:

1. Advance Payments (against PO)
2. Credit Payments (against PI)
3. Ad-hoc or emergency payments (Only Via Fiance user with role )

Invoice Linking:

1. Link multiple Purchase Invoices (PI).
2. Pull eligible PIs automatically based on supplier, department, and outstanding.
3. It will show PI which has outstanding amount
4. Select which invoices to include via includeinpayment checkbox.
5. PI child table will show “Unsettled Payments” in column.
6. Now it will create Payment Entry unique for PI whose key (Supplier, Cost Center, Location, Fiscal year, Budget Head) is same. It means any of the parameter is missing for not same, it will create another PE.
7. User can change amount in “Amount to be paid field” and select “Include in Payment”.
8. User can filter PI, by mentioning Supplier in upper field
9. Unselected PI will be deleted autiomatically upon save.
10. Optional limits per department.

PO Advance Handling:

1. Fetch linked Purchase Order details without any PI linked.
2. Only those PO will be shown who has advance amount mentioned in approved PO
3. Auto-calculate advance paid, requested, remaining, and payment in process.
4. If there is a Invoice against that PO, PO should not come here even though we have advance approved in PO
5. Pull PO Items and Payment Entries already made against this PO to show total visibility.

PO Advance Handling:

1. This is for payment for which we don’t have PO or PI, mainly used by Finance Team.
2. User needs to fill all fields manually . (Accounting dimension and amount), supplier, etc

Pending Amount Logic: Automatically reduces outstanding based on:

1. Draft Supplier Payment Requests
2. Draft Payment Entries

Approval Workflow:

1. Multi-level approval support based on amount, trust, and department. Refer VCM ALM
2. Optionally route via ALM (Approval Limit Matrix).
3. ALM works on department
4. If no department mentioned in ALM, it should give error.
5. ALM will work on amount mentioned in PREQ AMOUNT

Bypass department ALM logic

A new feature have been added to Supplier Payment Request , so that finance person in below role can bypass Supplier Payment Request ALM. There is Bypass ALM checkbox which will be visible to only users in any of these roles (VCM FIN Payable", "VCM FIN MGR", "VCM FIN Bank). Once they select, SPR will follow Accounts ALM not the department ALM.

Validation:

1. Prevent overpayment against invoice outstanding.
2. Optional limits per department. Finance will decide and share weekly limit per department.

Submission Outcome: 1. After approval, can directly create Payment Entry with mapped invoices or PO advance. 2.

If we want to check usage, please refer report Vendor Outstanding for Payment Requisition