Every invoice you send is someone else's AP problem.
Send structured eInvoices through the Peppol network or PDFs through email. Chase payments on policy, not memory. Match bank feed transactions against outstanding invoices automatically. Built for Australian and New Zealand finance teams on Xero, MYOB, Abel, Costar and X2 Framework.
Your invoice just arrived in someone else's inbox.
If you've read the AP page, you already know the journey of a PDF invoice through a finance team. Now flip the camera. Your invoice – the one you need paid – is going through exactly that process, right now, at your customer's end.
Dear finance team,
Your invoice arrived in our AP inbox at 9:47 this morning, along with thirty-one others.
We downloaded the PDF, printed a copy, and date-stamped it. Then we forwarded it to the branch manager who needs to code it, who is currently in back-to-back meetings until Friday. On Monday, he'll print it again, code it in ballpoint, scan it, and send it back.
Our AP officer will key the data into our accounting system on Tuesday. That's day eight, by my count.
You've got 30-day payment terms on your invoice. By the time we've verified it, matched it against the PO, and queued it for the next payment run, we're looking at day 47.
We're sorry about that. It isn't personal. It's what our AP workflow does to every PDF invoice we receive.
The AR problem is an AP problem – theirs, not yours.
Every invoice you send has to survive somebody else's handling tax before it becomes cash in your account. The way it's sent determines how fast that happens. A PDF in an email lands in manual processing. A structured Peppol eInvoice lands in the ledger.
The faster your invoice becomes something machine-readable in their system, the faster it gets approved, matched and paid.
- Angle 01Your DSO is partly a function of the format you send in.
- Angle 02Manual AP workflows compound delays. You're at the end of that chain.
- Angle 03Structured invoicing compresses the handling window from weeks to minutes.
Money not collected is money not working.
Late payments aren't just an annoyance. They consume working capital, force borrowing, and starve growth. The ANZ numbers are stark, and the Peppol mandate offers a structural path to shortening the cycle.
Send. Chase. Reconcile. Report.
Acume's AR workflow sits on top of your accounting system, automating the handling layer between invoice generation and cash reconciliation. Five steps. One platform. Every transaction tracked.
Send invoices via the Peppol network as structured eInvoices, or as PDFs through branded email templates. High-volume batch dispatch for billing runs. Customer preference routing so each customer gets your invoice in the format their AP system handles best.
Peppol invoices return delivery confirmation through the network – you know the moment your invoice lands in the recipient's system. PDF invoices get email tracking with opened/unopened status. No more guessing whether it arrived.
Configurable dunning logic chases payments on policy, not on memory. Set escalation rules by customer, invoice size, or days overdue. Reminders go out automatically. Human intervention happens by exception, not by default.
Bank feed integration pulls incoming payments directly. Acume matches them against outstanding invoices automatically – by reference, amount, customer ID or fuzzy match. Partial payments, overpayments and multi-invoice remittances handled without manual allocation.
Real-time DSO, aged debtors, collection rate by customer, and cash flow forecasting. Finance leadership sees where the cash is sitting, at any time, without waiting for the month-end pack. Multi-entity consolidation for group finance teams.
The same network. The other direction.
If you're going to receive Peppol eInvoices, you may as well send them too.
Peppol is bidirectional. The same Access Point that pulls supplier eInvoices into your AP ledger can push your customer invoices out to their AP ledger – without rebuilding your AR stack or licensing a separate platform.
The commercial gain is real. Your invoice arrives in your customer's system as structured data, not as a PDF attachment that needs manual processing. It can be coded, routed and scheduled for payment within minutes of receipt, not days.
If your customer is a New Zealand government agency processing 2,000+ invoices a year, from January 2026 they're on a five-business-day payment target for Peppol invoices. You should be sending through Peppol, not PDF.
Read the eInvoicing page →Public accreditations. Real customers.
Built into the systems finance teams trust.
Every trust signal on this page is independently verifiable. The Peppol registration is public. The authority accreditations are on the ATO and MBIE service provider registers. The case study is on a government site.
- PeppolApproved Provider on the Peppol Service Provider register.
- ATOAccredited Australian Peppol Access Point.
- MBIEAccredited New Zealand Peppol Access Point.
- NZ GovFeatured case study on einvoicing.govt.nz.
- IntegrationsXero, MYOB, Abel, Costar, X2 Framework.
Acume has transformed the way we manage accounts payable. We have real-time insight into every invoice, approval workflows we can actually trust, and the accuracy we need to make confident financial decisions.
Get paid, on your stack.
A live demo on your AR workflow. We'll show you how structured dispatch, bank feed reconciliation and automated chase logic compress your cash cycle on your actual customers and your actual accounting platform.