Troubleshooting

“Choose an active provider workspace before …”

Means: Almost every action is scoped to a provider workspace, and one is not currently active (you have not selected it, or your session lost it). The ending of the message names the action you tried (for example "before adding a shift").

Fix: Select your provider from the workspace switcher at the top of the app, then try again. If you belong to a single provider it should select automatically; if it keeps happening, sign out and back in.

“<Field> is required.”

Means: A required field was left empty. The message names the exact field.

Fix: Fill in the named field, then save again.

“Enter a valid email address.”

Means: The email address is not a valid format.

Fix: Use a full address like name@example.com, with no spaces and a real domain.

“Enter a valid Australian phone number (e.g. 04XX XXX XXX or 0X XXXX XXXX).”

Means: The number is not a recognised Australian format.

Fix: Enter a mobile (04XX XXX XXX), a landline (0X XXXX XXXX), or a 1300/1800 number. Spaces, dashes and brackets are fine.

“NDIS number must be 8 to 11 digits.”

Means: The participant NDIS number is the wrong length.

Fix: Enter the NDIS number from the participant's plan. It must be 8 to 11 digits, with no letters.

“NDIS Worker Screening ID must be 7 or more digits.”

Means: A support worker needs a valid NDIS Worker Screening clearance number, and the one entered is too short.

Fix: Enter the worker screening ID (7 or more digits) from their clearance.

“Enter a valid ABN.”

Means: The ABN failed the official 11-digit checksum, so it is not a real ABN.

Fix: Check the 11 digits against the business record (search abr.business.gov.au).

“ACN must be 9 digits.”

Means: The Australian Company Number is the wrong length.

Fix: Enter the 9-digit ACN (spaces are optional).

“Enter a valid WWCC or equivalent number for your state (e.g. NSW: WWC1234567E, QLD: 12345/1, SA: SRN 1234-5678, VIC: 1234567A, or digits for other states).”

Means: The Working With Children Check number does not match your state format.

Fix: Enter the check number exactly as it appears on the card, using your state format (the message lists examples).

“CRN must be 9 digits followed by a letter (e.g. 123 456 789A).”

Means: The Centrelink Customer Reference Number is in the wrong shape.

Fix: Enter 9 digits then a trailing letter, for example 123 456 789A.

“Medicare number must be 10 or 11 digits.”

Means: The Medicare number is the wrong length.

Fix: Enter the 10 or 11 digit Medicare number.

“Enter a valid website URL.”

Means: The website address is not a valid URL.

Fix: Enter a domain like example.com.au (the http prefix is optional).

“Enter a valid Australian postcode.”

Means: The postcode is not within a valid Australian range.

Fix: Enter a valid 4-digit Australian postcode.

“Select an address from the dropdown, or use "Enter address manually" to set the state.”

Means: You typed an address line but no state has been set, which the record needs.

Fix: Pick a suggestion from the address dropdown, or click "Enter address manually" and choose the state.

“First name and last name are required.”

Means: You tried to create or save a participant without both names.

Fix: Enter both the first name and last name, then save.

“Plan number is required.”

Means: Saving an NDIS plan needs a plan number and it was left empty.

Fix: Enter the plan number shown on the participant's NDIS plan, then save.

“Plan number must be 8 to 11 digits.”

Means: The NDIS plan number is the wrong length.

Fix: Enter 8 to 11 digits, with no letters or spaces.

“NDIA-managed plans require a valid NDIA organisation ID. Enter it in Account > Organisation, or ask the provider owner to do so, then try again.”

Means: The plan or one of its Mixed budget pools is NDIA-managed, but the provider does not have a valid 9-digit NDIA organisation ID.

Fix: Enter the provider ID under Account, then Organisation, or ask the provider owner to update it, and save the plan again.

“Select at least one budget pool.”

Means: A service agreement has to draw from at least one funded budget pool, and none is selected.

Fix: Tick one or more budget pools (for example Core, Capacity Building, or Capital) on the agreement, then save.

“This support item is already on the service agreement.”

Means: You added a support item that is already listed on this agreement.

Fix: Edit the existing line instead of adding it again, or choose a different support item.

“Missing before sending: …”

Means: The agreement or consent form cannot be sent for signature yet because some required details are missing. The message lists which ones.

Fix: Complete the listed fields (commonly a signer name and a valid email), then send for signature again.

“Could not find that goal to update.”

Means: The goal or risk you were editing no longer exists, often because it was changed or removed in another tab or by another user.

Fix: Refresh the participant profile and try the edit again.

“Participant first name and last name are required.”

Means: You tried to save an intake without both names.

Fix: Enter both the first name and last name, then save.

“Participant email is required.”

Means: The intake needs an email address and the field was left empty.

Fix: Enter the participant's email address, then save.

“Enter a valid participant email address.”

Means: The email address is not a valid format.

Fix: Use a full address like name@example.com, with no spaces, then save.

“Enter a valid phone number (8 to 15 digits).”

Means: A phone number was entered but it is not 8 to 15 digits.

Fix: Enter a phone number with 8 to 15 digits, or clear the field (phone is optional on intake).

“Enter a valid 9-digit NDIS number.”

Means: An NDIS number was entered but it is not exactly 9 digits.

Fix: Enter a 9-digit NDIS number, or clear the field (it is optional at intake but required to convert).

“Add … before converting to a participant.”

Means: Converting an enquiry to a participant requires a phone number, NDIS number, and address (with state). The message lists whichever of those are still missing.

Fix: Open the enquiry, fill in the listed details (phone, NDIS number, address), save, then convert again.

“A participant with this email already exists for this provider.”

Means: Converting would create a participant whose email already belongs to an existing participant.

Fix: Open the existing participant instead, or change the email on the enquiry before converting.

“Select an NDIS reportable category before saving.”

Means: Every incident must record a reportable category, even if it is "Not a reportable incident".

Fix: Pick a value in "NDIS reportable category", then save.

“Select at least one participant before saving.”

Means: The incident has no participant linked to it.

Fix: Choose one or more participants in the Participants field, then save.

“Select at least one support worker before saving.”

Means: The incident has no support worker recorded as involved.

Fix: Choose one or more workers in "Support workers involved", then save.

“Select the related shift before saving.”

Means: The selected participant has shifts on file, so the incident must be linked to one of them.

Fix: Pick the related shift in the dropdown (or choose "No related shift" if none applies), then save.

“Enter when the incident occurred before saving.”

Means: The "Occurred at" date and time is required and was left empty.

Fix: Set the date and time the incident occurred, then save.

“Enter the subject of allegation before saving.”

Means: The "Subject of allegation" field is required and was left empty.

Fix: Enter the subject of allegation, then save.

“Enter the incident location before saving.”

Means: The incident has no location set.

Fix: Pick a location from the address lookup, or use "Enter address manually", then save.

“Describe the incident before saving.”

Means: The "Incident description" field is required and was left empty.

Fix: Describe what happened in the Incident description, then save.

“Describe the immediate actions taken before saving.”

Means: The "Immediate actions taken" field is required and was left empty.

Fix: Describe the immediate actions taken, then save.

“Could not save the incident report.”

Means: The incident could not be saved, usually a temporary or connection problem.

Fix: Try saving again. If it keeps failing, refresh the page and re-enter any unsaved details.

“Could not archive the incident.”

Means: The incident could not be archived, usually a temporary or connection problem.

Fix: Try again. If it keeps failing, refresh the page and retry.

“Could not move the incident.”

Means: Dragging the incident card to a new status column did not save.

Fix: Try again, or open the incident and change its Status in the edit drawer instead.

“At least one participant is required for a support shift.”

Means: You tried to create a shift without selecting any participant.

Fix: Pick a participant in the people picker (group support allows several), then create the shift.

“Shift start and end are required.”

Means: The shift has no start time, no end time, or both are missing.

Fix: Set both "Starts at" and "Ends at" in the Time section, then save.

“Shifts must start in the future.”

Means: The start time you chose is in the past.

Fix: Choose a start time later than now, then save.

“Shift end must be after shift start.”

Means: The end time is the same as or earlier than the start time.

Fix: Set an end time later than the start time, then save.

“Choose a repeat end date.”

Means: You turned on Repeat but did not set the date the series should stop.

Fix: Pick an end date for the repeating shift, or turn off Repeat.

“Choose a repeat frequency.”

Means: You turned on Repeat but did not choose how often the shift recurs.

Fix: Pick a frequency (Daily, Weekly, Fortnightly, or Monthly), or turn off Repeat.

“Every group participant needs an address option in the Location section. Still missing: …”

Means: On a group support shift, one or more participants have no pickup address set. The message names who is still missing.

Fix: In the Location section add an address option for each named participant (use "Add another location"), then save.

“Group support participants must share the same pricing region. Selected regions: …”

Means: You selected group participants from different NDIS pricing regions, which cannot be billed together. The message lists the regions involved.

Fix: Remove participants so everyone on the shift shares one pricing region, or run separate shifts per region.

“Choose a location type.”

Means: The shift has no address type set (participant address or other address).

Fix: Pick an address type in the Location section, then save.

“Assign a worker before publishing this assignment.”

Means: You tried to publish an assignment that has no worker selected.

Fix: Pick an "Assigned worker" on the slot, then Publish.

“Attach at least one participant before publishing this group assignment.”

Means: A group assignment cannot be published without at least one participant attached to it.

Fix: Attach one or more participants to the assignment, then Publish.

“Add support items before publishing this assignment.”

Means: The assignment has no NDIS support items, which are required before it can go to the worker.

Fix: Add the delivered support items in the assignment support picker, then Publish.

“… participant(s) is/are not assigned to a worker. Allocate every participant to a worker assignment, or add another assignment to cover them, before publishing.”

Means: On a group shift some participants are not covered by any worker assignment, so the shift cannot be published.

Fix: Attach every participant to a worker assignment, or add another assignment to cover the rest, then Publish.

“… is/are allocated to a published assignment. Unpublish it before removing them from the shift.”

Means: You tried to remove participants who are tied to an assignment that is already published to a worker.

Fix: Unpublish the assignment first, then remove the participants from the shift.

“Choose who cancelled the shift.”

Means: The cancel form needs to know whether the participant or the provider cancelled.

Fix: Pick "Participant" or "Provider" under "Who cancelled?", then continue.

“Choose a reason.”

Means: A cancellation reason is required and none was selected.

Fix: Select a reason from the dropdown (the options depend on who cancelled), then confirm.

“This shift has already started, so it can no longer be restored.”

Means: You tried to restore a cancelled shift whose scheduled start time has already passed.

Fix: Restore is only possible before the shift starts. Create a new shift instead if cover is still needed.

“… has no active service agreement support for this date.”

Means: A cancelled participant cannot be restored because they have no active agreement support covering the shift date.

Fix: Activate or extend the participant's service agreement support for that date, then restore.

“You are not at the shift address yet. Head to …, then slide to clock in.”

Means: Shown to the support worker under "Clock in blocked". Geofencing is on for the workspace and the worker was more than 150 m from the address the shift starts at, after crediting up to 100 m of GPS accuracy, so a poor fix can pass from further away. The message names that address.

Fix: The worker goes to the address named and slides again; a moment outdoors helps the phone get a better fix. If they are genuinely there, check the shift's address in the Location section, or turn Geofencing off under Account > Features > Scheduling.

“You are not at your first pickup yet. Head to …, then mark the pickup.”

Means: The same check on a group shift, where the clock starts at the FIRST pickup rather than the destination. Only that pickup is fenced; later pickups on the run are never checked.

Fix: The worker marks the pickup at the address named. If the pickup address is wrong, correct it on the shift; a shift whose address cannot be placed on a map is not checked at all.

“This shift opens for clock in … minutes before it starts. Hang tight.”

Means: The worker tried to clock in earlier than the Clock-in window allows. The number in the message is the workspace setting, 5 minutes by default. Before the window opens their slider is locked and counting down.

Fix: Nothing to do: the slider unlocks itself. To let workers start earlier, raise or turn off Clock-in window under Account > Features > Scheduling (0 to 4320 minutes, up to three days).

“Your phone could not share your location. Turn location on for the app, then slide again.”

Means: Geofencing is on but the worker's phone returned no position, usually because location is switched off for the app or the signal is too poor for a fix.

Fix: The worker turns location on for OneForce Care in their phone settings (Settings > Device permissions in the app lists them), moves somewhere with signal, then slides again.

“Shift must be accepted before this action”

Means: The shift has Worker acceptance set to Required and the worker has not answered yet, so nothing they do can be recorded against it. The app normally hides those controls, so this is usually a change queued offline before the request arrived.

Fix: The worker accepts the shift in their app, then repeats the action. If they should not have to, switch Worker acceptance back to Automatic on the shift.

“Operational role is required.”

Means: You tried to send an invite without choosing the worker's operational role.

Fix: Pick a role (Support worker, Provider, or Admin), then send the invite.

“Worker phone number is required.”

Means: The invite needs a phone number and the field was left empty.

Fix: Enter a valid Australian phone number, then send the invite.

“Worker address is required.”

Means: The invite needs an address and none was set.

Fix: Pick an address from the lookup, or enter it manually (including the state), then send the invite.

“Select an access role for this worker.”

Means: A provider employee needs an access role that controls which screens they can use, and none is selected.

Fix: Choose an access role in the Access role dropdown (or create one), then send the invite.

“NDIS Worker Screening ID is required for support workers.”

Means: Support workers must have an NDIS Worker Screening clearance number, and it was left empty.

Fix: Enter the worker screening ID (7 or more digits) from their clearance, then send the invite.

“Choose an active provider workspace before inviting a worker.”

Means: No provider workspace is active, so the worker cannot be linked to one.

Fix: Select your provider from the workspace switcher at the top of the app, then invite again.

“Compliance item is required.”

Means: A compliance decision was saved without a compliance item selected.

Fix: Choose the compliance item, set its expiry or evidence, then save compliance.

“Select a worker category (day or shift worker) before saving.”

Means: The payroll classification needs a worker category and none was chosen.

Fix: Pick a worker category (day worker or shift worker), then save payroll.

“Select an employment basis (full-time, part-time, or casual) before saving.”

Means: The payroll classification needs an employment basis and none was chosen.

Fix: Pick full-time, part-time, or casual, then save payroll.

“Enter the agreed weekly hours for a part-time worker before saving.”

Means: Part-time workers need agreed weekly hours and the field was left empty.

Fix: Enter the agreed weekly hours (0 to 38), then save payroll.

“Select the worker's work state before saving.”

Means: The payroll classification needs a work state and none was chosen.

Fix: Choose the worker's work state, then save payroll.

“Select a type.”

Means: An availability or leave window was saved without a type.

Fix: Choose a type (Availability, or a leave type such as Annual leave), then save.

“Leave must have an effective from and to date.”

Means: A leave or exclusion window needs a start and end date, and one is missing.

Fix: Set both Effective from and Effective to dates for the leave window, then save.

“Document name and file are required.”

Means: You tried to add a document without both a name and a file.

Fix: Enter a document name and choose a file (images, PDF, Word, or text, max 10 MB), then add the document.

“Note is required.”

Means: You tried to save a worker note with no text.

Fix: Type the note, then save it.

“Enter Archive to confirm.”

Means: Archiving a worker needs you to type the word Archive to confirm, and it did not match.

Fix: Type Archive exactly in the confirmation box, then choose Archive worker.

“Billed time doesn't match the worked time.”

Means: The billable minutes on the charge do not add up to the actual time the worker recorded on the timesheet.

Fix: Open the shift and the worker assignment timesheet, then adjust the billable minutes per support code so they sum to the worked time. Use the "Open shift" link on the blocker panel.

“No NDIS support code is linked.”

Means: The charge has no NDIS support item code, so it cannot be claimed or invoiced.

Fix: Open the shift, open the support picker in the worker assignment, select the delivered support code and save. The charge regenerates with the code attached.

“Rate or pricing region isn't valid.”

Means: The rate is above the current NDIS price limit, or the rate or pricing region is not valid for this participant.

Fix: Open the participant's Service Agreements, find the support, then lower the agreed rate (or mark it quote-required), or set a valid rate and region for the participant's MMM area, and save.

“This support can't be claimed yet: its quote isn't approved, it has no agreed rate, or its catalogue entry needs review. Fix it in the service agreement.”

Means: The support item is not claimable yet because its quote is not approved, it has no agreed rate, or its catalogue entry needs reconciliation.

Fix: Open the participant's Service Agreements, then record the quote approval or reconcile the support against the current catalogue.

“Service agreement isn't active.”

Means: The service agreement covering this charge is not active for the shift date.

Fix: Open the participant's Service Agreements, then sign or activate the agreement, or extend its end date to cover the shift date.

“Funding type not set. Set it to NDIA, plan, or self-managed on the NDIS plan.”

Means: The charge has no concrete funding type, so the app cannot decide which batch (NDIA, plan-managed, or self-managed) it belongs in.

Fix: Open the participant's NDIS Plans and set a concrete funding type (NDIA, plan-managed, or self-managed, not Mixed) on the budget.

“Invoice contact incomplete. Add the recipient name and email to the service agreement.”

Means: A plan-managed or self-managed invoice needs a recipient, and the invoice contact name or email is missing.

Fix: Open the active service agreement's Invoicing section and add the invoice recipient name and email for this funding type.

“Shift crosses a band the agreement has no code for.”

Means: The shift runs across a time band (for example evening or night) that the agreement has no matching support code for.

Fix: Open the participant's Service Agreements and add the matching time-band variant of the support.

“Agreement doesn't permit this travel claim.”

Means: The travel on this charge is not covered by the participant's agreed travel terms.

Fix: Open the participant's Service Agreements and enable the relevant travel terms (provider travel time, return-to-base, activity transport, or transport actual costs).

“Travel details are incomplete or mis-coded.”

Means: The travel capture on the shift is incomplete or uses the wrong code.

Fix: Open the shift travel capture, select the correct 590 or 799 travel code, set the destination MMM, confirm the worker was paid, and enter the kilometres or duration.

“Receipt required for actual-cost transport.”

Means: Actual-cost transport (such as tolls or parking) needs receipt evidence and none is attached.

Fix: Open the shift travel review and attach a receipt for each actual-cost category (tolls, parking).

“Manual charge needs an approved quote.”

Means: This manual charge uses a quote-required support code but there is no approved agreement support to back it.

Fix: Open the participant's Service Agreements and add a quote-approved support, or change the manual charge to a non-quote code.

“Confirm this manual charge's budget draw-down.”

Means: A manual charge is not linked to a plan budget, so the budget draw-down has to be confirmed before the row can be billed.

Fix: Check the plan budget capacity, then use the "Include in billing" button on the row to confirm the draw-down and make it billable.

“This is a Group Activities support code on a direct (1:1) shift. … Select a 1:1 support code, or change the shift to Group Support.”

Means: A Group Activities support code is selected on a direct (1:1) shift, which is not a valid combination.

Fix: Open the shift assignment support picker and replace the Group Activities code with a 1:1 code, or change the shift type to Group Support.

“Cannot generate batch. …”

Means: Pre-flight validation found one or more problems on the rows in a bucket, so no batch was created. The full message lists the first several issues and how many more must be fixed.

Fix: Read the listed issues, fix each at its source (service agreement, shift, or provider invoicing settings), then press Generate again. No partial batch is created.

“Provider invoicing setup incomplete: …”

Means: Plan-managed and self-managed batches need your provider invoicing details (default GST code, ABN, remittance email, bank account name, BSB, account number, payment terms), and one or more are missing or invalid. The message names which.

Fix: Open Account, then the Invoicing tab, complete the named fields, save, then generate again.

“Provider NDIA organisation ID is required for the NDIS CSV.”

Means: The NDIS bulk claim file needs your provider's NDIA organisation ID and it is not set.

Fix: Open Account, then the Organisation tab, enter the NDIA organisation ID, then generate the NDIA batch again.

“Budget over-allocation blocks invoice batch generation:”

Means: Generating the batch would claim more than the participant's remaining budget. This is a hard stop checked against the live budget; the message lists the affected rows.

Fix: Reduce or remove the over-allocated charges, or confirm the participant has budget capacity, then generate again.

“You need payments edit access to void batches.”

Means: Your role does not have payments edit access, so voiding is blocked.

Fix: Ask an owner, admin, or a role with payments edit access to void the batch, or request the permission.

“You need payments edit access to record payments.”

Means: Your role does not have payments edit access, so you cannot record a payment or recovery.

Fix: Ask an owner, admin, or a role with payments edit access to record it, or request the permission.

“You need payments edit access to upload claim results.”

Means: Your role does not have payments edit access, so you cannot import an NDIA bulk claim-results file.

Fix: Ask an owner, admin, or a role with payments edit access to import the file, or request the permission.

“Your session has expired. Reload and sign in again.”

Means: Your login session lapsed while the Payments page was open, so the action could not be attributed to you.

Fix: Reload the page, sign in again, and retry the action.

“Payment amount must be greater than 0.”

Means: The Amount field on the Record payment drawer was left at 0 or a negative value.

Fix: Enter the amount actually paid or recovered, then save again.

“Amount exceeds the outstanding balance (…) by (…). Record up to the outstanding amount and query the remainder with the payer.”

Means: The amount entered is more than the batch currently owes. This guard exists so an over-large amount cannot silently vanish into the outstanding figure.

Fix: Lower the amount to the outstanding balance shown, then follow up the difference with the payer directly (for example as a credit against a future invoice).

“Choose a payment date.”

Means: The Date field on the Record payment drawer was left empty.

Fix: Pick the date the payment or recovery happened, then save again.

“Could not record payment.”

Means: The payment or recovery could not be saved, usually a temporary or connection problem.

Fix: Check the fields and try again. If it keeps failing, reload the page and retry.

“This batch has recorded payments and can no longer be voided.”

Means: Payments cannot be removed once recorded, so a batch with any payment or recovery against it can never be voided.

Fix: There is no fix, this is permanent by design. Issue a correction or credit note against the batch instead of voiding it.

“Claim results have been imported for this batch and it can no longer be voided.”

Means: An NDIA bulk claim-results file has already been imported against this batch, so voiding is blocked.

Fix: There is no fix, this is permanent by design. Correct rejected lines at source and bill them in a fresh batch instead.

“Could not void batch.”

Means: The void action failed, usually a temporary or connection problem.

Fix: Try again. If it keeps failing, reload the page and retry.

“Results file is larger than 10 MB. Export the results file again and retry.”

Means: The NDIA bulk results file you chose is over the 10 MB upload limit.

Fix: Re-export a smaller results file from the NDIA portal (for example split by date range) and upload that instead.

“Results file not recognised”

Means: The file could not be parsed, for example because it is empty ("File is empty.") or is missing the ClaimReference or Status column ("Required columns not found: …").

Fix: Check you selected the actual NDIA bulk results .csv export, not a different file, and try again.

“Could not import claim results.”

Means: The import failed to save, usually a temporary or connection problem.

Fix: Try Import again. If it keeps failing, reload the page and retry.

“You do not have permission to push invoices for this provider.”

Means: Pushing to Xero is restricted more tightly than the rest of Payments: only the account owner or an admin can complete it today.

Fix: Ask the account owner or an admin to push the batch.

“You do not have permission to sync Xero payments for this provider.”

Means: Syncing Xero payments is restricted the same way as pushing: only the account owner or an admin can complete it today.

Fix: Ask the account owner or an admin to run Sync Xero payments.

“Xero is not connected for this provider. Connect it in Account > Integrations.”

Means: The Xero connection was disconnected or has expired since the buttons last loaded.

Fix: Reconnect Xero under Account, then Integrations (owner only), then try the push or sync again.

“Pay rate too low: $X.XX/h is below the SCHADS minimum of $Y.YY/h.”

Means: A worker's agreed hourly rate, entered on their Payroll tab, is below the SCHADS award minimum for their stream, classification level and pay point.

Fix: Raise the agreed rate to at least the award minimum, or clear it to let the worker follow the plain award rate.

“SCHADS classification is all-or-none: fill SCHADS stream, Employment type, Classification level, Pay point, Work state and Worker category together.”

Means: Only some of the SCHADS classification fields were filled in for a worker on the bulk import Payroll sheet.

Fix: Fill in every SCHADS field together for that worker row, or leave all of them blank.

“Xero payroll access has not been granted for this connection. Reconnect Xero (the consent must include payroll), and check the organisation has AU Payroll enabled.”

Means: The connected Xero organisation's OAuth consent did not include payroll scope, or the Xero org does not have AU Payroll enabled.

Fix: Reconnect Xero under Account, then Integrations, making sure to approve payroll access during the Xero consent screen, and confirm AU Payroll is turned on in Xero.

“Finalise the week before pushing timesheets to Xero.”

Means: Timesheets can only be pushed to Xero for a week that has already been finalised.

Fix: Finalise the pay week first, then push timesheets to Xero.

“Nothing could be pushed. …”

Means: Every worker in the finalised week failed to match a Xero employee or pay item, or the finalised week has no payable hours at all. The message names the reason.

Fix: Match the named worker's name to a Xero employee (or add the missing pay item in Xero), or check the finalised week actually has payable hours, then push again.

“Enter your current password.”

Means: Changing your password requires your current password and it was left empty.

Fix: Type your current password, then change the password.

“New password must be at least 8 characters.”

Means: The new password is too short.

Fix: Choose a new password of at least 8 characters.

“Passwords do not match.”

Means: The new password and the confirmation do not match.

Fix: Re-enter the same password in both the New password and Confirm password fields.

“Current password is incorrect.”

Means: The current password you entered did not verify.

Fix: Re-enter your current password. If you have forgotten it, sign out and use the password reset link.

“Enter the 6-digit authenticator code.”

Means: Enabling two-factor authentication needs the 6-digit code from your authenticator app.

Fix: Open your authenticator app, enter the current 6-digit code, then verify and enable.

“Role name is required.”

Means: You tried to save an access role without naming it.

Fix: Enter a role name, then save.

“Choose an image file for the logo.”

Means: The file you picked for the workspace logo is not an image.

Fix: Choose a PNG or JPG image (max 500 KB).

“Logo must be 500KB or smaller.”

Means: The logo image is larger than the 500 KB limit.

Fix: Resize or compress the image to 500 KB or less, then upload it again.

“Default GST code is required.”

Means: Invoicing settings need a default GST code and none was chosen.

Fix: Pick a default GST code (P1, P2, or P5), then save.

“BSB must contain exactly 6 digits.”

Means: The bank BSB is not 6 digits.

Fix: Enter the 6-digit BSB, then save.