Start with the job in front of you
A total alone does not tell someone what was purchased, when it happened, or how it was paid.
A short test is usually faster than trying to fix a large final file after the fact. Keep the original nearby, name the exported version clearly, and change one setting at a time when the result matters.
Use a small, repeatable routine
Include seller details, date, item description, tax where relevant, total, and a payment reference that can be matched later.
The useful part of a browser tool is not simply getting an output. It is being able to reproduce the same result tomorrow, explain what changed, and notice when an input or assumption has changed.
Do one last check before sharing
Compare the receipt with the transaction record before handing it over or filing it.
If the result will be published, sent to a client, or used to make a decision, compare it with the source rather than trusting a filename or a successful download message.
Practical checklist
- Keep the original input until the output is checked.
- Test the workflow on a small sample first.
- Use clear names for exported versions.
- Review the result in the app where it will actually be used.
- Record important settings or assumptions.