Accounts payable policy: Template, examples and how to write one

An accounts payable policy is the written standard that governs how a company handles vendor bills, from the moment an invoice arrives to the moment cash leaves. Without one, approval limits live in people’s heads, duplicate payments slip through, and a spoofed bank-detail email can redirect money.

A policy with clear thresholds, named roles, and logged exceptions gives approvers a standard to follow and auditors something to test.

What is an accounts payable policy?

An accounts payable policy is your written set of rules for receiving, approving, recording, and paying vendor invoices, and for who owns each step. The policy sets rules and thresholds, such as who approves invoices above a set dollar amount.

Your procedures tell AP staff how to apply those rules, step by step, in the systems you use. Many teams keep accounts payable policies and procedures in one document so a rule change and its new steps get published together. If you split them across files, a threshold change in one leaves staff following stale steps in the other.

Accounts payable policy template

Replace every bracketed value with your own thresholds, roles, payment terms, and retention periods before you circulate the draft.

1. Purpose: This policy defines how [Company Name] receives, approves, records, and pays vendor invoices. It sets controls that protect company cash and keep the general ledger accurate.
2. Scope: This policy covers all vendor invoices for [legal entities] and [departments], including [spend types covered]. It excludes [payroll, employee reimbursements, corporate card transactions, intercompany transfers].
3. Roles and responsibilities: The [AP manager] owns this policy and reviews all exceptions. Budget owners approve invoices for their departments, and the [controller] approves each payment run. To maintain segregation of duties, no employee may both create a vendor record and release payments to that vendor.
4. Vendor onboarding and master file changes: AP collects a completed Form W-9 or W-8 from every vendor before the first payment. AP verifies all bank-detail changes by calling a vendor contact at a phone number already on file, and the [vendor master administrator] enters approved changes.
5. Purchase orders: A purchase order (PO) is required for all purchases over [$X] and for all [inventory or capital equipment] purchases. Invoices for [utilities, software subscriptions, and contracted recurring services] don't require a PO.
6. Invoice receipt and intake: Vendors send all invoices to [AP intake email address]. AP processes an invoice only when it includes the vendor's legal name, invoice number, invoice date, amount due, payment terms, and PO number where required. Employees who receive an invoice directly forward it to [AP intake email address] within [X] business days.
7. Invoice approval and approval thresholds: Every invoice requires approval under the approval matrix in [Appendix A] before payment. Invoices over [$X] require [department head] approval, and invoices over [$Y] also require [CFO] approval. No employee may approve an invoice for their own purchase or for a vendor they have a personal or family relationship with.
8. Invoice matching and exceptions: Invoices for [goods categories] require a 3-way match of PO, receiving record, and invoice before payment. Invoices for [services categories] require a 2-way match of PO and invoice. The [AP manager] resolves price or quantity differences above [X%] or [$Y] before payment.
9. Duplicate payment prevention: Before payment, AP checks each invoice against prior invoices from the same vendor for a matching invoice number, amount, or date. The [AP manager] reviews any match, any invoice without an invoice number, and any reissued invoice with a changed number.
10. Payment terms, payment methods, and payment schedule: Standard payment terms are [net 30] unless a signed contract states otherwise. Approved payment methods are [ACH, check, virtual card, and wire]. AP runs payments [weekly on Thursday], and the [controller] approves each run before release.
11. Early payment discounts and late payments: AP takes an early payment discount when its annualized value exceeds [X%] and cash on hand stays above [$Y]. AP documents the reason for every late payment and reports late payments to the [controller] monthly.
12. Expense coding and recording: AP codes each invoice to the general ledger account, department, and [class or location] defined in [chart of accounts reference]. AP records each invoice in [ERP] within [X] business days of receipt.
13. Period-end accruals and cutoff: AP accrues goods and services received before period-end but not yet invoiced when the amount exceeds [$X]. Invoices received after [X] business days past period-end post to the following period.
14. Record retention and audit trail: AP retains invoices, purchase orders, approvals, and payment records for [X] years. The system of record logs who approved, changed, or paid each invoice and when.
15. Policy exceptions, review, and update cadence: Any exception requires written approval from the [CFO or controller] and an entry in the [exception log]. The [policy owner] reviews this policy every [12] months and after any significant change in invoice volume, systems, or organization structure.

Your CFO or controller can review a filled-in draft line by line. An unset threshold is one nobody can enforce.

Accounts payable policy examples by section

Approvals, invoice matching, duplicates, vendor changes, and payment runs are the sections teams get stuck on most. Every number in brackets is a placeholder, so set yours based on your invoice volume and team size.

Approval thresholds and authority

Tie approval authority to invoice amount, then add rules for conflicts of interest and absences. A typical accounts payable policy example reads:

• Invoices over $500 require approval from the department head, and invoices over $10,000 also require approval from the CFO.
• No employee may approve an invoice for their own purchase or for a vendor they're related to. When an approver is out for more than 2 business days, the controller approves in their place.

Set the first tier high enough that routine bills don't wait on senior approvers. Name a backup for every approver role so invoices keep moving during vacations. Thresholds set this way keep senior approvers focused on the invoices that carry the most risk.

Invoice matching rules

Use 3-way matching for physical goods you receive and 2-way matching for services, where there's no receiving record. Here's some sample language:

• Invoices for inventory and equipment require a 3-way match of PO, receiving record, and invoice before payment.
• Differences within 2% or $50 of the PO price or quantity may be paid without further review. The AP manager resolves larger differences with the requester and vendor.

A tight tolerance catches more errors but sends more invoices into the exception queue. If your team can't clear exceptions within 5 days, loosen the tolerance on low-dollar invoices first. Pick a tolerance your team can keep up with, or the queue will hold up vendor payments.

Duplicate invoice and payment controls

Check every invoice against prior bills on vendor, invoice number, amount, and date before you pay it. Sample language includes:

• AP compares each invoice to prior invoices from the same vendor before payment. Any invoice that shares an invoice number, amount, or date with a prior invoice goes to the AP manager for review.
• AP assigns invoices without a number a reference in the format: vendor ID-invoice date-amount. A reissued invoice with a new number requires written vendor confirmation that the original is void.

Exact-number checks miss the duplicates that cause the most trouble, such as a rescanned invoice with a typo in the number. Decide how close a match has to be before AP holds the payment. A near-match rule catches the duplicates an exact-match rule lets through.

Vendor master file changes

Verify every bank-detail change through a contact you already have on file before anyone updates the vendor record. Sample language might be:

• AP confirms bank-detail change requests by calling the vendor at a phone number already in the vendor master file. AP never uses contact details from the change request itself.
• The vendor master administrator enters approved changes. That person can't create or release payments.

Smaller teams may not have a separate person for vendor setup. In that case, have the controller review a report of every master file change before each payment run. Without that check, one spoofed email can send a vendor's next payment to the wrong account.

Payment terms and payment runs

Set standard terms and a fixed run schedule, then decide when early payment discounts are worth taking. Here's some sample language:

• Standard payment terms are net 30 unless a signed vendor contract states otherwise. AP runs payments weekly on Thursday, and the controller]approves each run before release.
• AP takes early payment discounts when the annualized value exceeds 10% and cash on hand stays above $250,000.

Weekly runs give vendors predictable timing, while less frequent runs give you more time to review each batch. Compare the annualized value of a discount, such as 2/10 net 30, with what that cash earns elsewhere. A fixed schedule gives approvers a deadline so invoices stop going out one at a time.

How to write an accounts payable policy

Write the policy in eight steps, starting with how invoices move today and finishing with sign-off and a review date.

1. Map your current invoice-to-payment process

Trace how invoices arrive and who approves them today, then follow a few through to payment. Talk to AP staff and a few frequent approvers because informal workarounds rarely show up in system settings. Note each one, such as invoices approved over chat or vendors paid outside the payment run.

Every workaround you find becomes a rule you either formalize or ban.

2. Define scope and ownership

Decide which entities, spend types, and payment methods the policy covers. List the exclusions too, such as payroll and expense reimbursements, which usually have their own policies. Name one owner, usually the AP manager or controller, who keeps the policy current.

A named owner keeps updates on schedule.

3. Set approval thresholds and authority levels

Base thresholds on invoice volume and risk. If most of your invoices fall under $5,000, set your first tier there so budget owners handle routine bills on their own. Write each approver as a role, such as each department head, so the policy still works after someone leaves.

Role-based approvals survive reorgs and turnover without a rewrite.

4. Choose your matching and documentation rules

Decide when a PO is required and what an invoice must include before AP can pay it. Some categories, such as utilities and software subscriptions, can skip POs and matching because the amount is set in advance. Required invoice fields usually include the vendor's legal name, invoice number, date, amount, and payment terms.

Clear documentation rules let AP reject incomplete invoices without escalating each one.

5. Build in duplicate and fraud controls

Write rules for verifying new vendors and checking every invoice for duplicates. Require a W-9 and verified bank details before a vendor's first payment, and confirm any change by calling a known contact. Match the approval levels in these rules to your broader internal controls so the two never conflict.

Money sent to an altered bank account is hard to get back.

6. Separate key duties

Assign vendor setup, invoice approval, and payment release to different people. That split is the core of segregation of duties, and it keeps one person from creating a vendor and paying it. Smaller teams can use compensating controls, such as having the owner or CFO review every payment run before release.

With that review in place, a small team still gets a second set of eyes on every payment.

7. Set payment terms, methods, and timing

Pick a payment run schedule, such as weekly or twice a month, and a cutoff for invoices to make each run. List approved payment methods, such as ACH, check, card, and wire, and when each one applies. Then set a rule for early payment discounts based on the annualized return and your cash position.

Vendors get paid on a predictable schedule, and you decide when cash leaves.

8. Get sign-off, train the team, and schedule reviews

Get approval from the CFO or controller and record the effective date. Walk approvers and AP staff through your accounts payable policies and procedures in a short session, focusing on thresholds and exceptions. Schedule a review every 12 months, plus an earlier one when invoice volume or your systems change.

A signed, dated policy gives auditors something to test against.

Accounts payable policy best practices

The best AP policies stay short and match the AP best practices your team follows day to day.

• Write in plain language: Use the words your approvers use, and state every threshold in dollars or days.
• Keep it short: Move detailed steps into procedures so approvers can read the policy in one sitting.
• Update policy and procedures together: Review both in the same cycle so staff never follow steps that contradict a rule.
• Log every exception: Record who approved each exception and why. Recurring entries point to a rule that needs updating.
• Configure rules in your AP system: Set thresholds and routing in software so the written policy matches the live workflow.

Policies kept this way get followed, because nobody has to guess which rule still applies.

Common mistakes when writing an AP policy

Most AP policy failures come from rules that exist on paper and nowhere else.

• Thresholds nobody enforces: Limits that live only in a document get skipped, so set them up as routing rules in your AP system.
• Rules tied to people: Naming individual approvers breaks the policy at the first departure, so write every approver as a role.
• No rule for bank-detail changes: Without a required callback to a known contact, a spoofed email can change payment details, so make verification mandatory.
• A policy nobody revisits: Rules written for 50 invoices a month won't fit 500, so review annually and after any system change.

Each fix closes a gap before an auditor finds it.

Enforce your AP policy automatically with Ramp Bill Pay

You've written approval thresholds, matching rules, and duplicate controls. Enforcing them by hand means approvers check limits from memory and AP scans spreadsheets for repeat invoices, so rules slip at month-end.

Ramp Bill Pay supports finance teams in managing accounts payable through advanced automation. It’s an autonomous AP platform that deploys AI agents that categorize invoices using past transaction data, flag fraudulent activity pre-payment, generate approval records, and execute vendor payments via cards—removing manual roadblocks from your workflow.

Ramp Bill Pay’s OCR extracts invoice information at up to 99% accuracy and processes invoices 2.4x faster than traditional software,¹ accelerating your team's output while maintaining low error rates. After using Ramp, up to 95% of companies reported better control over their finance operations.²

Here’s a closer look at what Ramp Bill Pay brings to the table:

• Four AI agents: Code invoices automatically using transaction history, detect fraud pre-payment, build approval summaries with vendor background and pricing analysis, and execute card payments through vendor portals
• Intelligent invoice capture: Pulls data from every line item with 99% OCR accuracy
• Automated PO matching: Compares invoices to purchase orders with 2-way and 3-way matching to catch overbilling
• Custom approval workflows: Creates multi-level approval chains with role-based routing matching your organization structure
• Approval orchestration: Cuts clicks, boosts visibility, and speeds processing across reviewers
• Real-time invoice tracking: Provides visibility from invoice receipt through payment
• Payment methods: Sends payments through ACH, corporate card, check, or wire transfer
• Vendor Portal: Gives vendors secure access to update payment information, check payment status, and contact your AP team
• Real-time ERP sync: Connects vendor data bidirectionally with ERPs like NetSuite, QuickBooks, Xero, and Sage Intacct for audit-ready books
• GL coding: Assigns transactions to correct accounts with AI assistance
• Reconciliation: Automatically matches transactions for faster book closing
• Vendor onboarding: Gathers W-9s, verifies TINs, and manages 1099 information within the platform
• Batch payments: Processes multiple vendor payments at once
• Recurring bills: Processes regular payment schedules with templates
• Roles and permissions: Controls who can do what with granular user settings
• AI-powered 1099 prep: Automatically categorizes bill pay spend into 1099-NEC and 1099-MISC boxes with calculations
• Bulk W-9 collection: Sends W-9 and e-consent requests to all vendors simultaneously
• One-click IRS filing: Submits filings to IRS and states in minutes without extra portals

What makes Ramp Bill Pay worth it

Ramp Bill Pay shows what AP automation can achieve—precision, autonomous operations, touchless processing, and speed. Your AP objectives might center on faster cycle times, lower costs, higher accuracy, or live data access—Ramp supplies the automation tools and visibility needed to deliver. Finance professionals on G2 also consistently describe it as one of the easiest AP platforms to get started with.

Use Ramp Bill Pay independently as your core AP system, or connect it with Ramp's corporate card programs, expense management, and procurement platform for complete spend oversight.

AP doesn't have to be complicated. Ramp Bill Pay makes it easy.