Purchase Order Summary fields allow you to display a repeating list of Purchase Orders associated with a Project or Production Job in your WorkGuru document templates.
- Purchase Order Information
- Supplier Information
- Dates
- Purchase Order Financials
- Weight and Volume
- Delivery Information
Purchase Order Summaries vs Purchase Lines:
- Use PurchaseLines when you want to display individual Purchase Order line items associated with a Project.
- Use POSummaries when you want to display one summary row for each Purchase Order associated with a Project or Production Job.
For the complete list of Purchase Line fields, see the Purchase Lines Table Fields Reference.
Document Compatibility
The POSummaries table is intended for supported document types where multiple Purchase Orders are associated with the underlying record:
- Projects- see Project Document Templates
- Production Jobs - see Production Job Document Templates
Unlike Universal Fields, Purchase Order Summary fields must be placed inside a correctly configured table. WorkGuru automatically repeats the table row for each applicable Purchase Order. Merge fields and Table Alt Text are case sensitive and must be entered exactly as displayed below.
Setting Up a Purchase Order Summary Table
Purchase Order Summary merge fields must be placed inside a correctly configured table. The table requires:
- A header row
- A repetition row containing your merge fields
- The correct Alt Text Description. Set the table’s Alt Text Description to:
- POSummaries
When WorkGuru generates the document, the purchases line row is repeated for each applicable purchase order on the transaction. For detailed instructions, see Table Field Setup in WorkGuru Document Templates.
Purchase Order Information
| Description | Merge Field |
|---|---|
Purchase Order Number | [POSummaryNumber] |
Purchase Order Status | [POSummaryStatus] |
Purchase Order Description | [POSummaryDescription] |
| Accounting Reference Field | [POSummaryAccountingNumber] |
| Billable Status (Yes/No) | [POSummaryIsBillable] |
| Landed Cost Purchase Order (Yes/No) | [POSummaryIsLandedCostPo] |
| Purchase Order Exchange Rate (1 = default currency) | [POSummaryExchangeRate] |
| Purchase Order BackOrder Number | [POSummaryRevision] |
Supplier Information
These fields allow you to identify the Supplier and associated Supplier Invoice for each Purchase Order.
| Description | Merge Field |
|---|---|
Supplier Name | [POSummarySupplierName] |
| Supplier Invoice Number | [POSummarySupplierInvoiceNumber] |
Dates
All dates print in the DD/MM/YYYY format
| Description | Merge Field |
|---|---|
PO Issue Date | [POSummaryIssueDate] |
PO Expected Date | [POSummaryExpectedDate] |
PO Received Date | [POSummaryReceivedDate] |
| Supplier Invoice Date | [POSummaryInvoiceDate] |
| Supplier Invoice Due Date | [POSummaryInvoiceDueDate] |
| PO Emailed to Supplier Date | [POSummaryEmailedDate] |
| PO Sent to Accounting Date | [POSummarySentToAccountingDate] |
Purchase Order Financials
| Description | Merge Field |
|---|---|
| Forecast Total | [POSummaryForecastTotal] |
| Invoiced Amount | [POSummaryInvoicedAmount] |
| Tax Total | [POSummaryTotalTax] |
| Purchase Order Total | [POSummaryTotal] |
Purchase Order Total Including Tax | [POSummaryTotalIncTax] |
Weight and Volume
These fields can be useful for logistics, freight and delivery documentation.
| Description | Merge Field |
|---|---|
Purchase Order Weight | [POSummaryWeight] |
| Purchase Order Volume | [POSummaryVolume] |
Delivery Information
Displays delivery information associated with each Purchase Order.
| Description | Merge Field |
|---|---|
| Delivery Address 1 | [POSummaryDeliveryAddress1] |
| Delivery Address 2 | [POSummaryDeliveryAddress2] |
| Delivery City | [POSummarySuburb] |
| Delivery State | [POSummaryState] |
| Delivery Postcode | [POSummaryPostcode] |
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 [POSummaryNumber]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
Feedback sent
We appreciate your effort and will try to fix the article