Do not combine supplies needing different tax treatments into a single line that has only one tax category and rate. Separate the amounts so each treatment can be represented and reviewed independently. The decision about which treatment applies still depends on the actual transaction and applicable requirements; line separation does not make that decision for you.
In the line-item preparation workflow, resolve the commercial scope before entering tax values. The current creator allows manual tax information per line. It does not determine rates from the selected country, classify supplies or verify whether an exemption or other treatment is legally appropriate.
Identify the distinct supplies
Read the agreement and delivery evidence to understand what was supplied. Similar descriptions do not prove identical tax treatment, and different descriptions do not automatically require different treatments. Establish the relevant facts before deciding how many lines the invoice needs.
Where professional advice or a current official rule is necessary, obtain that determination outside the creator. Keep the basis with your records. Do not copy a rate from a sample invoice or another customer’s document and assume that it applies because the product name looks familiar.
If a fixed package contains components that require a justified allocation, determine that allocation using the appropriate rules and evidence. The creator does not calculate such allocations. Arbitrarily dividing a package total can produce neat rows while leaving the underlying treatment unsupported.
Understand the one-line limitation
Each current line has one manually selected category, one rate and a supported reason field where relevant. Its calculation applies that information to the line’s net amount. A description saying “part exempt” does not instruct the app to divide the line into different tax bases.
For a fictional illustration, suppose two independently priced services have determined treatments of standard-rated and exempt. Separate rows allow their amounts and reasons to remain distinguishable. This example does not establish that any particular real-world service qualifies for either category.
Do not average tax rates to make a combined row produce a preferred total. A blended number can conceal the amounts assigned to each treatment and may not correspond to a permitted representation. Keep the actual determined treatment attached to the relevant supply.
Keep category and zero amount distinct
A zero tax amount can arise for different reasons. A zero rate, an exempt category and an outside-scope category do not mean the same thing simply because the arithmetic adds no tax. Choose the supported category that accurately reflects your determination and provide a reason when required by the app.
The application’s zero, exempt and outside-scope categories use zero in the current calculation. Exempt and outside-scope lines require a reason for field validation. These are application rules, not a conclusion that the entered wording meets every legal or destination-profile requirement.
Avoid writing only “no tax” when the transaction needs a more specific explanation. Equally, do not invent statutory wording from memory. Confirm the appropriate basis and use a suitable final invoicing process if the required tax representation goes beyond the current model.
Review discounts on separated lines
Once the lines are separated, check that any percentage discount applies to the intended amounts. A discount formerly entered against a combined line may need deliberate review rather than automatic copying to every replacement row. Preserve the agreed discount basis in the preparation records.
The creator calculates tax after its supported line discount. If a transaction needs a different adjustment structure, document-level allowance, withholding or another unsupported treatment, do not force the result through an unrelated line field. Use a system that implements the required financial model.
After a split, compare the combined net scope with the original agreed charges. The separation should not accidentally duplicate a service or omit part of the price. A correct tax calculation on incomplete commercial data still produces an incorrect invoice.
Check both explanations and amounts
Read the preview line by line, confirming the description, quantity, price, category, rate and reason. Then compare the amounts with the source determination. The app’s live totals are useful for checking what the entered values produce, but they do not validate the tax decision itself.
The guide to separating different services helps distinguish commercial line structure from arbitrary fragmentation. Use separate rows to express genuine differences, while keeping one agreed supply intact where that is the appropriate representation and the required tax treatment can be expressed accurately.
Before delivery, confirm the recipient’s format and validation requirements. The current application exports its own JSON, line-item CSV and printable output. It does not produce a formally validated tax-standard document, submit to an authority or guarantee acceptance. Preserve the evidence for each treatment and resolve unsupported requirements before using the final invoice in a regulated or destination-specific workflow.
When reviewing a revised draft, compare the category and reason as well as the rate. A copied row may retain an explanation from a different supply even after its numeric rate is corrected. Read the whole tax statement as the recipient would, then compare it with the documented determination.