How do I set up invoice and payment-run bookkeeping for a SaaS startup with approval routing?

Here’s a practical way to set up invoice and payment-run bookkeeping for a SaaS startup with approval routing. I’ll frame it as a scalable AP/AR process you can implement in QuickBooks/Xero/NetSuite or similar, with controls that won’t be overkill for an early-stage company.

---

1) Define the process flow

You usually want two separate tracks:

A. Supplier invoices / accounts payable (AP)

1. Vendor invoice arrives
2. Invoice is coded to the right department / GL / project / contract
3. Invoice is routed for approval
4. Approved invoice is entered in accounting system
5. Invoice is included in a payment run
6. Payment is executed
7. Payment is recorded and matched to the invoice
8. Supporting docs are archived

B. Customer invoices / accounts receivable (AR)

1. Subscription usage / billing event triggers invoice
2. Invoice is reviewed if needed
3. Sent to customer
4. Payment received via ACH/card/wire
5. Cash is applied to open invoices
6. Dunning/collections follow if unpaid

If by “payment-run bookkeeping” you mean paying vendors, the rest of this answer focuses on AP, but I’ll include AR design where useful.

---

2) Set up your chart of accounts for SaaS

You don’t need a huge COA, but you do need enough granularity to manage SaaS-specific costs.

Common expense buckets

• Cloud hosting / infrastructure
• Software subscriptions
• Contractors / professional services
• Marketing spend
• Payroll and payroll taxes
• Sales commissions
• Travel and entertainment
• Office / general admin
• Legal / accounting
• Customer support tools
• Product / engineering tools

SaaS-specific items to think about

• Capitalizable software development vs expensed R&D, depending on your accounting policy and standards
• Deferred revenue for annual prepayments from customers
• Prepaids for annual software, insurance, hosting commitments
• Accrued expenses for vendor work performed but not yet invoiced
• Commissions amortization if you capitalize and amortize sales commissions

---

3) Create approval routing rules

Your approvals should be based on:

• Amount
• Department / cost center
• Vendor type
• Expense category
• Budget variance
• Payment method
• Entity / region if you have multiple legal entities

Simple approval matrix example

Invoice Amount	Approver(s)
<$500	Requester or team lead
$500–$5,000	Department manager
$5,000–$25,000	Finance + department head
>$25,000	CFO + CEO
Any unusual/one-off spend	Finance review + relevant manager

Add routing exceptions

• New vendor → finance review
• Non-PO invoice → extra review
• Contracted services → legal/procurement review
• Capex / software development costs → accounting policy review
• High-risk vendors or foreign payments → compliance review
• Budget overrun >10% → require budget owner approval

---

4) Establish a vendor onboarding process

Before an invoice can be paid, the vendor should be set up properly.

Required vendor onboarding data

• Legal name
• Tax ID / W-9 / W-8BEN/W-8BEN-E if applicable
• Address
• Payment method details
• Bank details
• Contact person
• Currency
• Contract / MSA / SOW
• Sanctions / fraud check if relevant

Controls

• Only finance can create or modify vendor bank details
• Bank detail changes require out-of-band verification
• New vendors require approval before first payment

---

5) Decide how invoices enter the system

You want one standard intake path.

Options

• Dedicated AP email inbox
• Bill capture tool (Ramp, Brex, Bill.com, Tipalti, etc.)
• OCR/scan upload
• Manual entry by finance

Best practice

Use a single AP inbox and a workflow tool that:

• captures invoice PDF
• extracts vendor, amount, due date
• routes for approval
• pushes approved bills into accounting

---

6) Design the bookkeeping rules

This is where the actual accounting discipline matters.

For each invoice, capture:

• Vendor
• Invoice number
• Invoice date
• Due date
• Amount
• Currency
• Tax/VAT
• Department / class / location
• GL account
• Cost center / project
• Approval status
• Supporting contract / PO / email

Typical journal entry when bill is entered

If you book the invoice before payment:

Dr Expense / Prepaid / Asset Dr Input VAT / recoverable tax if applicable
Cr Accounts Payable

Then when paid:

Dr Accounts Payable Cr Cash

If invoice is for a prepaid annual service

Example: annual software subscription for $12,000 paid in advance.

At payment:

• Dr Prepaid expense 12,000
• Cr Cash 12,000

Monthly amortization:

• Dr Software subscription expense 1,000
• Cr Prepaid expense 1,000

---

7) Build the payment-run process

A “payment run” should be a controlled batch payment process, not ad hoc payments.

Suggested workflow

1. Finance prepares open AP aging report
2. Filter invoices due in the next payment window
3. Confirm approvals are complete
4. Check cash balance / forecast
5. Review exceptions:
   • new vendors
   • duplicate invoice risk
   • bank detail changes
   • disputed invoices
6. Create payment batch
7. Second-person review/approval
8. Execute payments
9. Reconcile bank activity and update AP

Payment run cadence

• Weekly for startups
• Twice weekly if invoice volume is higher
• Ad hoc for urgent/critical items, but still through approval control

Recommended control

At least two people in the chain:

• Preparer
• Approver/releaser

This is especially important if the person entering invoices can also initiate payments.

---

8) Set approval controls for payment runs

Invoice approval is not the same as payment approval.

Recommended dual-approval structure

• Invoice approval: confirms business validity and coding
• Payment approval: confirms cash release

Payment batch approval rules

• Total batch over a threshold requires CFO approval
• Individual payment over threshold requires extra signoff
• Foreign wire payments require finance manager review
• Same-day/urgent payments require written justification

Separation of duties

Ideally:

• Requester submits invoice
• Manager approves invoice
• Finance enters bill
• Treasurer/AP clerk prepares payment run
• CFO approves payment batch
• Another person releases bank payment

---

9) Reconciliation and month-end close

This is where bookkeeping gets “real.”

Weekly

• Reconcile AP payments to bank
• Review aging
• Check unmatched vendor bills
• Validate prepaid amortization schedules

Month-end

• Reconcile AP subledger to GL
• Accrue unpaid vendor services
• Review prepaids
• Check duplicate/uncleared payments
• Ensure all approvals are documented
• Lock the period after close

Key accrual entries

If you received services in March but invoice arrives in April:

• Dr Expense
• Cr Accrued liabilities

Then reverse or clear when invoice comes in.

---

10) Handle SaaS-specific revenue bookkeeping too

If you’re also asking about customer billing, use this framework:

On invoice issuance

• Dr Accounts receivable
• Cr Deferred revenue if annual prepaid subscription
• Cr Revenue only when earned, depending on service period

On cash receipt

• Dr Cash
• Cr Accounts receivable

For monthly SaaS subscriptions billed in advance

You’ll usually record:

• Invoice: AR / Deferred revenue
• Monthly revenue recognition: Deferred revenue / Revenue

If you have usage-based billing, revenue recognition may be tied to the usage period or reporting date.

---

11) Tools that can help

For early-stage SaaS, a lightweight stack is usually enough.

Common options

• QuickBooks Online + Bill.com
• Xero + ApprovalMax/Bill.com
• Ramp/Brex for cards and bills
• Tipalti for AP + global payouts
• NetSuite once multi-entity/complexity grows

Helpful features

• approval workflows
• OCR invoice capture
• payment batch controls
• audit trail
• role-based permissions
• bill attachment storage
• bank feed reconciliation

---

12) Practical policy set to write down

Document these in a short accounting/finance policy:

AP policy

• All invoices must be submitted to AP inbox
• No payment without invoice and approval
• Payment terms and discounts policy
• Thresholds for approvals
• Handling of prepaids/accruals
• Duplicate invoice detection
• Vendor onboarding requirements

Payment policy

• Payment run frequency
• Batch approval thresholds
• Allowed payment methods
• Foreign payment restrictions
• Bank change verification process
• Urgent payment exceptions

Expense classification policy

• Which spend is COGS vs OpEx
• Prepaid vs expense
• Capitalization thresholds
• Software development cost treatment
• Commission capitalization policy if applicable

---

13) A simple operating model for a startup

If you want a lean version:

People

• Requester
• Department approver
• Finance/AP owner
• CFO or founder approver for high-value payments

System

• AP inbox
• Accounting platform
• Payment tool
• Shared approval log
• Monthly close checklist

Cadence

• Daily invoice intake
• Weekly payment run
• Monthly close and accrual review

---

14) Example workflow

Example: $8,000 annual design software invoice

1. Vendor sends invoice to ap@company.com
2. AP logs invoice in Bill.com
3. System routes to Design Lead
4. Design Lead approves
5. Finance reviews coding: software subscriptions / prepaid
6. Invoice is scheduled in next weekly payment run
7. CFO approves batch
8. Payment sent via ACH
9. Bill marked paid
10. Prepaid amortized monthly over 12 months

Example: $30,000 contractor invoice

1. Invoice received
2. AP checks contract/SOW and budget
3. Project owner approves
4. Finance reviews for completeness and tax treatment
5. CFO approves because threshold exceeded
6. Payment batch prepared and released
7. Journal entry posted to contractor expense or capitalized dev costs, depending on policy

---

15) Common mistakes to avoid

• Paying invoices without approval trail
• Letting the same person enter and release payments
• Not distinguishing prepaids from expenses
• No vendor onboarding controls
• Ignoring invoice-to-contract matching for services
• Not reconciling AP aging to bank
• Failing to accrue month-end expenses
• Inconsistent cost center coding
• No audit trail for bank detail changes
• Ad hoc payment exceptions becoming the norm

---

If you want, I can also give you:

1. a sample approval matrix,
2. a bookkeeping checklist for AP/payment runs, or
3. a process map for QuickBooks/Bill.com/Ramp.