Signing example

Sign a vehicle sale agreement online

To sign a vehicle sale agreement online, the seller and buyer do not need to meet: one envelope routes the seller first and the buyer second, each verified by an emailed code. This six page private sale of a 2019 dual cab ute, dated 12 October 2026, shows that flow, with each party typing their own licence number into the execution block the agreement already prints.

Send a document for signing2 signers, a one-time code by email for both

The document itself is written out in full on its own page: read the wording there. This page is only about signing it.

Who signs what

Dean Kowalczyk, the Seller, signs first
Initials on page 2, under the vehicle table · Block on page 6 under Seller, Dean Kowalczyk: signature, Name, Licence number, Date · Licence number typed by Dean, required · Verified by emailed one-time code
Rosa Ferreiro, the Buyer, signs second
Initials on page 2, beside the seller's · Block on page 6 under Buyer, Rosa Ferreiro: signature, Name, Licence number, Date · Licence number typed by Rosa, required · Verified by emailed one-time code

The signing journey

  1. Step 1

    Fields for two, order on

    Each party gets an initials spot on page 2, where the vehicle table prints the VIN, engine number and the 96,412 km odometer reading, then a signature, name, licence number and signed date on their own block on page 6. The seller signs first so the buyer executes a document the seller has already committed to.

  2. Step 2

    The seller signs

    Dean enters his emailed code, initials the vehicle details page, types his licence number into the Licence number line and signs his block. His name arrives prefilled from the recipient row and his date stamps itself as Oct 12, 2026.

  3. Step 3

    The buyer signs

    Rosa is invited only after his signature lands. She verifies with her own code, initials page 2 beside his mark, types her licence number and signs her block, which confirms she has read the disclosures in clause 2.2 and had the ute inspected.

  4. Step 4

    Both hold the same certified file

    Completion emails the certified agreement to seller, buyer and sender. The certificate shows both parties verified by emailed one-time codes, and either side can open the file in a reader and see the certification intact.

Opening the signed PDF in a reader

The completed file carries a certifying signature, so a PDF reader's signature panel reports a certified document with no changes since certification. That check works for either party without any access to this product, which matters when a buyer wants to verify the copy years later. The certification line in the certificate reads PAdES-SHA256-DocMDP with no timestamp suffix, meaning no RFC 3161 token is attached in the current setup.

What the signed agreement and certificate show

Page 2 carries both sets of initials under the vehicle table. Page 6 shows the Seller and Buyer blocks with drawn signatures, prefilled names, typed licence numbers and stamped dates. The certificate lists both signers with Email link + emailed one-time code, IP addresses, consent records and the two document hashes.

How to adapt this envelope

The handover receipt at the foot of page 6 records the odometer on 19 October, a week after signing, so this envelope places no fields on it; the parties fill it in on their printed copies at handover, which clause 4.3 allows. If the parties are meeting on the day anyway, the buyer's signature can happen in person from the status page. Registration transfer stays a separate Transport for NSW process either way.

What makes this signing flow work

The odometer and VIN are initialled, not retyped

The agreement already prints the 96,412 km reading, the VIN and the engine number on page 2, and clause 5 of the warranties names that reading. Initials from both parties on that page tie each of them to those exact figures, with their own signing events behind the marks.

Seller first means the buyer signs a committed document

Enforced order put the seller's initials and block on the file before the buyer could act. Rosa's signature was given over a page Dean had already executed, which is the sequence a cautious private buyer wants before paying a $26,500 balance.

Two strangers, two codes

Private sales happen between people with no shared systems. Each party verified with a six digit code emailed at signing time, so each signature ties to a mailbox, and the certificate names the method beside each entry.

Questions people ask

Do both parties get the signed copy?

Yes. The completion email carries the certified PDF to the seller, the buyer and the sender, and the certificate of completion is a separate download from the status page. Both sides hold byte identical files that a reader can verify independently.

Can the seller and buyer sign in the same room instead?

Yes. From the envelope's status page the sender can hand the current signer their turn in person, which waives the emailed code for that hosted session and records an in person event. It suits a sale where both parties meet at the seller's address in Kariong to inspect the ute and sign together.

Does the app check the registration or title?

No. The PPSR search, its certificate number 74102889B and the 10 October date live in the document's own warranty text, done by the buyer beforehand. The envelope's job is capturing who signed what and when, not checking the vehicle against a government register.

What if the buyer declines to sign?

The envelope moves to declined with the buyer's typed reason emailed to the sender, and nothing more is stamped. Since the seller signs first here, a decline costs one signature and produces a clean record that the sale did not proceed, while clause 1.3 of the agreement decides what happens to the $2,000 deposit.

Is the file timestamped by an authority?

No RFC 3161 token is attached in the current configuration, and the certification line says so by carrying no timestamp suffix. The signing instants are recorded in the certificate and the hash chained event log, which for a private sale is the record that gets used.

Why does each party type a licence number?

Because the agreement prints a Licence number line in both execution blocks, and no screen in the app lets the sender fill a value for someone else. Each party types their own number into a required text field, so the licence recorded against each signature was entered by that person during their own signing session.

Build your own in about a minute

The button below opens the generator with this use case already described. Change the wording to match your own, generate, then edit anything you like.

Make one like this

Other signing examples

Want the steps in the builder? Read Send a PDF for e-signature, then Send a document for signature. For everything this generator can do, see the signing flow maker.

Sources

Written and checked by the OneCraft team. Last checked .