Desk by Desk Automation MEL

Catalogue / Finance

Finance automations: accounts payable, invoice chasing and reconciliation

Four finance processes that eat bookkeeper and owner time in most Melbourne small businesses, with the before and after steps and the approvals that stay human.

FIN-01

Supplier invoices into Xero or MYOB

Supplier invoices arrive as PDF attachments in an accounts inbox, sometimes as links to a supplier portal, occasionally as a photo of a paper docket. Someone has to get each one into the accounting system correctly.

Before

  1. Open the accounts inbox and find new invoices among the statements and marketing emails
  2. Download each PDF
  3. Create a bill in Xero or MYOB and type the supplier, date, due date, invoice number and amounts
  4. Choose the account code and tracking category, check GST
  5. Attach the PDF
  6. Match to a purchase order if there is one
  7. File or delete the email

After

  1. New invoice emails are picked out automatically; statements and promotions are ignored
  2. The PDF is read and a draft bill is created with supplier, dates, number, line amounts and GST
  3. Account codes are suggested from how you coded that supplier before
  4. The PDF is attached and the PO matched where one exists
  5. Anything unusual is flagged: a new supplier, a price change, a duplicate invoice number, a changed bank account
  6. The draft waits in an approval list
A person still approves: each bill before it is approved for payment, and every flagged exception, especially changed bank details, which are a common invoice-fraud pattern.

Watch for: suppliers who send several invoices in one PDF, and handwritten dockets. Both can be handled, but they are worth testing early.

FIN-02

Chasing overdue invoices

Most small businesses know chasing helps and still don’t do it consistently, because it is awkward and there is always something more urgent.

Before

  1. Run the aged receivables report, usually when cash feels tight
  2. Decide who to chase
  3. Find the invoice and the contact
  4. Write an email, worrying about the tone
  5. Forget to follow up the follow-up

After

  1. Each morning, overdue invoices are checked against your chasing schedule (for example 3, 14 and 30 days overdue)
  2. A reminder is drafted for each, in your tone, with the invoice attached and a payment link if you use one
  3. The tone firms up with each step, using wording you have approved
  4. Customers on a do-not-chase list, or with a note on their account, are skipped and flagged
  5. Replies such as “paid yesterday” or “we dispute this” are recognised and routed to a person
A person still approves: the first run of each template; anything past the final reminder; any dispute or payment-plan request. Many businesses let the first friendly reminder go automatically once they are comfortable with it.
FIN-03

Bank reconciliation suggestions

Bank feeds already do some matching. The time goes on the lines that don’t match: part payments, combined payments, unexplained fees.

Before

  1. Work through the bank feed line by line
  2. Search for the invoice or bill for each unmatched line
  3. Guess at the odd ones and leave a note to ask someone
  4. Chase the unexplained items at month end

After

  1. Suggested matches are prepared for unmatched lines, including part and combined payments, with the reasoning shown
  2. Remaining unexplained lines are listed with what is known about each
  3. A short message is drafted to whoever can explain each one
A person still approves: every reconciliation. This automation suggests; it never reconciles on its own.
FIN-04

Staff expense receipts

Receipts are the classic month-end chase: lost slips, photos buried in phones, card transactions with no explanation.

Before

  1. Staff keep receipts, or don’t
  2. Finance emails everyone at month end
  3. Receipts are matched to card transactions by hand
  4. Coding is guessed for the ones without notes

After

  1. Staff forward a receipt photo or email to one address, or send it in chat
  2. An expense is drafted with amount, GST, supplier and suggested coding, and matched to the card line
  3. Card transactions with no receipt after a set number of days trigger a reminder to the cardholder
  4. Anything outside your expense policy is flagged
A person still approves: the manager’s sign-off for each claim, and every out-of-policy item.

A note on fraud

Invoice and payment-redirection scams target small businesses through fake invoices and “we’ve changed our bank details” emails. Good finance automation helps here: it compares every invoice against what it has seen from that supplier before and flags changed bank details loudly. It must never update supplier bank details on its own. The ACSC’s guidance at cyber.gov.au is worth sharing with whoever approves payments.

Is one of these your bottleneck?

Book 15 minutes and bring the code. We’ll tell you how it would work with your systems.

Book a call