Client-level CoA Mapping

The Chart of Accounts (CoA) in Zato operates at client level, not job level. One set of mappings is shared across all jobs for a client. Map an account once and it applies to every existing and future job for that client automatically.

Why this Matters

For firms running multiple jobs per client - or adding new jobs year over year - this removes the need to remap the same accounts repeatedly. It also ensures consistency: all jobs for a client always use the same account classifications.

Four access points

You can view and edit client-level CoA Mapping from any of the following:

• Clients list → click the list icon in the Actions column next to the client.

• Jobs list → click the row dropdown on the job → select CoA Mapping.

• Job Setup → CoA tab → click the Client Mappings button (opens as a side drawer).

• Client Mappings drawer → click the fullscreen icon to open the standalone mapping page.

Mapping saved from any of these access points propagates to the client level and applies to all jobs.

Job filter on the standalone mapping page

When a client has more than one job, a job filter dropdown appears on the standalone client CoA Mapping page. Select a job to filter the view to only accounts present in that job's Trial Balance. This helps when you want to check or update mappings in the context of a specific engagement, without being distracted by accounts from other jobs.

Mapping inheritance

• Mapping an account from either the client page or any job's CoA tab saves to the client profile.

• All existing jobs for that client pick up the updated mapping immediately.

• New jobs created for the client inherit the full mapping set automatically.

• When a new account code appears in a CoA reupload or Xero resync, it is added and auto-mapped. Existing mappings are not touched.

TB upload and missing accounts

When a Trial Balance is uploaded, Zato reads the client CoA mappings as the source of truth. If the TB contains accounts not found in the client CoA, a yellow toast appears: "X account(s) not found in the CoA - please update the Client CoA Mapping." Address these before running automation.

Resync CoA from Xero

For Xero-linked clients, the Resync CoA from Xero button is available in the Job Setup CoA tab and in the Edit Client modal. It fetches new account codes from Xero without overwriting any existing mappings.

CoA download

For non-Xero clients, the CoA download button is available in the Edit Client modal.

Saving notifications

When mappings are saved, a notification confirms: "{N} mapping(s) updated. {X} TB row(s) and {Y} WP categories updated." A secondary warning notes that changes apply across all jobs for this client.

How to access

• Go to Clients and click the list icon in the Actions column, or

• Go to Jobs, open the row dropdown on the relevant job, and select CoA Mapping, or

• Open Job Setup, go to the CoA tab, and click Client Mappings.