Custom Invoice Template for Xero

Standard Operating Procedure: Custom Invoice Template Deployment (Xero)

Document ID: TR-FIN-XERO-001
Effective Date: 2023-10-27
Version: 1.0.0
Review Cadence: Bi-annual (Q2/Q4)

---

1. Executive Summary & Purpose

This SOP dictates the standardized workflow for designing, configuring, and deploying custom DOCX invoice templates within the Xero ecosystem. The objective is to ensure brand consistency, financial data integrity, and compliance with regional tax reporting requirements.

---

2. Scope & Prerequisites

Scope: Covers the creation of Xero-compliant DOCX templates, mapping of merge fields, and system ingestion. Prerequisites:

• Software: Microsoft Word (Desktop Version, Windows/macOS), Xero Standard or Premium Subscription.
• Access: Administrator-level privileges in the target Xero organization.
• Assets: Official brand identity kit (Logo in high-resolution PNG/SVG, hex codes, typography assets).

---

3. Roles & Responsibilities (RACI)

---

4. Step-by-Step Procedure

Phase I: Preparation & Extraction

• Log in to Xero: Settings > Invoice Settings.
• Select Download on the Custom.docx template to establish the base schema.
• Enable "Developer" tab in MS Word to monitor field codes.

Phase II: Template Construction

• Define Static Layout: Insert logo, contact headers, and footer legal disclaimers.
• Field Mapping: Replace text placeholders with valid Xero merge fields (e.g., «InvoiceNumber», «DueDate», «Total»).
• Table Formatting: Configure the line-item table using a single row containing desired merge fields. Xero auto-expands this row based on line item count.
• Constraint Check: Ensure file size remains < 1MB.

Phase III: Deployment & Validation

• Upload the modified .docx via Invoice Settings > Upload.
• Assign as "Default" template.
• Execute an "Invoice Preview" using an existing record to verify field rendering.
• Send a test invoice to an external email address to confirm PDF rendering accuracy.

---

5. Quality Assurance & Pro-Tips

Quality Metrics

• Rendering Success: 100% of PDFs must generate without broken field tags.
• Brand Fidelity: Fonts must be embedded or web-safe to prevent substitution artifacts.

Pro-Tips

• Table Logic: Do not attempt to merge cells in the line-item table; Xero's rendering engine does not support advanced table nesting.
• Field Codes: Use standard MS Word Insert > Field functionality if manual syntax «FieldName» fails to pull data.
• Cache Clearing: If changes are not reflected, clear browser cache and re-upload the file with a version-controlled filename (e.g., INV_V1.1.docx).

---

6. Frequently Asked Questions

Q: My logo appears distorted or pixelated in the final PDF.
A: Xero compresses images for speed. Ensure your logo is exactly the size required (do not scale in Word) and is a 72–150 DPI PNG.

Q: Why does the template fail to upload?
A: Xero rejects files containing macros or complex embedded objects. Ensure the document is saved as a strict .docx (not .doc or .dotx).

Q: Can I add conditional logic (e.g., show text if a certain condition is met)?
A: Xero supports limited IF field codes in Word. However, ensure logic syntax is strictly standard MS Word field syntax, as advanced VBA-based logic is unsupported.

---

Authorized by: Julian Vance, Chief Architect, Template Registry.