Client workspace
Files
Find source files by batch, status, name, archive parent, and linked attachment context.
What this menu does
Provide a read-only client file inventory and processing-state trail for downstream invoice work.
Where to find it
Client workspace navigation: Files.
When to use it
- Find an uploaded source file.
- Review scanning/parsing state and failure reason.
- Trace a file inside an archive or its linked business attachment.
Before you begin
- Open the correct client workspace.
- Confirm the company name shown in the workspace header.
Page regions
- 01Batch, keyword, and status filters
- 02File list
- 03Name, status, source batch, archive parent, linked attachment, upload/processing time
- 04Failure reason
- 05Refresh and pagination
Supported operations
Find and inspect a file
- 1
Enter an upload batch number, file keyword, or status filter.
- 2
Review file name, status, source batch, archive parent, and linked attachment.
- 3
Read the business-safe failure reason when the file is unavailable.
- 4
Use Refresh for in-progress files or Reset filters to return to the full list.
The file and its processing context are identified without changing the file.
Business rules and fields
- The Files page is read-only.
- A file can be present while its invoice is still pending review.
- Archive child files retain parent information.
- Use the invoice pages for invoice-specific recognition, review, and re-upload actions.
States you may see
What happens next
- Staff can trace a source file to its batch and downstream attachment context.
Common problems
The page is view-only or an action is missing.
The workspace is read-only, the employee lacks maintenance access, or the record status blocks changes.
Verify the client lifecycle status and your access with a firm administrator. Do not work around the restriction in another client.
A save, generation, or load action fails.
Business validation, missing source data, an expired session, or a temporary service problem can block the action.
Read the business reason shown on the page, fix the source data, and retry once. Preserve the request identifier when asking support for help.