A percentage discount scales with its calculation base. A fixed-amount discount is a stated monetary reduction. They can produce the same result for one particular line and different results after quantity or price changes. Preserve the agreed type instead of treating the two representations as interchangeable.
The invoice amount workflow requires the adjustment basis to be clear before reconciliation. The current creator provides a percentage discount per line. It has no dedicated fixed-amount discount control, so a transaction requiring that representation may need a different final invoicing tool.
Compare the same line under two agreements
A line amount of 200.00 reduced by ten percent has a discount of 20.00. A fixed reduction of 20.00 produces the same net amount of 180.00 at that moment. The equal result does not mean the agreements are equivalent.
If the line amount later becomes 250.00, ten percent becomes 25.00 and the net is 225.00. A fixed 20.00 deduction instead leaves 230.00. This difference matters whenever the draft changes or the invoice is derived from a reusable preparation record.
Read the accepted terms carefully. “Ten percent off this service” and “20.00 goodwill reduction” state different facts. Do not replace the latter with a percentage merely because the app offers a percentage box. The result should remain explainable when someone reviews the source agreement.
Understand the current control
The discount field accepts a percentage from zero to one hundred with up to two decimal places. The creator applies it to the rounded initial line amount and rounds the resulting discount to cents. It then subtracts the discount before its supported tax calculation.
Writing 20 in that field means twenty percent, not a 20.00 deduction. On a 300.00 line it produces a 60.00 discount. Check the preview when entering or reviewing the value so a familiar monetary number is not accidentally interpreted as a rate.
A description saying “fixed discount 20.00” does not override the calculation. Free text can explain a transaction, but it does not give the app a separate adjustment model. Do not export an invoice whose wording states one deduction while its supported fields calculate another.
Avoid approximate conversions
A fixed reduction can sometimes be divided by a particular base to obtain a percentage, but the result may require more precision than the current control permits. Rounding that rate can change the deduction, particularly for larger line amounts. A coincidental cent match is not proof of faithful representation.
Even if the current numbers match, a later quantity change can break the equivalence. You would need to reconsider the conversion rather than simply trusting the original percentage. That makes the workaround fragile for a draft that is still being edited.
If the destination requires the allowance amount, reason or another typed field, a visible matching total is insufficient. The current application JSON is its own schema and does not claim a formal allowance mapping. Use a tool that implements the required financial and structured-data model.
Check the adjustment level
A percentage or fixed reduction can apply to one line or to the whole document under different agreements. The level is a separate question from the mathematical type. A document-wide fixed deduction should not be silently assigned to an arbitrary service line to make the total smaller.
The guide to line discounts and document-level allowances explains that distinction. The creator supports its line percentage model only. It does not allocate a document-level adjustment across tax categories or calculate the corresponding profile-specific totals.
Likewise, do not use a negative row to simulate an unsupported fixed allowance. Negative quantities and prices are outside the current ordinary positive-invoice model. A separate explanation does not make an unsupported calculation or document type implemented.
Review changes against the original agreement
After changing quantity or price, calculate what the agreed discount should now be. Compare that with the preview. A fixed agreement should not unexpectedly grow merely because the source line became larger; a percentage agreement should not remain frozen at an old monetary value unless the terms provide for that.
Check any maximum, minimum or eligibility conditions outside the creator. The app does not interpret promotional terms or enforce a discount cap from text. If the arrangement cannot be expressed within the supported model, resolve it in an appropriate system before issuing the final document.
Keep the agreed basis and your calculation review with the invoice records. This lets a later reviewer distinguish an intentional commercial adjustment from an input error. Field validation confirms supported input rules, not the correctness of the discount agreement, tax treatment or destination mapping. A clear boundary is more useful than a total made to match through an unexplained approximation.
For a fixed deduction of 7.00 on a 60.00 base, the equivalent percentage is recurring rather than a neat two-decimal rate. Entering 11.67 percent can appear close at that base, but it is an approximation and changes behaviour if the base changes. Keep the fixed amount as the source fact instead of replacing it with that rounded rate in your business records.