24 questions foundUnder self-billing, the buyer raises the invoice on the supplier's behalf (per an agreement), common where the buyer determines the quantity/value (e.g., commissions, royalties, scrap). It streamlines processing and guarantees data quality, but requires a formal agreement and correct tax handling so both parties report consistently.
Real-world example A manufacturer self-bills its subcontractors based on approved output, removing supplier invoice-entry errors.
Common follow-ups: When is self-billing useful? | What agreement does it require?
Vendor Management Purchase Orders & 3-Way Matching Invoice Processing
Recurring invoices for fixed, periodic charges can be automated with recurring-payment templates or standing entries that post on schedule, sometimes without a fresh invoice each period. Controls include periodic review to confirm amounts and that the service continues, preventing payment for cancelled services.
Real-world example Monthly rent posts automatically via a recurring template, with a quarterly review to confirm the amount and lease still apply.
Common follow-ups: What's the risk of automated recurring payments? | How are recurring amounts controlled?
Payment Runs Vendor Management Invoice Processing
Revenue (operating) expenditure is consumed in the period and expensed; capital expenditure creates or improves a long-term asset and is capitalized then depreciated. Correct coding at invoice stage ensures assets aren't expensed (understating profit) or expenses capitalized (overstating profit), affecting tax and the balance sheet.
$20,000 for a new machine -> Dr Fixed Assets (capitalize, depreciate).
$2,000 for machine servicing -> Dr Repairs Expense (revenue).
Real-world example An invoice for a new server is capitalized and depreciated, while a repair invoice is expensed—driven by correct coding.
Common follow-ups: How do you decide capital vs revenue? | What's the impact of miscoding?
Reconciliations Invoice Processing Purchase Orders & 3-Way Matching
Variable recurring invoices (utilities, telecom) can't use fixed recurring templates, so control relies on reasonableness checks against prior periods/budgets, approval routing, and trend monitoring to catch spikes or billing errors. Consumption analytics and consolidated billing help flag anomalies before payment.
Real-world example A utility invoice 60% above the prior month is flagged for review, revealing a meter-reading error before it's paid.
Common follow-ups: Why can't variable invoices use fixed templates? | How are billing spikes caught?
Payment Runs Vendor Management Invoice Processing