In this article:
- Finding the Unpaid Client Invoice Merge Fields
- Using the Unpaid Client Invoice Merge Fields
- Statement of Accounts Template
Actionstep offers a set of merge fields to display details for outstanding invoices. For any invoice with an amount still owing, the amount paid, balance due, invoices date, invoice reference, and invoice total can be displayed. This is helpful for conveying to clients, the specific amounts they can pay for specific invoices.
Finding the Unpaid Client Invoice Merge Fields
The Unpaid Client Invoice merge fields can be found in Actionstep's merge field list.
To find this list:
- In Actionstep, go to Admin > Document assembly.
- Click Manage in the Merge field list section. The Merge Field List page appears.
- Click the Filter drop-down list and choose
- From the Data Source list, choose Unpaid Client Invoices.
The available merge fields are:
Merge Field | Description |
UnpaidClientInvoice_Date | Date for the invoices |
UnpaidClientInvoice_Reference | Actionstep invoice reference |
UnpaidClientInvoice_TotalInclusive | Total of the invoice, including tax |
UnpaidClientInvoice_AmountPaid | Amount that has been paid on the invoice |
UnpaidClientInvoice_BalanceDue | Amount still owing on the invoice |
Using the Unpaid Client Invoice Merge Fields
The Unpaid Client Invoice merge fields can be used in bill/invoice templates.
Following is an example of a repeating table:
Date | Invoice Ref. | Invoiced Amount | Paid Amount | Amount Due |
[[*REPEAT|data_source=unpaid_client_invoice|tablerow*]] [[UnpaidClientInvoice_Date|fm=entry |rn=*]] | [[UnpaidClientInvoice_Reference|rn=*]] | [[UnpaidClientInvoice_TotalInclusive|rn=*]] | [[UnpaidClientInvoice_AmountPaid|rn=*]] | [[UnpaidClientInvoice_BalanceDue|rn=*]] [[*REPEAT|END*]] |
Which then merges a table that looks like this:
Statement of Accounts Template
You can download and edit a sample Statement of Accounts template. It is located at the end of this article.
Related Articles:
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