Example of Sop for Accounts Payable

SOP-FIN-AP-001: Accounts Payable Lifecycle Management

1. Document Control & Revision History

2. Executive Summary & Scope

This Standard Operating Procedure (SOP) defines the institutional framework for the Accounts Payable (AP) function. It ensures the integrity of financial obligations, mitigates fraudulent disbursement risks, and maintains Sarbanes-Oxley (SOX) compliance regarding internal controls over financial reporting. This scope covers all vendor invoice intake, validation, reconciliation, and disbursement activities globally within the entity.

3. Prerequisites & Tool Requirements

• ERP Access: Administrative/Functional access to Oracle NetSuite or SAP S/4HANA (AP Module).
• Documentation: Digital archive access (e.g., DocuWare or SharePoint) for invoice imaging.
• Security: MFA (Multi-Factor Authentication) enabled for all banking portals.
• Certifications: Completion of 'Corporate Fraud Prevention & Ethics' module; active credentialing for AP Clerk role.
• Software: Microsoft Excel (Advanced/Macro-enabled) for variance reporting.

4. Roles & Responsibilities (RACI Matrix)

5. Step-by-Step Operational Procedure

Phase I: Invoice Intake and Digitization

• Verify invoice meets legal requirements (Tax ID, Vendor address, Invoice #, PO Reference).
• Assign unique document control number (DCN) and upload to ERP imaging module.
• Route electronic notification to the appropriate department head for service validation.

Phase II: The 3-Way Match Protocol

• Confirm Purchase Order (PO) existence and open status in ERP.
• Compare Invoice line items vs. Packing Slip vs. PO.
• Validate unit pricing, extended totals, and sales tax/VAT calculations.
• Apply "Hold" status if variance exceeds threshold (see Section 6).

Phase III: Disbursement Authorization

• Schedule payment in accordance with vendor terms (Net 30/60).
• Generate Payment Batch report for secondary review.
• Secure electronic signature/digital authorization from Controller for batches >$10k.

6. Quality Assurance & Verification Criteria

• Tolerance Threshold: $0.01 variance allowed for rounding; any variance >0.5% or >$5.00 triggers immediate manual audit.
• Audit Frequency: 10% of monthly processed invoices are subject to internal audit reconciliation.
• Acceptance Benchmarks: 99.5% accuracy rate required for data entry fields.
• Segregation of Duties: The individual who enters the vendor profile must not be the individual who releases the payment batch.

7. Practical Troubleshooting Scenarios

Scenario A: Duplicate Invoice Suspected

• Failure: ERP flags an existing invoice number for a vendor that was processed in the previous cycle.
• Correction: Halt processing immediately. Review scanned images for physical document alterations. If confirmed duplicate, flag as 'Void' in ERP, generate a 'Duplicate Invoice Report', and archive the invalid document in the 'Exceptions' folder.

Scenario B: Goods Receipt/Invoice Receipt (GR/IR) Mismatch

• Failure: Invoice indicates service delivered; however, the Procurement module shows no Goods Receipt (GR) confirmation.
• Correction: Issue a 'Pending Verification' notice to the Budget Owner. If no response within 48 hours, escalate to the Purchasing Manager. Do not release payment until proof of delivery (POD) or authorized sign-off is digitized in the file.

Scenario C: Bank Detail Change Request

• Failure: Vendor requests a change to remittance/bank details via email.
• Correction: DO NOT update ERP immediately. Initiate mandatory 'Out-of-Band' (OOB) verification: Call the vendor contact using the trusted phone number on file (not the number provided in the request email). Execute a $0.01 test transaction before authorizing full payment.