Blog
When sending mail by API saves your finance team a day a week
Manual post from an accounts team eats 4-8 hours a week per person. An API integration turns it into seconds and recovers the time. Here's what the pattern looks like in practice.
Most finance teams spend a surprising amount of time doing manual mail: printing statements, folding invoices, licking stamps, waiting at the post office. It's not strategic work, it's not even thinking work — it's a physical queue between "the accounting system says send this" and "the customer has a letter in their hand." An API can remove that queue entirely.
The basic pattern
Here's what a typical invoicing flow looks like when someone integrates Intelliprint into their accounting stack:
- Invoice is generated in the accounting system (Xero, Sage, QuickBooks, custom in-house).
- A webhook or status change triggers a call to the Intelliprint API.
- The API receives the invoice PDF and the customer address, prints and posts it same-day from the UK.
- A webhook sends status events back — dispatched, delivered, returned — which your accounting system stores against the invoice record.
Total human time per invoice: zero. Total elapsed time from invoice creation to post: seconds. Compare that to the typical pattern of an accounts clerk batching invoices for a weekly print-and-post run, and you've recovered 4-8 hours a week per person.
Hello-world integration
The simplest API call posts a single letter with inline HTML content — no PDF required:
POST /v1/prints with multipart form data: type=letter, content=<your HTML>, recipients=[{name, address_line_1, city, postcode}], and confirmed=true to commit for printing. Bearer token auth. That's the whole integration — everything else is optional.
For finance teams, the usual pattern is to pass a PDF of the invoice (generated by your accounting system) instead of inline HTML. Same endpoint, just include a file part in the multipart request.
Webhooks close the loop
Sending the letter is only half the job — knowing what happened to it matters too, especially for accounts receivable workflows where "did the customer actually receive the demand?" is a real question. Intelliprint ships print job lifecycle events through Svix-powered webhooks: confirmed, dispatched, delivered, returned. Signed payloads, retries on failure, event replay. You subscribe your own endpoint and update the invoice record in your system on each event.
The no-code fallback
If your accounting system can talk to Zapier or n8n — most do — you can get 80% of the way there with no code at all. Our Zapier app handles letter triggers from 8,000+ connected apps. Our n8n community node (n8n-nodes-intelliprint) covers letters and postcards with full API fidelity. A finance analyst can wire up "Xero invoice marked Sent → Intelliprint letter posted" in 15 minutes through either.
The actual time reclaimed
Talk to finance teams who've moved from manual posting to API-triggered mail and the consistent answer is around a day a week reclaimed per person doing the work. That's not the stamp saving. That's the queue-at-the-post-office, the printer-jammed-again, the Friday-afternoon-invoice-run disappearing — and a person doing work worth their salary instead.