Use a separate, clear unit for each invoice line when an invoice contains different kinds of supply. Hours of support, individual products and metres of material can appear in the same document, but their quantities cannot be added into one meaningful count. Review each quantity against its own price basis before comparing money totals.
The line-item preparation workflow starts with those individual commercial facts. A single invoice currency does not imply a single measurement unit. The creator calculates each row independently using the quantity and unit price you enter; its text unit labels do not convert between measures.
Build a simple unit inventory
Before entering a long invoice, list the distinct charging units used by the agreement. You might have equipment sold each, installation billed as one package and support billed by the hour. This short inventory helps reveal where a copied row still carries the unit from a previous service.
For each unit, identify the source of the price. An hourly rate belongs to an hour quantity; a package price belongs to a package quantity. If the quote gives a price per box while the delivery record counts individual items, resolve the conversion explicitly rather than mixing the two records in one line.
Avoid treating “unit” as a universal label that hides every difference. A customer reviewing quantity four needs to know whether that means four products, four sessions or four boxes. Clear labels make the commercial basis visible even when the amounts happen to be similar.
Keep different bases in different rows
Consider an invoice with two devices at 75.00 each and 1.5 hours of setup at 40.00 per hour. The pre-discount amounts are 150.00 and 60.00. Adding the quantities gives 3.5, but that number has no useful shared measurement meaning. The money amounts can be combined because they share the invoice currency.
Check grouping rules before combining rows with similar descriptions. Two maintenance charges might use different units, such as monthly coverage and an emergency call-out. One generic service line with an average price can make the calculation difficult to explain or reconcile.
Different units also affect discount interpretation. A ten-percent reduction on one row applies to that row’s amount, regardless of its unit. It does not mean ten percent of all physical quantities in the document. Keep quantity review and money adjustment review separate.
Check copied and revised rows
When adding a similar line, inspect every field rather than only the description and price. A leftover unit of hour beside a product quantity creates a misleading document. A leftover quantity can also multiply a newly entered package price unexpectedly.
After changing a unit, revisit the quantity and unit price together. If three boxes become thirty individual products, entering thirty while keeping the box price would overstate the line. A label edit alone performs no conversion, and a numerically unchanged total does not prove that the revised basis is correct.
Do not rely on the preview to identify all unit mistakes. It shows the values you supplied. The app cannot determine whether a day means an agreed session, a defined number of hours or a calendar day. Those meanings must come from the underlying transaction.
Plan for structured unit requirements
Readable labels are sufficient to communicate some draft concepts, but a receiving structured-invoice profile may require codes from a specific list. The guide to unit labels and standard unit codes explains that difference. Do not assume entering several sensible labels creates a standards-ready mapping.
The current creator has no unit-code lookup, pack-size conversion or destination-specific code validation. Preserve any required mappings separately if you are preparing data for a later system. Keep the original source label and the confirmed intended meaning so the transfer can be checked.
If two source records use different labels for the same unit, confirm equivalence before standardising them. “Session” and “hour” may refer to different commercial bases even when a typical session lasts an hour. Consistency should reflect real agreement, rather than merely making the invoice look uniform.
Review amounts after the unit check
Once each row’s basis is correct, check the line amount, discount and manually selected tax information. Sum monetary values using the creator’s calculation sequence, not the physical quantities. Where another system calculates the invoice, confirm that it applies compatible precision and rounding rules.
Review the printed document to ensure the unit remains readable beside its quantity. Long descriptions should not make the relationship unclear. If necessary, simplify wording while retaining the facts that distinguish the goods or service being supplied.
Keep a final copy of the source-to-line decisions with the invoice records, especially where conversions were necessary. This gives a later reviewer a way to understand why different units appear and how each charge was derived. The current application’s field validation cannot replace that commercial review or verify a destination’s formal measurement requirements.
A useful review sheet gives each source charge its own quantity, unit and rate columns. Leave any overall quantity total blank when the units differ. This prevents a spreadsheet subtotal from presenting a meaningless combined number as though it were an independent check.