Standard Operating Procedure: Accounts Payable (AP) Processing

This Standard Operating Procedure (SOP) outlines the standardized workflow for the Accounts Payable function, ensuring that all financial obligations are verified, approved, and settled in a timely and accurate manner. The objective of this process is to maintain strong vendor relationships, ensure accurate financial reporting, and mitigate the risk of fraudulent or duplicate payments. This protocol is mandatory for all personnel involved in invoice intake, data entry, and payment authorization.

Phase 1: Invoice Receipt and Validation

• Receipt: All invoices must be received via the centralized AP email address or verified physical mail. Ensure no invoices are processed if sent directly to personal employee inboxes.
• Verification of Legitimacy: Cross-reference the invoice against the approved Vendor Master File. Ensure the vendor name, address, and tax identification number match existing records.
• Completeness Check: Inspect the document for all mandatory fields: unique invoice number, date, clear description of goods/services, line-item pricing, and total amount due.
• Standardization: If an invoice is missing data, return it to the vendor within 24 hours with a formal request for the required information. Do not enter incomplete documents into the ERP system.

Phase 2: Three-Way Matching and Coding

• Purchase Order (PO) Match: Locate the corresponding PO. Ensure the invoice quantity and price do not exceed the PO authorization limits (apply a standard 5% tolerance if company policy permits).
• Receipt Verification: Confirm the goods receipt (GR) note or signed delivery docket confirms the physical arrival of goods or successful completion of services.
• General Ledger (GL) Coding: Assign the appropriate GL account code based on the nature of the expenditure (e.g., Office Supplies, Software Licensing, Direct Materials).
• Managerial Approval: Route the invoice to the respective department head for electronic sign-off if the invoice exceeds a pre-defined dollar threshold (e.g., $1,000+).

Phase 3: Data Entry and Scheduling

• System Entry: Enter the invoice details into the ERP system. Ensure the currency, tax amount, and payment terms are keyed accurately.
• Schedule Payment: Set the payment date according to the vendor's agreed-upon terms (e.g., Net 30). Utilize the system’s scheduling function to prevent premature or late payments.
• Audit Trail: Attach a digital copy of the invoice and all supporting documents (PO, GR note) to the ERP record for future audit purposes.

Phase 4: Disbursement and Reconciliation

• Payment Run Preparation: Generate the "Proposed Payment Report" for review by the Finance Manager 48 hours before the scheduled disbursement date.
• Execution: Finalize the payment run via Electronic Funds Transfer (EFT) or corporate credit card. Minimize physical check usage due to security risks.
• Remittance Advice: Automatically generate and send remittance advice to the vendor via the ERP system to ensure transparency regarding what was paid.
• Reconciliation: Perform a monthly reconciliation of the AP sub-ledger to the General Ledger to ensure balances are accurate and discrepancies are addressed.

Pro Tips & Pitfalls

• Pro Tip: Early Payment Discounts. Always flag invoices with "2/10 Net 30" terms. If cash flow allows, prioritize these to capture the 2% discount; it represents a high annualized ROI for the company.
• Pitfall: Duplicate Payments. One of the most common errors occurs when a vendor sends a statement and a separate invoice for the same work. Always check the "Vendor Invoice History" in your system before processing any paper invoice to ensure it wasn't already paid.
• Pitfall: Unapproved Scope Creep. Never pay an invoice that is higher than the original PO without a documented "PO Change Order" or written email authorization from the original requestor.

Frequently Asked Questions (FAQ)

1. What should I do if a vendor invoice is missing a PO number? Hold the invoice and contact the department head who ordered the goods. If the expenditure is legitimate, create a "Non-PO Invoice" request, but require secondary managerial approval to ensure budget compliance.

2. How often should the Vendor Master File be audited? The Vendor Master File should be audited at least bi-annually. Inactive vendors (those with no activity for 18+ months) should be archived to prevent potential fraudulent activity.

3. What is the protocol for handling discrepancies in unit pricing? The AP clerk should immediately notify the procurement team. The invoice should be placed in "Hold" status, and the vendor must be contacted to issue a credit memo or a corrected invoice before the payment is released.

<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "What is the primary objective of the AP processing SOP?", "acceptedAnswer": { "@type": "Answer", "text": "The objective is to ensure all financial obligations are verified, approved, and settled accurately while maintaining vendor relationships and mitigating fraud risks." } }, { "@type": "Question", "name": "How does three-way matching work in Accounts Payable?", "acceptedAnswer": { "@type": "Answer", "text": "Three-way matching involves verifying that the invoice details align with the Purchase Order (PO) and the Goods Receipt (GR) note to ensure payment legitimacy." } }, { "@type": "Question", "name": "What should be done if an invoice is missing data?", "acceptedAnswer": { "@type": "Answer", "text": "If an invoice is incomplete, it should be returned to the vendor within 24 hours with a formal request for the missing information. Do not enter incomplete data into the ERP system." } } ] } </script> <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "SoftwareApplication", "name": "Accounts Payable ERP System", "applicationCategory": "FinanceApplication", "operatingSystem": "All", "description": "Standardized workflow software for managing invoice intake, data entry, three-way matching, and payment scheduling in accounts payable departments.", "featureList": [ "Invoice Validation", "Three-Way Matching", "GL Coding", "Payment Scheduling", "Approval Workflows" ] } </script>