Accounts Payable Management

01Purpose and scope

• This manual supports the course Accounts Payable Management. It describes how the accounts payable function works in practice, from the moment a supplier invoice arrives to the point where payment is released and the transaction is recorded in the general ledger. It is written as a working reference for accounts payable clerks, supervisors, controllers, and the operations staff who depend on them.
• The scope covers vendor setup and maintenance, invoice capture, matching to purchase orders and receipts, coding to accounts, approval routing, payment runs, payment method selection, duplicate and fraud screening, and month-end accruals for unposted liabilities. It also touches on how accounts payable interacts with procurement, receiving, treasury, and internal audit.
• The manual does not cover accounts receivable, payroll, or tax filing, although accounts payable records feed into several of those areas. Practices vary by company size, enterprise resource planning system, industry, and country. Where rules depend on jurisdiction, such as withholding tax on payments to contractors, unclaimed property reporting, or electronic invoicing mandates, check the current requirements with the relevant tax authority or qualified adviser. This guidance does not replace qualified professional judgment, your organization's approved procedures, or any required authorization from finance leadership.

02Core principles

• Accounts payable exists to pay the right amount, to the right supplier, at the right time, and to record it accurately. Those four goals pull against each other. Paying early may earn a discount but strain cash. Paying late may protect cash but damage supplier relationships and create penalty charges. A good process makes the trade-off visible rather than letting it be decided by whoever happens to be processing that day.
• Every payment should be supported by evidence that the goods or services were received, the price agrees with the agreed terms, and the person approving the payment had the authority to do so. This is the logic behind the three-way match, which compares the purchase order, the goods receipt or service confirmation, and the supplier invoice. When one of the three is missing, the item should be treated as an exception rather than forced through.
• Segregation of duties is the most important structural control. The person who creates or changes a vendor record should not also approve invoices for that vendor or release payments. The person who approves a payment should not be the one who keys the bank details. In small teams full segregation may not be possible, so compensating controls such as independent review of vendor master changes and periodic reports of activity become essential.
• Data quality drives everything else. Vendor master records, tax identification numbers, bank account details, chart of accounts codes, and tolerance settings all determine whether the automated and manual steps produce reliable results. Errors made in master data repeat with every invoice, which is why maintenance deserves as much attention as transaction processing.

03Planning and preparation

• Before running the process, agree on the policies that govern it. These include payment terms standards, approval limits by amount and cost center, tolerance thresholds for price and quantity differences, acceptable payment methods, and the cutoff times for each payment run. Write them down and get sign-off from the controller or chief financial officer. Most disputes later trace back to a policy that existed only in someone's memory.
• Map the stakeholders and their roles. Accounts payable clerks capture and match invoices. Accounts payable supervisors resolve exceptions and manage the queue. Buyers or procurement staff confirm pricing and purchase order changes. Receiving staff or budget owners confirm that goods or services were delivered. Treasury decides the funding and timing of payment runs. Internal audit or the compliance function tests whether the controls operate as designed.
• Choose the tools. Many organizations use an enterprise resource planning module for purchasing and payables, supplemented by optical character recognition or an invoice capture platform that reads incoming documents. Smaller businesses may rely on a dedicated accounts payable application or even spreadsheets with strict file controls. The tool matters less than whether it enforces the approval hierarchy, keeps an audit trail, and prevents duplicate invoice numbers from the same supplier.
• Prepare the vendor master. Confirm that each active supplier has a legal name, a tax identification number where required, verified remittance details, and the payment terms agreed in the contract. Verify bank account changes by calling the supplier on a known number, not the number supplied in the change request. This single step blocks a large share of payment fraud attempts, and it should be a fixed procedure rather than a judgment call.

04Recommended workflow

1. 1
   : Receive and log every invoice in one designated inbox, portal, or capture queue. Assign a unique internal reference number on arrival and record the date received. Invoices sent to individual employees should be forwarded to the central queue the same day so that the aging clock and the audit trail start at the correct point.
2. 2
   : Capture the key fields accurately. These include supplier identifier, invoice number, invoice date, due date, currency, line items, quantities, unit prices, taxes, and total amount. Check that the invoice number is not already recorded for that supplier, since duplicate invoices are one of the most common sources of overpayment.
3. 3
   : Match the invoice to the purchase order and the goods receipt or service entry. For goods, the usual check is quantity received against quantity invoiced and unit price against the purchase order price. For services, the receiving confirmation usually comes from the budget owner who certifies that the work was performed. Invoices within the agreed tolerance may be released automatically, while those outside it go to an exception queue.
4. 4
   : Resolve exceptions with the right owner. A price variance usually goes to the buyer, a quantity variance to receiving, and a missing purchase order to the requester or the buyer depending on the policy. Record the reason for each exception and the resolution. Avoid resolving exceptions by phone without a written note, because the reasoning disappears when staff change roles.
5. 5
   : Code the invoice to the general ledger. Assign the expense or asset account, the cost center, the project or department code, and any tax coding. Review coding for unusual patterns, such as a recurring supplier suddenly charged to a capital account, since miscoding affects financial statements and budget reports.
6. 6
   : Route for approval according to the delegation of authority matrix. Approval limits usually depend on invoice value and cost center. Approvers should see the supporting documents, not just a summary, and should confirm that the amount is consistent with the budget. Approval should be recorded in the system with the approver's identity and time stamp.
7. 7
   : Schedule and release payment. Group approved invoices into payment runs according to the agreed calendar and the due dates. Use early payment discounts where the return exceeds the cost of cash, and confirm the decision with treasury. Before release, a second person should review the payment file totals against the approved list, and any change to bank details should already have passed verification.
8. 8
   : Reconcile and close. Match payments to the bank statement, clear the open items in the payables subledger, and confirm that the general ledger control account agrees with the subledger. At period end, accrue liabilities for goods received but not yet invoiced, using the receiving log. Reverse those accruals when the invoices arrive so they are not counted twice.

05Quality checks, risk controls and compliance

• Build checks into each stage rather than relying on a single review at the end. Useful routine controls include a daily report of new and changed vendor records, a weekly review of invoices paid without a purchase order, a monthly check for duplicate invoice numbers across suppliers with similar names, and a sample test of approvals against the delegation matrix. Document the results and the follow up actions.
• Payment fraud deserves specific attention. Common patterns include business email compromise, where a message appears to come from a senior executive or a supplier asking for an urgent payment or a change of bank details, and invoice redirection, where an attacker sends a fake invoice with altered remittance information. Controls include call back verification to known numbers, dual approval for bank changes, restricted access to the payment file, and staff training on these specific schemes. The procedure should be written so that a clerk can follow it under time pressure without needing to escalate every case.
• Compliance obligations depend on where the organization operates. Some jurisdictions require withholding tax on certain payments to individuals or foreign suppliers, and some require the collection of tax identification numbers before payment. Electronic invoicing and reporting requirements are changing in many places, so confirm the current rules with the relevant tax authority or a qualified tax adviser. Retention periods for invoices and supporting documents also vary by jurisdiction and by tax or statutory rules that apply to the entity.
• Sanctions screening and anti-money-laundering checks may apply to payments to some suppliers or countries. Where the organization is subject to these rules, screening should happen when a vendor is set up and again before payment, and the results should be retained. This guidance does not replace the advice of a qualified compliance professional or the approved sanctions procedure of your organization.

06Collaboration and documentation

• Accounts payable depends on buyers, receiving teams, budget owners, and suppliers. Set service expectations for each group. For example, receiving confirmation for invoices over an agreed value might be expected within two working days, and buyers might be expected to resolve price variances within the same window. Track these expectations and share them with managers, because most aging invoices are waiting on someone outside the team.
• Keep a clear record for every invoice. The file should hold the invoice image, the purchase order, the receiving evidence, any correspondence about exceptions, the coding decision, the approval trail, and the payment reference. A reader who was not involved should be able to reconstruct the decision from that file. Store the documents in a system with access controls and retention rules rather than in personal folders.
• Document the procedures themselves. A current desk procedure for each task, a list of approved payment methods, a contact sheet for escalation, and a change log for policy updates make training and audit far easier. Review these documents at least once a year or when the system or policy changes, and retire versions that no longer apply.
• Supplier communication matters. Give suppliers a single contact address, a published remittance and invoice submission guide, and a clear statement of what information an invoice must contain. Respond to queries in a consistent way. Suppliers who receive clear answers are less likely to chase payment by phone or send duplicate invoices.

07Measures and continuous improvement

• Measure the process in a few meaningful ways. Common indicators include the percentage of invoices processed without manual intervention, the average time from receipt to approval, the percentage of invoices paid by the due date, the number of duplicate payments detected after release, and the cost per invoice. Set targets based on your own history and peer comparisons from trusted benchmarking sources, not on figures quoted without a source.
• Look at exception rates by cause. If most exceptions come from price variances, the problem may lie with purchase order pricing or supplier price increases not being loaded. If many invoices arrive without purchase orders, the cause may be an ordering habit in one department rather than a failure in accounts payable. Targeted fixes produce better results than general exhortations to work faster.
• Review the results regularly with the people who can change the process. Monthly reviews with the controller, and quarterly reviews that include procurement and receiving, usually provide enough feedback without overwhelming staff. Record decisions and check whether they worked at the next review.
• The trade-offs have limits. Automation reduces manual effort but can accept incorrect data quickly if the master data or tolerance settings are poor. Tight tolerances reduce overpayment but increase exception volume. Extended payment terms protect cash but may reduce supplier goodwill and eligibility for discounts. Choose settings that match the risk profile of each category of spend, and revisit them when volumes or suppliers change.

08Common mistakes and how to prevent them

• Paying from invoices alone without a purchase order or receiving evidence is a frequent error. It removes the checks that show the goods or services were actually received. Prevent it by configuring the system to block payment without matching evidence above a set value, and by requiring a documented exception approval for any manual override.
• Allowing one person to create vendors, enter invoices, and release payments is another common weakness. Even in a small team, separate the vendor master maintenance from payment release, and have a second person review vendor changes. Periodic access reviews help catch permissions that were granted for a project and never removed.
• Ignoring duplicate invoices is costly. Suppliers sometimes resend invoices, and staff sometimes key the same invoice twice under different numbers. Use the system's duplicate check on supplier and invoice number, and also check amount and date within a short window. Investigate any hit before payment rather than after.
• Accepting bank detail changes by email is the mistake most often linked to fraud losses. Make call back verification to a known number a mandatory step, record the verification, and require a second approver for the change. Treat any urgent request to change payment details as a warning sign rather than a reason to hurry.
• Accruing poorly at month end distorts reported results. Failing to record goods received but not invoiced understates liabilities, while leaving reversed accruals in place overstates them. Use a standard accrual report, review it with receiving and budget owners, and reverse accruals when the invoices are posted.
• Letting exception queues grow without owners is a process failure rather than a staffing problem. Assign each exception type to a named role, set an aging limit, and report the aged items to managers each week.

09Practical checklist

• Confirm that each vendor record has a verified legal name, tax identification where required, and bank details checked by call back to a known number.
• Log every invoice on arrival with a unique internal reference and the date received.
• Check for duplicate supplier and invoice number combinations before entering any invoice for payment.
• Match each invoice to its purchase order and receiving or service confirmation, and route variances outside tolerance to a named owner.
• Record the reason and resolution for every exception in the invoice file.
• Confirm coding to the correct general ledger account, cost center, and tax treatment before approval.
• Route approvals according to the current delegation of authority matrix and record the approver identity and time.
• Have a second person review each payment file total against the approved list before release.
• Reconcile payments to the bank statement and clear the payables subledger at each period end.
• Accrue goods received but not invoiced at period end and reverse those accruals when invoices post.
• Review vendor master changes, duplicate reports, and approval samples on a fixed schedule and record the results.
• Confirm current withholding, sanctions, and invoicing rules with the relevant authority or a qualified adviser for each jurisdiction in which you pay suppliers.

10

★Learning sources

• Micro Degree: Accounts Payable Management
• Micro Degree: Bank Reconciliation Operations
• Micro Degree: FinTech Fundamentals
• Micro Degree: Digital Payment Systems