Follow one requisition through the construction procurement workflow
Follow one material requisition through five handoffs, from job site to general ledger, and see what nobody has to retype.

Key Takeaways
- Every retype is a chance for error. One purchase becomes six records, with five handoffs between them.
- Code the job and phase at the request. Every record after it carries the coding.
- The supplier handoff decides the rest. When the PO goes straight into the supplier’s system, nobody keys it in again.
- Most ERPs stop at your company’s walls. They can’t reach the distributor’s system.
- Match every invoice against four records. That includes the small invoices, and a person reviews every flag.
The number on a job cost report is right when nobody retyped the line item that produced it. Every other version of that number rests on a purchasing agent reading one document and entering it into a second system correctly. Then the distributor's counter repeats the same act, and accounts payable repeats it again after that.
None of those people is the problem. A purchase order sent as an email or a PDF has to be read and keyed in before anything can happen with it. The purchasing agent or the distributor's counter rep is doing exactly what the documents require.
What runs from the job site to the ledger is one purchase: material a crew needs on a job. The office, the supply house, the warehouse, accounts payable, and the accounting system each hold a separate record of it. Let’s follow one requisition through those handoffs and name what stops being anybody's job at each one.
Five places the construction procurement workflow asks for a retype
Procurement software gets sold to MEP contractors as a fix for a pile of documents that need reconciling. The documents are the symptom. The requisition, the purchase order, the supplier's sales order, the proof of receipt, the invoice, and the job cost line are six records of one purchase. That leaves five handoffs, and at each one, the next role in the chain has to confirm that the record in front of them is the same purchase as the record before it. Every one of those confirmations is a place a variance can enter.
The order here is the clean version: no backorders, no partial receipts, no price disputes or credit memos, and no changes to the purchase order mid-flight. Each of those has its own handling and none of it is here.
Step 1: The field requisition becomes a purchase order
The requisition comes first and the purchase order comes second, and in most shops they are two separate acts of typing. The request arrives in whatever form the field has on hand (text message, photo, phone call, email), and a purchaser works out what was meant before anything can be ordered.
The crew orders from a visual catalog of 550K+ products that maps field slang to the right part number. The request lands already resolved: a real item, a quantity, a job, and a phase code. The purchaser reviews it and approves it, and the requisition becomes the purchase order. The line item on the order is the line item the field requested. It is the same record.
The job number and the phase code are attached at the moment of the request, by the foreman who knows which job the material is for. Every record downstream inherits them. Nothing has to be coded later by accounts payable working through a stack of invoices deciding where each one belongs.
Step 2: The purchase order arrives in the supplier's system
Everything in the three steps after this one depends on this handoff going clean.
A purchase order that leaves the contractor as an email attachment arrives at the supply house as a document, and a document is not a transaction. The distributor's inside sales rep reads it and enters it into the distributor's system to create a sales order. They are careful and they do it all day. It is still a second person typing an order they did not write.
The retype is structural on the distributor's side too. 55% of North American distributors have invested in ERP, CRM, ecommerce, and analytics without integrating those systems with each other. The supply house is inside the same black box as the contractor, absorbing the cost of a gap nobody built on purpose.
Remarcable connects 150+ suppliers across 3,000+ US branches, so the order transmits straight into the supplier's system and becomes their sales order with no manual re-entry step. Both companies are then looking at one order with one set of line items on it.
A contractor whose ERP already issues purchase orders will ask why this step needs anything else. ERP procurement modules connect the documents inside one firm, and mostly they do it well. Procurement is the exception. CMiC-sponsored research from Dodge Construction Network found that among eleven ERP functions studied, only 52% of ERP users integrate outside data into bidding and procurement, and just 8 of those 52 points call it good. The handoff they cannot reach is the one that leaves the firm. Their ERP has no account in the distributor's system.
Step 3: The delivery is received against the order
Step two decides whether receiving is a quick check or a second round of data entry. When the sales order was keyed in from a PDF, the warehouse or the foreman checks the delivery against a printed copy, counts it, and marks it up. The paperwork goes to the purchasing agent, who enters it, and the receipt becomes another document to reconcile.
When the order is the same record in both systems, receiving is posted against the ordered line and the quantity lands on it. Fred Robinson, a project manager at Copper State, sits on the distributor's side of this handoff, and he describes the order as a record that keeps working after it is placed: "The order has message boards, it has line level messaging... The communication evolves it into a great living document that can now be received against." The receipt is then an entry on the order itself, and the next step runs without anybody assembling paperwork first.
Step 4: The invoice clears a 4-way match
The invoice arrives and accounts payable has to decide whether to pay it. A 4-way match compares four records: the purchase order, the supplier's sales order, proof of receipt, and the invoice. The supplier's sales order is the record of what the distributor agreed to ship and at what price. General-purpose procurement software puts an inspection report in that slot instead, a different check built for a different industry.
The first three records were created without a retype, so the match runs on every invoice against records that already agree on what was ordered and what arrived. Remarcable Intelligence reads the invoice, holds it against those three, and flags a price or a quantity that does not line up before the payment goes out. Every flag still gets a human review. The customer sets the guardrails.
An invoice that clears carries a price and a quantity that three earlier records agree on. Small invoices get the same check as large ones. Nothing is waived because it's too small to check.
Step 5: The coded transaction reaches the general ledger
The coding was done back at step one, so nothing about this cost needs deciding when it reaches accounting. The transaction syncs into the contractor's accounting or ERP system, bidirectionally and in real time, and that system's accounting engine posts it to the general ledger. Remarcable feeds the system that does the posting; it does not replace it.
What arrives is a material cost carrying a job number and a phase code set by the foreman who made the request. It was verified against a delivery received on the order and matched to an invoice on four records. At no point in that sequence was it copied from one screen into another. The job cost report reads from that record. Nobody retyped the line item that produced the number.
Check it against your own stack. Take a line on last month's job cost report, find the material it paid for, and count the times that item got retyped between the job site and the ledger. Every one you find is a place where the number depended on a correct keystroke that day. See how procurement data reaches your accounting system.
Connected purchasing and material operations for MEP contractors
See how contractors run procurement with Remarcable
Request a demo and we'll walk through exactly how it fits your team's workflow.





