Versions Compared

Old Version 4

changes.mady.by.user Fiona Hardy

Saved on

compared with

New Version Current

changes.mady.by.user Fiona Hardy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Performance updates have been applied to ensure the function runs more efficiently in the background and also that the information shown within the import receipts from bank statement screen loads quicker

  • The import receipts from bank statement screen has been updated to assist usability

  • New configuration options have been developed which:

    • Only match a statement item using a payment reference (held in Reapit)

    • Prevent saving when a match payment reference is not unique

    • Assign users to a statement item
      All three of the configuration options listed here are disabled by default

...

Tip

The ability to enter a payment reference for a tenancy, tenant, landlord or Direct Debit is already available on the system in the following locations

This is the reference used by the match imported receipts strictly on payment reference configuration option therefore, if you wish to implement this feature, you need to ensure that your payment references are entered and are unique - if more than one match is found for the reference that is entered against a statement item, then it won't match in the window and it will need to be assigned manually
e.g. if two tenants have the same reference, they will not automatically match in Receipts from Statement, and instead will need to be matched manually

A unique payment reference needs to be entered in the following locations for a tenancy, tenant, landlord or Direct Debit, as follows

Tenancy

  • Access tenancy and click Financial & Extensions tab

  • Enter Payment reference
    This field should be used if the reference is used by all tenants - if not, individual tenant references should be used instead (see Tenant section below)

    Payment Ref - tenancy.png
Note

The exclamation mark to right of field in the example above, indicates that the payment reference in use is not unique

This is just a warning flag - however, if the configuration option outlined in the next section - Prevent save when payment reference is not unique - is enabled, the record cannot be saved until the payment reference is changed

See next section for more information

Tenant

  • Access individual tenant record

  • Enter Payment reference

    Payment Ref - tenant.png

Landlord

  • Access landlord record

  • In Landlord’s Properties panel, right-click required property and select Add/Edit payment reference

    Payment Ref - landlord.png

  • Enter Payment reference and click Accept

    Payment Ref - landlord 2.png

Direct Debit

  • Access Manage Direct Debits screen

  • Enter Reference

    Payment Ref - DD.png

...

When a payment reference is not unique:

  • A exclamation mark is displayed beside the payment reference

    Payment Ref - tenant with alert.png
Tip

The duplicate reference must be changed to a unique reference in order to save the record

If duplicate references already existed on the system they will remain (flagged as duplicates) and will continue to remain with the duplicate reference if no changes are made to the record
Once changes are made, the requirement to change the duplicate reference will be flagged

Filter by label (Content by label)
showLabelsfalse
max8
maxCheckboxfalse
sortmodified
showSpacefalse
reversetrue
cqllabel = "rec-from-state"

...