Exempt and outside scope are not interchangeable labels for a zero tax amount. Preserve the treatment that has actually been determined for the transaction, together with its supporting reason. The same numerical result does not make the legal or accounting meaning identical.
The tax preparation process separates that determination from data entry. The current creator calculates zero tax for both choices and requires a reason for its field checks. It does not decide which choice applies or formally validate the reason against tax law or a destination profile.
Identify the question behind the label
An exemption and a conclusion that a transaction is outside the relevant scope arise from different analyses. Which analysis applies depends on the circumstances and requirements. Do not choose either label because it sounds more suitable to a customer or produces the expected total.
Provide the responsible reviewer with the actual supply, parties, timing and relevant locations. Preserve the resulting determination and its scope. A general statement about the business may not cover every type of supply it makes or every customer arrangement.
If the reviewer has not reached a conclusion, mark the draft unresolved. The interface offering two choices does not imply that one can be selected safely without the necessary facts. A completed field can conceal uncertainty rather than resolve it.
Make the reason traceable
A reason should correspond to the actual determination. Avoid generic text copied from an unrelated invoice, particularly if it cites a provision or describes a different supply. Record where the wording came from and which line or group of supplies it covers.
The customer-facing explanation may be shorter than the internal advice. Keep supporting correspondence and detailed analysis in appropriate business records, rather than pasting confidential discussion into the invoice. The recipient needs the relevant statement, not necessarily every internal step used to reach it.
OpenPeppol’s published tax-category structure distinguishes category, rate and reason fields. That illustrates the need to preserve each role. It does not establish that the current creator maps its reason text into that profile or verifies any exemption code.
Understand what the app checks
The current creator checks that a reason exists for exempt and outside-scope lines. It can identify an empty field, but it cannot determine that a complete sentence is factually correct or legally sufficient. A string such as “as agreed” may pass a presence check without explaining the actual basis.
Review the reason beside the category and description. A copied exemption explanation on a newly outside-scope row can create a contradictory statement even though tax remains zero. Correct all related values when the determination changes.
Do not use the reason field for delivery notes, payment instructions or an internal approval message. Those facts have different roles. Mixing them with the tax explanation makes the review less clear and does not add missing structured functionality.
Preserve other required information
The final workflow may need identifiers, specific codes or a category-level explanation beyond the creator’s current model. Keep those requirements separately in the preparation record. Putting several labelled values into one text field does not create typed fields in a formal export.
Use the text-versus-code comparison when a recipient or software provider requests a coded reason. Confirm the applicable list and profile instead of guessing a code from a phrase. The app does not offer an official code selector or perform list-membership validation.
If a required representation cannot be expressed accurately here, use a suitable final invoicing system. Do not substitute another zero-tax category merely to fit the available controls. The monetary equivalence would hide the difference the recipient may need to process.
Review changes and final handoff
When the supply or customer circumstances change, check whether the earlier determination still applies. A copied draft can retain both category and reason from a previous transaction. Familiar wording is not evidence that it remains appropriate.
For a fictional review example, an adviser might return a corrected treatment and new explanation for one row while leaving the others unchanged. Update that row’s preparation record and application values together, then review the complete document for conflicting text. Do not apply the change globally without checking its scope.
After the supported fields are settled, run field validation and export a fresh version. The JSON uses the application’s own schema, CSV contains line items and printing uses the browser. None of those outputs establishes formal tax-category mapping, authority acceptance or recipient approval.
Keep the final determination, reason and exported version linked in your records. If the invoice needs a formal standard or submission workflow, complete those stages in verified software. The useful outcome of preparation is an explicit, traceable statement whose unresolved limits are visible, rather than a zero tax figure that appears to explain itself.
A practical review check
When asking for clarification, send the actual competing interpretations rather than asking only whether the invoice should have zero tax. Ask which treatment applies, which facts support it and which explanation the final document needs. This produces a more useful answer than confirmation of a numerical result shared by both choices.