A missing receipt and an uncertain GST treatment are different problems. An administrator can chase the receipt using an agreed process. Deciding how a transaction should be treated may require professional judgement and an appropriately authorised tax or BAS service.
That distinction matters when an Australian business outsources bookkeeping administration to the Philippines. A job description saying “manage the accounts” leaves too much unresolved: what decisions can the person make, who reviews them and what information can be shared?
Start with a defined workflow. This guide offers an operational planning method for business owners and their advisers. It does not classify a particular engagement or establish that a provider is authorised to deliver regulated services.
Describe each task by the decision it contains
List the actual actions in your monthly accounts process. “Prepare the bookkeeping” might include collecting invoices, matching reference numbers, investigating differences, choosing tax codes, preparing reports and answering a client's tax questions. Those activities need different boundaries.
The TPB explains that BAS services include specified work concerning BAS liabilities, obligations or entitlements where a client can reasonably be expected to rely on it. Its examples include determining GST codes and reconciling BAS data to establish activity-statement figures. The label “reconciliation” therefore does not make a task purely administrative. Providing BAS services for a fee or reward while unregistered can attract civil penalties. TPB: BAS services.
Ask your registered practitioner to review the proposed task list and service arrangement. Include what the worker sees, changes, concludes and communicates. A software permission is not a professional authorisation, and locating the work overseas does not settle the question.
Create a preparation and review boundary
The following is an illustrative operating brief to take to your adviser. It proposes restricted support actions; it is not a legal list of exempt services.
| Work item | Proposed support action | Review trigger |
|---|---|---|
| Missing supplier document | Request the exact document from an approved contact | Conflicting amounts or an unfamiliar document |
| Invoice register | Record supplied identifiers and attach the source | Duplicate reference or unclear business purpose |
| Payment matching | Suggest an existing invoice match for review | Split, partial or unexplained payment |
| Tax treatment | Collect facts and flag the question | Any new or uncertain treatment |
| Reporting pack | Assemble the agreed source documents | Any conclusion about tax or BAS figures |
Write explicit stop points beside the brief. For example, a missing invoice should remain flagged; the administrator should not create a replacement source document or guess an explanation to make the month close neatly.
Use a separate approval state for reviewed work. “Documents collected”, “question raised” and “reviewed” should mean different things. This makes unfinished decisions visible without rewarding someone for prematurely closing a task.
Make supervision a working arrangement
For a registered practitioner outsourcing tax agent services to an unregistered third party, TPB guidance requires supervision and control by that practitioner or another registered practitioner. The outsourcing practitioner remains responsible for quality. The guidance distinguishes this from outsourcing to a registered third party and emphasises that simply saying work is supervised does not establish competence. TPB: outsourcing and offshoring guidance.
For your proposed workflow, name the person who answers questions and reserve time for them to do so. Agree how an administrator identifies an urgent exception, how the reviewer records a decision and what happens during the reviewer's absence. A queue nobody has time to read is not a usable review process.
Before buying a service described as registered, verify the individual or entity and relevant registration details using the TPB Register guidance. Discuss scope and any conditions with the practitioner. Registration of one person should not be treated as an explanation of an entire provider's arrangement.
Set information permissions before the first file moves
Identify whether the work concerns your own business records or a practitioner's client information. That difference matters when designing permissions and responsibilities.
TPB guidance says practitioners must have client permission or a legal duty before disclosing information about a client's affairs to a third party. It discusses explaining the disclosure and overseas arrangements; a separate related company can still be a third party. TPB: confidentiality and offshore arrangements.
Its outsourcing webinar also discusses access controls, audit trails, segregation of duties and review of changes as practical information-protection measures. TPB: outsourcing and offshoring webinar.
Translate the approved arrangement into specific access. A person collecting invoices may not need bank-payment authority, employee payroll files or a complete customer export. Keep accounts individual and separate document preparation from payment approval. Record which devices, storage locations and tools are approved; introduce new AI or file-sharing tools only through your agreed review process.
Our CRM privacy checklist explores separate Privacy Act coverage and cross-border questions. TPB requirements and privacy obligations need their own assessment; one consent document should not be assumed to answer everything.
Trial the handover with a fictional month-end pack
Imagine a small solar retailer preparing its monthly records. This is an invented workflow example, not a client result. The administrator receives an approved list of documents to gather and a register containing references, dates, attachments and unresolved questions.
One supplier invoice has a different total from the purchase record. A customer payment has no usable reference. Another purchase raises an unfamiliar tax-treatment question. The administrator records all three exceptions and routes them to the named reviewer, rather than resolving them through guesswork.
The reviewer requests clarification, documents the relevant decisions and identifies which instructions can be reused. The administrator then updates only the authorised records and marks the outstanding items accurately. Neither party reports the pack as complete while an approval is still missing.
Test that sequence with synthetic records before allowing real access. Measure whether the reviewer can locate the source and understand the question without a long message exchange. Include a deliberately ambiguous item: appropriate escalation is a successful result in that test.
Measure readiness for review rather than speed alone
During the first month, track missing documents, repeat requests, unresolved questions and time spent finding source evidence. Keep support errors separate from delays awaiting customer information or professional decisions.
Review whether the scope has changed. If an administrator is now being asked to answer tax questions, configure new accounting rules or confirm activity-statement figures, return to the practitioner before treating those tasks as routine extensions.
Use a documented VA procedure to preserve the agreed workflow and version of instructions. Discuss administrative support with Nexus, bringing the task list and your practitioner's boundaries. A useful support role produces organised evidence and a dependable handover while the appropriate people retain the decisions they are engaged to make.
