To document the steps you use to generate an invoice, create a repeatable standard operating procedure that records every input, ordered action, calculation check, and final output.

When the application is the Invoice Generator, write the procedure as a numbered SOP with three layers: the information you enter, the actions you perform, and the evidence you check before downloading the PDF. This makes the process easier to repeat, hand to someone else, and review later.

how do i document the steps i use to generate invoice when using invoice generator
How to Document Steps for Using an Invoice Generator

Set the scope of the invoice procedure

Begin by defining when the procedure applies and what a completed run should produce. A useful SOP distinguishes the billing trigger from the mechanical steps in the generator. For example, a trigger might be “invoice the client after project delivery,” while the output is a completed PDF saved in the location designated for financial records.

  • Record the event that starts the invoice process.
  • Name the person who prepares the invoice and anyone who approves it.
  • State whether the procedure covers one-off work, recurring billing, or a particular client agreement.
  • List the documents or information the preparer must have before opening the tool.
  • Add a version number and review date so outdated instructions are easy to identify.

Next, create a field map showing where each required piece of information belongs. This is more useful than a generic instruction such as “complete the invoice,” because it tells the reader exactly what to enter and where to verify it.

Invoice area What to document Where to verify it
Business sender Name or company and address From block
Client Client’s identifying and address details Bill To block
Invoice control Invoice number, issue date, due date, and currency Invoice header
Charges Description, quantity, and unit price for every product or service Itemized table
Adjustments Tax rate and optional flat discount Summary section
Additional information Any notes needed on the invoice Bottom of the invoice
Final output The downloaded PDF and its filing location Completed browser download

Generate the invoice in the required order

Write the generation steps in the same sequence you actually follow. The order matters because later calculations and the final preview depend on the information entered earlier.

  1. Enter the sender, client, and invoice details. Under From, enter your business name or company name and address. Under Bill To, enter the client’s details. Set the invoice number, which defaults to INV-001, choose the issue date and due date with the date pickers, and select the currency symbol you use for billing.
  2. Add each product or service as a line item. Enter a description, quantity, and unit price for every charge. Quantities can be whole numbers or decimals, such as 1.5 hours. Use the Add item button when you need another row and the remove button to delete an unnecessary row. There is always at least one line available to start with.
  3. Apply tax and any discount. Enter the tax rate and, if applicable, a flat discount. The subtotal, tax, discount, and total update instantly in the live preview as the invoice data changes.
  4. Review the preview against your source information. Check the From and Bill To blocks, invoice number, dates, currency, descriptions, quantities, unit prices, line amounts, and summary totals. Add any notes that should appear at the bottom. The live preview mirrors the downloaded PDF, so this is the point to catch missing or incorrect information.
  5. Download the completed invoice. Select Download PDF to save a print-ready invoice. The PDF is generated locally in your browser and is never uploaded. You can then print it, attach it to an email, or archive it for your records.

After downloading, open the PDF and make a second visual pass. Confirm that the page contains the expected sections, that long item lists continue onto additional pages, and that no important text was cut off. This final file check complements the live-preview review rather than replacing it.

Write down the calculation and review rules

Your SOP should state how the invoice totals are formed so another person can reproduce the review without guessing. The subtotal is the sum of each line’s quantity multiplied by its unit price. The tax line applies the entered percentage to that subtotal, and an optional flat discount is subtracted to produce the final amount due. The discount is automatically kept between zero and the amount due, so the total cannot become negative.

Include the arithmetic method rather than documenting only the final amount. The generator performs its money calculations in integer cents to avoid floating-point rounding drift. A clear example for a procedure might read: 1.5 hours × $80.00 = $120.00. Use the source quote, timesheet, or agreed rate to verify that line before reviewing the invoice summary.

Turn the normal review into a repeatable table with a documented pass condition and a correction action.

Check Documented evidence Action when it does not match
Parties and dates From, Bill To, issue date, and due date match the source records Return to the relevant fields and correct them
Line items Every description, quantity, and unit price matches the agreed work Edit or add the affected row
Totals The live subtotal, tax, discount, and total agree with the documented calculation rules Recheck the entries and entered adjustment values
Notes Any required note appears in the lower part of the invoice Add or revise the note before downloading
PDF The downloaded file opens and displays the reviewed information Correct the source fields and download again

For a separate review of the arithmetic, see how Invoice Generator totals are checked for accuracy. Your SOP should still record your own expected values and approval points rather than relying on a general assurance alone.

Record the output, privacy, and tool limits

The second half of the SOP should explain what happens to the information and describe the boundaries of the current tool. These details prevent a future user from assuming that a browser workflow provides storage, conversion, or branding features that it does not provide.

  • Local processing: Invoice calculations and the final PDF are built locally in the browser with JavaScript. Nothing is uploaded to a server, and the tool does not store the invoice data.
  • No account: The generator is free and requires no login. It also works offline once the page has finished loading.
  • Clean output: The downloaded PDF has no watermark or third-party branding.
  • Currency display: The supported symbols are the US dollar ($), British pound (£), euro (€), and yen (¥). The symbol is for display only; the tool does not convert currencies or apply exchange rates.
  • No logo support: This version is text-based and cannot upload a company logo or image. If a logo is required, add it afterward in a PDF editor.
  • Character substitution: Characters the PDF font cannot represent may be replaced. Inspect descriptions and notes when using emoji or certain non-Latin scripts; the four supported currency symbols render correctly.

Also make clear that the generated PDF is the invoice record, not an automatic activity log. The SOP itself and the completed invoice must be kept in whatever records system or file location your business uses.

Store the SOP outside the browser tool

The generator creates the invoice but does not provide a place for storing a reusable procedure. Save the SOP as a document, page, or internal knowledge-base article that your team can access independently of the tool. Keep it near your invoicing records or link to it from the workflow your team already follows.

Include the invoice number as one controlled element of the SOP. The Invoice Generator provides INV-001 as the default, so your procedure should explain when and how a person changes it. If your business needs a more formal numbering policy, use a dedicated guide such as how to generate invoice numbers your bookkeeper will trust and keep that policy consistent with the SOP.

  • Give each SOP version a clear name, owner, and revision date.
  • Use a consistent file-naming pattern for downloaded PDFs, such as invoice number, client, and issue date.
  • State where the PDF should be saved and who receives it after approval.
  • Record the steps for correcting an invoice rather than silently replacing the original record.
  • Keep product-specific facts separate from general billing rules so future tool changes can be reviewed accurately.

Check the SOP before using it again

Read the completed procedure as though you were preparing the invoice without prior familiarity with the generator. The sequence should be unambiguous, every referenced control should have a matching field name, and each expected output should have a verification method.

  • The sequence starts with the sender and client, continues through invoice details and charges, and ends with the PDF review and download.
  • Every invoice field is named clearly, including the four available currency choices.
  • The subtotal, tax, discount, and total rules are stated in plain language.
  • The live preview and downloaded PDF are both included in the review process.
  • Local processing, no storage, no account, the offline behavior, and the absence of a watermark are documented accurately.
  • The logo, currency-conversion, and character-substitution limitations are visible to the person following the procedure.

A complete SOP turns a series of clicks into an accountable workflow. It shows what information must be available, how the invoice is produced, how the numbers and layout are checked, where the PDF belongs, and which capabilities the current generator does not provide.