Payroll and bookkeeping support in Castlereagh

Professional working at a laptop in an office

Bookkeeping support in Castlereagh can help make a supplier’s bank-detail change visible before a payment is released. An invoice may look familiar while the account details have changed. A tidy ledger does not establish that the new payment destination is genuine.

365 Bookkeeping & BAS is based in Penrith and supports businesses through agreed cloud workflows. This guide gives Castlereagh business owners a practical verification and approval process for supplier-detail changes, with a clear handover between bookkeeping and the person releasing money.

Do not treat a changed invoice as verified instructions

Business email compromise can involve altered payment details in what appears to be a legitimate business message. An expected invoice, familiar logo or ongoing email thread should not be the only evidence used to approve a different bank account.

Separate three decisions: whether the bill is valid, whether the account change is verified and whether the payment is approved. A real bill can still carry an unverified payment destination. Keep the change on hold until the business completes its agreed check.

Urgency should be visible as an exception, not a reason to remove the check. Explain that the business is verifying new instructions and record who is responsible for resolving the question.

1. Flag the change before editing the supplier record

Ask the person processing invoices to compare the new instructions with the approved supplier record. If they differ, record a change request rather than silently replacing the stored details.

Include the supplier reference, date received, affected invoices and the person who raised the request. Keep the original document in the controlled records. Avoid putting full bank details in a widely shared exception list when a restricted source reference will do.

Also inspect invoices already waiting for payment. Updating a supplier record does not prove that an existing payment proposal contains the intended details. The proposed payment needs its own final review.

2. Verify through a contact route already trusted

Use a previously verified contact method to confirm the change. Do not rely on a new phone number or link supplied in the same message requesting the change. Record how the contact route was established and who confirmed the instructions.

Where the usual contact is unavailable, leave the item unresolved and escalate it to the business’s authorised decision-maker. A reply from the same email account does not independently resolve the concern if that account may be compromised.

Keep the evidence factual. “Called the previously recorded supplier contact on the date shown in the verification record” is more useful than a bare “checked” tick. Do not record a verification that no one actually performed.

3. Approve the change separately from the payment

Once verification is complete, an authorised person should approve the supplier-record change under the business’s procedure. Record the effective date and retain the earlier version or an audit reference.

Then prepare the payment proposal and check the actual destination and amount against the verified instruction. The payment approver should be able to see that bank details changed, when they were verified and which proposal is being approved.

A fictional supplier-change example

A Castlereagh business receives a $1,240 invoice from an established supplier. The invoice asks for payment into a different account. The bookkeeper records a change request and leaves that payment outside the release batch while the owner verifies the instructions through a previously trusted contact route.

The other approved invoices total $2,760. Excluding the unverified $1,240 item gives a $2,760 release proposal, rather than the $4,000 total that would include it: $2,760 + $1,240 = $4,000.

This is a fictional control example, not permission to ignore agreed payment terms. The business must communicate and resolve the exception promptly, then separately approve any later release.

4. Keep a clear exception and release record

Record the item’s current status: awaiting independent verification, verified but awaiting approval, approved for the next batch or resolved without a payment change. Name an owner and the next action.

After a payment is released, retain its bank reference with the approved proposal. If the bank reports a rejected or returned payment, inspect the actual status before sending it again. Do not assume an unsuccessful-looking screen means that no money moved.

If money may have gone to a fraudulent account, contact the bank promptly and follow the relevant reporting guidance. Preserve the original messages and payment references. Do not continue transferring funds while trying to resolve an uncertain transaction.

Bookkeeping support in Castlereagh: agree the boundaries

When arranging payroll and bookkeeping support in Castlereagh, establish who can request a bank-detail change, who verifies it, who edits the record and who releases money. A small team can document these steps even when one person holds more than one role.

For a broader records and responsibility handover, use our guide to changing bookkeepers. The invoice workflow example explains how supporting records connect to bookkeeping work.

Check the current Scamwatch business email compromise guidance when reviewing these controls. For the scope of local assistance, see our Penrith and surrounding-region bookkeeping services.

Reviewed by our registered BAS agent (No. 26274944)

Need a clearer bookkeeping and payroll process?

Discuss your records, unresolved questions and approval responsibilities. We agree the scope before work begins.

Get started →

General operational guidance. Fictional examples illustrate workflow and arithmetic only. Check the requirements and treatment that apply to your business.