If you are considering an offshore finance team, this is the page you should read before the pricing. It sets out how access is granted, who uses it, what we will never ask you for, and what we do not claim.
Written for accountants doing diligence on us. If your firm runs a vendor-security questionnaire, send it over — we would rather answer yours than only our own.
The single most important thing about this arrangement is that control of access never leaves your side of the table.
We are added as users in your accounting platform — QuickBooks, Xero, Tally, Zoho — through its own invitation flow. Each of our people gets their own named login; we never work from a shared account.
Permissions are whatever you set them to. If a role does not need payroll visibility or bank feeds, do not grant them. We will tell you the minimum that lets us do the work.
When an engagement ends, you revoke access in your own platform. You do not have to ask us to do it, and you do not have to take our word that it happened.
In your platform, at a permission level you set, issued through the platform's own invitation.
Statements, invoices and supporting records for the work in hand — not a blanket copy of everything you hold.
Someone on your side who can answer a question about a transaction without a week's delay.
User invitations exist so credentials never change hands. Any provider asking you to share a login is telling you something.
We do not move money. We record and report on it. Payment rails stay entirely with you.
Nothing is set up so that removing us requires our cooperation.
Not aspirations. These are the terms an engagement starts on, and you should hold us to both.
We sign a non-disclosure agreement before any of your records — or your clients’ records — reach us.
If your firm has its own NDA, send it and we will sign yours; most firms prefer their own paper and we have no reason to argue. If you would rather we provided one, we will. Either way it is in place before access is granted, not alongside the first invoice.
For firms acting on behalf of their own clients, the agreement covers your clients’ information as well as your own, since in practice that is what we are handling.
Every person who works on your file has their own named account in your system.
We do not use a shared login, and we do not pass one set of credentials between staff. That is what makes the rest of this page meaningful: if each user is named, your platform’s own audit log shows you who opened what and when, without taking our word for it.
It also makes removal clean. When someone leaves the engagement, you remove that user — you are not left wondering who else knew a shared password.
Your records are handled by qualified in-house accountants, with our CA and CMA team behind them for review.
Nothing is subcontracted onward. Your work does not go to a marketplace, a freelancer pool, or a third firm we have an arrangement with. You deal with the same named people each cycle, which is also why they get faster at your file rather than starting fresh.
Where records travel, prefer the platform over email. If you send us statements as attachments, those attachments exist in your mail system and ours; granting platform access instead keeps the records where they already live.
On every US engagement, the return is reviewed and signed by your own CPA or EA.
We organise the records, build review-ready workpapers and get the return to a state where it can be signed. The professional responsibility, the engagement letter and the client relationship stay with you, or with your client's own advisor. We do not represent ourselves as the filer.
It matters here because it tells you what we are: a preparation and bookkeeping team you direct, not an advisor acting on your behalf.
Separate question from client engagements, and a much smaller one.
This is a static site. There is no login, no user account, no database and no API of our own. There is nothing here for an attacker to query.
Submissions post to Web3Forms, which delivers them to us by email. Send an enquiry, not a client's financial records — a web form is the wrong channel for those.
Google Analytics 4 for traffic, and a Tawk.to chat widget. Both are standard third-party embeds; our privacy policy covers what they collect.
Security pages are easy to pad. This one is not padded, and the omissions are the point.
We have not listed certifications, audit reports, encryption standards or retention schedules here, because we would rather tell you precisely what we do than publish a list that sounds reassuring and answers nothing. If any of those are a requirement for your firm, ask us directly and you will get a straight yes or no.
The practical route: send us your vendor-security questionnaire. It asks the questions your firm actually cares about, in the form your risk process expects, and it gets you a specific answer rather than marketing copy.
That access was granted by you, scoped by you, and disappears when you remove it.
Start on one client or a handful of files before anything larger is at stake.
A signed NDA and named-user access, in place before an engagement starts.
Anything above that your own risk process requires. Vague answers are a reason to walk.
Ask them before you send us anything. We would rather answer a hard diligence question than win work on a vague one.
This page describes how we work with client records in practice. It is not a contract, and it does not replace the engagement terms agreed for a specific piece of work. Where this page and a signed engagement letter differ, the engagement letter governs. See also our privacy policy and terms of service.