Accounts Payable Process: Steps & Best Practices

The accounts payable process is the workflow a business uses to receive supplier invoices, validate what is owed, resolve discrepancies, obtain approval, schedule payment, and reconcile the transaction after payment. A strong process helps Finance pay valid obligations on time while preventing duplicate, incorrect, or unauthorized payments and maintaining accurate financial records.

At a practical level, the workflow looks like this:

Invoice received → Validate → Match → Code & resolve exceptions → Approve → Pay → Reconcile

The goal is not simply to process invoices as quickly as possible.

A reliable accounts payable process balances:

speed + accuracy + control + cash timing

so Finance can meet supplier obligations without sacrificing working capital or financial governance.

The Accounts Payable Process at a Glance

This is the core operating workflow.

Upstream activities such as supplier sourcing, RFPs, purchasing negotiation, and requisitions belong more broadly to procure-to-pay, while this article focuses specifically on how AP handles the supplier obligation from invoice through payment and reconciliation.

For the broader lifecycle view, see Accounts Payable Cycle: Stages, Controls & Examples.

How the Accounts Payable Process Works

Stage 1: Receive and Capture the Invoice

The process begins when a supplier invoice enters the organization.

Invoices may arrive through:

• Dedicated AP email
• Supplier portal
• E-invoicing platform
• ERP integration
• Scanned documents

A decentralized intake process creates unnecessary risk.

If suppliers send invoices directly to individual employees, Finance may not know:

• whether an invoice was received,
• when the payment clock started,
• or whether another copy has already entered the system.

A stronger model uses a controlled invoice channel and records the document as soon as it arrives.

Important fields can include:

supplier → invoice number → invoice date → PO → amount → tax → currency → due date

At this stage, the objective is completeness rather than payment approval.

Stage 2: Validate Supplier and Invoice Data

Before an invoice moves further, AP should confirm that the basic information is valid.

Typical checks include:

• Is the supplier active and authorized?
• Does the supplier name match the vendor master?
• Has this invoice already been processed?
• Is the invoice number valid?
• Is the legal entity correct?
• Does the invoice contain required tax information?
• Are bank-detail changes involved?

Duplicate detection is particularly important.

A supplier may send the same invoice through email and a portal, or resend it when payment status is unclear.

Without a reliable validation step, the same obligation can enter the accounts payable process twice.

Stage 3: Match the Invoice to Supporting Records

For PO-based purchases, AP needs evidence that the supplier is billing consistently with the underlying transaction.

Depending on the purchasing policy, this may involve:

Two-Way Matching

Compare:

Purchase Order ↔ Invoice

This confirms that quantities or amounts billed align with the approved order.

Three-Way Matching

Compare:

Purchase Order ↔ Receipt ↔ Invoice

This adds proof that the organization actually received the goods or services being billed.

Oracle’s current Payables documentation similarly distinguishes two-way and three-way matching and requires the relevant quantities to match within configured tolerances before payment can proceed.

For the control in detail, see 3-Way Matching in Accounts Payable.

Matching Tolerances

A mismatch does not always mean the invoice is wrong.

Legitimate differences may come from:

• Freight
• Tax
• Rounding
• Partial receipt
• Approved price variance

Businesses can define tolerances so immaterial differences do not create unnecessary approval work.

Stage 4: Code the Invoice and Resolve Exceptions

Once the obligation is validated, the invoice needs to be assigned to the correct accounting records.

Coding can include:

• GL account
• Cost center
• Department
• Entity
• Project
• Tax treatment

Recurring invoices may follow predefined coding rules.

More complex invoices may need internal judgment.

The more important issue at this stage is exception handling.

An invoice might fail because of:

• Missing PO
• Missing receipt
• Quantity difference
• Price difference
• Incorrect supplier
• Tax issue
• Missing approval

Each exception should have an owner.

A mature accounts payable process should follow:

Exception → Owner → Resolution time → Escalation

rather than allowing invoices to sit in an inbox while AP asks several teams for help.

Stage 5: Route the Invoice for Approval

A validated invoice still needs appropriate authorization.

Approval rules can depend on:

• Invoice amount
• Department
• Entity
• Cost center
• Spend type
• Project
• Exception status

Approval workflows should reflect risk.

A $300 recurring utility invoice does not necessarily require the same approval structure as a $300,000 equipment purchase.

Too many approval layers can also become a process problem.

Oracle Payables supports rule-based approval workflows where invoices requiring approval cannot proceed to payment until the appropriate approvals are completed.

A useful performance measure here is:

approval aging

because it separates time spent waiting for management from time spent inside AP.

Stage 6: Schedule and Execute Payment

Approved does not mean:

Pay immediately.

It means:

The obligation is ready to be scheduled according to payment terms and cash strategy.

Suppose an invoice is approved on June 5 but due June 30.

Paying on June 5 may unnecessarily reduce available cash unless:

• there is an early-payment discount,
• contractual terms require it,
• or another commercial reason exists.

Payment preparation can include:

• Due-date review
• Payment proposal
• Cash requirement
• Payment batch
• Bank upload
• Remittance information

The business should maintain appropriate segregation between:

preparing the payment

and

authorizing the release of cash.

Where practical, one person should not independently be able to:

create supplier → enter invoice → change bank details → approve → release payment.

Stage 7: Reconcile and Close the Transaction

Payment is not the end of the accounts payable process.

Finance still needs to make sure the accounting records reflect what actually happened.

That can involve:

• Clearing the supplier liability
• Applying credit notes
• Resolving rejected payments
• Matching bank activity
• Reconciling AP subledger to GL
• Reviewing outstanding items

The basic relationship is:

Supplier balance → AP subledger → General Ledger → Bank

Unreconciled differences can affect:

• Expenses
• Liabilities
• Cash
• Working capital
• Month-end close

This is why reconciliation belongs inside the AP process rather than being treated as a separate afterthought.

AP reconciliation is also one input into the wider financial close. Finance teams can use this month-end close process checklist to connect AP cutoff and reconciliation with AR, payroll, accruals, intercompany, GL review, and final reporting.

What Happens When an Invoice Does Not Follow the Standard Path?

The standard workflow should be straightforward:

Invoice → Match → Approve → Pay

But AP performance is often determined by the invoices that do not follow that path.

Consider three examples.

Missing Receipt

AP has:

PO ✓

Invoice ✓

Receipt ✕

The invoice cannot complete the required 3-way match.

Possible root cause:

Goods were delivered, but Operations never entered the receipt.

Adding more AP headcount will not fix the underlying issue.

The correct action is to improve receiving discipline.

Price Mismatch

PO:

$100/unit

Invoice:

$108/unit

AP should not guess which figure is correct.

The discrepancy should move to the appropriate Procurement or business owner for review.

Invoice Approved but Still Paid Late

Suppose:

Invoice processing = 1 day

Approval = 2 days

but payment is still 10 days late.

The problem may sit in:

• Payment scheduling
• Treasury workflow
• Bank release

not AP processing itself.

These distinctions are why troubleshooting should follow root cause rather than symptoms.

For a full diagnostic framework, see Accounts Payable Challenges: Causes, Risks & Solutions.

Key Controls Across the Accounts Payable Process

Good AP controls should reduce payment risk without turning every invoice into a manual investigation.

Vendor Master Controls

Supplier creation and bank-detail changes should follow defined authorization procedures.

Use this vendor master data controls checklist to review supplier onboarding, sensitive changes, approval ownership, and the evidence required before updated records are used for payment.

Duplicate Detection

Invoices should be checked against supplier, invoice number, amount, date, and other relevant attributes.

Matching

PO-based invoices should follow the appropriate matching rule.

Approval Matrix

Authority should reflect transaction value and risk.

Segregation of Duties

Preparation and final payment authority should be appropriately separated.

Audit Trail

The organization should be able to determine:

who entered → who changed → who approved → who paid

a transaction.

Controls work best when they are embedded in the workflow rather than added as a separate manual review at the end.

AP controls also feed into the wider accounting review process. Controllers can use this accounting review and quality control checklist to validate whether AP balances, supporting documents, coding, duplicate risks, and unusual account positions are ready for financial reporting.

How to Measure Accounts Payable Process Performance

Do not measure AP only by the number of invoices processed.

A useful scorecard covers speed, quality, controls, and capacity.

APQC’s 2026 Accounts Payable benchmarking framework includes cost per invoice, first-time error-free disbursements, and invoice-to-payment cycle time among its key AP performance measures.

APQC also reports a cross-industry median of 4.7 calendar days from invoice receipt until approval and scheduling for payment across a sample of 8,686 companies. That figure is useful as context, but it should not be treated as a universal target because invoice complexity and operating environments differ.

For a broader measurement framework, see Accounts Payable Metrics: How to Measure AP Performance.

How to Improve the Accounts Payable Process in the Right Order

Technology should not automatically be Step 1.

Use this sequence.

Map the Current Workflow

Document:

Input → Owner → Action → Output → Exception

for every stage.

Measure Where Work Waits

Separate:

• Invoice capture time
• Matching time
• Exception time
• Approval aging
• Payment scheduling

This prevents Finance from solving the wrong problem.

Reduce Upstream Errors

If invoices frequently arrive without valid POs or receipts, improve Procurement and Receiving before adding more AP automation.

Define Exception Ownership

Every common exception should have:

• Owner
• Response expectation
• Escalation path

Automate Standard Transactions

Once the process is stable, technology can support:

• Invoice capture
• Data extraction
• Duplicate checks
• Matching
• Workflow routing
• Payment preparation
• Reporting

Review Capacity

If:

process stable + accuracy stable + productivity stable

but:

volume ↑ + backlog ↑

then the problem may simply be insufficient AP capacity.

Where External AP Support Can Fit

Businesses do not need to transfer financial control to move transactional AP work outside.

A practical responsibility split can look like:

This allows external teams to absorb recurring execution while internal Finance retains judgment, cash authority, and control.

External support becomes particularly relevant when:

• Invoice volume is growing
• AP backlogs repeatedly return
• Senior finance employees spend too much time on transaction processing
• Month-end close is being delayed
• New entities add workload
• The process is stable but available capacity is not

Businesses evaluating additional AP or broader finance capacity can explore Innovature Finance & Accounting Outsourcing Services.

Accounts Payable Process Review

If several areas are weak, the priority should be process stabilization.

If the process is controlled but backlog continues to rise, investigate capacity.

If the process is stable but repeated manual handoffs remain, investigate technology and integration.

That is the role this URL should own: how the accounts payable process works and how to improve its execution, not AP troubleshooting, software selection, or the wider procurement lifecycle.