Accounts Payable Procedures: The Complete Guide

An AP procedure is not bureaucracy. It is the thing that stops the same invoice being paid twice, stops payments going to an address a fraudster supplied, and stops the month closing with bills nobody entered.

What follows is a process that works at small scale, with the controls built in rather than bolted on.

1. Intake

One route in. A dedicated email address for invoices, not individual inboxes. Invoices arriving to whoever happened to order the thing is how bills get lost and how the same bill gets entered twice by two people.

• Single intake channel, monitored on a schedule
• Anything arriving elsewhere gets forwarded, not actioned
• Supplier statements handled separately, never paid as invoices

2. Matching

Before an invoice is entered, it is matched to evidence that the obligation is real: a purchase order and receiving record for goods, or a quote, contract, or completion record for services.

An invoice that cannot be matched to anything is a query, not a payable. Entering it and sorting it out later is how unauthorised charges get paid.

3. Approval

Someone with authority confirms the invoice should be paid. At small scale an email reply is sufficient documentation, provided it is retained against the transaction.

Set an approval threshold if useful, but do not set it so high that most spending bypasses review.

4. Entry

• Enter against the correct vendor record, one record per vendor
• Code to the correct expense account and, if relevant, the correct job or class
• Date to the period the cost belongs to, not the date you entered it
• Record the vendor invoice number, so duplicate warnings can work
• Attach the document to the transaction

5. Payment scheduling

Run payments in scheduled batches rather than ad hoc. Batching improves control, reduces bank fees, and makes cash forecasting far more accurate because payments happen on known dates.

Schedule to terms. Take early payment discounts only where the discount exceeds the value of holding the cash.

6. Release

Payment is released by someone other than the person who prepared the run. If you are the owner, this is the control to keep even when you delegate everything else.

7. Recording and review

• Payments recorded against the specific bills they settle, so payables clear
• Payment register reviewed after each run
• AP aging reconciled to the general ledger control account monthly
• Vendor statements reconciled on a defined schedule, prioritised by spend

The vendor master file

New vendors and bank detail changes are where the highest-value control sits. Require tax documentation at setup for vendors potentially subject to information reporting, and verify any bank detail change by phone to a number you already hold, never one supplied in the request.

What to document

A one-page procedure covering: where invoices arrive, who matches, who approves and up to what value, who enters, when payment runs happen, who releases, and what gets reviewed. One page that people follow beats a manual nobody opens.

Define the accounts payable policy first

Procedures explain how work is performed. Policy explains which work is allowed. Before documenting clicks and handoffs, define who may commit the business, which purchases require advance approval, what support is required, how exceptions are approved, when payment runs occur, and who can release funds. Without those decisions, an accounts payable procedure merely moves unapproved invoices faster.

Keep the policy proportionate to the business. A small recurring subscription may follow a light review. A new vendor, change in bank details, large purchase, or unusual rush payment deserves more evidence. Avoid rules so burdensome that staff work around them. A control that is routinely bypassed is neither efficient nor reliable.

Step 1: onboard and verify the vendor

Create a vendor record only after collecting the legal name, payment address, tax documentation when applicable, payment terms, business contact, and bank instructions needed for the chosen payment method. Search for duplicate names and related entities before creating a new record. Limit who can create or edit vendors.

Verify new or changed bank details using an independent contact method. Do not rely on the email that requested the change. Use contact information already on file or obtained from a trusted source, call a known person, and record who completed the verification. Separate vendor-master changes from payment release wherever the team allows.

Step 2: receive invoices through one controlled channel

Use a designated inbox, portal, or capture workflow so invoices are not scattered across personal email, paper, messaging apps, and project systems. Record the date received because it affects both processing time and payment planning. Preserve the original document even when data are extracted automatically.

Screen for duplicates using vendor, invoice number, date, amount, purchase reference, and attachment. Standardize invoice-number formatting carefully so punctuation differences do not defeat the search. Flag credit notes and statements separately. A statement is useful for reconciliation but should not be entered as if it were another invoice.

Step 3: validate the invoice

Confirm the vendor identity, invoice date, unique number, description, amount, currency, payment terms, remit information, and mathematical accuracy. Check that the invoice belongs to the business and the service period is clear. Route tax questions for appropriate review rather than guessing from a prior invoice.

Look for warning signs such as changed bank instructions on the invoice, unfamiliar contact details, split invoices, vague descriptions, round amounts without support, or pressure to pay outside the normal process. A warning sign does not prove fraud. It means the invoice requires independent confirmation before it can proceed.

Step 4: match authorization, receipt, and price

Where purchase orders are used, compare the order, receiving evidence, and invoice at line level. For services, use an approved quote, contract, timesheet, milestone approval, or other evidence that the work was authorized and delivered. Confirm coding and service period as part of the match.

Put differences into an exception queue instead of editing source documents to force agreement. Assign an owner and due date. Price differences belong with the buyer or requester, receipt differences with the receiver, and invoice errors with the supplier. Accounts payable coordinates resolution and records the result.

Step 5: code and enter the bill

Choose the correct expense, asset, liability, project, class, location, and service period based on the support. Use a consistent coding guide for recurring transactions. If a cost benefits more than one period, confirm whether a prepaid or other treatment is appropriate. Do not spread an invoice merely to make monthly results look smoother.

Enter the bill once, attach the source document, and retain the approval trail. The invoice date, due date, and terms should drive the payment schedule. Avoid changing the date to move a cost between periods without a documented accounting reason.

Step 6: obtain approval

The approver should see the invoice, business purpose, coding, match status, and any exception. Approval should be attributable to a named person and retained. Silence, forwarding an email, or being copied on a message is weak evidence that someone accepted the charge.

Approval limits can reflect role, amount, vendor type, project, or exception status. Prevent a requester from approving a purchase solely because that person initiated it when another owner is available. For owner-led businesses, bank release can provide the final independent review if the payment register includes enough detail.

Step 7: prepare a scheduled payment run

Select approved bills based on due dates, cash availability, discounts, disputes, and vendor terms. Prepare a payment register showing vendor, invoice, due date, amount, bank destination or payment method, and preparer. Exclude unresolved exceptions and retain the reason for any deliberate hold.

Scheduled runs reduce rush payments and make review easier. Genuine urgent payments may occur, but they should follow a documented exception path. A requester’s urgency does not replace verification, approval, or bank-detail control.

Step 8: approve and release payments

The payment approver should compare the bank batch or checks with the approved register and investigate additions or changes. Use dual authorization when available. Restrict bank permissions so the same user cannot create a payee, prepare the payment, and release it without review.

After release, record the bank confirmation and payment reference. Protect checks, payment tokens, and administrator credentials. Review failed or returned payments promptly because they can leave the ledger showing a bill as paid when cash never reached the vendor.

Step 9: post and communicate remittance

Apply each payment to the correct bill or bills so the vendor balance clears. Send remittance information through an approved channel when helpful. Record credits used and preserve any allocation across multiple invoices. Unapplied payments create old balances and unnecessary supplier inquiries.

If the supplier disputes the allocation, compare the remittance, bank confirmation, vendor statement, and ledger. Correct the specific posting rather than entering an unexplained adjustment. The goal is agreement between the business record, bank record, and supplier record.

Step 10: reconcile accounts payable

Reconcile the accounts payable control account to the vendor subledger at each month end. Review vendor statements for missing invoices, credits, duplicate payments, and timing differences. Investigate negative vendor balances, old debit balances, stale checks, and bills with dates or due dates that do not make sense.

Search the period after month end for invoices relating to the closed period so unrecorded obligations can be considered. The appropriate cutoff treatment depends on the reporting basis and facts. Document the review and any resulting entry rather than relying on memory.

Accounts payable controls for a small business

• Separate vendor setup, bill entry, approval, and payment release where possible
• Require independent verification of bank-detail changes
• Use one invoice intake channel and a duplicate check
• Retain purchase, receipt, invoice, approval, and payment evidence
• Review an itemized payment register before bank release
• Reconcile vendor statements and the control account
• Restrict direct journals to accounts payable
• Lock closed periods and review later changes
• Monitor rush payments, overrides, and repeated exceptions

Useful AP operating metrics

Track invoices received, processed, approved, on hold, past due, and paid. Measure exception age and reason, duplicate invoices prevented, invoices received without authorization, vendor credits outstanding, and payment failures. Supplier discount capture may matter where discounts are genuinely economic and cash supports early payment.

Use metrics to locate bottlenecks. A long receipt-approval delay belongs with operations, not data entry. Repeated missing purchase references may require a purchasing change. A growing vendor debit balance may indicate unapplied credits or overpayments. The report should show where the process needs attention and who owns the next action.

Turn the procedure into a responsibility matrix

List each step down the left side and the requester, approver, receiver, accounts payable preparer, vendor-master administrator, payment approver, and reviewer across the top. Identify who performs, approves, is consulted, and is informed. The matrix makes incompatible duties and unowned exceptions visible.

Where one person must perform several tasks, add a compensating review. Examples include owner approval of the itemized payment register, a bank rule requiring a second release, a report of vendor-master changes, or monthly review of credits and duplicate payments. Record the review instead of assuming it happened.

Test the procedure with exceptions

Walk through a duplicate invoice, missing purchase reference, partial receipt, disputed service, vendor bank change, credit note, overpayment, and failed payment. Define where each item is held, who owns it, what evidence resolves it, and how the ledger is corrected. Ordinary invoices rarely expose weak procedures.

Create a short exception guide rather than asking staff to improvise. State which situations stop payment automatically, which require buyer confirmation, which require supplier correction, and who may authorize a documented override. Review override activity periodically.

Year-end and provider-handoff checklist

• Reconcile vendor statements and the payable control account
• Resolve old debit balances, credits, and unapplied payments
• Confirm tax-information records required for current filings
• Retain payment registers and approval evidence
• Document recurring accruals and cutoff review
• Export vendor detail and open-item reports
• Remove access for departed staff and former providers