Vendor Payment Processing SOP: Step-by-Step Guide

Standard Operating Procedure: Vendor Payment Processing

This Standard Operating Procedure (SOP) outlines the mandatory workflow for processing vendor payments to ensure financial accuracy, internal control, and optimal cash flow management. By adhering to these procedures, the organization minimizes the risk of unauthorized disbursements, duplicate payments, and late fees while maintaining healthy professional relationships with our supply chain partners.

Phase 1: Invoice Receipt and Verification

• Centralized Intake: Ensure all vendor invoices are received via the dedicated accounts payable email address or official portal. Do not process invoices sent to personal or departmental email addresses.
• Data Integrity Check: Confirm the invoice contains:
  • Unique Invoice Number and Date.
  • Vendor name and contact details.
  • Purchase Order (PO) number (if applicable).
  • Clear description of goods or services rendered.
• Three-Way Match: Verify that the invoice details align with the original Purchase Order and the Goods Receipt Note (GRN) or proof of service completion.
• Approval Routing: Route the invoice to the department head who requested the goods/services for formal sign-off.

Phase 2: System Entry and Coding

• ERP/Accounting Entry: Input the invoice data into the accounting system within 24 hours of receipt.
• General Ledger (GL) Coding: Assign the appropriate GL account code to the invoice to ensure accurate financial reporting.
• Tax Validation: Confirm whether the invoice is subject to sales or use tax and ensure the tax amount is calculated correctly according to the vendor's jurisdiction.
• Payment Terms Mapping: Verify the due date in the system against the contractual terms (e.g., Net 30, 2/10 Net 30).

Phase 3: Payment Execution and Reconciliation

• Weekly Payment Run: Consolidate all approved invoices scheduled for payment for the current cycle.
• Dual Authorization: Ensure the payment file is reviewed by the Accounts Payable Manager and authorized for release by a designated Financial Controller or CFO.
• Remittance Advice: Generate a remittance advice notification to be sent to the vendor upon payment release to ensure they can apply the funds correctly.
• Final Archiving: Attach the proof of payment (e.g., bank confirmation or check stub) to the digital invoice record in the accounting system.

Pro Tips & Pitfalls

• Pro Tip: Early Payment Discounts. Always scan for "2/10 Net 30" terms. Taking a 2% discount on a large invoice can significantly impact the bottom line over a fiscal year.
• Pitfall: Duplicate Payments. Always search the system by vendor name and invoice number before processing to ensure the invoice hasn't been paid previously. Use automated duplicate detection software if available.
• Pro Tip: Vendor Portals. Encourage frequent vendors to use your self-service portal. This reduces manual entry errors and allows vendors to track their own payment status, reducing inquiry emails.
• Pitfall: Ignoring Statement Reconciliations. Do not rely solely on individual invoices. Request monthly statements from key vendors to ensure no credit memos or invoices were missed.

Template Document: Vendor Payment Processing SOP: Step-by-Step Guide

This document serves as the official Standard Operating Procedure for processing vendor payments to ensure financial accuracy and timely disbursement. It is intended for use by the accounts payable team, procurement staff, and financial controllers.

• Document owner: [Department Name]
• Effective date: [Date]
• Version: [Version Number]
• Applies to: [Process Name]

Roles and responsibilities

Steps

1. Receive the vendor invoice via [Email Address or Physical Mailbox] and assign a unique tracking number.
2. Verify that the invoice includes a valid purchase order number matching the [System Name] database.
3. Perform a three-way match by comparing the invoice, the purchase order, and the [Document Type] confirming delivery.
4. Flag any discrepancies in pricing or quantity that exceed the [Percentage] variance threshold.
5. Enter the invoice details into the [Accounting Software] using the correct general ledger codes.
6. Attach the digital copy of the invoice to the entry record within [Number] business days of receipt.
7. Submit the batch for approval to the [Job Title] if the total exceeds [Currency Amount].
8. Schedule the payment for the [Day of the Month] to ensure compliance with net terms.
9. Execute the payment through the [Bank Portal Name] and generate a remittance advice.
10. Update the status of the invoice to paid in the [Accounting Software] to prevent duplicate processing.
11. Reconcile the bank statement against the payment register at the end of [Month].
12. Archive the finalized payment packet in the [Folder Path or Storage Location] for audit purposes.

Record of completion

• Prepared by: [Full name]
• Reviewed by: [Full name]
• Date completed: [Date]
• Signature: ______________________
• Date signed: [Date]

Frequently Asked Questions (FAQ)

1. What should I do if an invoice does not match the Purchase Order? Do not process the payment. Contact the vendor immediately to request a corrected invoice or reach out to the internal department head to explain the discrepancy and initiate a PO amendment if necessary.

2. How do we handle urgent, "out-of-cycle" payment requests? Out-of-cycle payments are discouraged as they bypass internal controls. If absolutely necessary, they require a written justification from a Department Head and a secondary sign-off from the Finance Director.

3. What is the standard procedure for handling disputed invoices? The invoice must be flagged as "Disputed" in the accounting system to prevent automatic payment. The Finance team must notify the vendor in writing within 48 hours of the dispute, clearly outlining the reasons for the hold.