Accounts Payable & Receivable
Vendor Management
The vendor master file is the central record of each supplier: legal name, addresses, contacts, tax IDs, bank/remittance details, payment terms, currency, and status. Accurate vendor master data underpins correct payments, tax reporting, and duplicate/fraud prevention, so changes to it are tightly controlled.
Real-world example
Before a supplier can be paid, AP sets up a complete, verified vendor master record with validated bank details and tax ID.
Invoice Processing
Payment Runs
Vendor Management
Vendor onboarding is setting up a new supplier before transacting: collecting legal and tax details (e.g., W-9/W-8 or VAT registration), validating bank details, screening against sanctions/denied-party lists, checking for duplicates, and agreeing payment terms. Good onboarding prevents payment errors, tax issues, and dealing with prohibited parties.
Real-world example
A new supplier is screened against sanctions lists and its bank details verified by call-back before the first PO is raised.
Vendor Management
Credit Control
Invoice Processing
Payment terms define when payment is due and any early-payment discount, e.g., 'Net 30' (due in 30 days) or '2/10 Net 30' (2% discount if paid within 10 days, otherwise full amount in 30). Terms affect cash flow, working capital, and supplier relationships, and are stored on the vendor master and PO.
2/10 Net 30 on a $10,000 invoice:
Pay within 10 days -> 10,000 x 98% = 9,800 (save 200)
Otherwise pay 10,000 by day 30.
Real-world example
Finance pays a 2/10 Net 30 invoice early to capture the $200 discount, an attractive annualized return.
Payment Runs
Credit Control
Vendor Management
Changing a vendor's bank details is a prime target for fraud (business email compromise): a fraudster poses as a supplier and requests a new account. Controls include independent verification via a known phone number (call-back), dual approval of master changes, logging who changed what, and never using contact details from the change request itself.
Real-world example
An emailed request to change a supplier's bank account is verified by calling the supplier's known number, exposing a fraud attempt.
Invoice Processing
Payment Runs
Vendor Management
Duplicate vendors (same supplier set up twice with slight name/address variations) cause duplicate payments and fragmented spend. Prevent them with fuzzy-matching checks on name, tax ID, and bank account at creation, periodic cleansing, and standardizing naming conventions. Deactivate duplicates and merge history rather than deleting.
Real-world example
A cleansing exercise finds 'ABC Ltd' and 'A.B.C. Limited' share a tax ID; the duplicate is merged, consolidating spend visibility.
Reconciliations
Invoice Processing
Vendor Management
It compares the supplier's statement of what they say you owe against your AP ledger for that vendor, identifying missing invoices, unapplied credits, duplicate entries, or disputed items. Doing it regularly for key suppliers prevents surprises, catches errors and missed credits, and keeps the payable accurate.
Supplier statement balance: 45,000
Our AP ledger: 41,000
Difference 4,000 = 2 invoices not yet received + 1 credit not applied.
Real-world example
A statement reconciliation reveals an unrecorded $3,000 invoice and a missed $1,000 credit, correcting the balance before month-end.
Reconciliations
Aging Analysis
Vendor Management
Segmenting vendors (e.g., strategic, tactical, tail spend) lets you focus effort where it matters: negotiate terms and reconcile statements with strategic suppliers, automate and consolidate tail spend, and set risk-based onboarding. It improves working capital, reduces the supplier count, and targets relationship management efficiently.
Real-world example
The company concentrates 80% of spend with 40 strategic vendors and moves hundreds of tail suppliers onto a purchasing card program.
Credit Control
Payment Runs
Vendor Management
Static discounts are fixed terms like 2/10 Net 30. Dynamic discounting offers a sliding discount that shrinks the closer payment is to the due date, often via a portal, letting buyers deploy surplus cash for a return and suppliers choose when to accelerate payment. It's flexible and demand-driven rather than a single fixed rate.
Dynamic: 2% if paid day 5, ~1.3% if paid day 15, 0% at day 30.
Buyer earns a return on early cash; supplier picks the trade-off.
Real-world example
With idle cash, treasury funds early payments through a dynamic discounting portal, earning better returns than its bank deposits.
Payment Runs
Credit Control
Vendor Management
In supply chain finance, a bank/financier pays the supplier early on approved invoices, and the buyer pays the financier at the original due date. It lets suppliers get paid sooner at a rate based on the buyer's stronger credit, while the buyer can extend or keep its terms. It differs from factoring, which is initiated by the supplier.
Real-world example
Strategic suppliers opt into the buyer's SCF program to receive early payment at a low financing rate tied to the buyer's credit rating.
Credit Control
Payment Runs
Vendor Management
If a buyer's payables under an SCF program take on characteristics of bank debt (e.g., extended terms, bank involvement), auditors and standard-setters may require reclassifying them from trade payables to borrowings, and disclosing the program. Misclassification can understate leverage, so terms and program structure must be assessed carefully.
Real-world example
Regulators require a company to disclose its SCF program after concerns that large 'payables' were effectively short-term debt.
Reconciliations
Vendor Management
Credit Control