Document Upload

Route statements and supporting files into the right client workflow and verify what processing creates.

Wesley has several document paths. Choose the path based on the intended result: statement activity in Banking, evidence in Shared Files, or a separate converted export.

Choose the destination first

For bank or credit-card activity, open the client and use Banking > account > Add transactions > Statements.
For checks, use Banking > account > Add transactions > Checks.
For receipts, invoices, bills, and backup documents, use Add transactions > Receipts & Invoices, or organize/request them in Shared Files.
For a file that should be converted or exported without entering a client book, use Document Conversion.

The conversion tool is not a bookkeeping import. Exporting extracted data there does not automatically create client accounts, transactions, or journals.

Upload statement activity

Confirm the selected client, bank or card account, and period.
Compare the intended dates with connected and previously uploaded activity.
Upload related statements together when they belong to the same account and coverage.
Monitor Statements & API for Queued, Processing, Needs review, Complete, or Possible duplicate status.
Preview the account identity, dates, descriptions, signs, amounts, balances, and page coverage against the original.
Correct mapping and duplicate issues before transaction review.

Processing adds source activity; it does not prove that every row is unique, correctly coded, or posted. Continue through Add Data and Transaction Review.

Receipts, invoices, bills, and other backup files are stored in Shared Files. Wesley can suggest an existing transaction to link or prepare an unmatched document for review. Confirm the relationship before accepting it so the document does not produce a second posting for an existing expense or revenue item.

When evidence must come from the client, create a clear request through Client Work: name the document, account, period, and deadline. Review responses and attachments from the same item.

Verify the result

Before leaving the workflow, record:

which files were uploaded and their source;
the account and exact date range covered;
processing or review status;
possible duplicates or missing pages;
which transactions, journals, reconciliations, or client work items use the evidence.

Correct mistakes safely

Do not immediately re-upload a slow-processing statement; it can create duplicate candidates. If the wrong account or period was selected, stop review and correct the mapping before posting.

Unlink a mistakenly attached support file before linking it to the right record. Deleting a processed statement is permanent: Wesley first unposts all posted transactions imported from that statement, then deletes every transaction imported from it and removes the processed source. A closed period or another failed unpost blocks the statement deletion. Review the entire imported batch and preserve required evidence before confirming.

Common problems

Extraction totals do not match. Check missing pages, account identity, date range, amount signs, and opening/ending balances.

The same rows came from two sources. Compare dates, descriptions, amounts, and coverage. Match, exclude, or correct the duplicate source rather than posting both.

The client uploaded a file but it is not in Banking. A Shared Files upload is evidence, not necessarily a statement import. Route the document through the appropriate Banking flow.

A file is complete but rows remain uncategorized. That is expected. Processing and posting are separate stages.