Should Client Invoices and Bank Statements Go to Cloud Portals?

What actually happens to an uploaded file

A common pattern: a firm receives a client's bank statement as a PDF, finds an online tool that turns PDFs into spreadsheets, and uploads it. It works, it is quick, and everyone moves on.

Most of the time nothing goes wrong. But a few things are worth noticing:

• The file has now left your computer and sits on someone else's servers.
• You may not know where those servers are, how long the file is kept, or who at the vendor can see it.
• The client may not know their statement went there.

A bank statement shows balances, counterparties, salaries and personal spending. A vendor invoice shows pricing and terms the client may regard as commercially sensitive. These are the client's documents, shared with you to do a specific job.

The authorization question

Here is the part we think deserves a calm look. Did the client agree to their documents being uploaded to a third-party portal?

In many firms the honest answer is "we did not ask." The client authorized the firm. That does not automatically extend to every online tool the firm chooses to use. Your engagement letter, your client contracts and the law that applies to you may say something about this. We are not lawyers and this is not legal advice, so the practical step is to read what you have actually agreed with clients and ask your own adviser if unsure.

Why this matters to the firm, not only the client

If an online service has a data incident, the affected files include your clients' documents. The client's first question is not likely to be for the vendor. It is likely to be for the firm that uploaded them.

That puts the firm in a position of explaining why the files were there and whether the client had agreed. We do not raise this to alarm anyone. Most services handle files responsibly. It is simply a reason to make the choice deliberately rather than by habit.

Questions worth asking about any portal

Before the next upload, a short list helps:

• Where is the file processed and stored?
• How long is it kept, and can it be deleted on request?
• Is the content used for anything beyond producing your output?
• Who at the vendor can open it?
• Did our client agree, in writing or otherwise, to this kind of processing?

If a vendor cannot answer these in plain sentences, that is useful information.

How we approach it

Our automation is a script built around your workflow, and by default it runs on your own device. Invoices and statements are read from a folder on that machine, and the output files are written back to it. The files are not uploaded to a portal as part of a normal run.

We would not describe that as a promise about every possible situation, and we do not claim it removes every risk. Some workflows do connect outward when there is a reason to. Examples:

• Reading master data from a read-only internet endpoint, such as a vendor list kept online.
• Making public lookups to enrich a record, for instance checking a publicly available detail.
• Sending a payload to another system, if you ask for the output to go there.

When a workflow does any of these, we say so when we scope it, and we describe what is sent and where. If your policy is to keep a particular type of document off the network, we design around that and tell you if something has to change.

For a longer look at this, see our post on what leaves your computer during extraction.

Local does not remove your own responsibilities

Running on your device means the files stay under your own controls: your backups, your access permissions, your laptop security. Those still need care. A local script does not make an unlocked, shared PC safe. What it does is cut down the number of outside parties that hold your clients' files.

If you want to talk through what your own workflow would read, what stays on the machine and what would need an outside connection, you can show us your workflow. You can list the documents, the monthly volume and a sample in the document automation assessment.

FAQ

Is it safe to upload client bank statements to an online PDF tool?

It depends on where the tool stores files, how long it keeps them and whether your client agreed. Ask the vendor those questions before uploading.

Does your automation upload my files anywhere?

By default it runs on your own device and reads and writes files locally. A workflow connects outward only when it needs to, and we describe each connection when we scope it.

Do I need my client's permission to use a third-party portal?

Your engagement terms and applicable law may speak to this. We are not legal advisers, so check what you have agreed with clients and consult your own adviser.