As of 13 August 2026, AI can only partly automate your business invoices.

What to actually do

1. Hand it to a person

   The route this page recommends

   A person who owns the outcome does this end to end, worth it when the failure is dear.

2. Use a tool built for this

   Second choice

3. Do it yourself

   The distant third

   A chat interface, power-user skill, and roughly 1 hour until you can act on the result.

   How to actually do it

   1. Open your invoicing, order and accounting systems and export a small set of fictional or redacted records, then copy their current invoice template, numbering rules and relevant API documentation into separate files.
   2. Write down your UK VAT status, required invoice fields, approval rules, cancellation process and the person responsible for correcting accounting records.
   3. Paste those documents and details into the prompt, replacing each bracketed slot with your actual configuration and leaving any unknown item marked as unknown.
   4. Ask the chatbot to produce the workflow, field mapping, validation rules and test plan, then compare every proposed field and API action with the documentation you supplied.
   5. Build the workflow in a test account or draft-only environment using fictional customers and orders, and check that missing fields, duplicate orders, cancellations and VAT cases stop rather than create a live invoice.
   6. Compare each test invoice with its source order and accounting entry, ask your bookkeeper or system administrator to check the VAT and permissions, then approve a limited live rollout that keeps manual approval before sending.

   Prompt

   Design a safe invoice-automation workflow for a UK business using the information below.
   
   Business type: [BUSINESS TYPE]
   Invoicing system: [INVOICING SYSTEM]
   Order or sales source: [ORDER SOURCE]
   Accounting system: [ACCOUNTING SYSTEM]
   UK VAT status and invoice rules: [VAT STATUS AND RULES]
   Approval rules: [WHO MUST APPROVE AN INVOICE]
   Invoice numbering rules: [NUMBERING RULES]
   Customer and product fields available: [LIST THE FIELDS]
   
   I will paste the relevant API documentation, export examples and current invoice template after this instruction. Use only the information I provide for field names, tax treatment, permissions and API behaviour. Do not invent endpoints, credentials, VAT rules, invoice numbers or customer data.
   
   Produce:
   1. A plain-English workflow from a completed order to a draft invoice, approval and sending.
   2. A field-by-field mapping between the order source, invoice system and accounting system.
   3. Validation rules for missing customer details, duplicate orders, cancelled orders, unusual quantities, discounts, currency, VAT and invoice numbering.
   4. The minimum permissions and data that each connection needs.
   5. Implementation steps or code only for the documented APIs, with clear placeholders for secrets and environment variables.
   6. A test plan using fictional data, including failed and duplicate transactions.
   7. A manual approval stop before any invoice is sent or posted to the accounts.
   8. A reconciliation checklist comparing sent invoices with orders and accounting records.
   
   Keep the first version in draft mode. Mark every assumption and every item that needs confirmation from me or my bookkeeper. Do not recommend sending live invoices until the test plan passes and I have checked the VAT and accounting treatment.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.