How to Set Up AP Automation: Vendor Master, Approval Matrix and Coding Rules

To set up AP automation, clean the vendor master, build an approval matrix by amount and department, set GL coding rules and defaults, map each vendor's payment method, and define exception queues with named owners.

That's the configuration work, and it decides whether the software removes manual steps or just moves them to a new screen. Choosing the platform gets most of the attention. The weeks after the contract is signed, when someone on the AP team sits down with a configuration workbook, get much less, and that's where the results are won or lost.

Key Takeaways

• Setup is five configuration decisions in a fixed order, starting with the vendor master and ending with exception queues.

• A clean vendor master comes first because approval rules, coding defaults, and payment methods all hang off the vendor record.

• An approval matrix should route by amount and department, with thresholds high enough that routine invoices need one approver.

• Coding rules and vendor defaults let the system code most recurring invoices without anyone touching them.

• Manual steps that survive setup usually live in exceptions, so every exception type needs a queue, an owner, and a target turnaround.

How do you set up AP automation for invoices?

Set up AP automation in five steps, each building on the one before. Here's the order and the decision each step forces:

1. Clean the vendor master. Decide which records to merge, retire, or fix, and verify bank details before import.

2. Build the approval matrix. Decide who approves what, by dollar amount and department.

3. Set GL coding rules. Decide default accounts by vendor, how PO-backed invoices code, and when the system may code without review.

4. Map payment methods. Decide whether each vendor gets paid by virtual card, ACH, or check.

5. Define exception queues. Decide where every invoice that can't flow through goes, and who clears it.

The order matters more than it looks. Teams that start with the approval matrix because it feels like the interesting part usually rebuild it after vendor cleanup, when they find a pile of duplicate vendors and approval rules pointing at people who'd left. How long all of this takes depends on your vendor count and ERP, and the AP automation implementation timeline covers durations by phase.

How do you clean the vendor master before setup?

Clean the vendor master by merging duplicates, retiring inactive vendors, filling in missing tax and bank details, and verifying every bank account before it's imported. Every later setup step depends on the vendor record, so mistakes here multiply.

Which vendor records should you merge, update, or retire?

Merge duplicates, flag vendors with no payments in the last 18 months or so for review, and update any record missing a tax ID, remit-to address, or payment terms. Pull a vendor list from the ERP with last payment date, total spend, and tax ID, and sort it a few ways before you touch anything.

Treat that 18-month flag as a review trigger, not an automatic retirement. Before deactivating a flagged vendor, confirm none of these exist and get a sign-off from the business owner who uses that vendor.

• Open invoices or open purchase orders

• Unapplied credits or active contracts

• Uncashed checks

Annual and seasonal suppliers often look dormant and aren't.

Duplicates show up in predictable forms. The same vendor appears as "ABC Supply," "ABC Supply Inc.," and "ABC Supply Co." with three addresses, or one tax ID sits on two records with different bank accounts. The second case deserves a closer look than the first, since it's sometimes an innocent remit change and sometimes not. Merging duplicates before go-live also gives duplicate payment detection a fair chance, because the system can't flag a repeat invoice from a vendor it thinks is two different companies.

Tax details are worth fixing now rather than in January. The IRS backup withholding rules require payers to withhold at 24% when a payee fails to provide a correct taxpayer identification number. Collect missing W-9s during cleanup and run the IRS TIN matching program against the vendor list before import.

How should bank details be verified before import?

Verify every vendor bank account by calling the vendor at a phone number already on file, never one supplied in the same email as the bank details. Then import only verified accounts and hold the rest until they're confirmed.

It's tempting to import the bank data you already have, on the theory that it worked last month. The problem is that a vendor master migration is exactly when nobody notices a change. According to the AFP's 2026 Payments Fraud and Control Survey, 74% of organizations were affected by business email compromise in 2025, and 76% experienced attempted or actual payments fraud. Set up the new system so a bank-detail change requires a second approver, and turn that rule on before the first vendor is loaded.

How do you build an approval matrix by amount and department?

Build an approval matrix by setting dollar thresholds for each department, naming one approver per threshold, and keeping the number of levels as low as your controls allow. The goal is that a routine invoice needs one approval and a large or unusual one needs two.

A simple matrix for a single-entity company might look like this:

That last row does a lot of work. When an invoice matches its purchase order and receipt within tolerance, the spending decision was already approved on the PO, so routing it through approval again adds a manual step without adding control. Three-way matching is what earns that row its place.

Two mistakes come up again and again. The first is setting the CFO as approver on too many rows, which turns one person's travel week into an AP backlog. The second is forgetting delegates, so an approver on vacation stops every invoice in their department. Name a delegate for every approver in setup. The deeper design questions, including conditional routing and segregation of duties, are covered in designing an invoice approval workflow.

Protect cash flow with modern AP

Modernize AP to cut costs, speed approvals, and mitigate payment risk — gaining the real-time visibility to protect cash flow and scale with confidence.

Download the whitepaper

How do you set GL coding rules and defaults?

Set GL coding rules by assigning a default account and department to each recurring vendor, letting PO-backed invoices inherit coding from the PO, and defining which invoices the system may code without a person reviewing them. Done well, most recurring invoices arrive already coded.

Vendor defaults carry the most weight. Your utility company, your software subscriptions, and your cleaning service bill the same accounts every month, so the system should code them the same way every month. Start with your top 100 vendors by invoice count, since they usually cover most of the volume.

For the rest, set rules for splits and thresholds. Decide which vendors split across departments by a fixed percentage, which invoices need line-level coding, and the dollar amount above which a coded invoice gets a human look regardless of confidence. The invoice coding practices that apply in a manual process still apply here. Automation just applies them consistently.

Your chart of accounts sets the ceiling on all of this. APQC data reported by CFO.com in "Metric of the Month: Cycle Time for Monthly Close" found that organizations with widespread adoption of a standard chart of accounts shave about two days off their monthly consolidated statements. If your chart has six accounts that all mean "office supplies," fix that before you build coding rules on top of it.

How do you map payment methods to each vendor?

Map payment methods by assigning each vendor the lowest-cost method it accepts, usually virtual card first, ACH second, and check only when the vendor requires it. Store the method on the vendor record so every invoice pays the same way without a decision at payment time.

Sort vendors into groups. Vendors that already accept cards are candidates for virtual card payments, which earn rebates. Vendors that take ACH but not cards go to ACH, and ACH volume keeps growing, with Nacha's 2025 ACH Network report counting close to 8.1 billion B2B payments in 2025, up almost 10%. The remaining vendors stay on checks for now, and the comparison of B2B payment methods by cost and fraud risk is useful when deciding how hard to push each group.

Some will stay on checks for a while. The AFP survey found that 72% of organizations that use checks plan to keep using them, and 68% of those cite vendor requirements. Setup is the time to accept that and plan for it. Corpay pays suppliers by virtual card, ACH, or check from one approval flow, so the vendors who insist on checks don't need a separate process.

Mapping is easy. Enrollment is the work. Someone has to contact each vendor's receivables team, explain the change, and confirm details, and the patterns that make vendor enrollment for virtual cards succeed apply to ACH conversions too.

How do you reduce manual steps in accounts payable?

Reduce manual steps in accounts payable by configuring vendor defaults, matching rules, and approval thresholds so most invoices need no touch, then routing every remaining exception to a named queue with an owner and a turnaround target. The manual work that survives automation lives in exceptions.

Manual handling is where the cost sits. APQC data reported by CFO.com in "Metric of the Month: Accounts Payable Cost" put the median cost to process an invoice at $5.83 in 2018, with top performers at $2.07 or less and the bottom quarter at $10 or more. Much of the gap between those groups is how many invoices someone has to open, and the reasons invoices fall out of a touchless invoice processing flow are mostly configuration problems.

Set up queues like these:

Give each queue one owner, not a shared inbox. Then look at the queues weekly for the first two months. A queue that keeps filling up for the same reason is a setup problem you can fix, such as a tolerance set too tight or a vendor default that's wrong, and keeping exceptions from becoming the rule is mostly that weekly habit.

What should you ask a vendor to configure for you?

Ask the vendor exactly which configuration steps their team does, which ones your team does, and which ones cost extra. The answer varies a lot between providers, and it decides how much of this page lands on your AP team.

Questions worth asking before you sign:

• Who cleans and de-duplicates the vendor master, and who verifies bank details?

• Who builds the approval matrix in the system, and how do we change it later without a support ticket?

• Who writes vendor coding defaults, and how does the system learn from corrections?

• Who contacts vendors to enroll them in card or ACH payments, and for how long after go-live?

• Who sets up exception queues, and who reports on them in the first 90 days?

The answer to the enrollment question matters most, because it's the step that never really ends. A managed provider keeps contacting vendors after go-live, and Corpay's fully managed AP includes that ongoing vendor outreach as part of the service rather than handing it back to your team.

How much to hand off is a judgment call. Some teams want to own their approval matrix and coding rules because they know the business best, and hand off only enrollment and payments. Others would rather hand off everything. I don't think there's a right answer, only an honest one about how much time your AP team has in the next quarter.

Let Corpay handle setup and supplier enrollment

The configuration steps take real time, and the most labor-heavy part, vendor enrollment, keeps going long after setup. Corpay takes that work off your team.

With Corpay AP automation, Corpay's team helps configure approvals and coding, enrolls your vendors, and pays each one by virtual card, ACH, or check from one approval flow. Customers save about 40% of the time spent on invoice processing, connect through 100+ ERP integrations including NetSuite, Sage Intacct, Business Central, and Acumatica, and are typically live in weeks. Card payments earn rebates, with Corpay paying customers more than $800M in rebates each year.

Frequently Asked Questions

What are the steps to set up AP automation?

Clean the vendor master, build an approval matrix by amount and department, set GL coding rules and vendor defaults, map each vendor's payment method, and create exception queues with owners. Doing them in that order avoids rebuilding approvals after vendor cleanup.

How long does AP automation setup take?

Configuration usually takes a few weeks inside a larger implementation, depending on vendor count, ERP integration, and whether the provider does the vendor cleanup and enrollment. Vendor master cleanup is typically the longest single step.

What is an approval matrix in accounts payable?

An approval matrix is a table that names who approves invoices at each dollar threshold for each department. AP automation uses it to route every invoice to the right approver automatically, including second approvers for large or unusual amounts.

What should be in a vendor master file?

A vendor master record should hold the legal name, tax ID and W-9, remit-to address, verified bank details, payment terms, payment method, default GL coding, and a contact for payment questions. Each field should have an owner for changes.

Can AP automation code invoices automatically?

Yes, for recurring vendors with coding defaults and for PO-backed invoices that inherit coding from the purchase order. Set a dollar threshold above which a person reviews coding, and correct defaults when the same fix keeps coming up.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

AP Automation

Payments Automation