# How to Handle Landed Cost and Voucher a PO Receipt in SyteLine > Source: https://netray.co/erp-help/syteline-how-to-landed-cost-and-vouchering > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer Landed cost charges such as freight, duty, and brokerage are added against the PO or the receipt, allocated across the received line items by value or quantity, and rolled into the item's received cost before it is vouchered. Vouchering itself is the 3-way match between PO price, receipt quantity, and vendor invoice, and mismatches beyond your tolerance percentage get held for review instead of posting automatically. ## Kind how-to ## System syteline ## Erp Infor SyteLine (CloudSuite Industrial) ## Module Purchasing / Landed Cost and Vouchering ## Query how to add landed cost to a PO receipt and voucher it in SyteLine ## Alternate Queries - syteline landed cost allocation freight duty - syteline 3-way match po receipt invoice voucher - how to voucher a po receipt in syteline - syteline miscellaneous charges on purchase order ## Applies To Infor SyteLine 8.x and CloudSuite Industrial (CSI) 10.x, Purchasing and Accounts Payable modules. ## Steps ### Add landed cost and voucher the receipt **Items:** On the purchase order, add or identify the landed cost charge lines (freight, duty, brokerage, insurance) either as PO charge lines or as a separate landed cost/miscellaneous invoice tied to the PO. Choose the allocation method for the charge: by line value, by quantity, or by weight, depending on what best represents how the cost was actually incurred. Receive the PO through PO Receipts as normal for the physical goods, then apply or confirm the landed cost allocation so it lands in the received item cost, not just as an unallocated AP charge. Review the landed unit cost per item after allocation, since it should now be higher than the PO unit price alone by the pro-rated freight/duty amount. In Accounts Payable, enter the vendor invoice for the goods and, separately, the vendor or carrier invoice for the freight/duty charge if it is billed by a different party. Run the voucher match: the system compares PO price, receipt quantity, and invoice price/quantity within your configured tolerance. Resolve any line that falls outside tolerance manually, tying the variance back to either a legitimate price change, a freight allocation difference, or a data entry error, before releasing the voucher for payment. ## Sections ### Where landed cost actually lives **Body:** The mechanical point people miss is that landed cost is not just an AP line item, it is meant to become part of the item's inventory cost. If you post freight and duty purely as a general expense without allocating it back to the received items, your inventory valuation understates the true cost of the goods, and your margin on anything sold from that receipt looks better than it really is. SyteLine's landed cost functionality lets you attach charges to a PO or a receipt and spread them across the received lines using an allocation basis you choose. Value-based allocation makes sense when freight is roughly proportional to declared value (common for duty), while weight or quantity-based allocation fits better when the carrier bills by weight and the items on the PO have very different price points relative to their bulk. ### 3-way match and tolerance **Body:** Vouchering in SyteLine is standard 3-way matching: the PO says what you agreed to pay, the receipt says what you actually received, and the vendor invoice says what they are billing you. The system compares all three, and if price or quantity differences exceed the tolerance percentage or amount configured for that vendor or globally, the voucher does not auto-post and instead sits for manual review. This is by design, and the fix for a chronically stuck voucher queue is almost never to loosen the tolerance blindly. It is more often that the PO price was never updated after a vendor price increase, or that the freight/duty allocation is inflating the effective unit cost the invoice is being compared against, or that a partial receipt is being matched against a full-quantity invoice line. **Code:** - Purchase Orders > [PO] > charge lines / landed cost detail - PO Receipts > receive line > apply landed cost allocation - Accounts Payable > Vouchers > 3-way match (PO / receipt / invoice) - AP > Voucher > tolerance exception queue ### Freight billed separately from the goods **Body:** A common real-world pattern is the goods invoice arriving from the vendor and the freight invoice arriving separately from the carrier, sometimes weeks apart. Do not wait for both invoices before receiving and vouchering the goods portion. Receive against the PO and voucher the goods invoice on its own timeline, then apply the freight invoice against the landed cost charge lines when it shows up, and let the system's allocation logic re-spread the freight into the already-received items. If your process instead tries to hold every receipt open until both the goods and freight invoices are in hand, you end up with a backlog of open receipts that makes your open-PO and inventory-in-transit reporting inaccurate, and it defeats the purpose of matching each invoice to its own receipt as it arrives. ## Pitfalls - Posting freight or duty as a general AP expense instead of allocating it into landed item cost, understating inventory value. - Choosing value-based allocation for a carrier that actually bills by weight, skewing landed cost toward high-value, low-weight items. - Loosening voucher match tolerance globally to clear a backlog, instead of fixing the specific stale PO price or allocation causing mismatches. - Holding receipts open waiting for a freight invoice that arrives weeks after the goods invoice, distorting open-PO reporting. - Not reviewing the landed unit cost after allocation, so a costly freight surcharge silently changes item margin without anyone noticing. ## Ai Angle ERPray, grounded on your SyteLine PO, receipt, and AP voucher data, can flag which vouchers are sitting in the tolerance exception queue and why, for example a stale PO price versus a landed cost allocation swing, in plain language instead of someone re-deriving the variance line by line. It can also point out receipts whose landed unit cost jumped sharply versus the prior receipt of the same item, which is often the first sign of a freight allocation or vendor pricing problem. ## Faq ### What allocation method should I use for landed cost? **Answer:** Use value-based allocation when the charge (like duty) is roughly proportional to the goods' declared value, and weight or quantity-based allocation when the carrier bills by weight or unit count regardless of value, since matching the basis to how the charge was actually incurred keeps the allocated cost realistic. ### Why is my voucher stuck in the match exception queue? **Answer:** Usually a price, quantity, or landed cost allocation difference between the PO, the receipt, and the invoice exceeds your configured tolerance. Check the PO price against the invoice price first, then confirm the received quantity matches what is being invoiced, before assuming it is a system problem. ### Can I voucher the goods invoice before the freight invoice arrives? **Answer:** Yes, and you generally should. Voucher each invoice against its own receipt or charge line as it arrives rather than holding the whole receipt open, then let the freight allocation apply to already-received items when that invoice comes in. ### Does landed cost affect the item's standard cost or just this receipt? **Answer:** Landed cost allocation affects the cost of the specific receipt transaction. Whether that flows into the item's ongoing standard cost depends on your costing method and whether you subsequently run Cost Rollup or Recost Inventory to reflect the new landed cost trend in the item master. ## Search terms syteline landed cost, syteline voucher matching, syteline 3-way match, syteline freight allocation, syteline po receipt cost, syteline ap voucher tolerance, syteline duty allocation purchase order, csi landed cost setup, syteline purchase order charge lines, syteline invoice match exception --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json