Design, writing and digital services: describe the export accurately

Prepare a useful service description from your contract and deliverables before asking about EDF classification.

A good description tells the reviewer what the customer bought. Job titles and broad labels such as online work rarely explain enough. Use your contract and actual deliverables to prepare a description that is accurate, specific and consistent across the invoice and bank enquiry.

Describe the work without choosing an unsupported code

State the service, period or milestone and the customer-facing deliverable. A description such as editing six product articles under the October contract is more useful than miscellaneous digital services. For mixed work, explain the separate components. Do not assume that terms used for GST, a marketplace category or your professional profile settle the authority’s classification.

Handle ambiguity openly

Some digital deliverables raise software-definition or authority-route questions. Explain the format and scope to the appropriate desk rather than hiding the digital component. Keep the written classification guidance with the contract. If your next engagement changes substantially, check whether the earlier response still covers it instead of applying it to every future invoice.

Turn a vague label into a factual description

Start with the customer’s requested output, the agreed period or milestone and the work actually delivered. A statement such as preparing six product descriptions under the October engagement is easier to review than online earnings. Mention separately contracted work where the documents distinguish it. The description should be specific enough to understand without exposing confidential creative material unnecessarily.

Compare the wording across the contract, invoice and bank enquiry. If they differ, explain whether one is a short label for the same work or whether the scope changed. Do not rewrite the commercial history to fit an easier category. Where a digital deliverable creates an authority-route question, describe the actual format and ask the relevant institution to assess it.

Keep classification systems separate

A marketplace category, GST service classification, invoice description and bank remittance purpose can serve different purposes. The presence of a familiar number in one system does not automatically supply the correct value for another. Keep a plain-language summary as the stable starting point and ask which current taxonomy the particular field uses.

When a code or category is confirmed, record the source, version where available and transaction context. If the work later changes from advice to software delivery or another materially different output, check whether the earlier answer remains appropriate. Avoid a permanent default selected only because it worked on one past invoice. A good description makes the question easier; it should not pretend to replace the authority’s conclusion.

Describe mixed engagements without arbitrary splitting

Creative engagements can include strategy, workshops, production and delivery of files. Use the actual contract and invoice structure to explain those elements. If the documents price them separately, keep that distinction visible. If they are genuinely one combined engagement, do not invent separate invoices or dates merely to obtain a preferred process.

Ask the bank or designated authority how it wants the components described and whether different treatment is needed. Preserve the written response with the scope it assessed. Keep evidence of changes requested by the customer so later invoices remain understandable. The goal is a consistent documentary account of the work, with uncertainty surfaced early rather than hidden in a broad label.

A fictional example

A designer delivers a strategy workshop and a package of digital design files. The enquiry describes both elements and asks about classification. It does not simply select non-software because the exporter’s profile says creative freelancer.

Preparation checklist

Match the description to the actual contract.
Separate materially different deliverables.
Ask about unclear categories before selecting codes.

Can I reuse the wording in a fictional sample?

Use it only as an illustration. Replace it with an accurate description of your own work.

FICTIONAL WALKTHROUGH

A writing contract adds digital production work

A fictional writer initially supplies editing services under a clear engagement. A later customer asks for editing plus preparation of a digital asset package. The writer updates the scope summary using the actual agreement and does not assume the earlier classification answer covers the new component.
The enquiry describes the deliverables, invoice structure and delivery format. It asks which category and code guidance applies without selecting a number from another writer’s tutorial. The original contract and change correspondence support the explanation.
The response is stored with the engagement’s scope. Future invoices use descriptions consistent with the work supplied. If the customer later changes the scope again, the writer can identify what changed rather than treating every creative service as identical.

Your next step

Read field explanations

Sources and scope

Sources reviewed 9 October 2026. The routines and fictional examples are editorial preparation suggestions. They do not confirm your bank’s acceptance, classification or transaction status.