Phase 5 – Documentation Standards
Lesson 1 – Supporting Documentation, File Management & Audit Readiness
Learning Objectives
By the end of this lesson, the Junior Bookkeeper will be able to:
- Understand the importance of maintaining complete supporting documentation.
- Explain Eagleeye’s audit-ready documentation standards.
- Identify acceptable supporting documentation.
- Recognize when additional documentation is required.
- Properly organize client files within Dropbox.
- Understand Eagleeye’s file naming standards.
- Correctly attach supporting documentation within QuickBooks Online.
- Recognize common documentation errors.
- Apply Eagleeye’s research process before requesting missing documentation.
Why This Matters
One of Eagleeye’s core values is maintaining Audit Ready bookkeeping.
Every transaction entered into a client’s books should be supported by documentation whenever reasonably available.
Complete documentation benefits everyone involved.
It allows:
- Faster month-end processing.
- Easier year-end reviews.
- Better client communication.
- Reduced accounting costs.
- Stronger CRA compliance.
- Faster responses to client questions.
- Improved internal quality control.
A transaction without supporting documentation often creates uncertainty, delays, and unnecessary follow-up work.
Our objective is to maintain complete, organized, and easily accessible records that accurately support every accounting transaction.
What is Supporting Documentation?
Supporting documentation is the evidence that explains a financial transaction.
It answers the questions:
- What was purchased?
- Who was the supplier?
- When did the transaction occur?
- How much was paid?
- What taxes were charged?
- Why was the purchase made?
Supporting documentation allows another person to understand the transaction without making assumptions.
Acceptable Supporting Documentation
Examples of acceptable documentation include:
- Supplier invoices
- Sales invoices
- Cash register receipts
- Credit card receipts
- Purchase contracts
- Loan agreements
- Lease agreements
- Bank deposit records
- Payroll reports
- Government notices
- Online purchase confirmations (when sufficient detail is provided)
Whenever possible, original documents should be retained.
Documentation That May Not Be Sufficient
Some records alone do not provide enough information to properly support a transaction.
Examples include:
- Bank feed descriptions
- Credit card statements
- Bank statements
- Screenshots showing only payment amounts
- Interac or e-transfer confirmations without supporting invoices
These documents may confirm that money moved but often do not explain what was purchased.
Whenever possible, additional documentation should be obtained.
Eagleeye Documentation Standard
Our expectation is simple:
Every transaction should be supported by documentation whenever reasonably available.
If documentation is missing:
- Review existing client files.
- Search previous correspondence.
- Review historical uploads.
- Determine whether documentation may already exist elsewhere.
- Follow the Document Request SOP if additional information is required.
Our objective is to minimize unnecessary requests while maintaining complete records.
QuickBooks Online Attachments
Whenever documentation is available, it should be attached directly to the QuickBooks transaction whenever practical.
Benefits include:
- Faster file reviews.
- Reduced year-end questions.
- Easier client support.
- Improved audit readiness.
- Centralized documentation.
The accounting record and its supporting documentation should remain connected whenever possible.
Dropbox Organization
Dropbox serves as Eagleeye’s central document storage system.
Proper organization allows every team member to locate client documents quickly.
Documents should always be saved:
- In the correct client folder.
- Using consistent naming conventions.
- In the correct processing stage.
- Without creating duplicate copies.
Consistent organization reduces errors and improves team efficiency.
File Naming Standards
File names should clearly identify the contents of the document.
A good file name allows another team member to understand the document without opening it.
Whenever possible, include:
- Date
- Supplier name
- Document type
Avoid vague names such as:
- Scan001.pdf
- Receipt.pdf
- Document.pdf
- Image123.jpg
Clear naming improves searching, filing, and year-end review.
Duplicate Documentation
Before saving any document:
Confirm that it has not already been uploaded.
Duplicate files:
- Increase storage.
- Create confusion.
- Slow file reviews.
- Increase processing time.
Always search the client’s folder before saving another copy.
Missing Documentation
Sometimes documentation cannot immediately be located.
Before requesting documents from the client:
- Review Dropbox.
- Review QuickBooks attachments.
- Review previous email correspondence.
- Review prior bookkeeping periods.
- Determine whether similar documentation already exists.
If documentation still cannot be located, follow Eagleeye’s Document Request SOP.
Our goal is to minimize unnecessary requests while ensuring bookkeeping remains complete.
Documentation and GST
Supporting documentation is especially important when claiming GST Input Tax Credits.
Without sufficient documentation:
- Tax treatment may be uncertain.
- GST may not be recoverable.
- Additional client clarification may be required.
- Year-end adjustments may become necessary.
Documentation supports both financial reporting and tax compliance.
Common Documentation Errors
Saving Documents in the Wrong Client Folder
Incorrect filing creates delays and increases the risk of processing the wrong information.
Always verify the client before saving any document.
Using Poor File Names
Generic file names make future searches difficult.
Every file should clearly identify its contents.
Failing to Attach Available Documentation
If supporting documentation is available, it should be attached to the accounting transaction whenever practical.
Keeping documents connected to transactions improves future reviews.
Requesting Documents Without Research
Always perform reasonable research before contacting the client.
Many documents already exist within:
- Dropbox
- QuickBooks
- Historical client files
Research first.
Request second.
Keeping Local Copies
Documents should be stored within Eagleeye’s approved systems.
Avoid maintaining local copies of client documentation unless required temporarily during processing.
This protects client information and ensures the entire team works from the same records.
Audit Ready Philosophy
An Audit Ready file allows another qualified bookkeeper or accountant to understand the client’s books without additional explanation.
Every transaction should answer:
- What happened?
- Why did it happen?
- What documentation supports it?
- How was it recorded?
- Can another person verify the transaction independently?
If the answer to any of these questions is no, additional work may still be required.
Eagleeye Research Standard
Before requesting documentation from a client:
- Review Dropbox.
- Review QuickBooks attachments.
- Review previous bookkeeping periods.
- Review previous client communications.
- Confirm documentation does not already exist.
- Explain your reasoning before escalating questions.
Our expectation is thoughtful investigation before creating additional work for the client.
Competency Checklist
Upon completion of this lesson, the Junior Bookkeeper should be able to demonstrate the following competencies:
□ Understands Eagleeye’s Audit Ready philosophy.
□ Identifies acceptable supporting documentation.
□ Recognizes insufficient documentation.
□ Properly stores documents within Dropbox.
□ Uses Eagleeye file naming standards consistently.
□ Attaches supporting documentation within QuickBooks when appropriate.
□ Performs reasonable research before requesting missing documents.
□ Recognizes common documentation errors.
□ Understands how documentation supports GST compliance.
□ Maintains organized, complete, and easily accessible client records.