Home / Accounting sync
Accounting sync
From a logged hour to a draft invoice
Every hour your engineers log against a ticket is already the raw material of an invoice. Helios prices it, rolls it up per client, and pushes it into your accounting package as a draft you approve. Here is the whole path, screen by screen.
The hour is logged where the work happened
Time goes on the ticket, in the two seconds after an engineer finishes a reply. Quick buttons cover the common cases, because a form with a date picker is a form nobody fills in. Each entry carries a note and a billable flag, and the non-billable ones stay visible rather than quietly disappearing.
A real ticket in Helios. Two billable entries, one written up as non-billable.
It rolls up per client, priced at that client's rate
The Billing page is the month's money view. Every client's billable time, their hourly rate, and what that comes to. Set a rate inline. Clients with no rate are flagged rather than silently billed at zero, and the total only appears when every row shares a currency, because a mixed-currency total is a number that lies.
The CSV export is the artefact of record. Line rounding matches, so the invoice total always equals the figure your client was shown.
One month, five clients. The right-hand actions are the accounting sync.
One click raises a draft invoice
Press QuickBooks or Xero on a row and Helios creates a draft invoice for that client and that month: one line per time entry, billed against the service item or revenue account you chose, carrying your tax code or tax rate.
The row then reads Invoiced, so you can see at a glance what has gone across and what has not. Ask for the same client and month twice and Helios stops and asks, rather than quietly raising a second invoice.
Both packages connected, so the row offers both. Connect one and you get one.
You approve and send it, in your own package
Helios leaves the invoice as an unsent draft. You open it in QuickBooks or Xero, check it, and send it yourself. A platform should not be finalising an invoice to a real client on your behalf, so this one does not.
What Helios does, and does not do
The full extent of the permission you are granting.
| Action | In your accounting package |
|---|---|
| Read your customers or contacts | Yes, to map them to your Helios clients |
| Read service items, revenue accounts and tax codes | Yes, so invoice lines are coded correctly |
| Create a draft invoice | Yes, and this is the only thing it writes |
| Send an invoice to your client | Never. You send it |
| Edit or delete anything you already had | Never |
| Read your bank feeds, bills or payroll | Never. It does not ask for those permissions |
| Use your accounting data to train AI | Never. No AI feature touches it |
Setting it up takes about a minute
Connect under Settings, then Accounting. It is the standard Intuit or Xero sign-in, so your credentials never touch Helios. Pick the service item or revenue account your support time bills against, pick your tax treatment, then map each client to a customer or contact once from the Billing page.
Connection tokens are encrypted at rest with the same scheme as the credential vault, and disconnecting keeps your client mappings so a reconnect does not mean doing the whole thing again.
Both cards speak their own package's language: a service item and tax code in QuickBooks, a revenue account and tax rate in Xero.
Stop retyping timesheets into your accounts
Helios is a full RMM and service desk with this built in. Start free, log some time, and push a month across when you are ready.
QuickBooks and QuickBooks Online are trademarks of Intuit Inc. Xero is a trademark of Xero Limited. Helios is not affiliated with or endorsed by either company. Screenshots show a Helios demonstration account with fictional client names.