A purchase order request checklist is not a form that gets filed after the order is placed. For a virtual assistant, the checklist is the record that ties a business need to a budget line, a vendor, and an approver before anyone commits money. A request that starts with a preferred vendor skips the question of whether the spend was planned. The checklist makes that question impossible to skip.
Capture the request before the quote
Record the person asking, the business reason, and the date the goods or service are needed. The assistant should write the need in one sentence that a budget owner can judge. A request described only as urgent gives the approver nothing to test. The date matters because a late order can turn a cheap option into an expensive one.
Ask for the quantity and the unit of measure rather than a single total. A total hides whether the team needs three seats or thirty and whether the term is one month or one year. The assistant should record the unit amount and the quantity as separate fields. That split makes a later change easy to see and easy to challenge.
Separate a one-time purchase from a recurring commitment before anything else happens. A subscription that renews quietly is a different decision from a single delivery, even when the first invoice looks the same. The assistant should ask how the commitment ends and what notice is required. A recurring cost recorded as a one-time buy will surprise the next budget review.
Save the original request exactly as it arrived and note who supplied it. A message that is edited into a cleaner version loses the evidence of what was actually asked. The assistant should attach the source and record the date it was received. A clean summary is useful only when the original is still available.
Tie the request to an approved budget line
Name the budget line, the remaining balance, and the person who controls it. A request without a line is a wish that finance has to decode later. The assistant should confirm the code with the budget owner instead of copying an old order. A wrong code creates a correction that outlasts the purchase.
Check the balance before asking a vendor for a quote. A quote for spend that has no room in the plan wastes the vendor's time and the assistant's. The assistant should record the balance at the moment of the check and the date. A balance that is not dated cannot be trusted at approval time.
Record whether the spend is already in the plan or needs a new approval. A planned purchase follows one path, while an unplanned one needs a reason and a trade-off. The assistant should write which case applies in the request header. The approver should not have to guess which process is in force.
Write the accounting treatment for shipping, tax, and delivery charges in the request. A total that leaves out delivery costs will fail at the invoice stage. The assistant should ask the vendor for the full landed cost before routing the request. An amount that changes after approval damages trust in the whole checklist.
Check the vendor and the terms
Confirm the vendor is on the approved list and that the legal name matches the quote. A trading name can differ from the entity that will invoice the company. The assistant should record the registration or tax identifier the finance team requires. A payment sent to the wrong entity is slow to recover.
Compare the quote with the terms the vendor usually applies. A short quote may leave out support, setup, or a minimum commitment that appears only in the contract. The assistant should read the terms and record anything that changes the total. The cheapest headline is not the cheapest purchase when the missing lines are added.
Record the delivery date, the warranty, and the return window in the request. These terms decide whether the purchase can be fixed if the goods arrive wrong. The assistant should note who will receive the delivery and where it will be stored. A delivery with no named receiver tends to sit in a hallway.
Note any conflict of interest between the requester and the vendor. A personal relationship does not block a purchase, but it must be visible to the approver. The assistant should record the relationship in the request rather than in a private message. A disclosed conflict protects both the requester and the reviewer.
Route the request for approval
Route the request to the budget owner before the vendor is told the order is approved. A verbal promise to a vendor is hard to withdraw and easy to misread. The assistant should keep the vendor informed only after the written approval exists. A warm relationship does not replace a signed decision.
Give the approver a single page with the need, the amount, the budget line, the vendor, and the deadline. A long thread forces the approver to reconstruct the decision from fragments. The assistant should put the recommendation at the top and the evidence below. A clear ask gets a faster answer than a file dump.
Record the approval as a written decision with a name and a timestamp. An email that says looks fine may not identify who accepted the spend. The assistant should ask for the sentence that names the approver and the amount. A decision without a name is not an approval.
Set an expiry on the approval so an old yes cannot be reused months later. Amounts, budgets, and needs change, and an expired approval should trigger a fresh check. The assistant should write the expiry date beside the approval. A stale approval is one of the quietest ways to overspend.
Reconcile the purchase order after it is issued
Compare the purchase order with the approved request line by line before sending it. A typo in a quantity or a vendor code is cheaper to fix now than after delivery. The assistant should keep the approved request and the order in the same folder. A mismatch found later looks like a deliberate change.
Log the order number, the expected delivery, and the person who will receive the goods. The log should show the next action rather than only the date the order was sent. The assistant should update it when the vendor confirms the shipment. A request that disappears after approval cannot be reconciled.
Match the invoice to the purchase order and to the receiving record before payment. Three documents that agree are the minimum evidence for a clean payment. The assistant should flag any difference instead of adjusting the invoice quietly. A quiet adjustment hides a problem that will repeat.
Close the request only when the goods or service are accepted and the invoice is matched. Closing at order time leaves the team blind to a missing delivery. The assistant should record the acceptance and the name of the person who gave it. A closed request with no acceptance is an unfinished purchase.
Key takeaways
Record the need, the quantity, and the date before asking for a quote. A request without a budget line is a wish that finance has to decode later. Check the remaining balance at the moment of the request and write down the date. A total that hides delivery costs will fail when the invoice arrives.
Confirm the vendor legal name, the terms, and any conflict of interest. A short quote can leave out support, setup, or a minimum commitment. Record the delivery date, the warranty, and the return window in the request. A disclosed conflict protects both the requester and the reviewer.
Route the request to the budget owner and record a written decision with a name, an amount, and an expiry. Keep the vendor waiting until that approval exists. Put the recommendation at the top of a one-page summary and the evidence below. An approval without a name is not an approval.
Reconcile the purchase order with the request, the delivery, and the invoice before payment. Close the request only after someone accepts the goods or service. Flag every difference instead of adjusting the invoice quietly. A closed request with no acceptance is an unfinished purchase.
Continue building the workflow
Related support: onboarding operations support, contact us. The Acquisition.gov - Federal Acquisition Regulation publishes the acquisition rules that define how purchase requests are documented and approved.
Related reading
Set a confidential document access log for a virtual assistant
An access log that defines what counts as confidential, records the requester and the approver, grants the narrowest access, tracks expiry and removal, and survives a monthly review.
Build a customer escalation handoff note for a virtual assistant
A handoff note that opens at the moment of escalation, separates facts from the customer's theory, names the next owner and promised time, and closes with resolution evidence.
Set a contractor timesheet approval log for a virtual assistant
An approval log that matches each timesheet to an approved scope, checks hours against the rate and cap, routes a named approval, flags exceptions, and reconciles the invoice.
