Purchase Order Fields Reference

Modified on Thu, 24 Sep at 9:39 AM

Purchase Order fields allow you to insert information from a WorkGuru Purchase Order into your document templates.

These fields can be used to display information such as:

Document Compatibility

Purchase Order fields provide summary-level information about a Purchase Order and when linked, are also supported on the following document templates:

Purchase Order fields are Universal Fields, which means they can be placed directly within a document template and do not need to be inside a repeating table. If you need to display repeating order line information, such as individual products, you will need to use Table Fields. Common project table types include:

See the Table Fields Reference for instructions on creating and configuring table fields. Merge fields are case sensitive and must be entered exactly as displayed below.

Purchase Order Information

DescriptionMerge Field

Purchase Order Number

[PurchaseOrderNumber]

Purchase Order Description

[PurchaseOrderDescription]

Purchase Order Date (DD/MM/YYYY)

[PurchaseOrderDate]

Purchase Order Expected Date (DD/MM/YYYY)

[PurchaseOrderExpectedDate]

These fields display the Project or Projects associated with the Purchase Order. For Advanced Purchases associated with multiple Projects, the related Project numbers are displayed as a comma-separated list, but the project names are not displayed.

DescriptionMerge Field

Related Project Number

[PurchaseOrderProjectNumber]

Related Project Name

[PurchaseOrderProjectName]

Delivery Address

These fields display the delivery address recorded against the Purchase Order.

DescriptionMerge Field

Delivery Address Line 1

[PurchaseOrderDeliveryAddress1]

Delivery Address Line 2

[PurchaseOrderDeliveryAddress2]

Delivery Suburb

[PurchaseOrderDeliverySuburb]

Delivery State

[PurchaseOrderDeliveryState]
Delivery Postcode

[PurchaseOrderDeliveryPostcode]

These fields can be combined to create a formatted delivery address on your Purchase Order document. For example:

[PurchaseOrderDeliveryAddress1]

[PurchaseOrderDeliveryAddress2]

[PurchaseOrderDeliverySuburb] [PurchaseOrderDeliveryState] [PurchaseOrderDeliveryPostcode]

Delivery Instructions

Use this field to display any delivery instructions recorded against the Purchase Order. 

DescriptionMerge Field

Delivery Instructions

[PurchaseOrderDeliveryInstructions]

Purchase Order Financials

These fields can be used together to display the financial summary of the Purchase Order.

DescriptionMerge Field

Purchase Order Subtotal

[PurchaseOrderSubTotal]

Purchase Order Tax Total

[PurchaseOrderTaxTotal]

Purchase Order Total

[PurchaseOrderTotal]

Purchase Order Weight and Volume

These fields display the total weight and volume associated with the Purchase Order.

DescriptionMerge Field

Purchase Order Weight

[PurchaseOrderWeight]

Purchase Order Volume

[PurchaseOrderVolume]

Purchase Order Custom Fields

Custom fields assigned to Purchase Orders can also be included in document templates. Use Custom followed by the custom field name. For example, if you have a Purchase Order custom field called:

SupplierQuoteNumber

the merge field would be: 

[CustomSupplierQuoteNumber]

Custom field availability depends on the transaction type the field is assigned to and the document type being generated. For more information, see the Custom Fields Guide.

Troubleshooting

Purchase Order Fields Are Blank

This occurs when the source field does not contain data and the merge field is correctly "nothing". 

Check that:

  • The applicable information has been entered against the Purchase Order.
  • Supported documents are linked to a purchase order.

Merge Fields Appear Instead of Values

If fields such as [PurchaseOrderNumber] appear in the generated document instead of their values, check:

  • Merge field spelling
  • Capitalisation
  • Document compatibility
  • That both square brackets are present

Merge fields are case sensitive.

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