Quote to Cash · step 6 of 11
Order entry
Typing the accepted order into the system that everything downstream reads from. Every error made here is repeated by production, despatch and invoicing, and is discovered by the customer.
Also called: Sales order processing · Order booking · Order creation · Order administration
- Owned by
- Inside Sales / Sales Coordinator
- Also involved
- Production Planner, Credit Controller
- Documents
- Purchase Order (PO), Quotation
- Measured by
- On-Time Delivery (OTD), Gross Margin
What it is
Order entry is where an accepted purchase order becomes a sales order in your own system. It sounds clerical, and it is treated as clerical in most companies. It is in fact the point at which the commercial agreement is translated into instructions that production, despatch and finance will each act on without ever seeing the original.
Everything after this step reads from what was entered here. The works order comes from it. The picking list comes from it. The invoice comes from it. If the customer's purchase order number was mistyped, the invoice carries a number the customer's accounts payable system cannot match, and payment stops six weeks later for a reason nobody connects to this step.
It is also where the order book is created — the backlog that capacity planning, cash forecasting and delivery promises all depend on.
Why companies do it
Because the customer's document and your system speak different languages. Their part number is not yours; their delivery address is a site name not a bay number; their schedule is a set of dates that must become works orders and material requirements. Somebody has to translate, once, carefully — and record it so that the translation can be checked when a dispute arises.
Inputs and outputs
What has to be there first
- The reviewed and accepted purchase order — Receiving the customer's purchase order
- The quotation revision it was accepted against — Reviewing and issuing the quotation
- Agreed concessions and their conditions — Negotiation and revised offers
- Customer master data — addresses, terms, tax status, contacts — Finance
- Part master and routing — Engineering and planning
- Confirmed promise date — Production Planner
What it produces
- A sales order — Planning and making it
- A works order or production demand — Production Planner
- Material requirements — Purchasing
- An entry in the order book — Accounts receivable and collection
The basis of both the capacity plan and the revenue forecast.
- Order acknowledgement to the customer — Customer purchasing
How it is done
01Enter the customer's purchase order number exactly
Character for character, including prefixes, leading zeros and any suffix. This number is the key the customer's accounts payable system uses to match your invoice against their approved order. A single wrong character turns a routine payment into a manual investigation nobody has been asked to do.
02Enter the price the order states
Not the price from the quotation, not the price from last time, not the price you believe is correct. If they differ, that difference should have been resolved at contract review — and if it was not, stop and resolve it now rather than encoding it.
03Map the part number both ways
Record the customer's part number alongside your own on the order line. It has to appear on the acknowledgement, the packing slip and the invoice, because the customer's goods-in and accounts payable both search on theirs, not yours.
04Set the promise date, and keep it separate from the request date
Store both: the date the customer asked for and the date you committed to. On-time delivery can then be measured honestly against what was promised, and the gap between the two is itself a number worth watching.
05Enter the delivery address and the invoice address separately
They are frequently different — goods to a plant, invoices to a shared service centre in another country. Getting this wrong delays either the goods or the payment, and the second one is harder to detect.
06Enter schedules as lines, not as a note
If the order calls for 100 in March, 150 in April and 150 in May, enter three lines with three dates. A single line with the schedule typed into a comment field is invisible to planning, invisible to the order book, and will be shipped as one delivery.
07Attach the special requirements to the order, not to a person
Certification, packaging, labelling, batch traceability, delivery windows, booking-in procedures. If it lives only in the coordinator's memory it will be missed the week they are away, and it will be missed at despatch, which is the most expensive place to miss it.
08Check the order against credit before releasing it
Confirm the order does not push the account past its limit. Releasing to production first and discovering it afterwards means the cost is already sunk.
09Release and confirm
Release the order to planning and send the acknowledgement with the confirmed date. From this point the promise is public, and changing it requires telling the customer.
What needs approval
Approvals only work when they happen before the commitment. Retrospective approval is a manager being told what has already been promised.
| Trigger | Approver |
|---|---|
| Order value takes the account over its credit limit | Credit control |
| Promise date earlier than standard lead time | Operations |
| Price on the order differs from the quotationShould already be resolved; if it reaches entry, it stops here. | Sales manager |
| Non-standard packaging, certification or labellingBecause they, not sales, have to deliver it. | Quality and despatch |
One order, six deliveries, one field
A worked example with real numbers.
A customer places a blanket order for 900 brackets against a 12-month schedule, called off quarterly, with the first delivery in six weeks. The purchase order number is 4500-887-2261.
Entered correctly it becomes four order lines with four dates, each visible to planning as separate demand, each producing its own works order, its own despatch and its own invoice. The order book shows £15,480 spread across four quarters rather than arriving all at once.
Entered as a single line for 900 with the schedule in the notes field, planning sees demand for 900 in six weeks. Either the plant makes 900 and holds nine months of finished stock at its own cost, or somebody notices in time and re-plans manually, every quarter, forever.
Separately, the purchase order number is typed as 4500-887-2216 — two digits transposed. Everything proceeds normally for three months. The first invoice reaches the customer's shared service centre, fails automatic matching, and lands in an exceptions queue. Nobody tells the supplier. It is found 71 days later during a routine aged debt review, by which point three more invoices have failed the same way.
| Entered as four lines | Entered as one line plus a note | |
|---|---|---|
| Order book profile | £3,870 in each of 4 quarters | £15,480 in Q1 |
| Works orders raised | 4, one per call-off | 1, for 900 |
| Finished stock held | None | Up to 675 units for 9 months |
| Invoices | 4, matching 4 deliveries | 1, disputed against partial delivery |
| Planning effort | Automatic | Manual re-plan every quarter |
The point
Neither failure was a judgement error. One was a shortcut in a data entry field and the other was six transposed characters. Both were created in about ninety seconds and both cost months.
Common mistakes
MistakeMistyping the customer's purchase order number
Why it happens: It is a long alphanumeric string typed by hand from a PDF, and nothing at the point of entry tells you it is wrong. The consequence appears eight weeks later as an unpaid invoice.
What to do instead: Copy and paste rather than retype where the order arrives electronically, and make the number a mandatory field that also prints on the acknowledgement — so the customer sees your version and can correct it early.
MistakeEntering the schedule as a comment
Why it happens: It is faster than creating six lines, and the coordinator knows what it means. Planning does not see it, the order book shows one lump of demand in the wrong month, and the first call-off is shipped as the whole quantity.
What to do instead: One line per delivery, always. If the system makes that painful, that is a system problem worth fixing rather than a habit worth working around.
MistakeOverwriting the promise date when it slips
Why it happens: The order will be late, so the date in the system is updated to the new one. The order is then recorded as delivered on time, and the on-time delivery figure stays reassuringly high while customers grow angrier.
What to do instead: Store the original promise date in a field that cannot be edited after release. Measure against that. Record changes as revisions with reasons rather than overwriting history.
MistakeEntering the order from the quotation instead of the purchase order
Why it happens: The quotation is already in the system and can be converted with one click. Anything the customer changed on their order — quantity, date, address, price — is silently discarded.
What to do instead: The purchase order is the source document for entry. The quotation is what it gets checked against.
MistakeMissing special requirements
Why it happens: The certification requirement was in an email during negotiation and never made it onto the order. Despatch ships without a certificate of conformity and the delivery is rejected at goods-in.
What to do instead: Special requirements become fields or flags on the order line, checked at despatch. Anything agreed in negotiation gets transcribed here or it does not exist.
MistakeNot entering the order at all until production starts
Why it happens: The order is urgent, work begins on the paperwork, and entry is deferred. The order book is understated, capacity planning is wrong, and the revenue forecast misses it.
What to do instead: Entry happens on acceptance. The order book is only useful if it reflects everything the company has committed to.
Where the work happens
- ERP sales order module
- EDI for automated order intake
- CRM, where the quote and the concessions live
- Credit control system
Terminology
- Sales order
- Your internal record of what has been agreed with the customer. The document every downstream department actually works from.
- Order book
- The total value and profile of orders accepted but not yet delivered. The basis of capacity planning and revenue forecasting.
- Promise date
- The date you committed to, as distinct from the date the customer requested. On-time performance should be measured against this.
- Blanket order
- A single order covering an agreed quantity over time, against which deliveries are called off individually.
- Call-off
- An individual release against a blanket order or schedule agreement.
- Ship-to and bill-to
- The delivery address and the invoice address, which are often different organisations in different countries.
- Cross-reference
- The mapping between your part number and the customer's. Needed on every document they will read.
Common questions
›Why does the customer's PO number matter so much?
Because it is the key their accounts payable system matches on. Large buyers run three-way matching — purchase order, goods receipt, invoice — automatically, and an invoice whose PO number does not match anything drops into an exceptions queue that may be reviewed weekly, or monthly, or when someone chases. Nobody tells you. It is the single most common reason a correct invoice goes unpaid.
›What is the difference between a purchase order and a sales order?
They describe the same agreement from opposite sides. The purchase order is the customer's document instructing you to supply. The sales order is your record of what you have agreed to supply. Order entry is the act of turning one into the other, and any drift between them becomes a dispute.
›Should the promise date ever be changed?
The commitment can change — things go wrong, and telling the customer early is right. But the original should never be overwritten, because that is what performance is measured against. Keep the original, add a revision with a reason, and let the number of revisions be visible.
›How much of order entry can be automated?
A lot, where orders arrive by EDI or through a portal — the transcription errors disappear entirely. What cannot be automated is the review: the judgement about whether the order is one you should accept. Automating entry without keeping the review simply means encoding bad orders faster.
›Who should do order entry?
Someone close enough to the commercial agreement to notice when the order does not match it. When it is treated as pure data entry and pushed to whoever is free, the checking stops happening and the errors surface at the invoice.
Tools for this
Downloadable, self-contained, and yours to keep — they run in a browser with no account and no data leaving your machine.
- Order Backlog DashboardProSee your open order book as money: backlog value by due week, overdue and at-risk orders, customer concentration, aging and where the value sits in production. Runs entirely in your browser — nothing is uploaded.
- Purchase Order TrackerFreeTrack purchase orders from raising to invoice: committed spend by cost centre, overdue deliveries, goods received but not invoiced, and a three-way match that catches duplicate and inflated supplier invoices. Runs entirely in your browser — nothing is uploaded.
- Production ScheduleProSequence jobs on your work centres with planned dates, hours and priorities, catch late-running work before the promise breaks, and measure schedule adherence and estimating accuracy on every completed job. Nothing is uploaded.
Reviewed 2026-08-15. Nothing here is legal, tax or accounting advice — contractual and tax practice varies by jurisdiction.