Central Billing for Dealer Networks and National Accounts

A fleet manager at a large national account calls your operations team. One of their vehicles was serviced at a dealer location last month. The invoice they’ve received doesn’t match what they expected, with different line items and different pricing than the agreed rate. They want to know: which dealer raised the job, under which service agreement, on what date, and how the pricing was calculated.

Your operations coordinator starts digging. The dealer entered the job details in a spreadsheet and sent through an email summary at the end of the month. The pricing was applied manually, based on a rate card that may or may not be current. The invoice was generated from a template, reviewed by someone, and sent out. None of this is recorded in a single system. The answer to the fleet manager’s question will take the better part of a morning to reconstruct.

Meanwhile, the same query is sitting unresolved in the national account customer’s AP queue. Their team can’t match the invoice to a purchase order. The payment run is on hold. The dealer is waiting on reimbursement they’re owed.

This is the billing problem that’s specific to dealer-network businesses, and it doesn’t get much attention in the AP automation conversation, because most AP automation content is written for businesses processing their own supplier invoices, not businesses running billing infrastructure for a network of dealers servicing national account customers.

The two problems look similar from the outside, invoices, approvals, and accounting systems, but the architecture is fundamentally different. Standard AP automation handles inbound invoices from suppliers. Central billing handles outbound invoices to customers, triggered by jobs entered by a distributed network of dealers or service partners. The gap between the two is where reconciliation disputes, billing errors, and audit gaps accumulate.

How Decentralised Billing Creates the Problem

The dealer-network billing problem has a structural cause. Jobs are completed at the dealer level by technicians, service staff, and branch operators who have limited connection to head office systems. The billing that flows from those jobs has to travel upward: a record of what was done, at what rate, for which national account customer, under which agreement. Without a central system governing that flow, the record is informal.

In practice, this typically means one of three informal arrangements:

• Dealers submit monthly job summaries by email or spreadsheet. The operations team or billing coordinator at the central organisation compiles the billing run, applies the relevant pricing, and generates invoices. Every step is manual, and every hand-off is a reconciliation risk.
• Dealers raise their own invoices to the national account customer and submit copies to the central organisation for reimbursement. The central organisation can’t easily verify what was charged, when, or under what terms until the national account customer files a dispute.
• A hybrid: some dealers use email, some use a portal, some call it in. The central organisation maintains a spreadsheet of what’s been billed and what’s outstanding. The national account customer has no self-service visibility into their billing history.

Each of these arrangements creates the same downstream problems:

• Reconciliation disputes are slow to resolve.
• The national account customer cannot self-serve their invoice history, service records, or billing totals by location. Every query requires manual investigation.
• Pricing errors are systemic. Manual application of rate cards leads to rate drift, exceptions aren’t captured, and corrections require retrospective credit notes.
• Audit gaps are structural. There is no single source of truth for what was billed, when, to whom, and under which agreement. The audit trail is distributed across dealer inboxes, billing coordinators’ spreadsheets, and accounting system exports.
• Dealer reimbursement is delayed. Dealers can’t see what’s been processed, what’s been approved, and when payment will arrive. The lag creates friction in the dealer relationship and, in some cases, causes dealers to avoid taking national account jobs altogether.

The root cause in all cases is the same: the job record, the billing record, and the accounting record exist in separate places, maintained by different people, with no automated connection between them. A central billing portal changes the architecture not by adding a step to the process, but by making the job entry, billing generation, and outbound invoice delivery happen within a single governed system.

What a Central Billing Portal Changes: The Three Flows

A central billing portal doesn’t just digitise the existing process. It changes the sequence of events; who enters the record, when, and what gets generated automatically from that entry.

There are three core flows. Acume sits at the centre, connected to the accounting system on one side and the CBL portal on the other, and the client’s team performs a release step before documents go out:

Flow 1: Dealer job entry — Flow 2: Outbound PO or credit to dealer — Flow 3: Invoice to national account

Who Dealer / service partner – at the point of job completion — Who Client’s central billing team – reviews portal transactions in Acume and releases — Who Client’s central billing team – releases via Acume’s outbound invoice workflow

What Enters job details into the CBL portal: customer, service type, quantity, location, date — What Portal transaction flows into Acume’s outbound PO or customer credit workflow; team reviews and releases — What Portal transaction flows into Acume’s outbound customer invoice workflow; team reviews and releases

Output Transaction record created in the portal – timestamped, tied to applicable pricing, visible to the central organisation’s team in Acume — Output PO or credit note issued to the dealer – their confirmation of recorded job and committed reimbursement, posted via Acume — Output PDF invoice or Peppol eInvoice delivered to the national account customer – matched to the portal job record, auditable on both sides

Flow 1: Dealer Job Entry

The dealer completes a job; a tyre fitting, a vehicle service, equipment maintenance, a contracted delivery, and enters the details into the CBL portal. The portal captures the relevant fields: customer identity, job type, quantity or scope, location, date, and any applicable service agreement reference.

This is the moment the billing record is created. Not reconstructed from an email at the end of the month, created at the point of job completion by the person who did the work. The entry is timestamped, tied to the applicable pricing agreement, and immediately visible to the central organisation’s billing team inside Acume.

For dealers, this replaces the end-of-month spreadsheet summary. For the central organisation, the billing run starts from structured, real-time portal data, not compiled summaries with embedded manual errors.

Flow 2: Outbound PO or Credit to the Dealer

Once a portal transaction is entered, it flows into Acume’s outbound workflow queue, either as a purchase order (where the central organisation commits to purchasing the job from the dealer) or as a customer credit (where they credit the dealer for work completed under a self-billing arrangement).

The client’s central billing team reviews the transaction in Acume and releases it. The release step is deliberate; it’s the governance point where pricing, quantities, and applicable agreements are confirmed before the document goes to the dealer. The pricing itself comes from Acume’s configuration, which is synced from the accounting system and the agreed rate structures, not manually applied by the billing coordinator.

The dealer receives the PO or credit note once released. They can see what’s been recorded and what they’re owed. They don’t need to chase a monthly summary; the document comes through Acume once the central team has released it, and the posting flows back into the accounting system automatically.

Flow 3: Outbound Invoice to the National Account Customer

The third flow mirrors the second, but in the direction of the national account customer. The portal transaction flows into Acume’s outbound customer invoice workflow. The client’s central billing team reviews and releases the invoice from within Acume.

The invoice matches the portal job record exactly. The national account customer’s AP team receives a document they can match directly to their purchase order or service agreement, with a clear reference to the job, the dealer location, the date, and the rate applied. There’s no template invoice that may or may not match what was agreed, and no billing dispute from a discrepancy between what the dealer submitted and what the invoice shows.

If the national account customer is registered on the Peppol network, Acume delivers the invoice as a structured eInvoice directly into their AP platform. If they’re not yet Peppol-ready, it’s delivered as a PDF. The same job record, the same billing data, two delivery formats, one workflow.

Outbound Delivery: eInvoicing and PDF, and Why Both Matter

Not all national account customers are at the same point in their eInvoicing adoption. Fleet operators, major hire companies, and government departments, the kinds of customers that anchor national account programs, are at different stages of Peppol readiness. Some have implemented Peppol-compliant AP platforms and actively prefer structured eInvoices. Others are still processing PDFs.

For the central billing operator, this means outbound invoice delivery needs to handle both formats natively, not as a workaround, but as part of the standard billing workflow.

Peppol eInvoice delivery transmits the invoice directly into the national account customer’s AP platform as structured, machine-readable data. There’s no email attachment to download, no OCR extraction step, and no manual matching. The invoice enters their workflow the moment it’s generated by the portal, with all line-item details, pricing, and reference data intact. For national account customers who have implemented Peppol-compliant AP automation, this eliminates the entire inbound invoice-handling step for that supplier relationship.

PDF delivery handles the customers who aren’t yet Peppol-ready. The portal generates a structured, professional PDF invoice from the same billing record, formatted to the customer’s preferred layout where applicable, delivered by email or through a customer portal. The billing data is the same; the format is different.

Offering both isn’t optional for a billing operator whose customer base includes both Peppol-ready and PDF-dependent relationships. It’s the only way to deliver a consistent billing experience across a national account portfolio where customer readiness varies.

The 2026 mandate context: Australia’s eInvoicing mandate is expanding on a known trajectory. Commonwealth agencies are already required to receive Peppol eInvoices. Broader B2B adoption is accelerating. For central billing operators whose national account customers include government departments or large corporate accounts, the question isn’t whether Peppol delivery will be required; it’s when. Building Peppol-native outbound billing capability now positions the operator ahead of that requirement rather than scrambling to meet it when a customer demands it.

How It Connects to Xero, MYOB, and Your Accounting System

The architecture has three connected layers, and understanding how they relate is key to getting the implementation right.

The accounting system, Xero, MYOB, or your ERP, is the source of financial truth. Acume connects to it first: suppliers, customers, GL codes, and tax logic are pulled from the accounting system into Acume during setup. This means Acume already knows your chart of accounts, your supplier list, and your customer list before any billing workflow begins.

The CBL portal connects to Acume. Dealers enter jobs in the portal; those transactions flow into Acume’s outbound workflow queues, the PO or credit queue for dealer reimbursement, and the customer invoice queue for national account billing. The portal doesn’t talk directly to the accounting system and doesn’t post anything on its own.

Acume is the release point. The client’s central billing team reviews transactions in Acume and releases them, the PO or credit to the dealer, the invoice to the national account customer. Once released, Acume handles the delivery (Peppol eInvoice or PDF), and the posting flows back to the accounting system automatically.

In practice, this means:

• Supplier and customer data stays current because Acume syncs from the accounting system, no parallel list to maintain in the portal.
• Every document, dealer PO, dealer credit, and national account invoice originates in Acume and is posted back to Acume. The accounting system sees clean, approved transactions, not raw portal entries.
• The client’s team has one place to oversee the central billing workflow: Acume. The portal is where dealers enter jobs; Acume is where the central team manages, reviews, and releases everything.
• GL codes, tax treatment, and entity allocation are configured in Acume against the accounting system’s chart of accounts. The financial controller sees correctly coded postings from the outset.

For multi-entity businesses, Acume handles entity-specific routing. Jobs entered in the portal can be allocated to the correct entity in Acume before release; accounting system postings go to the correct entity automatically.

For businesses on Xero or MYOB, the accounting system connection is API-based and takes minutes to establish. The configuration work, mapping the CBL portal’s job types to Acume’s billing workflows, setting up the outbound document templates, and aligning the pricing rules, is where the implementation effort actually lives.

Ready to Talk About Your Billing Architecture?

If your business manages billing for dealer or franchise networks with national account customers, the central billing portal conversation starts with your specific commercial structure, the number of dealers, the national account relationships, the pricing agreements in place, and the accounting systems involved.

Acume works with ANZ businesses across automotive, equipment distribution, and service network verticals to implement central billing workflows, connecting the CBL portal, Acume’s outbound document workflows, and the client’s accounting system in a single governed process.

Frequently Asked Questions