Dropbox file naming for agency invoice handoffs

Use a stable folder structure

A simple agency pattern is client, project, then working, review, approved, delivered, and commercial. Adapt it to your security and retention needs. Keep working files separate from the version a client approved or received.

Avoid folders named for a temporary teammate. The structure should survive ownership changes.

Name files for recognition, not storytelling

Use a small set of stable elements such as client, project, deliverable, version, and date where the date helps. For example, northwind_campaign-key-visual_v03_2026-08-09.pdf.

Do not rely on final, final2, or use-this-one. Version numbers describe sequence. Approval and delivery should be recorded as workflow states.

Separate the file from the approval decision

The approved asset should be immutable or preserved as a distinct final. The decision record should name the approver, time, version, comments, and resulting action. A file moved into an approved folder is helpful organization, but it is not enough audit history for consequential work.

Define the billing trigger in advance

Use the agreement to decide whether billing happens at a date, delivery, approval, percentage of completion, or another milestone. When the trigger occurs, create or surface the invoice action with the client, project, amount basis, owner, and due terms already attached.

Do not ask finance to infer billability from the presence of a file.

Review the handoff exceptions

• Approved files with no delivery record.
• Delivered work with no billing decision.
• Billing triggers reached with no invoice owner.
• Issued invoices stored but not marked sent.
• Paid invoices with no reconciliation.
• Projects with several files that appear to be the final version.

A short exception review keeps the normal flow quiet and gives unusual cases a named next action.