Outsource Accounts Payable

Outsourcing accounts payable means an external provider handles invoice intake, matching, coding, entry, and payment preparation. You keep approval and payment release.

That division is not a limitation, it is the point. Handing over preparation while retaining authorisation creates separation of duties that a two-person business cannot otherwise achieve.

What the provider does

• Receives invoices through a single intake channel
• Validates against your vendor records and checks for duplicates
• Matches to purchase orders, quotes, or contracts
• Routes to your approvers and chases outstanding approvals
• Codes to the correct account, period, and job or class
• Enters into the accounting system
• Prepares the payment run for your release
• Reconciles the AP aging to the ledger and to supplier statements

What you must keep

Three things, without exception.

Payment release. The provider prepares; you release. If a provider offers to handle release as well, understand that you are giving up the single most valuable control in the process.

Bank statements delivered to you directly, not through the provider. If the party recording transactions also receives the statements, your ability to detect an error independently disappears.

Approval authority. Whether a charge should be paid at all is a commercial judgement about your business, not a processing decision.

The vendor bank detail rule

Verify vendor payment-detail changes through a known contact using an independently obtained channel. Separate the requester, processor, verifier, and payment releaser where staffing permits, and preserve the evidence and approval.

How the handover works

• Agree the intake channel and redirect suppliers to it
• Document approvers and thresholds
• Reconcile and clean the vendor master before transition
• Agree the coding convention and the payment run schedule
• Run a parallel period before switching fully

When it is worth it

• Invoice volume has become a real time cost
• You have no separation of duties and want one without hiring
• Invoices are being missed, paid late, or occasionally paid twice
• Nobody can currently say what is awaiting approval

AP may be bundled with bookkeeping or delivered separately. If providers are split, define ownership for invoice entry, coding, approvals, payment, reconciliation, close, and supplier communication.

Define the outsourced boundary

List invoice intake, vendor setup, bank-detail changes, purchase-order matching, coding, approval routing, entry, payment selection, bank release, supplier communication, reconciliations, close support, and reporting. Name which steps remain internal and who resolves tax, legal, purchasing, or contract questions.

Protect vendor and payment data

Separate vendor creation and sensitive changes from invoice approval and payment release where staffing permits. Verify bank changes through a known contact using an independently obtained channel. Require named access, multifactor authentication, change history, minimum privileges, periodic user review, and documented offboarding.

Design the workflow before transition

Use one controlled intake channel, required invoice fields, matching rules, coding standards, approval thresholds, backup approvers, exception reasons, escalation timing, and a payment calendar. Test duplicate invoices, credits, missing purchase orders, tax differences, changed bank details, and disputed services.

Keep payment authority explicit

Processing and approving an invoice does not by itself authorize bank release. Define who prepares the payment proposal, reviews due dates and credits, approves the batch, releases funds, records the payment, and reconciles the bank. Management should retain authority for unusual, disputed, or high-risk items.

Set close and reporting deliverables

Require an AP aging reconciled to the general ledger, vendor-statement review, unapplied credit log, unrecorded-liability search, payment forecast, exception queue, and cutoff support. Each report should state its date, population, exclusions, preparer, reviewer, and unresolved items.

Transition and exit checklist

• Starting aging and vendor master are reconciled
• Access and responsibility matrices are approved
• Recurring obligations and open exceptions are documented
• Historical invoices and approvals remain accessible
• Service levels and change rules are written
• Backup coverage and incident contacts are named
• Exit files, timing, and access removal are defined

Example onboarding sequence

First reconcile the vendor master, AP aging, bank and card accounts, recurring obligations, open purchase orders, credits, and recent payments. Then approve workflow rules and access in a test environment. Run representative invoices and exceptions in parallel with the existing process before transferring the live queue.

Set a cutover date and identify invoices received before and after it. Confirm who communicates with suppliers, who owns unresolved items, and how urgent payments are handled during transition. Reconcile the first completed cycle to the ledger and bank before closing onboarding.

Questions for a provider

Ask where work is performed, who has access, which subcontractors are used, how staff are trained, how bank changes are verified, how approvals are evidenced, what happens during an outage, how errors are corrected, which reports are delivered, and how the records are returned. Document answers in the engagement rather than relying on sales conversations.

Review the engagement after the first close and payment cycle. Compare actual exceptions, response time, reconciliations, access, errors, supplier questions, and internal effort with the agreed process, then approve corrective actions.