About Marty

Marty · ‎15-04-2019

Hi @Limeconveyancing, Just saw your message. Not sure what caused the Stamp Duty technical error. But I see now that your workspace is settling. Hopefully you don't encounter the issue again. Thanks, Marty

Marty · ‎25-03-2019

Hi @BytheBay, Thanks for the feedback! We'll look at the usage patterns for these panels and decide whether to do a holistic change or implement some sort of preference setting. Thanks, Marty

Marty · ‎08-03-2019

Hi @DMc, They could have javascript disabled. Here's a website they can check whether that's the case: https://www.whatismybrowser.com/detect/is-javascript-enabled Alternatively, try with a different browser? Thanks, Marty

Marty · ‎06-03-2019

Hi Community, This year PEXA is continuing to make enhancements to the platform based on your feedback. Some feedback we’ve received is that you want to know what you have to do next in the platform as fluidly as possible. As a result, the team are working on improving the current tasks functionality in PEXA, what we’re currently calling, PEXA Flow. It’ll tell you what you need to do in your workspace next, what you can’t yet do and why, and the next steps of other participants. It’ll also tell you when you need to complete your tasks by and whether your workspace is falling behind schedule. You’ll be able to access PEXA Flow at any point during your transaction via a slide out on the right of the screen: This is subject to change as we test it with PEXA members. If you have any questions or feedback, please let me know below. Thanks, Marty

Marty · ‎06-03-2019

Hi @TonyaDixon, Thanks for the feedback. You'll be pleased to hear we are making this exact change in the next PEXA release. From the 8th April (Release 9.1.2) the User Report will contain a 'Last Active' column to help you identify inactive users within your organisation. I'd recommend using the CSV option so you can easily sort all your user records by this new piece of data. R9.1.2 Release Notes Thanks, Marty

Marty · ‎13-02-2019

Hi @Weston3130, Thanks for reaching out. When I print PEXA screens on my machine, the margins seem ok. Nothing gets cut off. Could you send me what it looks like when you print? Email or private community message is fine. Thanks, Marty

Marty · ‎25-01-2019

Hi @mjswan, Thanks for raising this with us. We'll apply a fix for this issue in an upcoming release. Thanks, Marty

Marty · ‎10-12-2018

Hi @CraigVL, @Karolidis_and_Co, You'll be pleased to hear that over the weekend we added the ability for you to tag Settlement Notifications as 'private', which hides them from other participants in the workspace. Let us know what you think of the new feature. Thanks, Marty

Marty · ‎14-11-2018

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

Marty · ‎13-11-2018

Hi @elynch, Yes. If you have a particular Workspace in mind, you can go to: Reports -> Workspace Activity Report -> Select Workgroup -> Select Workspace(s) This will give you the same entries as on the History screen, but with the addition of which user performed the action. Note: only actions performed by users within your organisation will have the user listed against them. A ctions performed by users from other subscribers will only have the subscriber listed. I hope that helps. Thanks, Marty

Marty · ‎05-11-2018

Hi @sylvester, Thanks for the feedback! We do have guidance in PEXA for some of the errors relating to documents: https://community.pexa.com.au/t5/Ideas-and-Suggestions/Document-Error-Guidance/m-p/9508#M577 But if there are errors that you find confusing, or that you think others will get confused by, let us know and we'll include guidance for them. Thanks, Marty

Marty · ‎26-10-2018

Hi @cpodosky, Thanks for the feedback! We do have this on to-do list. It hasn't been prioritised yet, so I'm not quite sure which release it might be included in. We'll keep you posted on any progress. Thanks, Marty

Marty · ‎24-10-2018

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

Marty · ‎23-10-2018

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

Marty · ‎08-10-2018

Great feedback, and yes, we’re working on solutions for when you’re out and about on your mobile phone. We have spent a lot of time recently working on a mobile responsive portal, called PEXAPlus. This is a new dashboard of all your PEXA workspaces, providing you with a visual view of your transactions, including a calendar view. It’s in pilot at the moment. For more details read our FAQ page here. We’re also reworking the Workspace Summary screen. This new screen consolidates all the statuses and indicators for the workspace, clearly informing you what’s outstanding, which will help you get your workspace ready for settlement. Thanks, Marty

Marty · ‎08-10-2018

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

Marty · ‎21-09-2018

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

Marty · ‎19-09-2018

Hi @Larraine, Stamp Duty must have encountered an error earlier this morning, but it was successfully retriggered at 11am. So that issue is now resolved. However, it looks like there’s still a bit of work to be completed for this workspace to settle today. Hopefully all participants will complete their tasks by end of day. Thanks, Marty

Marty · ‎06-09-2018

Hi @annafazzini, @Clarkee, We've been discussing the ability to broadcast messages live in PEXA to all impacted users for a while now. It's definitely on our to-do list, but probably won't be complete till next year. Thanks for the feedback, Marty

Marty · ‎06-09-2018

Hi @LG, Good suggestion. We'll soon be adding the TAC Exception panel to the Workspace Summary screen to make it more obvious when this occurs. But that won't solve your issue. I'll add your suggestion to our to-do list. Thanks, Marty

Marty · ‎22-08-2018

Yeah, we could look at that. We might just have to have a separate entry for the Re-supply to clearly delineate the pre-registration RIS from the post-registration RIS Re-supply, as opposed to the current approach of overwriting the data. To avoid confusion. I'll add it to our to-do list.

Marty · ‎22-08-2018

Ah, yes, you're right, @DMc. Workspaces lock post settlement to prevent data changes, such as Information Re-supplies. My bad. Looks like the registration status of a dealing on the document screen is the only real option within PEXA.

Marty · ‎20-08-2018

Hi @DMc, Yes, the behaviour is the same for all docs. The Land Titles screen is currently a snapshot of land title data at time of workspace creation (Registry Information Supply). It can be updated by triggering an Information Re-supply (cost $5), but there is not automatic trigger to update it, such as the registration of a doc. But perhaps this is something we could look at doing. In the meantime, the best place to check the registration status of a dealing is the document screen. Or if you'd like an updated snapshot of a land title's data on the Land Title screen, you'll need to trigger an Information Re-supply. Thanks, Marty

Marty · ‎20-08-2018

Hi @MichelleWhite, Sorry for the delayed response. On your first suggestion, would these invitation notes only be visible to you or the sender of the invitation? As for notes in the workspace, we don’t plan on providing such a facility any time soon. But we are looking into the ability for you to add your own tasks on top of the ones already generated by PEXA. Thanks, Marty

Marty · ‎20-08-2018

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

Marty · ‎25-07-2018

Hi @Kellylaw, @helene is correct. You can read more about the Settlement Notifications functionality here. Thanks, Marty

Marty · ‎23-07-2018

Hi @elynch, No, unfortunately we don't currently have such a capability. But I like the idea. I'll add it to our list for future consideration. For visibility of upcoming settlements, if generating the report is a bit tedious, maybe consider sorting your dashboard by the Settlement Date &Time. Thanks, Marty

Marty · ‎19-07-2018

Hi @NatalieCole, Do you have a Transfer document in your workspace yet? The Stamp Duty screen won't be accessible until a Transfer document is created. Thanks, Marty

Marty · ‎22-06-2018

Hi @Cory, You and I have discussed over email, but for anyone else that has the same feedback I thought I'd also respond here. Thanks for your feedback. We haven't heard of any push back from agents so far. When we were gathering the requirements for this functionality, there was a desire to replicate the look and feel of the existing Order on the Agent process as much as possible (letterhead, signature, scan, email) to ensure as little resistance from recipients as possible. But this doesn’t translate well to the new electronic world, so we opted for the fairly simplistic approach of text in an email. Having the ability to upload your company’s logo to be included in the email (analogous to a letterhead) was on the cards, but unfortunately capacity was an issue. Allowing subscribers to upload logos and patching them through into emails PEXA generates is harder than it sounds. Perhaps a future release will include it. Even so, when we analysed the existing Order on the Agent process we got the impression that the conventions of letterheads and signatures were just that, conventions. Hopefully the streamlined Settlement Notification process we've introduced will become popular enough to change these conventions. Even if that takes a while. Thanks, Marty

Marty · ‎08-06-2018

Hi @MargaretD, This error is caused by an invalid combination of values in the NOA. But it looks like you've already updated the Primary Construction Type to the correct value. Now you just need to edit the Lodgement Instructions in order to retrigger verification. Are you able to do that? Thanks, Martin

About Marty

Re: Manually trigger stamp duty verification?

Re: dashboard layout

Re: Sharing Feedback directly with PEXA

PEXA Flow | PEXA upgrade coming soon

Re: Inactive users | FAQs

Re: workspace margins are too wide

Re: Statement of adjustment error - describes vend...

Re: Property Information - Automatic email(s) adde...

Re: Recent Workspaces tab

Re: User Audit Activity

Re: Common messages in PEXA

Re: Destination Funds Details screen and we click ...

Re: Document Signing Page showing other party's De...

Re: Sorting Options (QOL Improvement)

Re: PEXA mobile app

Re: Property Information - Automatic email(s) adde...

Re: When can we "Complete Lodgement Instructions"

Re: Manually trigger stamp duty verification?

Re: settlement delay

Re: Acknowledging Positive Title Activity from the...

Re: Title Search/after settlement reports

Re: Title Search/after settlement reports

Re: Title Search/after settlement reports

Re: Making notes on a PEXA Invitation prior to acc...

Re: Title Search/after settlement reports

Re: Order on the Agent - New option in property in...

Re: Scheduled Reports Emailed

Re: Stamp duty verification

Re: Order on the Agent - New option in property in...

Re: Notice of Acquisition - VIC