Invoice Template for Virtual Assistant

STANDARD OPERATING PROCEDURE: VIRTUAL ASSISTANT INVOICE GENERATION & LIFECYCLE MANAGEMENT

---

1. EXECUTIVE SUMMARY & PURPOSE

This Standard Operating Procedure (SOP) defines the institutional requirements for the generation, validation, issuance, and lifecycle management of Virtual Assistant (VA) billing artifacts within the Template Registry ecosystem. The purpose of this document is to eliminate billing variance, enforce strict audit trails, accelerate cash flow velocity through standardized invoice composition, and ensure total compliance with international remote-contractor financial frameworks.

---

2. SCOPE & PREREQUISITES

2.1 Scope

This protocol applies to all internal and external personnel operating in a Virtual Assistant capacity who submit billing requests, compile timesheet data, or manage accounts receivable (AR) processing for Template Registry operations.

2.2 Prerequisites & Tooling

Execution of this procedure requires verified access to the following institutional systems:

• Template Registry Certified Billing Engine: (v4.2 or higher, providing immutable document ID generation).
• Time-Tracking Telemetry: Toggl Track, Harvest, or approved automated epoch-logging mechanism.
• Accounting Ledger Interface: QuickBooks Online, Xero, or Stripe Invoicing.
• Document Security Protocol: Cryptographic signing utility or PDF/A-1a compliance validation software.

---

3. ROLES & RESPONSIBILITIES (RACI MATRIX)

• Responsible (R): The entity that performs the activity.
• Accountable (A): The entity with final approval authority and fiduciary ownership.
• Consulted (C): The subject matter expert providing operational inputs.
• Informed (I): The entity updated on execution status.

---

4. STEP-BY-STEP PROCEDURE

Phase 1: Data Harvesting & Telemetry Verification

• Pull immutable time-tracking logs from the approved telemetry tool for the designated billing cycle.
• Cross-reference logged hours against the Master Services Agreement (MSA) scope and project allocation limits.
• Collate itemized expense receipts (if pre-authorized) and verify tax-inclusive digital copies are stored in the secure artifact repository.
• Compute sub-totals, categorizing line items strictly by billable task taxonomy (e.g., Administrative Execution, Technical Support, Data Engineering).

Phase 2: Invoice Assembly via Template Registry Engine

• Instantiate a fresh document instance using the certified TR-VA-INVOICE-v2.1 template schema.
• Populate the Header Block with exact legal entities: Corporate Provider Name, VA Legal Name, physical address, and Tax ID/EIN.
• Assign a deterministic Invoice Number utilizing the required format: [TR-VA]-[YYYYMMDD]-[SequentialID] (e.g., TR-VA-20231024-004).
• Input explicit Net Payment Terms as defined in the contract (default: Net-30).
• Insert granular line items containing: Date of Service, Task Description, Hours Rendered, Hourly Rate, and Extended Line Total.
• Apply applicable regional taxes (VAT/GST/Sales Tax) only where legally mandated by jurisdiction.

Phase 3: Quality Control & Cryptographic Validation

• Perform a mathematical verification of all line extensions and cumulative totals.
• Ensure customer purchase order (PO) numbers are embedded if required by the client’s procurement protocol.
• Export the finalized document to immutable PDF/A format.
• Execute digital cryptographic signature validation to ensure anti-tamper compliance.

Phase 4: Transmission & Accounts Receivable Tracking

• Transmit the validated invoice PDF via the designated secure enterprise email gateway or accounting portal.
• CC the assigned Project Manager and Accounts Receivable (ar@templateregistry.internal).
• Log the transaction state change in the AR Ledger as SUBMITTED_AWAITING_ACKNOWLEDGEMENT.
• Schedule automated payment reminder triggers at T-minus 7 days, T-zero (Due Date), and T-plus 5 days.

---

5. QUALITY ASSURANCE & PRO-TIPS

5.1 Operational Best Practices

• Zero-Ambiguity Descriptions: Never use generic labels like "Admin Work." Use precision descriptors: "Executed batch data cleansing of 1,200 CRM records in Salesforce."
• Time-Stamp Hygiene: Submit timesheets weekly, even for monthly billing cycles, to prevent memory degradation and dispute latency.
• Immediate Exception Handling: If a client challenges an hour allocation, place the disputed line item into a hold state while the un-disputed balance is processed immediately.

5.2 Common Pitfalls to Avoid

• Stale Metadata: Utilizing outdated tax IDs or superseded corporate addresses.
• Late Submission: Failing to submit invoices within 48 hours of the billing cycle closure, which breaks fiscal quarter closing windows.
• Ad-Hoc Formats: Using native Word or Excel formats instead of locked PDF/A standards, exposing the document to unauthorized alterations.

5.3 Metric Thresholds

• First-Pass Yield (FPY): $\ge 98%$ of invoices must pass client procurement review without revision requests.
• Days Sales Outstanding (DSO): $\le 28$ days average collection velocity.

---

6. FREQUENTLY ASKED QUESTIONS

Q1: What is the mandatory protocol if a client fails to provide a Purchase Order (PO) number prior to the invoice submission deadline?

A: Escalate immediately to the Project Manager via high-priority ticketing. Do not hold the invoice generation; instead, issue the invoice with a placeholder PO notation (PO-PENDING-PM-APPROVAL) and notify the AR Clerk to flag the transaction for conditional processing.

Q2: How are fractional billable hours rounded for administrative tasks?

A: All time metrics must be tracked in decimal increments of tenths of an hour (6-minute intervals). Standard rounding applies: mathematical floor for 1–2 minutes, ceiling for 3–5 minutes. Never bill in arbitrary block increments not substantiated by telemetry logs.