Does the invoice print cleanly?
The sample should show enough spacing and hierarchy that the PDF still looks finished on paper or in attachment view.
A sample invoice PDF should be a preview step, not the whole workflow. Use it to answer the format question first: does the invoice look clean enough to print, are the totals obvious, and does the page already feel finished when opened? Once the layout is clear, the next move is to switch into the real draft so the final PDF comes from real invoice data, not a copied sample.
The sample should show enough spacing and hierarchy that the PDF still looks finished on paper or in attachment view.
The amount due and payment instructions should still stand out even after the draft becomes a static file.
If the layout is fine but the editing looks painful, switch to a different template choice before you fill real data.
The preview should make the final invoice easier to start, not keep the user trapped in another sample loop.
Use it to confirm the finished PDF layout, readability, and totals placement, then move into the actual draft before exporting the real invoice.
Check spacing, totals visibility, payment instructions, and whether the invoice looks ready to print or send.
Once the PDF shape is clear enough to start the real invoice, the preview has done its job.
Most users should open the PDF template page or the live generator and let the final PDF come from the actual invoice data.
Confirm the printable layout, start the actual draft, and export the final file from the live invoice once the fields are real.