Architecting an Automated Order-to-Cash Engine
Automating invoice grouping and delivery for large accounts with their own configuration requirements — without disrupting the default process used by everyone else.
A prominent, multi-site Australian equipment hire and logistics enterprise was experiencing significant operational load within its accounts receivable (AR) and financial administration functions. Processing thousands of monthly commercial transactions across various customer categories, sites, and purchase orders (POs), the business relied heavily on manual handling to generate and distribute the customised documents these accounts required.
Delivering the customised invoicing these accounts required through manual processing created administrative delays and operational risk as volumes grew.
The standard invoicing setup was able to meet around 80 percent of customer requirements out of the box. For the remaining accounts — typically larger customers trading across multiple branches or managing high volumes of purchase orders — the available invoicing options didn't line up with what they specifically needed.
Some customers wanted invoices consolidated differently — grouped by site, by site group, or across the whole customer account rather than by individual contract. Others needed purchase orders combined onto one invoice instead of split out separately. On the delivery side, requirements varied just as much: some accounts wanted a single PDF per email covering every invoice for the period, others needed multiple invoices attached individually within one email, and a few required data delivered as Excel, CSV, or XML rather than PDF at all.
A separate challenge was processing time. As transaction volumes grew, the invoice run began taking longer than the overnight processing window allowed for, putting timely delivery at risk regardless of formatting requirements. Delivering the customised invoicing these accounts required, within a reliable processing window, went beyond what could be handled through manual processing alone, and required purpose-built configuration across the reporting and distribution layers.
Engineering the delivery layer
Led by principal architect Ron Le Mesurier, Bilby Fusion conducted deep-dive discovery workshops to map the client's transactional data structures and the specific requirements of its larger accounts. Rather than introducing an isolated piece of software, the engineering approach centred on architecting a unified, automated data-delivery system purpose-built to support these account-specific requirements, acting as a single point of operational accountability.
Database query engineering
Filtered, parameter-driven data sets built so reporting could be tailored per account without impacting core system performance.
Crystal Reports engineering
Existing report templates re-engineered with new grouping parameters and formula fields, letting one report dynamically re-group and reformat per account.
Visual CUT configuration
The report distribution engine configured and extended to handle bursting, formatting, and multi-channel delivery for each account's requirements.
ERP parameter configuration
Additional parameters added within the ERP so account-level settings drive the automated process, rather than requiring manual selection each run.
Email queue optimisation
Background services configured to monitor, throttle, and process outgoing messages reliably, with automatic recovery from delivery disruption.
Delivery throttling controls
Outgoing email traffic paced to avoid triggering spam protections or overloading mail servers.
A scalable, per-account distribution system
Bilby Fusion engineered and deployed a scalable, automated invoice and statement distribution system tailored to the business's mix of standard and custom-configured accounts.
Per-account grouping & formatting
Each large account's invoice grouping and document format configured and automated individually, while standard accounts stay on the default process.
Flexible delivery formats
Support for single consolidated PDFs, multiple individually attached PDFs, and structured Excel, CSV, or XML exports, selected per account.
Automated, personalised email
Emails generated with account-specific subject lines, message content, and attachments matched automatically to each account's configuration.
Scheduled, unattended processing
Nightly, weekly, and monthly automated runs with built-in recovery if a background process fails.
Delivery visibility
Logging and reporting on sent, undeliverable, and pending messages for fast issue resolution.
Getting invoices reliably into inboxes
Generating the right invoice in the right format was only half the job — delivering it reliably required its own infrastructure build, separate from the reporting and grouping logic.
Email authentication setup
SPF, DKIM, and DMARC records configured to authenticate outgoing mail and keep delivery out of spam folders.
SendGrid SMTP relay
SendGrid configured as the dedicated SMTP relay handling all outgoing automated invoice traffic.
Delivery queue service
A background Windows service built to monitor, send, and retry outgoing messages independently of the reporting engine.
Bounce & failure handling
Failed and undeliverable messages automatically routed to a separate folder for review, with automatic retry logic before failure.
Delivery reporting
Visibility into sent, pending, and failed messages, so delivery issues could be caught and resolved quickly.
Business Outcomes
Moving from manual, one-size-fits-all invoice handling to an automated system that meets each account's requirements without extra administrative effort.
- Large accounts receive invoices in the exact grouping and format they require, generated automatically
- Administrative staff no longer manually rework invoices to meet individual account preferences
- New large accounts with custom requirements onboarded by configuration, not a new manual process
- Reduced processing time and lower risk of manual errors across standard and custom-configured accounts
- A scalable framework supporting continued growth across branches and account types
Not every legacy system needs to be replaced. ERP platforms evolve at different speeds, and vendors regularly leapfrog each other on features — a platform that leads the market today may fall behind in three years, only for the gap to close again as the vendor catches up. Chasing the newest feature set with a full platform replacement carries real cost: licensing, migration risk, retraining, and disruption to daily operations, often for capability the business may only need in a specific, narrow area.
In this case, the right answer wasn't replacement — it was targeted engineering around the existing platform to deliver exactly what these accounts needed, without the cost, risk, or disruption of a wholesale system change. Total cost of ownership and business continuity were weighed alongside capability, and extending the existing investment was the more sound decision.