PingtailWrong documents: why you ask twice, and how to stop
Most chasing is not about missing files. It is about files that arrived wrong. How to catch them at the moment of upload.
Ask a bookkeeper what slows the monthly close and the answer is "clients do not send their documents". Look at one month of email threads and you often find something different. The client did send something, usually quickly. It was the July statement for an August request, or a screenshot of the transactions, or the first two pages of six. Nobody noticed for ten days.
That is the wrong-document problem, and it is rework, not chasing. Reminders do not fix it, because the client believes the job is done. If your firm often asks for the same file twice, this page is for you: the six ways a document arrives wrong, what it costs, why it happens, and three fixes in order of effort.
The six ways a document arrives wrong
Most unusable files fall into six groups. Each has its own cause, and its own sentence in the request that prevents it.
| What arrives | A typical case | Why the client did it |
|---|---|---|
| Wrong month | You ask for August on 2 September. The client sends the newest statement in online banking, which is July, because August is not published yet. | "The latest statement" and "the August statement" are the same thing in the client's mind. |
| Wrong account | Harbour Cafe has a checking account, a savings account and a card with the same bank. You receive savings. | The request said "bank statement". The client chose one. |
| Transaction list instead of a statement | A CSV export, or a screenshot of the activity page, with no opening balance, no closing balance and no account holder. | It is what the banking app shows first, and it looks like the same information. |
| Missing pages | Pages 1 and 2 of 6. The summary page is there. The transactions are not. | The client scanned what looked important, or the scanner stopped. |
| Unreadable photo | A paper statement photographed at an angle on a dark table. The amounts cannot be read. | It looked fine on a phone screen. |
| Locked PDF | A payroll report or bank statement that asks for a password on opening. | The provider sent it that way, and the client knows the password. |
What a wrong file costs
Seeing that a file is wrong costs a minute. The real cost is the second request cycle, in four parts.
- The discovery delay. In many firms nobody opens the file until the work starts. A file that arrived on day 2 is found wrong on day 14.
- A new round trip. You write to explain. The client reads it some days later, looks for the document again, and sends it. This second cycle can take as long as the first, because the client considered the task finished.
- Your schedule. That client's close moves out of its slot and competes with the clients who were on time.
- The relationship. The client did what you asked, quickly, and is now told it was wrong. If the explanation is vague, the next file is wrong too.
Count it in your own firm: take last month's follow-up messages and mark each one "nothing had arrived" or "something arrived but was not usable". That count, not an industry percentage, tells you which problem to work on.
Why do clients send the wrong document?
Two reasons cover almost every case, and neither is carelessness.
The client cannot tell. You see at once that a transaction list is not a statement. A cafe owner sees a page from the bank with August on it. The difference that matters to you, the opening and closing balance, a complete period, every page, is invisible to someone who never reconciles an account.
The request did not say. "Please send your bank statements for August" leaves the account, the format and the exact period to the client. Most requests are written by people who know what they mean, for people who do not.
A smaller reason is timing: if the bank publishes on the 5th, a request on the 1st invites the July statement.
Fix 1: better request wording
This costs an hour, once. Rewrite your standard items so each one names the document, the account, the period and the format, says where to find it, and says what is not enough.
| Instead of | Write | Prevents |
|---|---|---|
| Bank statement | Business checking account ending 4471: the full statement for 1 to 31 August. | Wrong account, wrong month |
| August statement | The statement that ends on 31 August. If your bank has not published it yet, please wait until it has. The July one will not help us. | Wrong month |
| Bank transactions | The statement PDF from Statements or Documents in online banking. A transaction list or screenshot is not enough, because we need the opening and closing balances. | Transaction list |
| Send the statement | Please send all pages, including the ones that look empty. The first page says how many there are. | Missing pages |
| A copy of the invoice | A PDF if you have one. If you take a photo: flat on a table, good light, the whole page in the picture, one photo per page. | Unreadable photo |
| Payroll report | The August payroll summary from your payroll provider. If the PDF asks for a password, please send a copy without one, or print it to a new PDF first. | Locked PDF |
Save the new wording where the team copies from. Ready wording for the usual monthly items is in the document collection checklist; statements get their own bank statement checklist.
Fix 2: a receiving routine
This costs a few minutes a day. Better wording reduces wrong files but does not end them, so the second fix shortens the discovery delay from weeks to one day.
- Name one person who opens every incoming file within one working day, not to do the work, only to check it.
- Give them a four-point check: right account, right period, all pages, readable. Under a minute per file.
- A wrong file goes back the same day with a note, while the client still remembers where they found it.
- A right file is marked received in the tracker, so the next reminder does not ask for it again.
The routine fails in busy weeks, when it matters most, so give it a fixed time: the first twenty minutes of each day, say. The full procedure, with roles and statuses, is in the document chase SOP.
Fix 3: check at the moment of upload
The best moment to catch a wrong file is while the client is still looking at it. They are logged in to the bank, the right statement is one click away, and the fix takes a minute. A day later, the same fix takes a new email, a new login and a new decision.
Email cannot do this, and neither can a person, unless they sit and wait for uploads. It needs an upload page that reads the file and answers at once: "this statement covers July, and the request is for August". This is the highest-effort fix, because it means a tool and not a habit. It is also the only one that removes the second cycle, the expensive part of the wrong-document problem.
A check at upload should warn, not block. Sometimes the client is right: the account opened on 12 August, so the statement starts there. The client needs a way to say "this is correct, send it anyway", and a person at the firm decides.
What a good "please fix" message says
A fix message has one job: the next file is right. It needs four parts, in this order: thanks, because the client did act; what arrived, so they know you looked; what you need, in the same words as the request; and where to find it. Leave out the word "wrong", and leave out everything about other items.
Subject: One small fix for [period]: [document name]
Hi [first name],
Thank you for sending the [document name] so quickly.
The file we received is [what arrived, for example: the statement for 1 to 31 July]. For your [period] books we need [what is needed, for example: the statement for 1 to 31 August, all pages].
You can find it here: [where, for example: online banking, Statements, then August 2026]. If it is not there yet, reply and tell me, and we will wait for the bank.
Everything else you sent is fine. This is the only open item.
Thanks,
[your name]
[firm name]
Wording for other situations is in the email templates for missing client documents.
Questions
Is it not faster to fix a wrong document yourself?
Sometimes. If you have read-only bank access, downloading the statement yourself is faster than any message. But you cannot rebuild a statement from a transaction list, read a blurred photo, or open a locked PDF without the password. Fix it yourself when it takes a minute, and still tell the client what to send next time.
What if the client insists the file is correct?
Look again, because they may be right: a new account with a short first period, a card that closed mid-month, or a bank that prints statements from the 15th to the 14th. If so, accept the file and change the item wording for that client. If not, explain once more, pointing to the date that shows the difference.
Can you ask clients to check their own files before sending?
One line helps a little: "before you send, check that the first page shows August and the account ending 4471". A long pre-send checklist makes the request harder to act on, and the people who read checklists are not the ones sending the July statement. Clear wording and a same-day check do more.
Doing this with Pingtail
Pingtail does the third fix. Each upload is checked at once, on the same page and normally in seconds, for a password-locked PDF, missing pages, the wrong period or tax year, and a photo that is too small or too blurred; when fixed rules cannot decide, the check reads the document for its type and period. The check never rejects a file: the client can answer "This is correct, send it anyway", and it reaches you with a flag. Only a person at your firm can send a file back, and the client gets your note by email at once. The details are on the upload checks page. You can try it on yourself first: send a test request to your own email and upload the wrong file on purpose.