Separate services into different invoice lines when they have different charging bases or need independent review. A fixed design package and hourly implementation support usually need separate quantities and prices. Several activities included in one agreed fixed package may belong together. Use the commercial agreement to decide, rather than automatically making one row per task.
This grouping decision comes before calculation in the line-item workflow. If a row combines services that should be priced differently, a correct multiplication can still produce a misleading invoice. Establish what each charge represents before entering quantity, discount or manually selected tax information.
Read the agreement as a pricing document
Identify the separately agreed charges. A proposal might list research, design and revisions under one package price, then offer training at an hourly rate. In that case, the task list and the invoice line structure need not be identical. The package can remain one charge while training has its own line.
Use the accepted version of the agreement. An early quotation may have separate prices that were later replaced by a combined offer. Keep the accepted basis with the preparation records so a reviewer can understand why the invoice does not mirror every heading in the original proposal.
If the evidence is ambiguous, clarify the pricing basis before issuing the invoice. Do not infer a split from internal cost estimates or divide a total into arbitrary amounts merely to make the document look detailed. Those amounts could later be mistaken for prices the customer actually accepted.
Separate different quantity and rate bases
Consider a fictional project with one setup package at 420.00 and three training hours at 65.00. Two lines preserve both bases: one package and three hours. Combining them as four units at an averaged price hides what the customer is paying for and makes later reconciliation more difficult.
Similarly, do not merge days and hours unless the agreement provides a conversion and the resulting unit is appropriate. Internal timekeeping conventions are not automatically contractual billing rules. A day could mean a defined service session, not a universal number of working hours.
The creator calculates each row from its own positive quantity and unit price. Its editable unit label does not convert quantities, combine rates or understand a bundle. You must enter the intended basis explicitly. Use separate rows when one quantity and one unit price cannot accurately express the charges.
Keep tax decisions visible
Different tax treatments are another reason to separate lines. A single row has one category, rate and any supported reason. A paragraph saying that part of the line has a different treatment cannot make the current calculation apply two treatments to that row.
Determine the appropriate treatment from the transaction and applicable requirements, using qualified advice where needed. The country selector and line description do not make that decision. Splitting a line improves the ability to express distinct treatments; it does not establish that either treatment is correct.
Keep records of how amounts were allocated if an agreed package needs a justified split for the final invoicing process. The creator does not calculate allocation rules or verify the legal basis. Do not invent proportions solely to make a preferred tax result appear in the preview.
Avoid unnecessary fragmentation
More rows are not automatically clearer. If the customer purchased a single fixed workshop package, separating preparation calls, slide design and attendance into invented prices may create confusion. The description can identify the package and its main scope without pretending that each internal activity was separately sold.
Likewise, avoid repeating the full project description on every row. Each row should identify its own supply. The guide to writing recognisable line descriptions helps you distinguish line wording from the broader project narrative while preserving enough information for an accounts reviewer.
A useful test is whether the customer could question or verify the charge independently. A separately priced training session normally can be checked against attendance and the agreed rate. An internal design revision included in a fixed package may have no independent billing amount to verify.
Review the split before export
After adding the rows, compare their combined scope with the agreement. Check for duplicated services and missing components. A setup task repeated within both a package description and a separately charged row deserves investigation, even if the document total matches the amount you expected to bill.
Check whether discounts apply to all services or only selected ones. Enter a line percentage only where it belongs. The current creator does not provide a document-level allowance field, and splitting services should not be used to disguise a separate unsupported adjustment as an ordinary service.
Finally, read the preview from the customer’s perspective. Can the recipient connect each amount to an agreed charge without reconstructing your internal project plan? You can use the invoice workspace to revise the rows before export. Its field checks help with supported inputs, but the commercial grouping and evidence still need your review. Retain the accepted scope and any clarification alongside your business records.