DocsHead contractorRecording a claim you have received

Recording a claim you have received

Entering a subcontractor's payment claim as it was served on you, by hand or read off their document, and the schedule queue that tracks the answer you owe.

  • Reviewed 20 Oct 2026
  • 8 min read
  • Head contractor

When a subcontractor serves a payment claim on one of your companies, you record it here. It is not sent anywhere. The deadline for the payment schedule you owe in reply runs from the day the claim was served on you, whether or not you have recorded it yet. Recording it is what lets the platform track that deadline, and puts the claim in your schedule queue until you answer it. Record a claim as soon as it arrives.

Before you start

The head contractor features are switched on for an organization by paymentclaims.ai. They are not self-service, so if you cannot see them, contact us.

Once they are on, set each company that receives claims to Head contractor or Both under Settings → Contracting mode. Both is for a company that also claims on its own head contract, and it keeps everything it already does. The mode changes what the navigation shows, and switches nothing else off. Setting up as a head contractor walks through the rest, from the first project to the first subcontract on it.

A company in Both has a switch at the top of the sidebar: Head contractor or Subcontractor. Each side shows its own overview and pages. The schedule queue and your projects are on the Head contractor side, and your claims and their reports are on the Subcontractor side. Contracts and counterparties are on both, each filtered to that side, and you can clear the filter on the page. The switch remembers your last choice for each company.

You can record a received claim only on a contract where your company is the respondent, the party claims are made against. Owners, admins and members can all record one.

Recording it

Open the subcontract and choose Record a claim received at the top of its page. Everything happens on that one page, whether you have their figures read for you or type them in.

Their claim

The page opens on a place to drop their claim. Drop it there to have it read. The documents and your contract's items are read by an AI model, and the figures it finds fill in the fields below, matched against your contract's items. It takes a moment; you can leave the page and come back to it. If you would rather not wait, choose Stop and type it in; once it has been read, Type it in instead does the same. If it cannot be read, the page says why. Either way the file stays on the claim as their document, and you type the figures into the same fields. To read a different file instead, drop it on the page.

You can also drop their claim into Add documents at the top of the subcontract. Once it is sorted it shows Claims received beside it; File them brings you to this page with the reading open.

If you drop several files that hold more than one claim, the page shows one claim at a time, oldest period first, and says which one it is. Recording it brings up the next.

You do not have to drop anything. Choose Type it in instead, under the place to drop their claim, and the fields appear empty for you to type. You can still drop their claim at the top of the page afterwards to have it read instead.

The claim as it arrived

  • Their claim reference, exactly as it appears on their document.
  • Claim period.
  • Date they issued it, if the claim shows one. This is optional.
  • GST, meaning whether their claim charges it.
  • How it reached you: by email, by post or by hand.
  • Date served on you. This is the day the claim arrived, not today and not the date printed on it. The response deadline counts from this date, so it is the field to get right. Once you enter it, the page shows the date your payment schedule is due by.

A reading never fills in the last two, because a claim does not state them.

Fields that were read are marked Read, and change to Edited when you change them.

What they claimed

This is a grid of the contract's items with their contract value, what was claimed before, what is claimed this period and the retention withheld. Below the items, a retention release they requested and any one-off charges they added, such as an administration fee, go in rows of the same grid. A reading does not read one-off charges, so add those yourself.

A line that was read is marked Read, or Read · check where the reading was unsure of it, and Edited once you change it. A line on their claim that matched none of your contract's items is shown to you above the grid, not placed against the closest one: put it against the right item, or record the variation it belongs to and choose Check again against the contract.

Where their claim states progress as a percentage, type it in the % complete column and the claimed figure follows. It is the share of the whole item finished to date, not the share claimed this period, so a line at 50% before that their claim puts at 80% claims the 30% between. If the period you chose is earlier than a claim for work already recorded on the contract, the column is not offered, because what was claimed before already includes that later claim. Enter the claimed figures instead.

The retention column is what they withheld. On a claim you type, each cell starts at what your contract's terms give, so change it to the figure their document prints, and enter 0 where it withholds nothing. On a claim that was read, a blank retention cell has to be filled in before you can record it. Where theirs differs from your contract's figure, your contract's figure shows under theirs in the same cell, marked Differs. You still record their figure: the difference is a point to answer in your payment schedule, and the claim page shows it again when you get there.

The bottom line

Under the grid, the page totals the claim the way a claim document does: claimed this period, less retention, plus any release and one-off charges, the net, GST and the total including GST. These are the figures that will be recorded. Where their claim was read, the totals printed on their document sit beside them, with a tick where the two agree and the difference where they do not. On a claim you type, you can type the totals their claim prints into that column to have them checked the same way. They are only a check: they are not recorded, and a difference does not stop you recording the claim. A difference is not corrected for you: check which figure is wrong, which may be theirs.

Recording it

Record this claim saves it. Until you do, there is no claim and no deadline is counted. The bar beside the button says what is still needed, if anything.

Some claims raise a point you may want to answer in your payment schedule: it was served outside the window the contract allows, after the contract was terminated, before the end of the period it claims for, or in a month another claim already names. Each one shows on the page above the button, with the fields it concerns marked. Recording the claim concedes nothing, so tick Record it anyway and record it. If you change one of those fields, the point is checked again when you next record.

Add a note is optional, and for your own reference only.

Each contract can have one reading open at a time. If one is open when you come to the page, you are offered it.

The schedule queue

Schedule queue in the sidebar lists every claim served on your companies that still needs a payment schedule, across every project. Each row shows the subcontractor, project, contract and claim, the date served, when the schedule is due and the amount claimed, with the total of the claims shown at the foot. Deadlines are counted on each contract's own jurisdiction calendar.

Each row is tagged with how close its deadline is: Overdue, Urgent, Soon or Comfortable. You can filter the queue to one of those, and sort it by Least time remaining (the default), Earliest served or Largest claimed. With any sort other than the default, an overdue claim is not necessarily at the top. The Schedule column shows Not started until you start one, then In progress. The button beside the amount is the next step: Prepare, Continue for a draft, or Issue once the schedule is ready to go out, where the platform issues schedules for the contract's jurisdiction.

A claim leaves the queue only when a schedule is issued. Saving a draft does not answer the claim, and the deadline keeps running while a draft sits there. See preparing and issuing a payment schedule.

If the head contractor features are switched off for your organization, the claims you have already recorded stay where they are. They keep opening, and their deadlines keep being counted, but you cannot record a new claim.

Internal notes and files

While you assess a claim, you can keep notes and files on it for your own team: a site measure, a memo from the project manager, a reminder of what is still in dispute. Add them under Internal notes on the claim's page. They also appear, read-only, above the grid when you prepare the payment schedule, so the person writing the schedule has them in view.

Only people in your organization who can see the claim see them. They are never sent to the subcontractor, and they do not appear on the payment schedule or in its email.

A note cannot be edited once it is added, so a colleague who has read it can rely on it. If a note is wrong, delete it and add a new one. You can delete your own notes and remove the files you added; an owner or admin can remove anyone's. A note holds up to 5,000 characters, and a claim holds up to 20 files.

Was this page useful?Something wrong? Contact support