Finance Processes: How Finance Teams Map and Automate Procure-to-Pay, Order-to-Cash, and the Close

By Kirill Stolbushkin

Short answer: Finance processes are the repeatable workflows a finance team runs to move money, record it, and report on it. The core list: procure-to-pay, invoice approval, expense reimbursement, order-to-cash, the month-end close, reconciliations and journal review, budget approval, and vendor setup. Automate the routing, matching, and reminders. Keep people on payments, payment details changes, and judgment calls.

Each of those has a trigger, an owner, a few approval points, and a handful of exceptions. For most finance leads the list is not the hard part. They know what they do. The hard part is that each process lives somewhere different: a shared inbox, a spreadsheet tab, the controller's memory. This guide puts the full list in one place, with enough detail on each process to decide which one to write down first.

What are finance processes? P2P, O2C, and R2R explained

Finance teams usually group the work they do to commit, move, record, and report money into three cycles: procure-to-pay (P2P), order-to-cash (O2C), and record-to-report (R2R). Put simply, P2P is how money goes out. O2C is how it comes in. R2R is how it gets recorded and reported.

Around those three cycles sit supporting processes that cut across them: expenses, budgeting, and vendor master data. A useful test for whether something is worth mapping: it has a clear start, a clear finish, more than one person involved, and at least one decision along the way. For the processes other departments run, see our business process examples by department.

Finance processes list: the 8 core processes at a glance

If one of these lives in a doc or someone's head, paste it into the free AI process mapper (no account needed) and see it as a map.

1. Procure-to-pay

Procure-to-pay covers a purchase from the first request to the supplier being paid. In a finance process list it is the umbrella over several smaller processes, so here it gets a summary. What finance cares about is narrow: money is checked against a budget before anyone commits it, anything above a set amount has a PO, and nothing is paid until the order, the delivery, and the bill agree.

For the step-by-step version, see our procurement process guide. The front end, deciding whether to spend at all, is covered in our guide to the purchase requisition approval process, and our procure-to-pay use case shows an example app that takes a request through conditional approval, the PO, delivery, and reconciliation.

2. Invoice approval

A bill arrives, someone records it, the person who owns the spend confirms it is right, and it gets scheduled for payment. The usual pain is not the approval itself. It is bills sitting in an inbox because nobody knows whose they are, or bills paid twice because they came in once by email and once by post.

The design questions are who approves which bills, what happens when a bill does not match the PO, and how long an approver has before the bill moves to a backup. The invoice approval workflow guide walks through the approval matrix and the exception paths. For an example of the capture side, see our invoice processing use case, an example app that reads invoice data and suggests GL coding for a person to review.

3. Expense approval and reimbursement

An employee spends their own money or a company card, submits the receipt, their manager approves, finance checks it against policy, and the employee gets paid back or the card charge gets coded. Simple on paper. In practice the process breaks on missing receipts, claims submitted months late, and managers who approve everything without looking.

The rules worth writing down: what needs a receipt, the deadline for submitting, who approves a manager's own expenses, and which categories always get a second look (travel upgrades, entertainment, gifts). It is also the process I walk through step by step further down.

4. Order-to-cash: billing and collections

Order-to-cash starts when a customer commits and ends when the cash is applied to the right invoice. For most service businesses it has six parts:

1. Credit check: for new customers or unusually large orders, before you commit to the work.

2. Order or contract confirmed: the terms billing will work from.

3. Billing: who triggers the invoice (a signed contract, a delivered milestone, a date), who checks it, and who sends it.

4. Collections: when the first reminder goes out, when a person calls, and when the account goes on hold.

5. Disputes and deductions: routed to whoever can fix the cause, whether that is sales, delivery, or billing.

6. Cash application: matching payments to invoices, including partial payments and payments with no reference.

Credit notes and write-offs sit alongside: decide who can approve them and up to what amount. Reminders and dunning sequences are easy to automate. Decisions about putting a good customer on hold are not, and should land with a named person.

5. Month-end close (record-to-report)

The close is the process most finance teams already treat as a process, because it repeats every month and it has a deadline. It is a long checklist with dependencies: cutoffs, accruals, reconciliations, review, then reporting. The weak spots are handoffs, where one person cannot start until another finishes, and tasks that only one person knows how to do.

I won't repeat the full checklist here. Our month-end close process guide has it day by day, with owners and the parts you can automate.

6. Account reconciliations and journal entry review

Reconciliations prove that the balance in your books matches something outside them: a bank statement, a subledger, a vendor statement. Manual journal entries are where errors and, rarely, fraud get in, so most teams want a second person to review them.

Write down three things for each: who prepares, who reviews, and what amount or account type triggers a review. Segregation of duties means the person who prepares a transaction or reconciliation is not the person who approves it. If you document controls for an auditor, our guide to SOX internal controls documentation explains what reviewers expect to see, and it is good practice to keep a record of who reviewed what and when, even if you are nowhere near SOX.

7. Budget approval and reforecast

Budgeting is less a workflow than a season, but it has a process inside it: finance sends out targets and a submission sheet, department heads fill it in, finance consolidates, leadership pushes back, and a final version gets approved. A reforecast repeats a smaller version every quarter or every month.

The parts that benefit from a map are the deadlines and the loop. Who gets reminded, who can change a submitted number, and how many rounds of review happen before the CFO approves the final version. A simple map stops the third round of revisions from turning into an email thread nobody can follow.

8. Vendor onboarding and payment details changes

Adding a vendor sounds like admin. It is also one of the main ways money goes to the wrong place. A new vendor needs tax details, payment details, and an owner inside the company. A request to change a vendor's payment details needs the most care of anything on this list, because it is a common route for payment fraud.

Good practice for a payment details change:

1. Treat every change request as unverified, however urgent it sounds.

2. Call the vendor on a contact you already have on file, not the number or email in the request.

3. Have a second person approve the change.

4. Make the change before the next payment run, not during it, and tell the vendor contact you already know.

Automate the collection of documents. Keep the verification human. Procurement owns the due diligence on new suppliers; finance owns this check.

Finance processes this list leaves out

The eight above are the ones most teams map first. A few more belong on a complete finance process list:

• Payroll: collecting changes, calculating pay, approving the run, and paying on time. Often shared with HR or an outside provider.

• Cash forecasting: gathering expected receipts and payments into a forecast, then reviewing it against actuals.

• Tax: preparing and filing returns, plus the sales tax or VAT steps inside billing and AP.

• Consolidation: combining entities, removing balances the entities owe each other, and producing group reports. It matters once you have more than one entity.

Which accounting processes can be automated, and which should stay manual

A rough way to split it:

• Automate: collecting documents and data, routing to the right approver, reminders and nudges, matching documents against each other, building checklists, and moving a task to the next person when the previous one is done.

• Keep a person in the loop: approving payments, changing where a vendor gets paid, posting unusual journal entries, writing off debt, and anything where the right answer depends on context.

• Write down before you automate anything: who owns each step, the amounts that change the routing, and what happens when someone is out. If ownership is fuzzy, sort it first with a simple RACI for the process.

How to measure finance processes

Pick two or three measures per process and track them monthly. Useful ones:

• Days to close

• Invoice approval cycle time

• Days sales outstanding (DSO)

• Invoices paid on time

• Reconciliation exceptions carried forward

• Duplicate or late payments

Finance processes by team size

1 to 49 employees

Finance is often one person plus an outside accountant or bookkeeper. The processes that matter most are invoice approval, expenses, and collections, because they touch cash every week. Keep approvals light: one approver per bill, a clear limit above which a founder approves, and a second person on any payment details change. Write each process down in a paragraph before you think about tools.

50 to 249 employees

This is where the informal version stops working. The usual trigger is something like the controller being the only person who knows the accrual steps, or a bill getting approved by someone who also set up the vendor. More people can spend money, so a purchase request process and spend limits become necessary. The close needs a real checklist with owners. Map the handoffs between finance and the rest of the company first.

250 employees and up

Each process probably has several owners and possibly several entities. The work shifts from "do we have a process" to "is everyone following the same version". When the expense policy changes, Vevos saves a restore point and shows the old and new versions side by side, both the diagram and the documentation text, so you can see exactly which approval rule moved. Rolling back never erases history, and you can export the current version as BPMN XML, PDF, or an image for the controls file.

Expect auditors to ask how each control works, and to want evidence that it ran. A process map shows how a control should work. The evidence that it ran comes from your accounting system and your approval records.

How to map a finance process: expense approval in one sitting

Vevos is an AI-powered Playbook platform for operations leaders, team managers, and business analysts: describe a process in plain language or upload a document, and it generates a BPMN 2.0 process map and process documentation you can review, version, and export.

Here is how I would map the expense process with a finance lead in about an hour, using a made-up but typical policy.

Step 1: describe it in plain sentences. For example:

"An employee submits an expense claim with receipts within 30 days of spending. Claims under the receipt threshold can skip the receipt. The employee's manager approves or sends it back with a reason. If the claimant is a manager, their own manager approves. Finance checks the claim against the expense policy. Travel and entertainment over the policy limit go to the finance manager. Approved claims are paid in the next reimbursement run. Claims older than 90 days are rejected unless the CFO approves an exception."

Step 2: generate the map. Put those sentences into the free AI process mapper and Vevos turns them into a BPMN 2.0 model with process documentation next to it. If the policy already exists as a PDF or Word file, upload it in a free Intro account instead. Look for lanes covering the employee, the manager, finance, and the CFO; decision points for receipt required, manager or not, and over the limit; a loop for claims sent back; and an end event when the claim is paid or rejected.

Step 3: review it with the people who do the work. Walk through it with someone from finance and two managers who approve a lot of claims. Then run last month's awkward claims through it on paper: the one without a receipt, the late one, the manager's own trip. If any of them has no path on the map, add it. Our guide to reviewing an AI-generated process model has a checklist.

Step 4: decide what happens next. For many teams, the reviewed map and the documentation are the deliverable: everyone knows the rules and new hires can read them. If you want an expense approval app built on those rules, Conductor Agents on Tempo build and deploy it from the model you reviewed. Either way, keep a record of who approved each claim. That is good practice whatever tool you use.

You can start free on Intro (250 Beats, one time, no card). Pulse is $9/month and Rhythm $29/month for ongoing mapping, and Tempo, which adds Conductor Agents, is $199/month. The pricing page has the full comparison.

One tip for bigger maps: if the process crosses several teams, lay it out as swimlanes so you can see at a glance where duties are kept apart.

FAQ

What are the core finance processes?

The core finance processes are procure-to-pay, invoice approval, expense reimbursement, order-to-cash billing and collections, the month-end close, account reconciliations and journal entry review, budget approval and reforecasting, and vendor setup with payment details changes. Smaller teams often combine several of them under one person. Larger finance teams usually split each one further by entity or region.

What is the difference between P2P, O2C, and R2R?

P2P, O2C, and R2R are the three main finance cycles. Procure-to-pay (P2P) runs from a purchase request to paying the supplier, and our procurement process guide has its full steps. Order-to-cash (O2C) runs from a customer order to cash applied to the invoice. Record-to-report (R2R) runs from recording transactions to issuing financial statements.

What accounting processes can be automated?

The accounting processes that automate well are data capture, document collection, routing bills and claims to approvers, reminders, matching purchase orders to receipts and invoices, recurring journal entries, and month-end close checklists. Approving payments, approving payment details changes, writing off debt, and posting unusual journal entries should keep a person making the decision.

How do you verify a vendor payment details change?

To verify a vendor payment details change, treat the request as unverified and call the vendor on a contact you already have on file, never the phone number or email in the request itself. A second person should approve the change before the next payment run. Automate the paperwork around it, but keep the verification itself with people.

Which finance process should you automate first?

The finance process to automate first is usually the one that touches cash most often and causes the most chasing, which for many teams is invoice approval or expenses. Map it, agree the rules with the people who approve, and run it as a documented process for a month before automating it or moving on to the next one.

What is the difference between a finance process and a finance procedure?

A finance process is the end-to-end flow with its owners and decisions, such as invoice approval from bill received to bill paid. A finance procedure is the detailed instruction for one step inside it, such as how to record a bill in your accounting system. Map the process first, then write procedures only for the steps that need them.