Paystruct

Talk to us

Questions about Paystruct, about pricing, or about whether it fits the way you run your claims. Email is the fastest way in, and it is read by the people who build the product.

However you reach us, it is the same people

Email

Write to support@paystruct.com.au about anything: how the product works, pricing, teams and volume, a bug, or your account. Everything that comes in is read.

In the app

If you already have an account, log in and open Support from the navigation. It reaches the same people, and it arrives with your account attached, so nobody has to ask which contract or claim you mean.

Log in

Teams and volume

Organisations running many contracts can ask about multiple users, help setting up the first contracts and claims, and priority support. Tell us how many contracts you run and who needs access.

See pricing

Send the dates, even the ones you are unsure about

Almost everything under the BIF Act turns on dates and on what the contract says. Six lines of detail will get you a far more useful answer than a page of background, and it saves a round of questions.

What to include
  • The contract. What form it takes (AS 4000, AS 4902, a subcontract, something bespoke), and which entities are named as the parties.
  • The jurisdiction. Where the work is being carried out. Paystruct is written to the Queensland Act, and that is where it is at its strongest.
  • What happened. What you claimed, and what came back: a payment schedule, part payment, a phone call, or nothing at all.
  • The dates. The reference date, the date the claim was served, how it was served, the date any schedule arrived, and where the job sits today.
  • The documents. The claim itself, any payment schedule, and the payment clauses of the contract.
  • What you want. Whether you are asking how to do something in Paystruct, or asking what the position is.

What we can and cannot help with

What we can help with

  • Setting up a contract: reference dates, retention, securities and the schedule of works.
  • Bringing claims you have already served into Paystruct so the numbering and history carry on.
  • Why a compliance check is showing, and exactly what it is measuring.
  • Claim packs, attachments, payment schedules, service records and exports.
  • Accounts, access, pricing, teams and volume, and anything that looks like a bug.

What we cannot do

  • Give legal advice. Paystruct is software, not a law firm, and nothing we send you is advice.
  • Tell you whether your claim is valid. That turns on your contract, your facts and the Act.
  • Advise on an adjudication, or act for you in one.
  • Advise on a dispute, a termination or a final claim. Those are worth a construction lawyer, and we will say so.
  • Decide what you should do about a respondent who is not paying.

One thing worth saying plainly: if you are close to a deadline, do not wait on us. The response windows under the Act are short, they run whether or not anyone answers your email, and a reply from us is not a substitute for advice.

A lot of it is already on the site

If the question is about how security of payment works in Queensland, or about how a part of the product behaves, there is a good chance it is written down. Start there and write to us about what is left.

  • Guides: plain-English guides to security of payment in Queensland.
  • Help centre: setup guides and product documentation.
  • Pricing: what each plan includes.
  • About: why Paystruct exists and what it will not do.
  • Legal: privacy policy and terms of use.