Xcelerate
Menu
Get in touch
All articles on council finance and operations

Council finance and operations

Council invoice approval software from receipt to payment

Trace an eInvoice through order matching, a disputed delivery and delegated approval. Give suppliers a practical council accounts payable demonstration.

A reserve supervisor checks invoice lines against completed work on screen.
AI-generated editorial image.

A contractor invoices a council for mowing three reserves. The reserve supervisor confirms two visits and queries the third. A useful invoice approval workflow can show which line is disputed, who can resolve it and what finance has actually posted. It also gives the contractor a consistent answer when they ring. Use this ordinary disagreement as the centre of an accounts payable software brief.

Where does an invoice enter the workflow?

List each channel suppliers use and the identifier that travels with the document. Inland Revenue describes eInvoicing as the exchange of invoice data between financial systems through Peppol. An emailed PDF needs a different intake path. Ask the software supplier to show where these channels converge and which fields the team must validate in each.

For the mowing example, match the incoming invoice to the supplier record and purchase order. Keep supplier identity, invoice number, GST treatment, line quantities and delivery location visible to the reviewer. If a supplier emails a copy after sending an eInvoice, staff should be able to link it to the first record and explain why there is one payment request.

Who can clear a disputed line?

Separate evidence of delivery from authority to spend. A parks supervisor might confirm work on site while a budget holder has the financial delegation. Ask both people what they need to see before acting. NZ Government Procurement's contract administration guidance covers checking invoices, preconditions and approvals. Each council can map these activities to its own delegations and supplier terms.

Show a disputed line to the contractor through the council's agreed communication channel. Record the query, supporting evidence and next action in the invoice history. Finance should set the treatment of undisputed amounts. The software should make that choice explicit and preserve links to any replacement invoice or credit that follows.

What happens when an approver is away?

Try a fictional week in which the usual approver is away and a relief manager covers only part of their role. Give the substitute a start date, end date and approval limit. A queued invoice above that limit should reach a named escalation point with its previous reviews intact.

Also simulate an approval arriving just as a supplier sends a correction. Staff need to tell which version was authorised and whether the posting has already occurred. Ask for a clear route back to finance when a correction affects a closed accounting period.

Set an acceptance test finance can repeat

Have the supplier replay the same batch after a simulated interruption. Ask finance to match workflow references against postings in its ledger. One invoice sent twice should result in one payable item, while an unmatched invoice should remain visible with a reason and an owner. Finish by exporting the history for the disputed mowing visit. Someone unfamiliar with the purchase should be able to reconstruct who confirmed the work, who authorised the amount and how the contractor's query ended.

Sources and further reading