Docketbook News

Both Sides of the Docket: Why Purchase-to-Pay Only Works When Everyone Wins

Written by Mark Shepherd-Smith | Aug 16, 2026, 11:24:35 PM

 Digital dockets only work when both parties hold the same record. Docketbook is a network-based digital docket platform for the Australian construction and infrastructure industry. Unlike portal-based systems that serve only one party, Docketbook gives the head contractor and the supplier a single version of the truth for every docket, while each runs their own side in their own account, on their own terms, with permanent access to their data long after the job finishes. 

 

The docket is the financial backbone
of purchase-to-pay

In construction, the docket is the proof. A digital docket is an electronic record of work performed or goods delivered. It proves the plant turned up, the crew worked the hours, and the load was delivered. It's created in the field, signed by the customer's representative, and shared as structured data rather than paper or PDF.

Everything downstream in the purchase-to-pay (P2P) cycle, from cost reporting and productivity, to accruals, claim assessment, invoice approval and payment, depends on that single piece of evidence being accurate and agreed.

When the docket is wrong, late, lost, or unsigned, the cost doesn't stay in the field. It shows up sixty days later as an invoice dispute, a blown accrual, a payment run held up, or a supplier chasing cash they earned last month.

So the real question isn't "how do we digitise dockets?" It's "how do we get both parties to agree on the same numbers, on the day, and keep that agreement traceable forever?"

That is an architecture question, not a features question.

 

 

Three architectures for digital dockets

There are three possible architectures for digital dockets: the Head Contractor portal, the Supplier-centric system and the Network Model, as shown in the table below.

 

1. Head-contractor portal

2. Supplier-centric system

3. Network model (Docketbook)

Who buys it

The head contractor

The supplier

Either party. Both hold an account

Where the supplier works

In the contractor's portal, in the contractor's language

In their own system

In their own account

Where the customer works

In their own system

In a supplier portal, or in their inbox

In their own account

What the customer receives

Structured data

PDFs by email, or another login

The same docket record, live

Who owns the data

The contractor's tenancy

The supplier's tenancy

Each party holds their own

A supplier with 8 customers

8 logins, 8 rule sets, 8 end-of-month rituals

1 system, but customers left outside

1 account, all customers

When the project ends

Supplier access ends with it

Customer keeps PDFs only

Each party retains their own records ⚑

Who absorbs the cost

The supply chain

The customer

Shared. Both sides gain

 

1. Head-contractor-centric portals

The contractor buys a system. Suppliers are told to log in to the contractor's portal to submit dockets.

What this typically means in practice:

  • The supplier works in the contractor's language, not their own.  The contractor's resource names, the contractor's structure, the contractor's process.
  • A supplier with eight customers logs in to eight different systems, each with its own login, its own rules, and its own end-of-month ritual.
  • The supplier has no ownership of the data. It lives in someone else's tenancy.
  • When the job ends, access ends. The record of work the supplier performed, their evidence, their history, their audit trail, all disappears with the project.

The contractor gets a good outcome. The supply chain absorbs the cost. And because the supply chain absorbs the cost, adoption is a fight on every project.

 

2. Supplier-centric systems

The supplier buys a system for their own operations. That's a genuine improvement for the supplier, but the customer is now on the outside looking in.

The customer ends up either:

  • logging in to yet another supplier portal (and a large project has dozens of suppliers, which means dozens of portals), or
  • receiving PDFs by email, which is a filing problem dressed up as a digital solution.

A PDF is not data. It can't be cost-coded automatically. It can't roll into a productivity report. It can't three-way match against a purchase order. Someone has to read it and type it in, and someone else has to check what they typed. Meanwhile the site engineer has no way to reject a docket on the day, so the first real conversation about whether the work was right happens when the invoice lands.

 

3. The network model

Docketbook takes a third approach: one docket, two owners, two experiences.

The supplier holds their account. The customer holds theirs. The docket is exchanged between them across the network, not uploaded into somebody else's system. Both parties see the same docket, the same status, the same line items, the same rates, at the same time. Each configures and controls their own side.

Neither party is a guest in the other's software.

 

 

A single version of the truth means
disputes are resolved in the day

Because both parties are looking at the same record, disagreement surfaces immediately rather than at invoice time.

 The site team signs the docket on glass, on their own device, or at their desk. They apply a cost code, then pass it to the engineer to accept or reject.   The value of rejection is that the issue gets resolved in the day, while the crew, the supervisor and the plant are still on site and everyone remembers what happened. A rejected docket is edited and resubmitted with the correct details.

Critically, the supplier sees that status change in their own account, in real time. They aren't waiting to be told. They can fix the problem before it ever becomes an invoice dispute.

By the time the claim is raised, the argument has already been had. And resolved.

In a study completed in 2026 by a major head contractor, it was found that invoices created on Docketbook had five times fewer issues than those sent by traditional means.  That means less effort, less noise and on-time payments for the supply chain.

 

Orders make invoices arrive pre-agreed

In Docketbook, rates and quantities are locked into the order before any docket exists. The supplier accepts the order, confirming the agreed rates. Order lines map the supplier's resources to the contractor's line items, so the data flowing back is meaningful to the contractor's ERP without translation.

The result is a three-way match - order, docket, invoice - that is already reconciled when the invoice arrives. Not reconciled later, by a person, in a spreadsheet. Reconciled by the data, because the data was agreed at every step.

Invoices that are accurate, agreed and easy to approve get paid on time. That is the whole point.

 Read more about order management and digital dockets.  

 

The customer doesn't even need to be a paying customer

This is the part that most systems can't do.

If a supplier sends a docket through Docketbook to a customer who isn't connected, the customer still receives it as a PDF by email, and they can sign it remotely via a link. 

But if that customer creates a free personal Docketbook account, something changes: they see every docket ever sent to them through the Docketbook cloud, in one place, permanently.

What that single point of access delivers:

  • Dockets never get lost. They aren't in an inbox, a glovebox, or a shared drive nobody maintains.
  • Nobody has to call and ask for a resend. The person who used to spend their week re-sending dockets gets that week back, and the person who used to chase them stops chasing.
  • It's data, not PDFs. Searchable, sortable, exportable, and available to flow into other systems.
  • Access outlives the job. The record is still there next year, and the year after, when the claim, the audit, or the dispute arrives.

The barrier to a shared version of the truth is now effectively zero.

Receiving dockets from a supplier already on Docketbook? Create a free account and keep every docket in one place. 

 

What each side gets

Each party controls their side of the process, and the capability is built for the job they actually do.

For head contractors and project teams

  • Know your committed cost before the invoice arrives. Every docket is cost-coded as it's accepted, with parent/child cost code hierarchies and granular budget, quantity and rate tracking in real time.
  • Settle disputes on the day. Accept or reject on site, in the web UI or the Site Manager app, with the supplier notified instantly.
  • One set of numbers for commercial and delivery. Budgets, quantities, production rates, costs, actual-to-date, forecasts and variance, pulled straight from accepted dockets. It replaces the non-standard site spreadsheet, and because it draws on the same data as the commercial process, the productivity report and the invoice tell the same story.
  • Assess claims against evidence. Supplier claims are assessed in the platform against pre-approved dockets and connected orders, with three-way match indicators showing what's ready to pay.
  • Get the data into the tools you already report from. Cost, cost-code and productivity data flows into Power BI, BigQuery and project data warehouses. See ERP integration for head contractors.

For suppliers and subcontractors

  • See every docket and its status across every customer, in one account. Including whether it's been signed, and whether it's been accepted or rejected.
  • Stop losing revenue to unsigned dockets. If work finished at the depot rather than on site, the docket goes out for the supervisor to sign remotely. No unsigned docket sitting in a ute becoming lost revenue.
  • Turn a month of dockets into a claim in a few clicks. A simple wizard built from dockets the customer has already accepted at rates they've already agreed.
  • Stop keying invoices twice. Create the invoice in Docketbook and push it straight to MYOB or Xero. No hunting for dockets at month end.
  • Get the commercials right automatically. Smart Dockets turn start time, finish time and breaks into a fully interpreted, commercially accurate docket, whether the rules come from a complex EBA, a plant hire schedule with allowances and surcharges, or a distance-based materials contract.

Same docket. Same truth. Two different jobs, each done properly.

 

 

Why the two-sided model is the only sustainable one

Any system that shifts cost onto one side of the transaction is fighting gravity. The party bearing the cost resists adoption, does the minimum, or quietly reverts to paper and email, and the system's data quality degrades until it isn't a source of truth at all.

Docketbook is built on the opposite premise. Suppliers, subcontractors and head contractors don't operate in isolation; they're one commercial system, and the docket problem isn't solved until it's solved for all of them at once.

When the supplier gets paid faster and spends less on admin, the contractor gets cleaner data, fewer disputes and better cost visibility. When the contractor codes and accepts dockets on the day, the supplier invoices with confidence and gets paid on time. The benefits compound rather than cancel.

That's a genuine win-win.  That's why the model holds up across projects, across companies, and across the years after the job is finished.

 

 

Common questions

How does Docketbook differ from a head contractor portal?

In a portal, the supplier works inside the contractor's system and loses access when the project ends. On Docketbook, each party holds their own account and their own data, and the docket is exchanged between them across the network.

 

Does a customer need to pay for Docketbook to receive dockets?

No. Customers can receive dockets by email as a PDF and sign remotely via a link. A free personal Docketbook account also gives them permanent access to every docket ever sent to them, as data, through the Docketbook cloud.

 

How much does Docketbook cost?

Pricing is built around your monthly docket volume, so you pay for what you use. Every plan includes unlimited users and a 7-day free trial, with Smart Dockets and accounting integration available as add-ons and enterprise options for larger deployments. Build a plan for suppliers and subcontractors or for head contractors. View our pricing page for more information.

 

What documents are needed for a three-way match?

Three: the purchase order, the docket that proves the work or delivery, and the invoice. In Docketbook the order carries the agreed rates and quantities; the docket records what actually happened, and the invoice is built from dockets the customer has already accepted.

 

Can dockets be created and signed on site without phone reception?

As long as you are working from an Order or a Job on your mobile device, you can complete the end-to-end process in offline mode. Dockets are sent when you are back in range.

 

What happens to a supplier's docket data when a project ends?

On Docketbook, nothing. The supplier's dockets live in the supplier's own account, not in a customer's portal, so access continues after the job is complete.

 

Getting started with Docketbook

Head contractors and project teams: see what committed cost, on-the-day dispute resolution, and three-way matched claims look like on your project. Book a demo.

Suppliers and subcontractors: get every docket signed, accepted and invoiced from one account. Get started today.


Docketbook is an Australian digital docket and purchase-to-pay platform used across civil construction and infrastructure. Find out more at docketbook.com.au.