# The invoice pipeline that ended the Friday admin block

> A service company spent every Friday afternoon typing invoices from timesheets, chasing PO numbers, and re-sending the ones that bounced. The pipeline that replaced it runs Friday morning, unattended.

The manual process was four disconnected steps wearing a calendar reminder: export timesheets into a spreadsheet, type the invoice lines into the invoicing tool, hunt the right PO number and billing contact per client, send, and two weeks later discover three invoices missing or wrong. Each step was small; the compound cost was a half-day of senior time weekly and a two-week payment delay baked in.

The pipeline is deliberately unglamorous: a scheduled job pulls approved timesheets, builds invoice drafts per client with the right PO and contact pulled from a small mapping table, pushes them through the invoicing API, and posts a digest — what went out, what is blocked on what — to one channel. The only human step left is a two-minute review of flagged edge cases: a new client without a PO on file, an unusual amount, a missing contact.

## The pipeline is the boring parts, sequenced

Trigger on schedule, not on memory. Pull timesheets with their approval state — unapproved hours get flagged, not invoiced. Resolve the per-client quirks in a mapping table (PO, contact, payment terms, VAT handling) instead of encoding them in an employee. Draft, review flag, send, digest — each step logged so a failed run says what stopped.

## Design for the exceptions, not the happy path

The 90% of invoices that are routine should need nobody; the value is in the flagging, not the automation. New client without a PO? Flag, do not guess. Amount 3× the client's average? Flag. Customer record missing a billing email? Flag with the fix being one form field — so the exception fixes the data, not just the invoice.

## What actually changed for the business

Invoices go out Friday morning instead of Friday evening — and invoices sent two weeks earlier get paid two weeks earlier. The admin Friday became a review-and-coffee task. The unglamorous part is the durable part: no AI, no cleverness, just three systems connected and the exceptions routed to a human.

## What to take away

- Four manual steps became one scheduled job: pull, draft, flag, send, digest.
- Design for exceptions — the automation handles routine, humans handle flagged edge cases.
- Invoices sent two weeks earlier get paid two weeks earlier.
- No AI needed — three connected systems and routed exceptions beat cleverness.

## Tags

Automation, Invoicing, Case study, Ops

## We build this for clients

https://dfieldsolutions.com/en/services/ai-automation

## More from the lab

- https://dfieldsolutions.com/en/lab/whatsapp-order-pipeline.md — From WhatsApp chaos to a real order pipeline
- https://dfieldsolutions.com/en/lab/n8n-self-hosted-vs-zapier.md — Self-hosted n8n or Zapier — where the bill actually differs
- https://dfieldsolutions.com/en/lab/booking-pipeline.md — Enquiry to booked call, without the inbox
- https://dfieldsolutions.com/en/lab/mcp-servers-production.md — MCP servers in production, not in the demo

---

Source: https://dfieldsolutions.com/en/lab/invoice-pipeline-automation
DField Solutions — Dunakeszi, Hungary — dezso@dfieldsolutions.com
Booking: see https://dfieldsolutions.com/en/contact