What is netsuite bookkeeping?
Transaction and reconciliation work inside NetSuite.
A business running NetSuite in Australia has almost always outgrown a single-entity, single-GST-registration setup — multiple subsidiaries, sometimes a mix of GST-registered and non-registered entities, sometimes an offshore subsidiary in the same OneWorld instance. The work is transaction processing and reconciliation inside NetSuite: bank feeds matched through the reconciliation tool, GST tax codes applied correctly at the line-item level across every subsidiary, intercompany transactions posted and matched between entities, and each subsidiary's trial balance closed on the shared close calendar before the group's consolidated view is trusted for anything.
GST tax-code hygiene sits at the center of the AU-specific work in a way it doesn't in a single-currency US instance. NetSuite's tax engine assigns a code to every line — GST on Income, GST Free, Input Taxed, and their export or reduced variants — and a multi-subsidiary instance often mixes GST-registered subsidiaries with ones that aren't, or mixes domestic and export transactions inside the one entity. A line posted with the wrong code doesn't just misstate the ledger; it feeds directly into the subsidiary's next Business Activity Statement, so getting the code right at point of entry keeps the BAS agent's lodgment work from becoming a code-by-code audit each quarter.
Who does what
| Your CapEasy team | NetSuite bookkeeping, the reconciliations and reporting behind it, and the questions list that keeps it honest. |
| Your registered BAS or tax agent | Everything that carries a licence in Australia — rendered exactly as written: work out what goes on your bas, or advise you on it — under tasa 2009 that requires registration we do not hold. |
| You | One conversation with one named person, and the decisions that are genuinely yours. |
NetSuite bookkeeping in Australia
GST tax codes are assigned per line item, and a wrong code compounds every quarter
A wrong default code on a recurring supplier or customer record repeats every period until someone catches it. We check GST tax-code assignment as part of ongoing processing, not just at BAS time, so a misclassified code is caught the period it happens.
Multi-subsidiary GST grouping links the close calendar to the BAS calendar
Where several AU subsidiaries in one OneWorld instance are grouped for GST reporting, the group's activity statement depends on every grouped subsidiary being closed and reconciled. We flag a lagging subsidiary to the registered BAS agent early, not at the lodgment deadline.
Ascertaining or advising on a BAS liability sits with the registered BAS agent, not us
Under the Tax Agent Services Act, only a registered BAS or tax agent can ascertain or advise on GST or BAS liability. We apply tax codes to transactions and reconcile the ledger they feed; if a transaction's GST treatment is genuinely unclear, we flag it to the client's agent rather than deciding it ourselves.
STP reporting is the registered agent's obligation, separate from the ledger entry
Wages and superannuation post to the NetSuite ledger as part of the ongoing close, but the actual Single Touch Payroll report to the ATO is filed by the registered agent running payroll. Our processing keeps the entries that feed that report accurate, with submission staying entirely with the registered agent.
What your registered BAS or tax agent receives from us
- A closed, reconciled trial balance for each subsidiary, on its close-calendar date
- Bank reconciliations matched against the actual downloaded statement, not the connector feed alone
- A GST tax-code review, with any line flagged where the code doesn't match the transaction's apparent nature
- An intercompany schedule with both subsidiary sides shown and matched
- Amortisation, prepaid, and fixed-asset schedules run for the period, with drifted schedules flagged
- A BAS-ready GST summary per subsidiary — collected, paid, and net position — handed to the registered agent


