Use a fractional quantity when the agreed supply is measured in part of a unit, such as 1.25 hours or 2.75 metres. Keep the measurement basis clear and enter only the precision the current creator supports: up to four decimal places for quantity. A currency amount having two decimal places does not mean every quantity should be rounded to two decimals.
The line-item preparation guide places quantity review before totals. That order matters because rounding the quantity too early can change the charge. Preserve the source measurement, confirm the charging unit and then decide whether the app can represent the transaction accurately enough for your intended workflow.
Keep measurement and money separate
A quantity describes the supplied amount. A unit price describes the charge for one unit. The resulting line amount is money. These values have different roles and may need different precision. Avoid copying a rounded monetary result back into quantity simply because it looks familiar.
For example, 1.375 metres at 20.00 per metre gives an unrounded product of 27.50000 and a money amount of 27.50. Rounding the quantity first to 1.38 would instead produce 27.60. Both entries fit the form, but only one reflects the stated measurement.
Retain the measurement record outside the invoice where appropriate. A scale ticket, approved duration or measured length can explain why the quantity has several decimals. The finished invoice alone should not be the only evidence for a precise value that a customer might reasonably ask you to substantiate.
Confirm that fractions make commercial sense
Not every item can be billed fractionally. A product sold only as complete sealed packs may require whole-pack quantities, while a product sold by weight may naturally use fractions. The input field accepting 0.75 does not determine whether that is a valid commercial unit for your supply.
Check minimum quantities, agreed billing increments and package rules. If the contract charges a full session whenever part of it is used, do not enter a proportional fraction without agreement. Conversely, do not round measured goods upward simply to remove decimals from the preview.
A unit label should make the quantity understandable. “0.75 hour” is a different statement from “0.75 day”. Keep the entered rate on that same basis. The app does not convert between units or infer that a fractional day means a particular number of hours.
Use supported decimal notation
Enter a plain decimal value in the quantity field, without a unit suffix or a mathematical expression. Use 1.25 rather than “1 + 1/4” or “1.25 metres”. The unit has its own field. This keeps the quantity available for calculation rather than leaving the app to interpret text.
The current quantity limit is four digits after the decimal point. If the source record needs more, do not silently truncate it. Check whether a justified billing increment or a different unit basis resolves the precision issue. Where exact representation remains necessary, choose a tool that supports the required model.
Avoid changing the quantity merely to force a preferred final total. That can make the invoice disagree with the delivery evidence. A calculation difference should be investigated through the rate, quantity, discount and rounding policy, rather than concealed by an unexplained adjustment to the measured supply.
Review time fractions separately
Time quantities often cause decimal mistakes because minutes use a sixty-part hour. Forty-five minutes is 0.75 hours, not 0.45. One hour and six minutes is 1.1 hours. Convert the duration before entering the numeric field and retain the original record.
For day-based work, use the agreed definition of a day and any partial-day pricing rule. The guide to entering hours and days provides a focused time-billing workflow. Do not apply a universal hours-per-day assumption to consulting, attendance and fixed-session services that may use different agreements.
Inspect the rounded result
The creator multiplies the supported quantity by the two-decimal unit price and rounds the resulting money amount to cents before its subsequent line calculations. Percentage discounts and tax are then calculated using the app’s defined sequence. A precise quantity can still lead to a rounded money amount.
Test a representative line with the actual quantity and rate before completing a long invoice. Compare the preview with an independent calculation that follows the same rounding sequence. If a receiving system uses another sequence, a matching unrounded multiplication does not guarantee matching totals.
After editing the quantity, reread any description that states a measurement in words. Then check the exported application JSON or CSV if you will use it in another process. The export preserves supported application data; it is not a formal standards file or proof that another system accepts the same quantity precision. Resolve that destination requirement before sending the invoice.
For weighed supplies, compare the measurement unit on the evidence with the invoice unit before copying the digits. A kilogram value entered as tonnes changes the meaning dramatically even when every decimal digit is preserved. Record the conversion and review the corresponding price basis together.