Why we integrate instead of rebuilding

What you will have

• Why ezCyber meets your accounting software at the invoice instead of rebuilding the ledger, and exactly what crosses that boundary.
• Why there is no screen control of our own, and what runs beside the agent instead.
• Where each kind of record comes from, so nobody plans a migration around the wrong door.
• A straight answer to "why does it not just do that", on one page you can forward without editing it.

Why it works this way

Steps

1. 1

   Why you need an accounting software.

   Every service desk that tried to be the ledger as well ended up asking its customers to keep their books twice. Tax tables change by jurisdiction and by year. Inventory, purchase orders, payroll, expenses and multi-currency books each carry decades of accounting rules and an audit trail your accountant has to be able to defend. A second copy of all of that inside a PSA is not a feature, it is a second set of books to keep in step with the first. So ezCyber runs the operating record and stops at the invoice. The agreements and plans you sell, the time your techs capture as a byproduct of the work, tickets, quotes, and the invoice as it is generated, approved and sent: that part is ours. What happens to that invoice afterwards belongs to the system your accountant already runs. At the boundary, customers, invoices, estimates, items and tax codes sync to QuickBooks Online. Once it is connected QuickBooks owns tax, so the local rate goes read only and you map its tax codes instead. The product catalogue is audited against it, and payment state is read in one direction only, so nothing here ever writes a payment into your books. The same line explains the rest of it. Ordering and provisioning stay in the distributor's own portal, and ezCyber reads the catalogue, the price tiers and each client's licensed quantities so cost and margin sit where the client already lives. Time reports leave as CSV for whatever runs your payroll. Every invoice is stamped with the currency it was billed in, and a total that would mix two currencies is refused rather than guessed, because a converted figure in a book is a figure somebody has to defend later.

   Note: With your own Stripe keys saved and client card capture switched on, a client puts a card on file on your account, on a page that shows the brand, the last four digits and the expiry and no amount at all.
2. 2

   Why you bring a screen control tool.

   A screen session is its own product. The companies that build them do nothing else: codecs, NAT traversal, session recording, and staying usable on a bad hotel connection. A platform that bundles one, or writes a web viewer to tick the box, ships something less efficient than the tools built for that one job, and every shop pays for it in the price whether they use it or not. So ezCyber does not build screen control of its own, and that is the position rather than a backlog item. Everything else about the machine stays in the portal: a live PowerShell or CMD terminal, a file browser, saved scripts, one-click actions, patching, the software inventory, and the Get Support button your users click. Run Splashtop Business or ScreenConnect on the same machines as the agent. The two do not get in each other's way. The Splashtop Business integration is complete: the device page launches the session in the technician's own signed-in Splashtop Business app, so nobody hunts for a machine name in a second console. ezCyber is looking for a ScreenConnect partner to build the same launch.

   Note: The switch on a device labelled Remote control governs remote actions and the terminal for that machine. It does not turn on a screen session, because there is none to turn on.
3. 3

   Why every record arrives from the system that owns it.

   A migration plan that treats the PSA as the source of everything gets the shape of the move wrong. In a real shop the passwords live in the documentation tool, the devices live in the agent and the RMM, the identities live in Microsoft 365, and the invoices live in the accounting system. What the PSA holds is the operating record, plus a pile of copies that went stale the day somebody stopped updating them by hand. So ezCyber reads each record from the system that owns it, rather than from whichever system happened to hold a copy. The PSA import carries the operating record: clients, contacts, technicians, and tickets with their replies and the time logged on them. Invoices, customers, estimates, items and tax codes come from QuickBooks Online. Devices, their hardware and the software installed on them come from the agent, and from NinjaOne where a shop already runs it. Identities, groups, mailbox state and Microsoft security signals come from Microsoft 365 over Graph, on a delta cursor rather than a nightly re-read. Documentation, passwords, procedures, assets, websites and networks come from IT Glue or Hudu. Detections come from Huntress, SentinelOne, Microsoft Defender and ThreatLocker, and licensed quantities and price tiers come from Pax8.

   Note: A vendor password export also loads as a CSV, which is how the one thing no documentation API hands over, the TOTP seed, arrives with the password it belongs to.
4. 4

   Why there is no app marketplace.

   A marketplace is a long tail of connectors nobody owns, and a support call that ends in talk to the plugin author. Every integration on the Integrations page is one ezCyber builds and maintains, around thirty of them across identity, PSA, RMM, security, billing, documentation and AI, which means a broken integration is our bug rather than a listing's. For anything not connected directly, the outbound webhook is the door. It signs every call, carries a finite list of events, and switches itself off after ten failures in a row, so a dead endpoint never becomes a queue of retries nobody is reading.

5. 5

   Using a tool or platform we don't integrate with yet? Contact us because we want to add more integrations.

   Write to [email protected] and name the tool and what you need to move. If it has an API, we can get your data out of it.

The pages behind each click

• Screen control →
• Switching →
• Integrations →
• QuickBooks Online →
• Agreement to invoice →