Invoice Template for Designers

Standard Operating Procedure: Design Agency Invoice Generation & Lifecycle Management

Document ID: SOP-TR-FIN-042
Effective Date: October 24, 2023
Version: 3.2
Review Cadence: Annual

---

1. Executive Summary & Purpose

1.1 Purpose

This Standard Operating Procedure (SOP) defines the institutional baseline for generating, validating, and issuing commercial invoices for graphic, UX/UI, and multidisciplinary design services originating from Template Registry. The objective is to eliminate revenue leakage, ensure tax compliance, enforce payment terms, and maintain precise audit trails for all billable creative outputs.

1.2 Policy Statement

All design engagements executed under the Template Registry brand must transition from a signed Statement of Work (SOW) to a formally registered invoice utilizing this protocol. Informal billing, unitemized line items, and verbal payment terms are strictly prohibited.

---

2. Scope & Prerequisites

2.1 Scope

This procedure applies to all internal designers, project managers, contractors, and financial administrators generating client-facing invoices for design deliverables, retainer fees, and licensing rights.

2.2 Prerequisites & Tooling

• ERP/Accounting Engine: QuickBooks Enterprise / Xero (Authorized instance).
• Design & Document Engine: Adobe InDesign / Figma (Template ID: TR-INV-DES-09).
• Payment Gateway: Stripe / ACH Direct / Wire Transfer Routing.
• Authentication: Multi-Factor Authentication (MFA) enabled on all financial portals.

---

3. Roles & Responsibilities (RACI Matrix)

• Responsible (R): Executes the specific phase tasks.
• Accountable (A): Owns final approval and institutional sign-off.
• Consulted (C): Provides input on scope, milestones, or tax laws.
• Informed (I): Receives notification of status changes.

---

4. Step-by-Step Procedure

Phase 1: Data Aggregation & Verification

• Retrieve the approved Statement of Work (SOW) and change orders from the enterprise repository.
• Audit time-tracking logs and milestone completion certificates for accuracy.
• Confirm client billing entity, exact legal name, tax ID (if applicable), and physical mailing address.
• Calculate net figures, applying applicable discounts, retainer draw-downs, or pass-through expenses (e.g., stock asset licensing, fonts).

Phase 2: Template Assembly & Line-Item Structuring

• Open the authorized design invoice master template (TR-INV-DES-09).
• Populate the header with the unique Invoice ID (TR-[YYYY]-[MM]-[Sequence]), Issue Date, and Payment Due Date (Standard: Net 30).
• Input itemized creative services using distinct professional nomenclature (e.g., Phase 2: High-Fidelity UX Wireframing rather than Design Work).
• Detail licensing rights granted (e.g., Exclusive global digital usage for 24 months).

Phase 3: Compliance & Financial Validation

• Verify applicable sales tax, VAT, or GST rates based on the client's jurisdictional nexus.
• Embed explicit payment instructions (ACH routing numbers, SWIFT codes, or secure payment gateway URLs).
• Cross-reference the subtotal against the signed SOW to ensure zero variance without an approved change order.
• Attach mandatory supporting documentation (e.g., third-party licensing receipts, sign-off logs).

Phase 4: Transmission & Lifecycle Tracking

• Export the finalized document as a linearized, text-searchable PDF (Lock formatting layers; disable editing).
• Transmit the invoice via the official enterprise billing portal or secure email to the client's Accounts Payable contact.
• Log the invoice issuance date in the ERP system to initiate the automated aging and collection workflow.
• Archive the master PDF and verification logs in the permanent financial audit directory (/Finance/Invoices/[YYYY]/).

---

5. Quality Assurance & Pro-Tips

5.1 Best Practices

• Granular Itemization: Separate conceptual ideation from execution and licensing. This minimizes dispute vectors during client review.
• Immediate Milestone Billing: For long-term design projects, issue invoices strictly upon milestone sign-off, never upon project completion.
• Visual Hierarchy: Maintain typography and whitespace standards from the master template to reinforce brand equity even in billing documents.

5.2 Common Pitfalls

• Scope Creep Ambiguity: Invoicing for unapproved revisions without a signed change order leads to chargebacks.
• Delayed Issuance: Failing to issue the invoice within 24 hours of milestone completion increases Days Sales Outstanding (DSO) by an average of 14%.

5.3 Metric Thresholds

• Target DSO: $\le 35$ Days.
• Dispute Rate: $< 2%$ of total issued invoices.
• Data Accuracy: $100%$ match between SOW terms and invoice line items.

---

6. Frequently Asked Questions (FAQ)

Q1: What is the protocol if a client disputes a line item on an issued invoice?
A: Immediately log the dispute status in the ERP system, freezing automated collection reminders for that specific invoice. The Project Manager must cross-reference the disputed item against the signed SOW within 24 hours. If an error occurred, issue a corrective Credit Memo and a revised invoice; if the scope was delivered as contracted, present the signed approval documentation to the client's Accounts Payable department.

Q2: How should pass-through costs (e.g., specialized typography licenses or stock photography) be handled?
A: Pass-through costs must be listed as a separate, un-marked-up line item accompanied by the original vendor receipt attached as an addendum to the invoice PDF. Ensure sales tax rules are applied to pass-through costs in accordance with regional tax laws.

Q3: Can we alter the standard Net 30 payment term for enterprise design clients?
A: Modifications to payment terms (e.g., Net 45 or Net 60) require formal written authorization from the Chief Financial Officer and must be explicitly codified within the master SOW prior to invoice generation.