Understanding Bill Field Settings

Modified on Wed, 1 Jul at 12:48 PM

Bill Fields are used to determine what information is captured and displayed against documents in Payreq Delivery. They are a subset of the Mail Details, and are separate from Contact Fields.

This document-specific information can include additional account information, or values that may change from one document to the next even though the Contact/Account/Customer details remain the same.

These are commonly used where the value needs to be displayed in Payreq Delivery, used in a template, or made available as part of the document record.


Example Payreq Delivery account set up

In this example, the Account Number is the mandatory unique identifier (the Contact ID) and the first two Bill Fields are being used to capture additional key reference details displayed on the bill:

Bill Field #1 is the Customer Number.
This is the payment reference shown on the bill. It may be different from the Contact ID, depending on the sender’s configuration and payment requirements.


Bill Field #2 is the Property Address.
This is the property or service address printed on the bill. It can be useful for councils, utilities and other senders where the customer may recognise the bill by the property or service location.


Important Notes

The Contact ID must still be supplied for each bill so Payreq can match the document to the correct contact.

Bill Fields should not be used as a substitute for maintaining the Contacts file. If a value is used to identify or authenticate the customer, it should be configured and supplied through Contact Fields.

Bill Fields should be used for information that appears on the bill itself, such as payment references, property addresses, document references, due dates and bill-specific customer display names.

Where a sender is using a PDF template or manual email template, the same field labels should be used consistently across the Bills file, PDF parsing rules and email template setup.

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