About Marty

Hi @BGoodwin, Yes, we have a defect that is stopping this tab from working correctly. We are working on a fix for this issue. Should have it resolved as part of the December 1st release, at the latest. Thanks, Marty ... View more

Hi @FionaS, Where destination line items are created with an "Associated Subscriber" (Water Rates, Council Rates, Body Corporate Fees, Third Party Beneficiary, GST Withholding etc.) these will be displayed for the associated subscriber when they are on the signing screen. I suspect that in your scenario you were specified as the  associated subscriber for the three line items in question. Which is why they appeared at the top of your signing screen. In the November release we'll be updating the instructions on the signing screen to say "These are the destination line items that your organisation has created, or are associated with. Please confirm the details are correct and consistent with your instructions before signing." Does that address your concerns?   Thanks, Marty ... View more

Hi @Schofield, Thanks for your feedback! We haven’t built any order or sorting logic on these screens, hence the random nature of these lists. But I agree, it can be frustrating. Sorting would be useful, but in the short term we might just build some default ordering logic (alphabetic or time created) to prevent items jumping around when refreshing the screen. I’ll add this to a future release.   Thanks, Marty ... View more

Hi @CraigVL, @Karolidis_and_Co, When designing the Settlement Notifications functionality we asked prospective users whether they'd like the emails to be visible to all or hidden. There was some debate, but most people felt that transparency would be beneficial. For example to prevent duplication. But it's clear that one size does not fit all. Would having the option to tag a  Settlement Notification as 'private' to  hide it from other participants in the workspace address your concerns?   Thanks, Marty ... View more

Hi @Clara, I've had a look at your workspace. The lack of a Consent document is causing a Lodgement Verification error. Because this is a Lodgement Case level error we display it against the Lodgement Instructions document (LI). Hence the task to address an issue with the  LI. However, I can see a few issues here. First of all, the Responsible Subscriber looks after the LI, so any tasks relating to it should be assigned to them. In the case of your workspace this is the Incoming Mortgagee. Second of all, it's usually the Mortgagee on Title's responsibility to create a Consent document. And I can't see any task or other alert that would prompt them to do so. I'll raise both of these issues internally. In the meantime, perhaps send a conversation to the MoT asking them to create a Consent document. Once they do this, the error and task assigned to you will disappear. Thanks, Marty ... View more

Hi @LeFevre, Sorry for the delayed response. PEXA doesn't have a report to cover this, but the document's status in the workspace is updated when it is registered. See below screenshot for example. Hopefully that's enough detail for you not to need a title search.  We also send an email notification upon successful settlement and lodgement. But if you're interested in registration then this email wouldn't meet your needs. Thanks, Marty ... View more