Your ERP already made the invoice. Why are you the one emailing it?

Here's a scene from more Ross shops than you'd think. The ERP generates the invoices — good, clean, correct invoices. And then a person opens each one, exports it, looks up the customer's email, attaches the PDF, and sends it. Then the next one. Then the purchase orders. Then the statements. Every day.

When I describe this out loud, people who live it laugh the specific laugh of someone who's been caught. "We know CFB can do more," they'll say, "but nobody wants to touch it." That's the real situation: the system could send its own paperwork, but the tool that does it has a reputation as a black box, so instead a human does the black box's job by hand.

The thesis of this post is short. Document delivery is a solved problem in modern software and an unsolved daily chore in a lot of ERP shops. You can automate it without ripping anything out — and the newest way to do it skips the black box entirely.

What CFB actually is

CFB is the Crystal Forms Bundle — the set of Crystal Reports-based forms in Ross for your standard business paperwork: invoices, sales orders, credit notes, purchase orders, and so on. It's genuinely good at the thing it's named for, which is generating the forms.

What it was never graceful at is delivery. Getting each generated document to the right recipient, automatically, on a schedule, without a person in the loop — that's the gap. And because getting CFB configured could be finicky and opaque, it earned its black-box reputation honestly, which is exactly why so many shops leave the delivery half to a human instead.

What "automated delivery" actually means

The good news is that the delivery problem is not hard once you decide to solve it properly. I know because I built exactly this at Aptean — automation on top of CFB that handled the whole delivery lifecycle — and the design comes down to two decisions.

Drive delivery off the record on file. Every customer, vendor, and payee in Ross already carries the contact where their documents are supposed to go. So the automation sends each document to the contact on its own record — the invoice to the customer contact, the PO to the vendor contact, the remittance to the payee. No separate list to maintain and fall out of date. The system of record stays the single source of truth for who-gets-what, which is where that truth belongs.

Treat delivery as more than email. Sending the PDF is only half the job. The other half is being able to prove, later, what went out and when. So alongside emailing each document, the automation files a copy to SharePoint automatically — a durable, searchable archive of everything sent, organized instead of scattered across someone's Sent folder. That archive earns its keep the first time there's a dispute, an audit, or a "we never got that invoice" phone call.

Put together, it covers the full spread of everyday paperwork — invoices, sales orders, credit notes, purchase orders, ACH remittances — going out consistently, to the right party, filed as it goes.

The quiet wins

The benefits of this kind of automation stack up in the way plain automation tends to, and a few of them don't show up until you've lived with it.

It builds its own audit trail. Because every outbound document is archived as it's sent, nobody has to remember to keep a copy — the record assembles itself.

It makes the wrong-invoice-to-the-wrong-customer mistake much harder, because the recipient comes from the record, not from memory at 4:45 on a Friday.

And it gives AP and AR their time back. The people doing the manual sending are usually the ones who understand the money, and attaching PDFs is the least valuable possible use of that understanding. Handing the chore to the system isn't a headcount play — it's letting the people who get the numbers spend their hours on the numbers.

The modern path: no black box required

I'm now building a modern successor to that original automation, and this is the part I'm genuinely excited about. The old approach was shaped by its era — tied to EMF and Crystal, with templates that were painful to change and an interface that assumed you already knew its secrets.

The new package keeps the good idea — the ERP delivers and archives its own documents automatically — and rebuilds everything around it with modern tooling: no EMF, cleaner and editable templates, and an interface a person can actually use without training. It's built to be SaaS-friendly, and it can bypass the old CFB black box entirely when a shop wants a clean break instead of another layer on top.

Automate on top, or replace?

If you're deciding what to do about your own document delivery, the honest guide is short. If your CFB setup works and you just need the delivery half automated, automating on top of it is the fast, low-risk win. If CFB itself is the thing causing you pain — unmaintainable, opaque, nobody left who understands it — then the modern package that skips it is the better long game. Either way, the manual send ritual doesn't need to be part of your week.

The bottom line

Your ERP already made the invoice. It can send it, too — to the right contact, filed to SharePoint, without a person in the loop. I've built this once inside the old stack and I'm building the version that doesn't need the black box at all. If manually emailing paperwork is quietly eating your AP team's afternoons, it's one of the cheaper problems you'll ever fix.

Still emailing your ERP's paperwork by hand — or fighting CFB to stop doing it? I've solved this before and I'm building a better version. Let's talk →. Related: rebuilding EMF processes in something you can maintain.