Landed cost in NetSuite helps businesses add inbound costs such as freight, customs duties, insurance, and handling fees to inventory value instead of recording them as unrelated expenses. The standard workflow is to enable the Landed Cost feature, define landed cost categories, configure allocation methods, enter costs on an item receipt or related transaction, review the calculated distribution, and verify the resulting inventory and general ledger impact. A successful setup depends on accurate item data, clear ownership of estimated versus actual costs, and testing across partial receipts, multiple items, currencies, and purchase order scenarios.
What Is Landed Cost in NetSuite?
Landed cost is the total cost required to bring purchased goods to their intended location and make them available for sale or use. The supplier’s item price is only one part of that total. Depending on the business process, landed cost can include:
International freight
Domestic transportation
Customs duties and tariffs
Brokerage fees
Cargo insurance
Port, terminal, or handling charges
Inspection and compliance costs
Other directly attributable inbound charges
NetSuite’s Landed Cost feature distributes eligible charges across received inventory. The allocated amount increases the inventory value of the items on the receipt, which affects inventory costing and the cost of goods sold when those items are later sold.
This is different from simply posting a freight bill to an expense account. An expense treatment records the charge in the period when the bill is entered. A landed cost treatment attaches the cost to inventory, allowing the charge to flow through inventory valuation and eventually cost of goods sold as the goods are sold.
The distinction matters most when a business imports products, receives goods through multiple shipments, or relies on reliable product margin reporting. If inbound charges are expensed inconsistently, product profitability becomes difficult to measure and inventory values do not reflect the full cost of acquisition.
For the broader question of planning a NetSuite deployment, our guide to NetSuite implementation services and project planning covers delivery models, project scope, and implementation risk. This article focuses specifically on the landed cost configuration and transaction workflow.
How Does Landed Cost Work in NetSuite?
Landed cost in NetSuite works by applying a cost amount to an item receipt and allocating that amount among eligible inventory lines according to a selected method. The allocation method determines how much of the charge each item receives.
For example, suppose a receipt contains two products with different quantities and values. Allocating freight by quantity gives each unit an equal share. Allocating by value assigns a larger share to the higher-value product. Allocating by weight is more appropriate when transportation expense is driven by shipment weight rather than purchase price.
The core entities in this process are:
Landed cost categories, which identify the nature of the charge, such as freight or duty.
Item receipts, which establish the inventory quantity and value being received.
Allocation methods, which determine how the cost is distributed.
Inventory costing, which records the resulting value in inventory.
General ledger accounts, which capture the offsetting accounting entry.
Vendor bills or other payable transactions, which record the actual obligation when the charge is invoiced.
NetSuite does not eliminate the need to reconcile estimated and actual charges. It provides a transaction framework for associating costs with inventory, but the business still needs a policy for when costs are estimated, when they are finalized, and how differences are corrected.
A key implementation decision is whether the landed cost is entered at receipt, added later through an adjustment process, or supported by a custom integration. The correct choice depends on when reliable cost information becomes available and whether inventory is sold before the final vendor charge arrives.
How to Set Up Landed Cost in NetSuite
The setup should begin with accounting policy, not with fields and checkboxes. Before configuring NetSuite, document which inbound charges qualify as inventory cost under your accounting policy and which charges remain period expenses.
Once that policy is clear, use the following sequence.
1. Enable the Landed Cost Feature
An administrator enables the relevant landed cost functionality in NetSuite accounting or inventory feature settings. The exact available options depend on the account configuration, enabled modules, permissions, and NetSuite release.
Feature activation is only the beginning. Users also need the permissions required to view and enter landed cost information on the applicable transactions. Test with the actual roles used by receiving, purchasing, accounts payable, and finance teams. An administrator seeing a field does not prove that an operational user will see or edit it.
Confirm the feature in a sandbox before enabling it in production. This provides a controlled environment for validating forms, roles, workflows, reports, and accounting results.
2. Define Landed Cost Categories
Landed cost categories classify the charges that will be applied to received inventory. Common categories include freight, duty, insurance, brokerage, and handling.
A category should have a clear business purpose. Avoid creating a separate category for every supplier or shipment unless reporting or accounting requires that level of detail. Excessive categories make data entry slower and produce fragmented reporting.
For each category, establish:
The name users will recognize
The related expense or clearing account
The responsible team
The acceptable source transaction
The default allocation method, if appropriate
Whether the charge is normally estimated or actual
The account mapping deserves particular attention. The debit side of the transaction generally increases inventory value, while the offsetting credit or clearing treatment depends on how the business records the source charge. The exact accounting result should be confirmed in a test account with the organization’s accountant.
3. Confirm Item and Location Data
NetSuite needs reliable item and receipt data to allocate cost correctly. Review inventory items, units of measure, locations, subsidiaries, currencies, and costing methods before testing the feature.
Weight and volume allocation require usable weight and volume values on the relevant item records. If those fields are blank or inconsistent, an allocation method based on shipment characteristics will produce poor results or fail to allocate as expected.
Also confirm whether the items are:
Inventory items
Lot-numbered or serialized inventory
Matrix items
Assembly items
Special-order items
Drop-ship items
Non-inventory items
Not every item type follows the same inventory valuation behavior. Landed cost is intended for costs associated with inventory being received into stock. It should not be assumed that the same process applies to drop shipments, service items, or goods that never enter owned inventory.
4. Select Allocation Methods
The allocation method is the mechanism that divides a landed cost amount across receipt lines. NetSuite configurations commonly support methods based on factors such as quantity, weight, volume, or value, subject to account features and transaction context.
Choose the method based on the economic cause of the charge:
| Cost type | Practical allocation basis |
|---|---|
| Per-unit handling fee | Quantity |
| Ocean or air freight driven by mass | Weight |
| Freight driven by cubic capacity | Volume |
| Insurance based on shipment value | Value |
| Customs duty based on declared value | Value |
| Mixed logistics invoice | Separate categories or documented allocation rules |
The best method is not always the easiest method. Quantity is simple, but it can distort cost when one item is lightweight and inexpensive while another is heavy or high value. Value-based allocation is useful for insurance and ad valorem duties, but it can overassign freight to expensive, compact items when physical shipment characteristics drive the invoice.
Document the allocation policy so receiving and finance users apply the same logic. A consistent method is more valuable than an apparently precise method that changes from one receipt to the next.
5. Configure Transaction Forms and Roles
Users need a practical way to enter landed costs without exposing irrelevant fields or creating unnecessary manual steps. Review the item receipt form used by the receiving team and confirm that the landed cost information is visible where expected.
Test the process for each relevant role:
Purchasing
Receiving
Accounts payable
Inventory control
Finance
System administration
Role testing should cover field visibility, edit permissions, subsidiary restrictions, location access, and approval behavior. If a workflow modifies item receipts after approval, verify that it does not overwrite or block landed cost information.
Custom forms can improve usability, but customization should not hide accounting significance. A receiving user should understand whether the entered amount is an estimate, a supplier invoice amount, or a manually allocated charge.
How to Enter Landed Cost on an Item Receipt
The item receipt is usually the central transaction for applying landed cost because it records the inventory entering the location. The exact screen layout depends on account configuration and form customization, but the operating sequence is consistent.
1. Create or open the item receipt
Start from the purchase order or create the item receipt through the standard receiving process. Confirm the vendor, subsidiary, location, currency, quantities, and receipt date.
The receipt date matters because it determines when inventory is recognized and can affect period reporting. Backdated receipts require additional care when accounting periods are closed or inventory has already moved through subsequent transactions.
2. Verify the receipt lines
Review the items and quantities before entering additional costs. Check units of measure, lot or serial details, inventory location, and any partial-receipt quantities.
A landed cost allocation should be based on what was actually received, not automatically on the full purchase order. If only part of a shipment arrives, allocating the full freight amount to the partial receipt may overstate the initial inventory value unless the business policy specifically requires that treatment.
3. Enter the landed cost categories and amounts
Enter the applicable charge by category. For example, freight and customs duty should remain separate if the business needs to reconcile them to different vendor documents or analyze them independently.
Separate categories also make exception review easier. A large duty amount and a large freight amount should not be hidden inside one generic “landed cost” line.
When the charge is estimated, label or document it according to the organization’s policy. Users should be able to distinguish a preliminary amount from an invoice-backed amount during month-end review.
4. Apply the allocation method
Select the method that matches the cost category and confirm that the resulting distribution is reasonable. Review both the total allocated amount and the amount assigned to each item.
Check for common anomalies:
A zero-weight item receives no cost under weight allocation.
A line with an incorrect value receives too little or too much cost under value allocation.
A partial receipt receives an allocation that does not match policy.
Rounding creates a small difference between the category total and line-level allocations.
A non-inventory line appears in a transaction that should contain only inventory.
Do not approve the receipt simply because the total equals the external invoice. The line-level distribution is the part that determines product cost and margin accuracy.
5. Save, approve, and review the accounting impact
After saving the receipt, review the resulting inventory value and accounting details. Confirm that the inventory asset account increased by the expected amount and that the offsetting entry follows the established policy.
A useful test is to compare three values:
The original item cost
The allocated landed cost
The resulting inventory cost
The sum of the original item cost and allocated landed cost should reconcile to the inventory value recorded for the received goods, subject to rounding and the account’s costing method.
What Happens When the Vendor Bill Arrives Later?
The vendor bill should not automatically duplicate a cost that was already applied through landed cost. This is one of the most important controls in the process.
Businesses generally choose one of two approaches. The first is to enter the landed cost based on the actual bill when the inventory receipt is created. This produces accurate cost immediately, but it requires the invoice or reliable charge information to be available at receiving.
The second is to apply an estimated amount at receipt and reconcile it when the actual vendor bill arrives. This supports timely receiving when invoices arrive later, but it requires a defined variance process.
That process should answer:
Who compares estimated and actual amounts?
At what threshold is a correction required?
Which transaction records the difference?
What happens if the inventory has already been sold?
How are closed accounting periods handled?
How are foreign exchange differences treated?
For imported goods, the payable invoice may arrive after inventory has already been transferred or sold. In that situation, changing historical inventory cost may affect current-period reporting or require an adjustment. Finance should define the treatment before go-live rather than handling each variance as an isolated exception.
Landed Cost and NetSuite Inventory Costing
Landed cost affects inventory costing, but the final result depends on the costing method and item configuration. FIFO, average costing, standard costing, and other inventory valuation approaches do not necessarily present the same downstream result.
Under a cost flow method such as FIFO, a receipt-specific landed cost is associated with the inventory received and flows through the cost of goods sold as those units are issued or sold. Under average costing, the additional cost can influence the average cost of the item at the location. Standard costing follows a different variance model because inventory is carried at a predefined standard and differences may be captured as variances.
This is why a landed cost test must include more than the initial receipt. Test the complete sequence:
Purchase order
Item receipt
Landed cost entry
Vendor bill
Inventory transfer
Sales order fulfillment
Invoice or cash sale
Return, if relevant
Month-end inventory reporting
For manufacturing businesses, the effect can continue into assemblies and work orders. If purchased components receive additional cost before consumption, the component value can affect the cost of the finished assembly. Our NetSuite work orders and assemblies guide explains how component costs flow into manufacturing records and how WIP and routings introduce additional labor and overhead considerations.
Common Landed Cost Implementation Problems
The most serious landed cost problems are process problems, not configuration errors.
Applying every inbound charge to inventory
Not every logistics-related charge belongs in inventory value. Storage after goods are available for sale, general administrative expense, avoidable inefficiency, and unrelated overhead may require different accounting treatment. Establish capitalization rules before configuring categories.
Using one allocation method for every charge
A single default method makes data entry convenient, but it can create distorted product costs. Freight, insurance, duty, and handling do not necessarily have the same cost driver.
Entering costs against the wrong receipt
When a shipment arrives in multiple parts, users sometimes attach the full charge to the first receipt. This creates an inaccurate cost profile and makes later reconciliation difficult. The receiving procedure should explain how freight and duty are assigned across partial receipts.
Duplicating the vendor bill
If the landed amount increases inventory and the vendor bill also posts the full amount as an expense, the business records the cost twice. The accounts payable procedure must distinguish the inventory-related charge from any separate expense component.
Ignoring currencies and subsidiaries
A purchase order, item receipt, freight invoice, and customs charge may use different currencies or subsidiaries. Test exchange rates, intercompany restrictions, tax treatment, and account mappings. Currency differences can create a variance that is unrelated to the allocation method itself.
Failing to test returns and corrections
A returned item may reverse inventory quantity and cost, but the treatment of related freight and duty requires a documented policy. Test item returns, vendor returns, receipt corrections, and credit memos before users rely on the workflow.
Reporting and Controls for Landed Cost
A useful landed cost process includes reporting that connects the charge to the receipt, item, vendor, location, and accounting period. Finance should be able to identify how much landed cost was applied, which categories were used, and whether estimated amounts remain unreconciled.
Useful controls include:
Reconciliation of landed cost categories to vendor bills
Review of unusually high allocation amounts
Exception reporting for missing item weight or volume
Comparison of estimated and actual charges
Approval thresholds for manual adjustments
Period-end review of open receipts and unbilled charges
Audit trails for changes to receipts and cost adjustments
NetSuite saved searches and standard reports can support these controls, while SuiteAnalytics Workbook can provide more flexible analysis where the account has the required functionality. A report should not only show the total landed cost. It should show the calculation context, including the receipt, allocation basis, category, and responsible user.
For businesses with high transaction volume, integration may be appropriate. An external freight, customs, or transportation system can send cost details into NetSuite, but the integration should pass enough information to preserve traceability. A total amount without shipment, category, currency, and receipt references creates an accounting entry that is difficult to audit.
How to Test a Landed Cost Setup Before Go-Live
Testing should use representative transactions rather than a single simple purchase order. Build a test matrix that includes ordinary receipts and the exceptions most likely to expose configuration problems.
At minimum, test:
One receipt with a single item
A receipt with multiple items
A partial purchase order receipt
Quantity-based allocation
Weight- or volume-based allocation
Value-based allocation
Multiple landed cost categories
A foreign-currency transaction
A serialized or lot-numbered item, if used
A vendor bill that differs from the estimate
A return or receipt correction
A transaction crossing an accounting period
For every case, capture the expected result before entering the transaction. Compare the expected line allocation, inventory value, general ledger impact, inventory report, and margin report against the NetSuite result.
User acceptance testing should include the people who perform the work. Finance should validate accounting, receiving should validate usability, purchasing should validate purchase order behavior, and accounts payable should validate invoice matching and reconciliation.
If your organization needs help documenting requirements, testing integrations, or governing a NetSuite inventory process, contact Versich to discuss your NetSuite requirements.
Conclusion
A reliable landed cost process in NetSuite connects purchasing, receiving, accounts payable, inventory accounting, and financial reporting. The configuration itself is manageable, but accurate results depend on the choices around cost categories, allocation methods, item data, estimated charges, vendor bills, and exception handling.
Start with the accounting policy, configure only the categories and methods the business can govern, and test the full transaction lifecycle from purchase order through inventory sale. When the workflow is documented and reconciled consistently, NetSuite provides a stronger view of true product cost, inventory value, and gross margin.
