Prepare discount information for a tax review by stating what was reduced, how the reduction was agreed and which supplies it affects. Include whether the quoted price already contains the discount and whether the adjustment belongs to a line or the document. A reviewer should not have to infer those facts from the final total.
This evidence forms part of the tax-information preparation workflow. The creator can calculate its supported line percentage discount, but it does not determine tax consequences or implement every kind of allowance, charge or settlement adjustment.
Identify the actual agreement
Retain the accepted offer, contract amendment or other record supporting the reduction. Distinguish a percentage discount from a fixed monetary allowance. They can produce the same amount on one draft and different amounts after the quantity changes.
Record the scope precisely. A discount on equipment may exclude installation, delivery or another service. “Ten percent off” is incomplete if the reviewer cannot tell which charges form its base. Keep the accepted terms rather than relying on a colleague’s summary from memory.
If the reduction is conditional, state the condition and whether it has been met. The creator does not interpret promotional terms, payment incentives or eligibility rules. A percentage entered in the field is applied to the current line calculation regardless of an explanatory note about a condition.
Separate embedded and explicit reductions
Confirm whether the source unit price is the original price or an already reduced price. Entering a discounted unit price and then applying the same percentage again creates a second reduction. The preview cannot determine whether that was intentional.
For a fictional preparation record, retain the original quoted rate, the agreed concession and the final invoicing basis. This allows the reviewer to distinguish a genuinely separate allowance from a negotiated final price. Do not reconstruct an original price without evidence simply to make a discount visible.
If different source documents show different stages of the negotiation, identify which one was accepted. Keep superseded documents distinguishable. A tax review based on an abandoned quote may reach conclusions about an adjustment that is no longer part of the sale.
Explain where the adjustment belongs
A line-level reduction relates to particular charges, while a document-level allowance has a different representation and may require additional allocation. The creator currently supports percentage line discounts only. It has no dedicated document-level allowance or fixed-amount discount model.
Do not distribute a global allowance across lines arbitrarily just to fit the controls. The reviewer may need to establish the appropriate basis before the final system represents it. Preserve the original adjustment type and scope in your working records.
Likewise, distinguish a discount from a payment already received. A payment settles an obligation; a discount changes the commercial charge under its terms. Converting one into the other to reduce the displayed total can misstate both the supply and the amount requested.
Give the reviewer a complete line record
Provide each affected supply’s description, quantity, unit, agreed price and adjustment evidence. Include the proposed treatment and any unresolved questions without presenting an assumption as a confirmed decision. The reviewer needs facts, not a total chosen in advance.
Where several determined tax treatments are involved, show which amounts the adjustment affects. The current app does not decide allocation across categories or produce a formally validated breakdown. Use a suitable final workflow when the determination requires a more complete financial structure.
The guide to organising lines by treatment explains how to keep this relationship visible. Do not average rates or move an allowance to an unrelated row solely to simplify the arithmetic.
Keep timing and revision evidence clear
Record whether the adjustment was agreed before the invoice, during draft review or after an earlier invoice was issued. Those events can require different business and document processes. Editing a local draft is not a universal method of correcting an issued invoice.
Keep the relevant prior document reference and amendment evidence where applicable. The creator does not maintain a correction chain, credit-note ledger or account history. If the required process exceeds its model, finalise through software that implements the appropriate document relationships.
When the review changes the adjustment basis, update the preparation record and affected values together. Reread descriptions and notes for stale promises or old amounts. Numeric recalculation does not rewrite those statements.
Review the final representation
Ask the responsible reviewer to confirm the treatment scope and remaining actions. Then check that the final invoicing system expresses the agreed reduction at the correct level and uses the required fields and calculation policy. A matching total alone does not verify the representation.
Retain the accepted adjustment evidence, reviewed conclusion and exact final export together. The current application JSON, line-item CSV and printable preview do not establish formal allowance mapping or tax correctness. Their usefulness lies in supported preparation, while any required determination, standards validation and delivery must be completed through an implemented workflow.
A practical review check
A one-page adjustment brief is often enough if it states the accepted source, affected charges, calculation type and remaining review question explicitly.