Document Upload

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

1. Confirm the selected client, bank or card account, and period.
2. Compare the intended dates with connected and previously uploaded activity.
3. Upload related statements together when they belong to the same account and coverage.
4. Monitor Statements & API for Queued, Processing, Needs review, Complete, or Possible duplicate status.
5. Preview the account identity, dates, descriptions, signs, amounts, balances, and page coverage against the original.
6. 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.

For a completed statement, View opens the document preview modal with the original and imported transactions. Scroll through the PDF pages, or hover over a transaction to see its source location when available. The table keeps the amount and status visible alongside the description. Amount verified indicates that statement debit and credit totals match. When a statement has unresolved extraction issues, Review opens the same full-size PDF-and-transactions layout in Banking. When a statement's printed totals differ from the transaction totals only because refunds or reversals offset other activity inside those totals, the footer shows a second Statement totals line with each printed total and a check mark. Otherwise the footer shows one Totals line.

Uploaded file rows have no individual Delete button. To discard eligible uploads before import, select their checkboxes and use Delete above the list. Deletion requires edit permission.

When review is needed, the file list explains whether the issue affects the file or specific transactions. Questions about the whole file appear in the Statement section above the Transactions table, together with the statement account when it needs confirming. When an affected transaction can be identified, its row is shaded and shows the reason and a question. Use Needs review and All to switch between the affected rows and the remaining activity, or edit the affected row directly.

Answer from the original statement, or edit the cell directly. Below the totals, the bar shows how many issues are left; the count drops as you answer a question, choose the statement account, or delete an affected row. After you enter an answer, Apply N answers appears; it sends every answer you entered in the Statement section and the table to update the extracted values. If an answer is incomplete, Wesley asks for the missing detail. Check the corrected values, then choose Confirm & finalize to continue processing. Answers do not change registered transactions; those must be edited in Banking.

Upload supporting evidence

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.