What should I scrub before sending a screenshot to my accounting software support?

Everything that is not the thing you are asking about. The reconciliation quirk or the error stays readable; the client or company name, the supplier bank details, the salaries, the VAT and tax references, and every adjacent ledger row get scrubbed. Support needs to see the broken behavior, not your client list and not real figures, so cover the rest before the image leaves your Mac.

Is a screenshot of one client's books safe to share with that client?

Only if it shows just their books. The trap is that an accounts package usually lists several clients in adjacent rows, dropdowns and recent-items menus, so a screenshot meant for one client can carry three others in frame. Before you send it, scrub every row, name and reference that is not theirs, and check the corners and account menu for a client switcher.

How do I train staff on real screens without exposing client data?

Capture the screen you want to teach from, then scrub the identifying parts before it goes into the training doc or the shared walkthrough: client names, real figures, bank details and reference IDs. Keep the layout and the busyness intact so the junior still learns the real package, they just cannot read whose data it is. Scrub the value, keep the shape.

Can a scrubbed figure be recovered from the file later?

Not with ScrubShot. The Scrub tool rewrites the underlying pixels, and the blocks it lays down are random samples of the region's colors, not averages of the digits underneath, so there is nothing for depixelation software to work back from. A salary or an account number scrubbed this way cannot be un-scrubbed or brute-forced from the saved image.

← Resources

Screenshot redaction for accountants and finance teams

Short answer: in finance work, client and payroll data is on screen all day, so the screenshots you fire off to a software vendor, a colleague or a client almost always carry more than you meant. The discipline is the same every time, the figure you are pointing at stays readable and every other identifier goes, scrubbed in a way that cannot be peeled back off, because the file ends up in email threads and ticket systems that outlive the question. Here is where screenshots happen in accounting and bookkeeping, what tends to leak on each screen, and the loop that keeps it quick.

Screenshots fly around finance work all day

If you keep the books, a screenshot is one of the fastest tools you have. The trouble is that real client and personal data is the wallpaper of the job, so almost every grab catches something it should not. Think about how often it comes up:

You ask the software vendor about a reconciliation quirk and screenshot the screen that is misbehaving.
You show a colleague a ledger entry that does not add up and ask them to sanity-check it.
A client queries their figures and the quickest answer is a screenshot of their own books.
You train a junior on the accounts package by walking them through a real client file.
You hand a client over at month-end and screenshot where things stand for the next person.

Every one of those is reasonable. None of them is the problem. The problem is that the screenshot captures the whole frame, and in an accounts package the frame is crowded with names, figures and references that belong to people who have nothing to do with the question you are asking.

One client's question, three other clients in frame

The thing that makes finance work different from most jobs is that you hold many clients at once, and the software shows them together. A client emails to query a single invoice, you open their record, screenshot it and send the answer, and without thinking about it you have just shown them the recent-items list with two other clients in it, or the dropdown where you switch between accounts, or the adjacent rows of a shared ledger. You answered one person and exposed three.

The same risk runs the other way for supplier and payroll views. A payroll run lists everyone's salary in one column. A supplier record carries their bank details. An invoice screen shows amounts, VAT and tax references that tie back to a specific business. Send any of those to a vendor or a colleague without scrubbing and the figures travel with the file. Working out exactly which of those fields counts as sensitive is its own subject, and I have set it out field by field in the rundown on hiding bank details and personal information in screenshots.

What leaks on the common finance screens

Here is a quick map of the screens accountants and bookkeepers grab most, what they tend to carry, and what to cover before the image goes anywhere.

Screen	What leaks	What to scrub
Ledger / reconciliation	Adjacent rows, running balances, the client name and reference up top	Every row except the one you are pointing at, plus the client name and any account ID
Payroll run	Names against salaries, tax codes, national insurance and other staff references	The whole pay column and every name but the example you are discussing
Supplier record	Bank details, contact email and phone, invoice amounts, VAT and tax references	The bank fields and references first, then the contact details and amounts
Client dashboard	The client switcher, recent-items list, headline figures and the corner account menu	Other clients in the switcher and the list, the figures, and your own logged-in details

The discipline: keep the number, lose the identity

The rule I would hold to is short. The number or the line you are pointing at stays readable; every other identifier goes. Whoever you are sending it to, the vendor debugging a quirk, the colleague checking your entry, the client reading their own books, needs the one thing the screenshot is about. They do not need the other clients, the salaries, the bank details or the references around it.

And in finance the redaction has to be the kind that cannot be peeled off. A box you draw on top of a figure is a separate layer in a lot of tools, so it can be nudged aside or stripped out, and a soft blur over a short string like a salary or an account number can sometimes be reversed. That matters more here than almost anywhere, because the file does not vanish after the question is answered. It sits in an email thread, a ticket system or a shared drive for years. Pixelating the value straight into the image, so the pixels themselves are rewritten and there is no layer to lift and nothing to compute back from, is the version I trust for anything financial.

The training case deserves its own note. When you teach a junior on a real client file, the screenshot ends up in a doc or a shared walkthrough that lives on, so scrub the names, figures and references but keep the layout intact, the junior still learns the actual package. That is the same instinct as keeping a screenshot believable while removing who it belongs to, which is the territory of anonymizing client screenshots for case studies and demos.

The loop, capture to send

The honest reason finance staff skip redaction is the same as everyone else: when you are mid month-end, saving a screenshot and switching to a separate editor is a detour you will not take. So the redaction has to live in the same few seconds as the capture. With ScrubShot the loop is:

Press the shortcut. It captures the screen you are looking at, the ledger, the payroll run, the supplier record, the client dashboard.
Drag the Scrub tool over the rows, names, figures and references that are not the point. They pixelate into the image as you go.
Check the client switcher, the recent-items list and the corner account menu for another client or your own login, and scrub those too.
Use the Marker to circle the entry you are asking about, or the Text tool to label it, so the reader looks exactly where you want.
Copy the cleaned image to the clipboard or let it save to the ScrubShot folder in your Pictures, then paste it into the email, the ticket or the reply.

Because the Scrub tool rewrites the underlying pixels, a scrubbed salary or account number cannot be recovered from the file later, which is what you want when the image is heading into a thread that outlives the question. If you over-scrub there is Undo, and none of it touches the network, so the only version that leaves your Mac is the cleaned one. That is the whole argument in the guide to redacting screenshots on a Mac without uploading them.

FAQ

What should I scrub before sending a screenshot to my accounting software support?: Everything that is not the thing you are asking about. The reconciliation quirk or the error stays readable; the client or company name, the supplier bank details, the salaries, the VAT and tax references, and every adjacent ledger row get scrubbed. Support needs to see the broken behavior, not your client list and not real figures, so cover the rest before the image leaves your Mac.
Is a screenshot of one client's books safe to share with that client?: Only if it shows just their books. The trap is that an accounts package usually lists several clients in adjacent rows, dropdowns and recent-items menus, so a screenshot meant for one client can carry three others in frame. Before you send it, scrub every row, name and reference that is not theirs, and check the corners and account menu for a client switcher.
How do I train staff on real screens without exposing client data?: Capture the screen you want to teach from, then scrub the identifying parts before it goes into the training doc or the shared walkthrough: client names, real figures, bank details and reference IDs. Keep the layout and the busyness intact so the junior still learns the real package, they just cannot read whose data it is. Scrub the value, keep the shape.
Can a scrubbed figure be recovered from the file later?: Not with ScrubShot. The Scrub tool rewrites the underlying pixels, and the blocks it lays down are random samples of the region's colors, not averages of the digits underneath, so there is nothing for depixelation software to work back from. A salary or an account number scrubbed this way cannot be un-scrubbed or brute-forced from the saved image.

Try it

ScrubShot is a Mac app built for exactly this kind of work: press the shortcut, drag over the rows, names, figures and references you are not pointing at to pixelate them into the image, annotate the one entry you are, then copy or save. The cleaned screenshot is the only version that ever leaves your Mac. There is a free 7-day trial with no card required. After that it is $30 once.

Try ScrubShot free →