Prepare a service invoice by identifying the customer, describing the work supplied, recording the agreed billing basis and entering the relevant quantities and prices. A service description should let the customer recognise what it is being charged for without requiring it to reconstruct the whole project from email. The approved work and contract determine the billable facts; the creator calculates the data you enter.
Before writing lines, confirm whether the agreement is hourly, daily, per session or fixed-price. Also confirm the currency and whether prices are tax-exclusive or tax-inclusive. These choices affect the meaning of the numbers. The first-invoice workflow puts those decisions before data entry and the final output check.
Start with the approved scope
Collect the quotation, statement of work, order or other agreed billing record. If time is billed, retain the approved time record separately. If a milestone is billed, identify the event that made it billable and any acceptance the agreement requires. The application cannot determine whether a task was authorised or completed.
Avoid turning every internal activity into a separate customer charge unless the agreement supports that breakdown. Conversely, do not combine clearly different deliverables into an unexplained “services” line simply because it is shorter. The level of detail should support identification, matching and review.
Check the billing entity and order reference with the customer’s accounts-payable contact. The person receiving the work may not be the legal customer named in the order. A correct technical export cannot compensate for billing the wrong group company.
Describe the work with enough context
For a fictional translation job, “Translation of product manual, agreed June revision” is more identifiable than “professional services”. Retain a project or order reference in its appropriate field where available. If a service period matters, record the actual period rather than replacing it with the invoice issue date.
The current creator does not have a dedicated structured service-period field. A readable description or note can help explain the period in a printable document, but it is not a substitute for a required period field in an external standard. Preserve the underlying dates for software that supports the recipient’s structure.
Keep confidential project details out of the invoice unless genuinely needed for identification. A description can identify a deliverable without including passwords, personal case histories or unnecessary customer data. Ask the recipient how to reference sensitive work when ordinary project names are unsuitable.
Match quantities and prices to the agreement
Suppose an approved task contains 7.5 hours at EUR 48 per hour. Enter quantity 7.5, unit “hour” and unit price 48.00. The amount before any discount or tax is EUR 360. Do not enter 360.00 as the unit price while retaining quantity 7.5, because that would multiply the total again.
For a fixed-price deliverable of EUR 360, a quantity of 1 and a meaningful unit such as “project” can describe the agreed charging basis in an ordinary preparation workflow. The numeric result may be the same, but the commercial meaning differs. Choose the representation supported by the contract and final recipient requirements.
The application accepts quantities to four decimal places and unit prices to two. If your service contract uses more precise rates, preserve them and choose software that can represent the required calculation. Rounding an agreed rate before entry can change a long invoice’s total, even when the editor correctly calculates its rounded inputs.
Keep adjustments and tax decisions explicit
A line-level percentage discount can be entered where that is the agreed arrangement. The creator rounds the line amount, rounds and deducts the discount, and then calculates tax on the line’s net amount. This is its application policy, not a universal rule for all structured invoice profiles.
If the agreement includes a prepaid deposit, retention, withholding or a document-level fee, do not hide the adjustment by changing hours or reducing the unit price. Those structures are outside the current ordinary invoice model. Retain the real values and complete the invoice in supporting software where needed.
Enter the tax category and rate you have confirmed. A service being supplied remotely, to another country or to a business does not by itself give the editor enough information to determine treatment. An exemption or outside-scope selection needs an explanation in this application, but completing that box does not prove the treatment is legally correct.
Review against the evidence and recipient instructions
Compare the final description and quantities with the approval record. Confirm that the billing period, invoice number, buyer reference, currency and payment instructions are consistent. A field check can detect certain missing or invalid entries, but not an unapproved hour or the wrong contract rate.
For a transaction involving physical goods as well as service work, use the product-sales preparation checks for the relevant lines. Keep distinct units and prices rather than forcing every component into the service’s charging basis.
The current creator offers a readable printable invoice, application JSON and line-items CSV. If the customer requires recognised XML or a hybrid standard, you still need an appropriate external output process. Review the actual exported file and select the correct version for sharing. The preparation is useful only when both the billing facts and the eventual recipient requirements remain intact.