Landed Cost Table Fields Reference

Modified on Fri, 25 Sep at 9:31 AM

Landed Cost Lines are used to display the landed costs applied to line items of a purchase order.

Document Compatibility

The Landed Costs table is available for use on the following document templates:

Landed Cost fields are table fields, meaning they must be placed inside a correctly configured table in your Word document template. Merge fields and table Alt Text are case sensitive and must be entered exactly as shown below. For detailed instructions, see Table Field Setup in WorkGuru Document Templates.

Setting Up a Landed Costs Table

Payment merge fields must be placed inside a correctly configured table. The table requires:

  • A header row. Headers can be customised to suit your document.
  • A repetition line row containing your merge fields
  • The correct Alt Text Description. Set the table’s Alt Text Description to: 
    • LandedCostLines

When the invoice document is generated, WorkGuru will repeat the payment row for each lead landed cost associated with the purchase order.

Landed Cost Merge Fields

DescriptionMerge Field
Landed Cost Amount

[LandedCostAmount]

Landed Cost Name[LandedCostName]
Landed Cost Tax[LandedCostTaxAmount]

Troubleshooting

Table Does Not Populate

Check that:

  • The Alt Text Description is correct.
  • Capitalisation matches the required table name - alt text descriptions are case sensitive.
  • There is only one table of the same type on the document.
  • The table is supported by the document type.
  • There is applicable data to display.
  • The table has a header

Merge Fields Appear in the Generated Document

If fields such as [LandedCostName] appear instead of actual values, check:

  • The spelling of the merge field. 
  • Check capitalisation - merge fields are case sensitive.
  • Confirm the field belongs to the table type being used.
  • Confirm the field is supported by the document type.

Table Formatting Is Incorrect

Check that:

  • Header and repetition row columns align.
  • Cells have not been incorrectly merged.
  • Nested tables are configured correctly.
  • Each table has the correct Alt Text Description.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article