tario.
Accounting close6 minTario Team

Missing attachments: collecting accounting evidence without chasing unidentified files

Turn incomplete records into specific requests. An example follows a repair report, a missing bank statement and goods without receiving evidence.

'Send whatever is missing' usually produces another folder of unidentified files. To collect accounting evidence, each request should identify the transaction, the missing evidence and the person who can obtain it. Having an attachment proves that a file exists, not that the record is complete. A purchase may have a PDF but no confirmation that the service occurred. A bank screenshot may show a balance without the full period. Stop counting attachments and ask which review question each file answers. That makes the request useful to the recipient and the eventual evidence useful to the accountant.

Define evidence by transaction type

Goods purchases may need supplier documents and receiving evidence. Repairs may need a work report and the responsible employee's acceptance. Bank reconciliation needs the complete statement for the relevant period. Agree an evidence matrix with the accountant and distinguish commercial, banking and fiscal records rather than treating them as interchangeable. This is an operational review procedure, not a universal list of legal requirements or retention periods. If a decision depends on a particular tax rule, verify the applicable requirement separately. The evidence matrix should explain the company's review expectations without pretending every business has identical documentation obligations.

Example: three different gaps before close

A maintenance business preparing September finds three incomplete records. Bill B-642 for CRC 85,000 has an XML but no explanation of the repair. Bank account 02 has a balance screenshot but no complete September statement. PO-208 has a bill for twenty filters but no receiving confirmation. Asking for 'September invoices' will not resolve these different questions. Create a list identifying the record, unresolved question, expected file or confirmation and the person with access to it. Add an agreed response date. The purpose is to make ownership clear while the people involved still remember the transaction.

  • B-642: request the repair report identifying the equipment, completion date and acceptance.
  • Account 02: ask treasury for the September 1 to 30 statement with opening and closing balances.
  • PO-208: ask the warehouse for evidence of twenty filters received or an explanation of the shortage.
  • Record an owner, agreed date and response state for each request.
  • Check the contents before marking a request complete.

For B-642, a useful request says: 'Please provide the repair report for B-642, CRC 85,000, identifying the equipment and when work was completed. We already have the XML; it does not need to be resent'. That avoids collecting another copy of existing evidence. If the manager says the work remains unfinished, the issue changes. It is now a difference between billing and service delivery, not merely a missing attachment. Keep that response and alert the accountant. A checklist should not pressure employees into sending a document that appears complete while the underlying transaction remains disputed.

Inspect the file before linking it

Open the repair report and check the equipment, scope and completeness of its pages. A PDF containing only the first page may omit conditions or signatures. For the bank statement, verify holder, account, currency and period; a movement export without a header may not establish the opening balance. Compare quantities and units on receiving evidence for the filters. Record the conclusion, not just 'received'. If another question remains, keep the case open and specify it in the next request. Reviewing a file on arrival prevents an apparent success today from becoming another missing-evidence problem at final close.

Using Tario's library and attachments

Tario has a company file library and supports uploading evidence or selecting library files to attach to records such as bills, purchase orders, contracts and repairs. A file in a folder is not necessarily linked to the purchase being reviewed. Open the record and check the association. Files uploaded before a document is saved can be linked when the record is created. Use recognizable names such as 'B-642-equipment-17-report' while avoiding unnecessary personal details. Preserve the document's original identity where it matters. The reviewer should be able to find the evidence from the transaction, not only by remembering a folder name.

Removing an attachment from a record does not delete its library file. These are different actions, and the attachment service retains who performed the unlinking. If evidence from another company was uploaded by mistake, inspect where it remains stored and resolve access under your organization's procedure. Library and attachment features do not establish an automatic queue enforcing every item in your evidence matrix. The missing-item list, owners and collection requests described here are a process for your team to organize. Keep product functionality separate from the controls that people must operate and verify themselves.

Search assistance is not verification

Depending on file processing, the library can extract text to help classification and AI search. This can locate a contract by its contents, but inspect the original before treating the result as evidence. Blurred photos and scanned tables may produce incomplete extracted text. A suggested filename does not establish that the file belongs to B-642. Search with a specific reference and confirm the result. Share only the evidence needed for the review and respect company permissions. Sending a whole folder through chat adds exposure and confusion when a single repair report would answer the question.

B-642 is resolved when its report confirms the work and is linked correctly. Account 02 is resolved when the complete statement allows the period to be reviewed. PO-208 needs confirmation of twenty filters or an explained outstanding difference. Record who checked each item and when. If evidence never arrives, retain the accountant's decision and the unresolved exception instead of inventing support. Review recurring gaps weekly and improve initial capture, for example collecting delivery evidence when goods arrive rather than waiting for the close. The useful outcome is a reviewable transaction, not a folder that happens to contain more files.

Sources consulted

Frequently asked questions

Does one attachment mean a purchase is supported?

Not necessarily. It must belong to the transaction and answer the review question. An incorrect or incomplete PDF does not replace the missing evidence.

Does removing an attachment delete the file?

Unlinking it from the record does not delete the library file. Review the association and file management separately, especially after uploading another company's information.

Keep reading

Organize purchase evidence

Explore supplier document reception in Tario and define the evidence your team needs to complete its review.

See supplier XMLs