# E-invoicing implementation plan for UK finance teams

> A phased e-invoicing implementation plan for UK finance teams preparing for April 2029: governance, workstreams, milestones, risks and a go-live checklist.

- Canonical URL: https://einvoices.uk/news/e-invoicing-project-plan-finance-teams
- Published: 20 October 2026 (2026-10-20)
- Last updated: 20 October 2026 (2026-10-20) (not updated since publication)
- Author: Floris Lindenaar, Editor, e-invoicing expert (https://einvoices.uk/authors/floris-lindenaar)
- Publisher: einvoices.uk (https://einvoices.uk)
- Type: Guide
- Topics: Finance teams, 2029 mandate, Peppol, Compliance
- Language: en-GB (UK English); covers the United Kingdom

## Sources

- [Tax update 2026: simplification, modernisation and fairness summary](https://www.gov.uk/government/publications/summary-of-tax-update-2026-simplification-modernisation-and-fairness/tax-update-2026-simplification-modernisation-and-fairness-summary)
- [Promoting electronic invoicing across UK businesses and the public sector: consultation response](https://www.gov.uk/government/consultations/promoting-electronic-invoicing-across-uk-businesses-and-the-public-sector/outcome/promoting-electronic-invoicing-across-uk-businesses-and-the-public-sector-consultation-response)
- [HMRC Transformation Roadmap: update 2026](https://www.gov.uk/government/publications/hmrc-transformation-roadmap-progress-update-2026/hmrc-transformation-roadmap-update-2026)
- [Peppol BIS Billing 3.0](https://docs.peppol.eu/poacc/billing/3.0/)

---

A good e-invoicing implementation plan has **six phases: mobilise, discover, design, build, pilot and roll out**, with five workstreams running through them: accounts receivable, accounts payable, master data, technology and trading partners. Start the first two phases now; the later ones depend on the UK specification, expected from the roadmap at **Budget 2026 on 28 October 2026**, ahead of the mandate on **April 2029**.

This plan is written for finance teams in mid-sized and larger UK businesses. Smaller businesses can use the [readiness checklist](https://einvoices.uk/news/uk-e-invoicing-readiness-checklist) instead.

## Fixed points to plan around

**Confirmed:**

- Mandate for VAT invoices from April 2029 (consultation response).
- Peppol as the network: "The government has announced that the electronic procurement system Peppol will be the core interoperability network for e-invoicing in the UK" (GOV.UK Tax update 2026 summary, 23 June 2026).
- Decentralised model, no real-time reporting at launch.
- HMRC's 2026 transformation roadmap update says HMRC is working with the Department for Business and Trade "to publish an e-invoicing roadmap at Budget 2026 that will set out the milestones" to implementation in April 2029.

**Not yet confirmed:** interim milestones, the data standard, phasing by business size, penalties, provider accreditation. Build your plan with these as dependencies and revisit it after 28 October 2026.

## Governance

| Role | Typical owner | Responsibility |
|---|---|---|
| Sponsor | CFO or finance director | Budget, priority, decisions |
| Project lead | Financial controller or finance systems lead | Plan, risks, reporting |
| AR lead | Credit control / billing | Sales invoice process, customer readiness |
| AP lead | Purchase ledger | Supplier invoice intake, matching, approvals |
| Tax lead | VAT manager or adviser | VAT rules, scope, edge cases |
| Technology lead | IT / ERP team | Integration, Access Point, testing |
| Procurement lead | Procurement | Supplier onboarding and contracts |

Hold a short monthly steering meeting from now, weekly once build begins.

## Phase 1: Mobilise (start now)

- [ ] Appoint sponsor and leads.
- [ ] Agree scope: which legal entities, which invoice flows.
- [ ] Set up a risk log and decision log.
- [ ] Budget for discovery and vendor engagement (see [what e-invoicing costs](https://einvoices.uk/news/e-invoicing-cost-uk)).

## Phase 2: Discover

- [ ] Inventory every system that creates or receives invoices, by entity.
- [ ] Measure volumes: invoices and credit notes sent and received, by channel and partner.
- [ ] Identify edge cases: [self-billing](https://einvoices.uk/news/self-billing-e-invoicing-uk), [VAT groups](https://einvoices.uk/news/e-invoicing-vat-groups), [reverse charge](https://einvoices.uk/news/domestic-reverse-charge-construction-e-invoice), [foreign currency](https://einvoices.uk/news/multi-currency-e-invoices-gbp), [Northern Ireland](https://einvoices.uk/news/e-invoicing-northern-ireland-xi-vat), [Isle of Man](https://einvoices.uk/news/e-invoicing-isle-of-man).
- [ ] Ask software vendors for written Peppol plans (see [checking software support](https://einvoices.uk/news/check-accounting-software-peppol-support) and our [ERP guide](https://einvoices.uk/news/e-invoicing-erp-sap-oracle-dynamics-netsuite)).
- [ ] Record a baseline of costs and cycle times, so you can measure [benefits](https://einvoices.uk/news/e-invoicing-benefits-uk).
- [ ] Assess [master data quality](https://einvoices.uk/news/master-data-cleanup-e-invoicing).

**Output:** a discovery report with systems map, volumes, gaps and options.

## Phase 3: Design

- [ ] Choose the connection approach: native ERP feature, add-on, or a separate [Access Point](https://einvoices.uk/news/how-to-choose-a-peppol-access-point).
- [ ] Decide your [Peppol identifiers](https://einvoices.uk/news/peppol-participant-id-uk) for each entity.
- [ ] Map invoice data to [Peppol BIS Billing 3.0](https://einvoices.uk/news/peppol-bis-billing-3-uk-guide) fields, flagging items to confirm against UK rules.
- [ ] Map tax codes to [VAT category codes](https://einvoices.uk/news/uk-vat-category-codes-peppol).
- [ ] Design exception handling: validation failures, delivery failures, customer rejections.
- [ ] Decide whether to send and process [invoice responses](https://einvoices.uk/news/peppol-invoice-response-message-level-response).
- [ ] Design archiving to meet HMRC record-keeping rules (see [archiving and retention](https://einvoices.uk/news/e-invoice-archiving-retention-uk)).
- [ ] Segment trading partners for onboarding.

**Dependency:** the UK specification. If it is not published by the time you finish design, design against Peppol BIS Billing 3.0 and keep a list of assumptions.

## Phase 4: Build and test

- [ ] Configure software and Access Point; register Peppol IDs.
- [ ] Build integrations and mappings.
- [ ] Unit test with sample invoices, including credit notes and edge cases.
- [ ] Run validation testing; fix the [common errors](https://einvoices.uk/news/common-peppol-validation-errors).
- [ ] End-to-end test with friendly partners already on Peppol.
- [ ] Update procedures and train users.

## Phase 5: Pilot

- [ ] Go live with a small group of customers and suppliers.
- [ ] Monitor rejection rates, delivery failures and processing time.
- [ ] Fix issues before scaling.

## Phase 6: Roll out

- [ ] Onboard remaining partners in waves (see [supplier onboarding](https://einvoices.uk/news/supplier-onboarding-e-invoicing)).
- [ ] Retire old channels where possible, keeping fallbacks for out-of-scope documents.
- [ ] Hand over to business-as-usual owners with clear service levels.
- [ ] Complete well before April 2029.

## Workstreams across the phases

| Workstream | Key deliverables |
|---|---|
| Accounts receivable | Send process, customer IDs, exception handling ([AR guide](https://einvoices.uk/news/accounts-receivable-e-invoicing-uk)) |
| Accounts payable | Intake, matching, approvals, responses ([AP guide](https://einvoices.uk/news/accounts-payable-e-invoicing-uk)) |
| Master data | Clean customer and supplier records, VAT numbers, Peppol IDs |
| Technology | Connection, integrations, testing, archive |
| Trading partners | Segmentation, communications, onboarding |
| Tax | Scope, edge cases, VAT invoice compliance, tracking HMRC guidance |

## Risk register starters

| Risk | Mitigation |
|---|---|
| UK specification published late or differs from Peppol BIS Billing 3.0 | Design for change; keep mappings configurable; contract for updates |
| Vendor not ready | Get dated written commitments; identify an alternative Access Point |
| Poor master data | Start clean-up in phase 2 |
| Legacy systems cannot produce structured data | Replace, consolidate or route through an integration layer; track government engagement on legacy systems |
| Partners not ready | Segment and communicate early; keep a fallback channel |
| Resource clash with year-end or other projects | Plan phases around your finance calendar |

## What to do now

- [ ] Name a sponsor and a project lead this month.
- [ ] Start discovery: systems, volumes, vendors, data.
- [ ] Watch the Budget on 28 October 2026 and update the plan with any official milestones. We will update the [timeline](https://einvoices.uk/timeline).

## Frequently asked questions

### How long does an e-invoicing implementation take?

It depends on the number of systems, entities and trading partners. A small business on cloud software may need weeks; a group with several ERPs should plan a multi-phase project and start discovery now, ahead of April 2029.

### Who should own an e-invoicing project?

Usually finance, with a named sponsor, and IT, tax, procurement and credit control as workstream leads. E-invoicing touches AP, AR, master data and VAT, so it is not purely an IT project.

### Can we start before the UK specification is published?

Yes. Discovery, data clean-up, vendor questions and supplier segmentation do not depend on the final specification. Technical build should be confirmed against UK rules once published.

### What are the key official milestones?

The roadmap is due at Budget 2026 on 28 October 2026 and the mandate starts on April 2029. HMRC says the roadmap will set out the milestones in between.

---

How to cite: "E-invoicing implementation plan for UK finance teams", einvoices.uk, 20 October 2026, https://einvoices.uk/news/e-invoicing-project-plan-finance-teams

einvoices.uk is an independent publication and is not affiliated with HMRC or the UK Government. Nothing here is tax advice; check the sources and official GOV.UK guidance before acting.