Signing example
Bill of sale e-signature
A bill of sale e-signature is really two records: the sale itself and the receipt on collection, which happens on a different day and states a different fact. This cafe equipment package from the documents examples runs as two envelopes on one PDF, the sale signed by both companies in parallel and the receipt signed in person when the truck arrived.
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
- Theo Marchant, for the Seller, envelope one
- Block headed FOR THE SELLER: Name, Company, Date · Email link
- Isla Beaumont, for the Buyer, envelope one
- Block headed FOR THE BUYER: Name, Company, Date · Payment reference for the balance, typed and required · Email link
- Isla Beaumont again, envelope two, at collection
- Signature and stamped date on the receipt line · Collected by, typed · Signed in person on the seller's phone
The signing journey
Step 1
Envelope one carries the sale
The two page bill of sale goes out to both companies at once with the order switch off. Each signatory gets a headed block, and the buyer also types the payment reference for the balance so the transfer can be matched without a phone call.
Step 2
Both companies sign the same afternoon
Theo and Isla each open their own link, type their company lines and sign. Their dates stamp themselves, the listener certifies the file, and both businesses hold the executed sale with its eleven event certificate.
Step 3
Collection day gets its own envelope
When the goods are picked up, a second envelope on the same PDF carries only the receipt fields: the buyer's signature and date on the receipt line and a typed Collected by field naming who actually took the goods.
Step 4
The receipt is signed in person
At the roastery door the seller opens the receipt envelope's status page on his phone and hands Isla her turn in person, which waives the emailed check for the hosted session and records the event. She types the collection details, signs, and the receipt certifies as its own file.
What the two signed files and certificates show
Envelope one's file shows FOR THE SELLER and FOR THE BUYER blocks with both company lines typed, two stamped dates, and the payment reference field completed. Envelope two's file shows the same document with the receipt line now signed and dated and the Collected by field naming the carrier. Each envelope has its own certificate: the sale with two email link signers over eleven events, the receipt with one signer and the in person start recorded before the signature.
How to adapt this pair
If collection happens at signing, fold the receipt fields into the first envelope and one certificate covers everything. If a carrier collects without the buyer present, the Collected by field earns its keep, and the buyer can equally sign the receipt remotely from a link once the driver confirms loading. For goods delivered in stages, each delivery can carry its own small receipt envelope against the same PDF.
What makes this signing flow work
The receipt is its own record, not a leftover field
A completed envelope cannot be reopened, and collection is a later fact with its own date. Two envelopes mean the sale certificate proves the sale day and the receipt certificate proves the collection day, without either pretending to be the other.
The payment reference is typed by the payer
Isla's required field carries the transfer reference and date in her own keystrokes, under her own signing event. When the seller's bookkeeper reconciles the balance, the executed document itself says which transfer to look for.
Parallel where nothing depends on order
Neither company's signature depended on the other's, so the switch went off and both signed the same afternoon. Sequence is saved for documents that need it, like the loan chain, and skipped where it only adds delay.
Questions people ask
Why two envelopes instead of one?
Because a completed envelope is sealed and collection is a later fact. The sale was certified on the day it was signed; the receipt was certified on the day the goods left. Each has its own dates, its own certificate and its own hash chain, which is what two different facts deserve.
Can the receipt be signed on a phone at the door?
Yes, and it was. The seller opened the receipt envelope's status page on his phone, handed the buyer her turn in person, and she signed on the spot. The hosted session is recorded in the trail immediately before her signature.
Do both companies get the files?
Yes. Each envelope's completion email carries its certified PDF to every recipient and the sender, so both businesses hold the executed sale and the buyer holds her signed receipt, with the certificates available as separate downloads.
Can the seller pre-fill the payment reference?
No. The editor has no way for a sender to type a value into a field; every field is completed by the recipient it belongs to. The reference belongs to the buyer because she made the transfer, and her typing it is what makes it evidence.
Is a bill of sale signed this way valid?
The envelopes preserve the signatures, the typed reference, the dates and the hash chains, and the document carries the register search and disclosures the parties agreed. Whether particular goods need anything more formal is a question for the transaction's advisers, not this page.
Could the equipment list be a signing field?
No, and it should not be. The goods table with serial numbers is fixed inside the document and covered by the document hash. Signing fields are for values decided at signing time, like the payment reference and the collection details.
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 my bill of sale e-signatureOther signing examples
Sign a service agreement online
A service agreement that starts on a fixed date does not need its two signatures in any particular order, so making one party wait for the other only costs a day. This envelope carries the Beacon Systems managed IT agreement from the documents examples with Sign in order off, both invitations sent in the same minute, and an optional purchase order box the client fills in its own words.
Purchase order approval by e-signature
A purchase order approval signature is a two step routing problem: the requester raises, the approver commits the spend, and the order matters. This page shows PO-8842 from the documents examples signed that way, with block headings that print RAISED BY and APPROVED BY, a required cost code typed by the approver, and a resend after the approver's original invitation went missing.
Statement of work e-signature
A statement of work e-signature runs client first: the sponsor approves the scope, then the vendor executes what was approved. This claims data migration SOW from the documents examples shows that order, with four line blocks carrying name, title, company and date, and an earlier version withdrawn with its reason on record when the schedule changed.
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 .