A purchase request and vendor approval app for growing companies

In a company of fifteen, purchasing is a quick question to the owner. In a company of sixty, it is a dozen emails a day, a company card that three people share, a subscription nobody remembers approving, and an invoice from a vendor that finance has never heard of. Somewhere between those two sizes, informal purchasing stops working, and the signs are familiar: budget overruns found at month end, duplicate orders, rush shipping fees because nobody ordered in time, and a growing list of vendors with no tax form on file.

A purchase request and vendor approval app gives that process a simple shape without slowing anyone down. This guide covers what the current way costs, what the app should contain, a plain-words request you can hand to FORGE, a rollout plan, the mistakes to avoid and how to measure the result. It is written for owners, controllers, finance managers and operations leads.

What the current way costs you

• Spending is seen only after it happens. Finance learns about a purchase when the invoice or card charge arrives, too late to question it.
• Approvals live in email. "I approved it in that thread" is hard to check and impossible to report on.
• No budget check at the moment of asking. Department heads approve requests without knowing what is already committed this quarter.
• Vendors added without checks. New suppliers get paid before anyone collects a tax form, confirms banking details or checks insurance.
• Payment fraud risk. Requests to change a vendor's bank details by email are a well known fraud pattern. Without a verification step, a single email can redirect a payment.
• Duplicate and rogue purchases. Two people buy the same thing, or someone signs a software subscription on a personal card and expenses it for years.
• Procurement suites built for large enterprises. Full procurement platforms are powerful, but a growing company often finds them heavy to set up and expensive to license for every employee who just needs to ask for a monitor.

What the app should contain

Roles

• Requester: any employee who needs something; submits requests and confirms receipt.
• Approver: manager, department head, finance or owner, based on the ladder.
• Purchasing or office manager: turns approved requests into purchase orders, places orders, manages vendors.
• Finance: owns budgets, vendor onboarding, matching and export to accounting.
• Owner or admin: sets policy, sees everything.

Purchase request fields

• Requester, department, date needed, ship-to location.
• Category (office supplies, equipment, software, services, inventory, travel, marketing, facilities, other).
• Items: description, quantity, estimated unit price, link or quote attachment.
• Preferred vendor, or "new vendor" with their details.
• Business reason in a sentence.
• Budget line or cost center, which the app can suggest from the department and category.
• For services and software: contract length, renewal terms, whether customer or employee data is involved.
• Statuses: Draft, Submitted, Waiting on approval, Changes requested, Approved, Declined, Ordered, Partially received, Received, Closed, Cancelled.

Approval rules

• Amount ladder: for example, under a small amount the manager approves; above it the department head; above a larger amount finance and the owner. Your amounts, your names.
• Category rules: software and anything handling data adds IT or security review; contracts over a set length add finance; capital equipment adds the owner.
• Budget rule: a request that would push a budget line over its remaining amount adds finance, with the budget impact shown.
• No self-approval: nobody approves their own request.
• Delegation: approvers can name a backup while away, with dates, so requests do not stall.

Vendor onboarding

• Vendor name, contact, address, what they supply, tax form received, banking details verified, insurance certificate and expiry where needed, contract on file, payment terms.
• Statuses: Proposed, Documents requested, Under review, Approved, Inactive.
• A purchase order cannot go to a vendor that is not Approved.
• Bank detail changes require a verification call to a known phone number already on file, recorded with who called and when, before the change is approved.

Card purchases and recurring spend

Not every purchase needs a request. Small, routine buys on a company card are often better handled by a clear limit and a receipt upload than by an approval. Decide the amount below which card purchases skip the request step, and build a short receipt form for those: date, amount, vendor, category, budget line and a photo of the receipt. Recurring spend deserves its own list. Every subscription and service contract gets a record with its owner, renewal date, cost and notice period, and the owner is reminded before each renewal to confirm it is still needed. That one list is often where growing companies find the money they did not know they were spending.

Purchase orders and receiving

• Purchase order number, vendor, items, quantities, agreed prices, terms, delivery date, linked request.
• Receiving: requester or receiver confirms what arrived and in what quantity, with notes or photos for damage.
• Matching: when the invoice arrives, finance compares purchase order, receipt and invoice, and differences over a tolerance you set are flagged.

Budgets

• Budget lines by department and category for the year or quarter, with committed (approved but not yet invoiced) and actual (invoiced) amounts, and what remains.

Screens

1. New request: short, phone friendly, with a quote upload.
2. My requests: status of everything the person has asked for.
3. Approvals: each approver's queue with the amount, reason, budget impact and history.
4. Purchasing board: approved requests waiting to be ordered, open purchase orders, overdue deliveries.
5. Vendors: onboarding status, missing documents, expiring insurance.
6. Budgets: each line with budget, committed, actual and remaining.
7. Reports: spend by department, category and vendor; approval times; requests by status.

Notifications

• Approvers: new request waiting, reminders after a day, escalation to their backup after a set time.
• Requesters: approved, declined with a reason, ordered, delivered.
• Purchasing: request approved and ready to order.
• Finance: new vendor proposed, bank change requested, match exception, budget line near its limit.

Example request

Example request: "Build a purchase request app for our 60-person company. Any employee can submit a request with category, items, quantities, estimated prices, a quote or link, vendor, date needed, a one-sentence reason and their department. Managers approve under $1,000, department heads from $1,000 to $5,000, and over $5,000 needs the finance manager and the owner. Software requests always add our IT lead, and any request that would put a department budget line over its remaining amount adds the finance manager, showing the impact. Nobody can approve their own request, and approvers can set a backup while they are away. Remind approvers after one business day. New vendors need a tax form, verified bank details and, for services, an insurance certificate before they are approved, and purchase orders can only go to approved vendors. Any change to a vendor's bank details needs a recorded verification call to the phone number already on file. Purchasing turns approved requests into purchase orders. Requesters confirm what was received. Finance matches purchase order, receipt and invoice, and flags differences over 2 percent. Show budgets by department with committed, actual and remaining, and a monthly spend report by department, category and vendor."

Comparing the options

Rollout plan

1. Write the purchasing policy first. Approval amounts, category rules, who can buy on a card without a request, and what counts as a new vendor.
2. Load budgets for the current quarter or year by department and category.
3. Clean the vendor list. Mark existing vendors with missing documents and start collecting them.
4. Pilot with one department that buys often, such as operations or marketing, for three weeks.
5. Announce the rule: from a set date, purchases above a small amount need an approved request, and invoices without a purchase order go back to the requester.
6. Roll out company-wide with a short video or a five-minute demo at a team meeting.
7. Review approval times weekly for the first month and adjust the ladder if requests stall.
8. Move to monthly spend reviews with department heads using the reports.

Mistakes to avoid

• Too many approval steps. If a $40 purchase needs three signatures, people will find a way around the app. Keep small purchases fast.
• No backup approvers. Vacations will stop the whole company.
• Approving vendors after paying them. The vendor check must come before the first purchase order.
• Accepting bank changes by email. Always verify through a contact method already on file.
• Building budgets nobody updates. Assign an owner for each budget line.
• Forgetting receiving. Without a receipt record, matching cannot catch short shipments or services not delivered.

How to measure that it works

• Share of spending with an approved request before the invoice arrived.
• Average time from request to approval.
• Budget overruns discovered at month end, which should fall.
• Vendors with complete documents.
• Duplicate purchases and unused subscriptions found and cancelled.
• Invoice match exceptions caught before payment.

Checklist before you build

1. Write the approval ladder and category rules.
2. Decide which purchases skip a request, such as small card purchases.
3. Load budgets by department and category.
4. List vendor onboarding requirements.
5. Write the bank detail change procedure.
6. Decide who creates purchase orders and who confirms receipt.
7. Set the matching tolerance.
8. Pick the pilot department and the company-wide date.

How FORGE handles it

With FORGE, your controller or office manager describes the app in plain words, like the example above. A panel of top AI models plans it, a dedicated AI crew builds it, and every piece is checked for quality and security before it is saved. Most teams have their first real tool the same day, on phones and desktops.

Every app lives inside your company and only the people you invite can get in. Roles in FORGE decide who builds and who uses, and employees who only submit requests or approve them are free, so the whole company can use the front door. FORGE keeps a complete record of who did what, which pairs naturally with an approval trail. When your ladder or categories change, describe it; a change costs a small fraction of a build and only counts when something actually changes.

It is $49 a seat a month for each person who builds, with 3 builds included, and caps and alerts at 80 and 100 percent keep your own FORGE spending predictable too. Our team onboards every company starting with a workflow workshop. Talk to us.

Questions people ask