Your contact forwards your invoice with “All good from me.” The person opening the PDF has never seen the work. They have a charge labeled “September updates” and a colleague's approval, but no way to connect those words to the files you delivered.
Take a four-page fall catalog as an example. The approver needs to connect the $960 charge to those four pages, even if the contact who commissioned them is away. Open a draft in Tallyspar or use your existing invoice document.
Replace “Design services” with the delivered work
Your draft invoice says “Design services: $960.” The description sends the reader away to find out what you delivered. Open the project folder before you edit the invoice. Find the approved scope and the file you sent.
Write the line again: “Fall catalog: design and layout of four product pages, approved September 18.” Keep the price beside it. A count gives the approver something to match against the scope. A date distinguishes this delivery from the catalog cover you finished in August.
In Tallyspar, put that description in the client-facing item field. Keep your working note, “Third photo swap took ages,” in the private note. Keep that note out of the PDF you send to Lena.
Make the reference survive a forwarding chain
Give the invoice a stable number, such as TS-1042, and use it in the filename and email subject. “Invoice TS-1042: fall catalog pages” can be found again after your contact forwards it. “Final invoice NEW” asks the next person to guess which file won.
If the client supplied a purchase order or job code, copy it exactly into its own reference field. Do not shorten “CAT-26-09-B” to “September.” The code distinguishes this job from the client's other September work. If you have not received the required code, ask for it before sending the invoice.
Ask the person handling the work who should receive the invoice. A designer approving a layout and a team handling invoices may use different addresses. Confirm the address rather than guessing that the person copied on the last review email owns the next step.
If the project has phases, name the phase you are charging for. “Catalog, phase two” still makes the reader look elsewhere. “Catalog: layout of pages 5–8” gives them a boundary. Keep an unfinished cover redesign off this description if it belongs to a later delivery.
Put the evidence next to the description
Add a reference to the approved PDF or the dated handoff email. “Approved catalog PDF, September 18” is a better label than “Click here.” It tells the person what they are opening before they leave the invoice.
Check who is allowed to open the delivery reference. For a confidential catalog, ask the authorized recipient to confirm access; keep the sign-in requirement. A signed-out test suits a deliberately public file. Do not make a private folder public to get through the test.
Link to the approved file itself, rather than its parent folder. The approver needs the four catalog pages, not rejected layouts or another client's draft. If the approved file moves, update its delivery reference before you export the invoice.
For work that cannot be linked, name the handoff precisely. “Sent to Lena on September 18; subject: Catalog pages approved” points to an email someone can locate. Do not paste a private conversation into the invoice to prove a two-sentence decision.
Ask Lena for the next action
In the delivery email, name TS-1042 and ask for the one action you need from Lena:
“Hi Lena, attached is invoice TS-1042 for the four fall catalog pages approved September 18. The approved PDF is linked beside the description. Please forward it to the person handling invoices. Thanks, Mara.”
If Lena has already given you the correct recipient, send it there and change the request. “Please confirm receipt” suits that situation. A copied template that asks for an introduction you already received makes the rest of the message look unchecked.
Compare the dates on TS-1042 with the agreed brief and your delivery message. September 18 is the approval date in our example. If it was actually the date you sent a first draft, label it that way. An approval you are still waiting for cannot become a fact by appearing in a PDF.
Run the phone test
Open the exported invoice on your phone, away from the delivery email. Read it without looking at the total. You should be able to identify four fall catalog pages and their approval date. Check that a wrapped description has not disappeared below the visible item row. Download the attachment and check its filename, too.
Forward the draft to yourself with no explanation. Open its delivery link from that message. If you need to reopen a chat to understand “September updates,” the description needs another edit.
If a colleague is available, ask them to identify the charge from the draft. Do not explain the project first. Write down their first question before answering it. If they ask which catalog, replace “catalog” with its actual title.
Once Lena confirms the right recipient, save that address with the project in Tallyspar. Add a routing note dated September 19. Check it again if the client changes the process or your next project has a different owner.
When the answer comes back
If someone queries the four-page count, compare TS-1042 with the approved scope before sending a reminder. A question about whether page eight was included needs a scope check. A missing CAT-26-09-B reference needs a corrected field. Repeating the original attachment answers neither message.
When you make a correction, follow the numbering and correction process you already use. In the reply, identify the version you are replacing and the field you changed: “The attached copy replaces my earlier TS-1042; the job reference now reads CAT-26-09-B.” Check that the filename and document show the same invoice number.
Download the attachment once more. Name it TS-1042_fall-catalog.pdf, open that copy, and send it to the address Lena confirmed.