Skip to content

MYOB Advanced — Admin Procedures (Finance View)

Common change tasks in MYOB Advanced for the finance team. Each section names the screen, the rough steps, and what downstream consumers (PWG_DATA, ezyCollect, Hex dashboards) expect afterwards.

Status: draft. This page captures process at a high level. Step-by-step screen flow — and any change-control gates — should be confirmed with the finance team and the Axsys support partner before publishing as current.

StepScreenNotes
1GL.GL202500 — Chart of AccountsAdd the account against the relevant company (PWG or JV — the CoA is per-company)
2Set Type, AccountClass, and TaxCategoryThese flow through to PWG_DATA’s CORE.MYOB_GL_Account and drive every downstream P&L view
3Confirm Active = True and PostOption = DetailDetail is required for posting; Summary is for header roll-ups
4Notify Tech if it is a P&L accountThe PWG_DATA mapping table STAGING.PWG_Revenue_Expense_Mapping may need a MYOBIncludePL flag — see dev/known-issues

The Chart of Accounts CSVs in the source repo’s data/ folder are extracts, not the source of truth. To regenerate them after adding accounts, see the dev admin procedures.

Tax codes and categories are tenant-wide (shared between PWG and JV) and settle to control accounts 240000 (GST claimable) and 220000 (GST payable).

StepScreen
1TX.TX205000 — Taxes
2TX.TX205500 — Tax Categories
3Verify against the taxes.csv and tax_categories.csv in the source repo’s data/ folder

The monthly close cadence is finance-owned. The relevant MYOB screens are:

  • GL.GL503000 — Close Financial Periods
  • GL.GL501500 — Generate Recurring Transactions
  • AP / AR sub-ledger close screens

Downstream effect: once a period closes, the PWG_DATA staging tables continue to receive any back-dated postings on the next ADF run, but STAGING.MYOB_GL_Transaction_Detail_* carries the PeriodID so MART views can scope correctly. Do not delete or reopen periods without notifying Tech — partial reposts can produce duplicate lines if the staging load runs mid-change.

Open issue. Users and roles are not exposed via any published Web Service Endpoint on this tenant (see known-issues). Documentation here is manual-screen only until that’s resolved.

TaskScreen
Add a new userSM.SM201010 — Users
Assign rolesSM.SM201005 — Roles
Audit who has whatManual export from the two screens above

For the regular access-review (target cadence: quarterly), the fastest path today is to UI-export both screens to CSV and drop the files into the source repo’s data/ folder.

Owned by Axsys (the MYOB support partner) under the support contract. Raise a ticket through the standard Axsys channel rather than editing in the production tenant — the workflows touch AP approvals, journal posting, and intercompany transfers, and are not currently version-controlled outside MYOB.