The Universal Payment Report includes a number of unique features, allowing for detailed customisation and advanced use of the report. This article will explain each of those features, including how they work, and why they may be useful to consider for your reporting processes.
Please note: Currently, this report is only visible for select customers. If your company has not requested to use the report, you will not see it available in your view of the system. If you believe the report would be useful for your company's accounting practices, please reach out to your Account Manager or our Support Team (support@nomosone.com) to discuss further.
Agreement Filtering
To run the report based on a certain Agreement filter:
- Choose the “Filter Groups” option.
- In the “Group” field, type a forward slash (/). A list of Agreement-related data fields will appear. You can search within the list to find the exact data field you want to use.
- Select the data field you want to filter the group by. It will appear in in the text box.
- Type an equals sign (=), then, in quotation marks, enter the value that you want to see Agreement information for.
As an example, the filter for the Report to only display payment information from lease-type Agreements would be:

Some examples of other filters you may want to use are:
-
agreement.agreementType="Sublease"- this will only display payment information from sublease-type Agreements. -
agreement.currency="NZD"- this will only display payment information from Agreements with New Zealand Dollar selected as the currency. -
agreement.currency="AUD"- this will only display payment information from Agreements with Australian Dollar selected as the currency. -
agreement.paymentMode="advance"- this will only display payment information from Agreements with “in advance” selected as the payment mode.
Custom Data Field Filtering
You can also use Agreement Custom Fields to filter which Agreements are included in the report. The syntax for this would be agreement.custom.ExampleCustomField="Example Data". The start of each individual word in the custom field name needs to be capitalised, and the data in the quotation marks needs to exactly match what has been recorded for each Agreement.
For a custom field named “Region”, filtering for Agreements where the recorded region is “Otago”, the syntax would be agreement.custom.Region="Otago". For a custom field named “Cost centre”, filtering for Agreements where the recorded bank name is “Bank of New Zealand”, the syntax would be agreement.custom.CostCentre="Bank of New Zealand".
Column Builder Features
There are a few features unique to the Column Builder section that we wanted to highlight: the ability to exclude automatic wash up/pro-rata payments, to recognise holdover Agreements, to increment the values of your report output, and to view taxation information for non-rent payments.
Automatic Wash Up/Pro-Rata Payments
The Universal Payment Report recognises if any of your rent payments are “Wash Up” payments. These payments may occur when a rent review or change in rent doesn't line up with the Rent Payment Date. If paying rent in advance, on the following Rent Payment Date, there will be a pro-rata rent amount recorded. This is to account for the additional rent that would have been paid between the date of the change in rent, and the next Rent Payment Date.
If you run the report without using a Preset, the default Column Builder set up will include a column called Detail. If any payments are identified as “wash up”, this column will produce the word “remove” for those payments.
In the lower left corner of the Column Builder, you will see a check box to “exclude rows with the value REMOVE”. If this is ticked, the report output will not include any rows that include the word “remove”, meaning payments identified as wash ups will not be included.

Please note: The “Exclude rows with the value REMOVE” check box will apply to any rows that include the word “remove”, not just the Detail column (regardless of format). If you have other columns that can produce the word “remove” in the report output rows, the check box selection will apply to those rows too.
Holdovers
If you have entered into a Holdover arrangement on any of your Agreements, you can reflect this in the Universal Payment Report.
Please note: Flagging this Agreement as “Holdover” using the Sub Mode feature does not actually alter how your Agreement appears or behaves in the system – it is solely reflected in the Universal Payment Report. To accurately reflect your Agreement being in holdover, allowing you to continue both contractual and financial management of the Agreement, you will need to follow one of the processes outlined in this article.
To flag your Agreement as “Holdover”:
- In the current version of the Nomos One system, navigate to the Agreement you need to flag as “Holdover”.
- Click “Action”, then “Repair Data” in the top right corner of the Agreement overview page.
- On the Settings page, scroll to the Sub Mode section, and select “Holdover”.

- Leave the selection as “Date”.
- Enter an Expected End Date for your Agreement. The Universal Payment Report will record that payments stop on that date. You can always update this date if the circumstances of your holdover arrangement change. Note again that your selection here will not impact your Agreement in any way, as it only alters the treatment in the Universal Payment Report.
- Do not make any selection for the “Accrue payments” option, as it does not impact anything.

- Click “Done” at the top or bottom of the page to return to the Agreement timeline.
To see this reflected in your Universal Payment Report:
- Navigate to the report in OneLease (Beta).
- Open the Column Builder.
- In the blank column at the bottom, enter a Column Name. Something like “Sub Mode” or “Holdover” would be appropriate here.
- In the Value field, begin typing “/submode”. This will bring up the data field
agreement.subMode. Click it to add the data field to the Value field.

- Remember to click “Add” so the column is included in your report output.
- Click Run Report.
For any Agreements flagged as “Holdover”, the output will display “Holdover” in the column you just created. For Agreements not flagged as “Holdover”, the output will be blank.

Incrementing
The Universal Payment Report offers an easy method of incrementing identical Agreement values in your report output. To do so:
- In the column you want to increment, type parentheses around the text that is currently in the Value field.
- Type “INCREMENT” before the first parentheses. You need to use all capital letters when typing “INCREMENT”, meaning that typing “increment” will not work.
If an Agreement produces multiple rows in the report output (e.g., if there are multiple payments for the Agreement during a month, or the report has been run for a longer time period), any identical outputs for those specific rows will be incremented. This appears as a hyphen and relevant number after the standard output.
For example, we have used the INCREMENT method for the Payment Type column:

The report has been run for 3 months. This produces the following output:

This feature makes it easy to display how many of a certain data point occur for the same Agreement within the reporting period. In the above example, using INCREMENT shows us how many of each payment type occur for each Agreement during the 3 month reporting period.
Taxation
For non-rent payments, i.e., those found in the IFRS Component and Non IFRS Component sections of the Rent & Payment page, you can view the taxation details using two columns.
Using the Value field, type “/payment.t” to bring up the data field “payment.taxation”. This field will produce one of four outputs for each payment, depending on the option selected for the Taxation field when setting up the payment. These four options and their relevant outputs are:
| Component Payment Taxation option | UPR output - payment.taxation | UPR output - payment.gstStatus |
| Plus Tax | Plus Tax / Tax Excluded | P |
| Incl. Tax | Tax Included | I |
| Exempt | Tax Exempt | E |
| Tax Free | Tax Free / Tax Excluded | F |
Using the Value field, type “/payment.gs” to bring up the data field payment.gstStatus. This field will produce one of four letters: P, I, E, or F, depending on the option selected for the Taxation field when setting up the payment. You can find which output will appear - depending on the taxation option chosen - in the table above.
These fields can help to output useful information about how each of your non-rent payments is being taxed. These fields can also be used to produce tax-related calculations in the report. For example, if you want to see the amount of a payment classed as “Plus Tax / Tax Included”, with the tax amount added on, you would enter the following into the Value field: IF(payment.gstStatus = “P”, payment.amount*1.15," "). This would produce the tax inclusive amount for payments where the GST status is P, based on a tax rate of 15%. For payments where the GST status is I, E, F, or blank, this would produce a blank output.
Please note: As you will have seen in the table above, the output options “Plus Tax” and “Tax Free” both have “Tax Excluded” on the end. In practice, both options are actually the same - they describe the amount of money before tax has been applied. They were created as separate options for the payment set up process, so you are able to choose whichever option fits your preferred payment terminology best. We would recommend being consistent in which option you choose across all of your Agreements, as that would make any subsequent use of the information in the UPR more simple and effective.
Mapping
The Mapping section allows you to create specific “keys” that can then be used in columns. These keys can only pull information from entities and assets (properties). These keys are similar to filters, in that they allow you to narrow down information about entities and assets so that you just get the information you need.
To create a key:
- Input a Key Name. This is what will create the second half of the key.
- In the Value section, type a forward slash (/) to choose from a list of entity and asset related identifiers.
- Still in the Value section, type an equals sign (=), then a value inside quotation marks, in order to filter the key.
- Click Add.
The keys you create can then be used in the Column Builder. Any of the available data fields for either Entity or Asset that appear in the Column Builder can be used in conjunction with keys. Using keys in the Column builder allows you to view more specific information about certain data fields. For more information on how to use keys in the Column Builder, check out this article.
Nomos One does not provide or purport to provide any accounting, financial, tax, legal or any professional advice, nor does Nomos One purport to offer a financial product or service. Nomos One is not responsible or liable for any claim, loss, damage, costs or expenses resulting from your use of or reliance on these resource materials. It is your responsibility to obtain accounting, financial, legal and taxation advice to ensure your use of the Nomos One system meets your individual requirements.