Frequently asked questions

Not in v1. Connect Zero for Timesheets reads from ConnectWise time entries as the source. If you run a different time tracker, Hubstaff, Toggl, Harvest, or a custom system, talk to us about your setup. A Hubstaff connector is on the roadmap for a future release. For now, the supported source is ConnectWise.

Yes. Only approved time entries sync. Draft, pending, and rejected entries stay in ConnectWise and skip the sync. If your ConnectWise workflow requires a manager approval before time leaves the tech's hands, that flow is honoured. The compliance dashboard distinguishes "logged but not approved" from "not logged" so you can spot where the bottleneck sits.

Yes. Per-staff mapping decides which Xero org each member's hours land in. Common case is a multi-site MSP with separate Xero books per office. Set the mapping at setup, bulk-import via CSV if you are onboarding many staff, and edit individual mappings when staff move between entities. Changes apply from the next cycle.

ConnectWise: a dedicated integration user with public + private API keys, scoped to time-entry read, member read, and pay-period read. Xero: an OAuth-2 connection with payroll.timesheets and payroll.employees.read scopes. For SMS reminders: your own Twilio account SID, auth token, and sending number. All credentials are encrypted at rest. You can revoke from the source system at any time and Connect Zero stops syncing on the next cycle.

No. Twilio is required only if you want SMS reminders. Without Twilio, email reminders work the same way, same threshold, same schedule, same content. You can start without SMS and add Twilio later when you are ready. The bulk of the product (entry sync, compliance reporting) works fully without SMS.

Yes. Public holidays are calendar-aware. South Australian holidays load by default, and any of the other Australian state calendars (NSW, VIC, QLD, WA, TAS, NT, ACT) can be enabled in a click depending on where your team is based. You can also add your own custom dates per tenant for things like Christmas shutdowns, conference weeks or single-site events. Expected hours adjust automatically for each blackout day so the compliance dashboard stays honest.

It does not. Super, PAYG, and leave calculations stay in Xero. Connect Zero's job is to land the right hours on the right timesheet in the right pay period. Once the hours are in Xero, your payroll administrator runs the pay using Xero's payroll engine, which handles super, PAYG, leave accruals, and ATO reporting. We never touch the pay run itself.

The next sync cycle replays the edit. The Xero timesheet is updated to match the latest approved state in ConnectWise. Nothing gets dropped. The audit log records the original entry, the edited entry, and the timestamp of each. You can trace any change back through the log.

Connect Zero retries on the next cycle and the next, with exponential back-off. Xero outages are rare and usually resolve within minutes; multi-hour outages roll into the next regular cycle and catch up automatically. The audit log records every retry attempt. You see the status on the dashboard in real time.

Yes. Both products run on the same tenant. Each has its own setup, its own dashboard, and its own pricing tier. They share the same auth, the same Xero connection, and the same ConnectWise connection (you only configure ConnectWise once). Most customers who run both products do so under a single tenant.

Per-staff metered, with a base monthly fee. Three tiers covering 5 to 50 staff and up. AUD only, billed via Stripe through the dashboard. See the pricing page for current rates. A 30-day trial is free, no credit card required.

Yes. The trial is no-credit-card. Once you are on a paid tier, cancel any time from the dashboard. No annual lock-in, no cancellation fee. Your data is exportable to CSV up to 90 days after cancellation, then purged from our systems.