An AI requisition creation agent takes the approved request and builds a draft requisition, mapping quote lines to items, quantities, unit prices, delivery details and the vendor record.
A request has passed checks and needs a requisition.
The agent gathers vendor, items, price and coding.
It builds the formal requisition from the record.
Vendor, budget and cost centre are matched.
The requester checks lines and delivery details.
It is passed on for approval and ordering.
It proposes accounting codes and the budget owner from the department and category, and notes anything it inferred rather than read.
The draft is checked for completeness and shown to a buyer for review. The agent prepares the document; a person releases it.
A requisition is only as useful as its accuracy, and small keying errors here carry into the purchase order and the invoice.
Items, quantities and prices are copied from a quote by hand, so typos creep in.
Requesters pick a cost centre or account they are unsure of.
The wrong remit address or legal entity is chosen from a long list.
The requisition lists something different from what was approved.
Mistakes found later force the requisition to be amended and re-approved.
The agent starts from the approved record, including the quote and any conditions attached.
Quote lines are matched to item descriptions, quantities, units and prices.
Vendor details come from the vendor record, and proposed account and budget codes are added with their basis.
The draft's total and scope are compared with what was approved, and differences are flagged.
A buyer reviews the draft, fixes anything wrong and releases it.
Bring a small sample and watch Flo work through it.
| Aspect | By hand | With the agent |
|---|---|---|
| Rekeying | The requisition is typed again from the request. | The requisition is drafted from the confirmed request fields. |
| Line detail | Item lines are rounded or merged by hand. | Lines are copied from the quote with quantities and units. |
| Coding | Cost centre and account are guessed or left blank. | Coding is proposed from department and category with its basis noted. |
| Mismatch | Requisition values differ from the quote. | Values are cross-checked against the quote before the requester sees them. |
| Traceability | The requisition cannot be traced to the original request. | Each requisition links to its request and source documents. |
| If | Then | Who decides |
|---|---|---|
| Quote lines are clear | Copy lines, quantities and unit prices into the requisition draft | Requester confirms |
| Coding cannot be determined | Leave coding blank and flag it | Requester or budget owner supplies it |
| Requisition total differs from the quote | Flag the difference with both figures | Buyer investigates |
| Vendor is not yet in the vendor record | Mark the requisition as waiting on vendor setup | Buyer or onboarding team creates the vendor |
| Delivery date is earlier than a realistic lead time stated by the vendor | Flag the conflict | Requester adjusts or accepts |
| Request was changed after approval | Create a revision and show the change | Approver sees the revision |
The quote covers several delivery dates. The agent builds separate lines and the requester confirms the split.
The requisition keeps the quoted currency and does not convert. Finance decides how the budget view is stated.
Edits to scope or price void the earlier draft. The agent rebuilds it from the revised request and tells the requester.
The quote gives a single price for several items. The agent keeps it as one line unless the vendor gives a breakdown, and the buyer decides whether to ask.
Talk it through with the team. We will map it to your steps and show where a person stays in control.
Have the agent prepare requisitions that buyers still review line by line.
Check agent drafts against hand-built ones for several weeks.
Begin suggesting cost centres once line accuracy is high.
Let requesters confirm directly where buyer edits have become rare.
It shows how often the draft was right the first time. Falling accuracy usually traces to one source of errors, such as coding or unit conversion.
Quick answers to what people ask most about requisition creation.
Book a demoIt is turning an approved purchase request into a formal requisition with items, prices, vendor and accounting codes. An AI agent drafts it and checks it, and a person reviews and releases it.
No. It prepares and checks the draft. An authorised buyer reviews it and decides when it is released.
It proposes codes from the department, category and past similar purchases, and marks them as suggestions. Finance or the budget owner confirms.
The agent flags the difference, such as an extra line or a higher total, and a person decides whether the requisition needs another approval.
An existing contract check is the step that asks whether a vendor already has an agreement with your company before a new purchase goes ahead.
→Request status tracking is the step of keeping requesters informed about where a purchase request stands and who is acting on it.
→Preferred vendor recommendation is the step where a requester is pointed to approved or contracted suppliers before going to market.
→Request SLA monitoring is the step of tracking how long each purchase request spends in each stage against the service targets your team has set.
→Bring a small sample of real items. We will show what Flo handles on its own and where it hands over to your team.
