The obligation profile is a per-client declaration of what that client's activity statement carries. Nagaris records it once, when the client is onboarded or their ledger is first read, then reads it on every period afterward instead of guessing at it from the ledger.
Every field in the profile is declared, not inferred. If a field hasn't been declared, the engine treats it as unset rather than assuming an answer.
The profile covers:
Field | What it declares |
|---|---|
| Whether the client's activity statement is a BAS or an IAS |
| The client's GST reporting cycle |
| Whether the client reports under simpler BAS |
| PAYG withholding cadence: quarterly, monthly or large |
| Whether PAYG instalments apply, and the method and cadence used |
| Whether an FBT instalment is included |
| Whether the client is registered for fuel tax credits |
| Whether wine equalisation tax applies |
| Whether luxury car tax applies |
| Whether deferred GST applies |
| Whether the client reports as part of a GST group |
Some of these fields duplicate a setting Nagaris already stores on the client, usually synced from your practice management or accounting software. Where both exist, the existing client setting stays authoritative and the profile has to agree with it:
Profile field | Existing client setting |
|---|---|
| PAYG withholding cadence |
| Fuel tax credit registration |
| WET registration |
| LCT registration |
| PAYG instalment method and cadence |
| The family of the client's declared form type |
If the two disagree when a period is composed, composing halts before it reads any figures. The hold names both settings and the value each one holds, so you can see the mismatch and correct whichever one is wrong. There's no override for this hold.
Five fields have no matching client setting and come from the profile alone: gst_cycle, simpler_bas, fbt_instalment, dgst and gst_group.
Agreement checks run before any other check on the client's obligations for that period. A period only reaches later checks once the profile and the client record match.
Every workpaper run's audit trail carries the client's obligation profile exactly as declared, field for field, with unset fields shown as none. If you're trying to work out why a period composed the way it did, or why a hold names a particular setting, the audit trail is where to check what Nagaris had on file for that client at the time.
