When you compose a BAS return, Nagaris reads the connected Xero ledger for the period and builds a workpaper: the figures, a control tie, any exceptions and queries, and a checklist. This can take a moment, since the work is queued and the page updates once it finishes.
A composed workpaper lands in one of these statuses:
Composing: the run is in progress.
Ready: the workpaper composed cleanly.
Held: composing stopped because something needs your decision first.
Failed: the engine hit an error.
A held run can be waiting on one of two different things. Nagaris shows a different confirmation for each, because accepting one is not the same as accepting the other.
If there are unreconciled bank transactions dated inside the period, any figure computed from the ledger could still move. Clicking Compose anyway opens a dialog explaining this. Confirming writes the override into the workpaper's queries, so anyone reviewing it later can see it was used.
Nagaris composes every BAS on an accrual basis: each transaction is dated by its document. If the client's Xero file is set to report GST on a cash basis, where GST is recognised when money actually moves, an accrual-dated composition produces the wrong figure in every box, even though the pack looks ordinary.
When this is the hold reason, clicking Compose anyway opens a dialog warning that you're about to compose a cash-basis client on accrual. Use this only to see the shape of the ledger, never to lodge from. If you confirm, the workpaper's Checklist and queries both record that the basis override was used.
If a workpaper was composed with the basis override, it carries a visible warning at the top of its findings:
Composed on the wrong basis. Do not lodge.
The workpaper's provenance line also shows which basis it composed on (for example, "accrual basis" or "cash basis") alongside the engine version and composed date, so you can confirm at a glance which figures you're looking at before sending anything to the client or the ATO.
