# AI Help And Docs Search (/docs/ai-help) ## Search The Docs Use the search control in the docs header to find product guides by workflow, feature, or accounting task. ## AI-Readable Sources The docs publish machine-readable text for future AI answer flows: * `/llms.txt` lists the available docs pages. * `/llms-full.txt` contains the full docs text. * `/docs/.md` exposes a single page as Markdown. ## Intended Answer Behavior An AI docs assistant should answer from the published documentation, cite the relevant page, and avoid claiming account-specific facts unless it has authenticated product context. # Getting Started (/docs/getting-started) ## Product Map Wesley is organized around the accounting workflow: * Firm setup and client list management. * Client setup and source data. * Bank and card transaction review. * Automation with AI suggestions, rules, and Autopilot. * Client requests, shared files, communications, and portal access. * Reconciliation, journals, period locks, and reports. * Integrations, team access, billing, and audit controls. ## Start With Your Question * New to Wesley: open [Work through a client book](/docs/workflows/client-book) to see the major screens. * Creating or importing clients: use [Client onboarding](/docs/workflows/client-onboarding). * Connecting banks, QuickBooks, or uploaded statements: use [Document upload](/docs/workflows/document-upload) and [Integrations and admin](/docs/workflows/integrations-admin). * Reviewing bank activity: use [Transaction review](/docs/workflows/transaction-review). * Reconciling or reporting: use [Close and reports](/docs/workflows/close-and-reports). * Waiting on a client answer or file: use [Client collaboration](/docs/workflows/client-collaboration). ## Firm Workspace The firm workspace is the top-level view for clients, firm settings, team members, billing, and portfolio-level queues. Use it to create clients, import client lists, filter client work, review client-level status, and open firm settings. ## Client Book A client book is the firm-side workspace for one client. It contains bank and card accounts, transactions, client work, shared files, communications, reports, journals, accounting lists, integrations, and client-specific settings. ## First Setup Decisions Before creating or opening a client, confirm: * The client name and ownership inside the firm. * Whether source data comes from QuickBooks, Plaid, uploaded statements, imported ledger data, or fresh setup. * Whether the client needs portal access or must authorize an integration. * The first period or cleanup scope. * Whether classes, locations, chart of accounts, and reporting categories are already known. ## Review Before Posting Wesley can suggest accounts, vendors, filters, rules, and next steps. Keep accounting-impacting changes explicit, reviewable, and tied to source evidence. # Wesley Docs (/docs) Wesley helps accounting firms run client bookkeeping work from setup through source data, transaction review, automation, reconciliation, reporting, and client follow-up. ## Start Here * [Getting started](/docs/getting-started): Choose the right guide and understand the product map. * [Work through a client book](/docs/workflows/client-book): Find the next screen or button inside a client workspace. * [Client onboarding](/docs/workflows/client-onboarding): Create clients, choose a source data path, and verify setup. * [Document upload](/docs/workflows/document-upload): Upload statements, create bank accounts, and review extracted activity. * [Transaction review](/docs/workflows/transaction-review): Find, categorize, ask about, match, transfer, post, and automate bank activity. * [Close and reports](/docs/workflows/close-and-reports): Reconcile accounts, review journals, lock periods, and build report packages. * [Client collaboration](/docs/workflows/client-collaboration): Use the client portal, shared files, work items, and communications. * [Integrations and admin](/docs/workflows/integrations-admin): Manage integrations, QuickBooks sync, firm members, automations, and audit controls. ## Reference * [Connecting bank accounts](/docs/reference/connecting-bank-accounts): Connect bank and card accounts through Plaid and troubleshoot common issues. * [Transaction categorization](/docs/reference/transaction-categorization): Understand suggestions, reviewer responsibilities, and when to ask the client. * [QuickTool for QuickBooks Online](/docs/reference/quicktool-for-quickbooks-online): Use a focused path for QuickBooks Online-related review. ## Normal Workflow 1. Create or select the client. 2. Choose the source of truth: live connection, uploaded statements, imported ledger data, or fresh start. 3. Verify accounts, integrations, owners, and client access. 4. Review bank and card activity, then post, ask, match, transfer, exclude, or rule. 5. Use client work, shared files, and communications when evidence is missing. 6. Reconcile accounts, review journals, lock periods, and run reports. 7. Package client reports or return to settings when access, source data, or audit history affects the work. ## AI-Readable Docs This documentation is also exposed through: * [/llms.txt](/llms.txt) * [/llms-full.txt](/llms-full.txt) * Per-page Markdown, for example [/docs/getting-started.md](/docs/getting-started.md) ## Need Help Use the in-app support chat when product behavior is unclear. For account or connection issues, include the firm, client, affected integration or account, and the exact error or screen state. # Connecting Bank Accounts (/docs/reference/connecting-bank-accounts) ## Supported Institutions Wesley connects to bank and card accounts through Plaid. Supported institutions include major US banks, regional and community banks, credit unions, business banking platforms, credit card issuers, and many investment institutions. ## Connect An Account 1. Open the client integrations or bank connection flow. 2. Choose Connect Account. 3. Search for the bank or credit union. 4. Complete the Plaid authorization steps. 5. Choose the checking, savings, credit card, or other accounts to sync. 6. Return to Wesley and confirm the connected accounts appear in the client book. ## What Syncs Connected accounts can provide account name, type, institution, current balance, transaction history, and connection status. Transaction history coverage depends on the institution and connection. ## Multiple Accounts Use separate connections or account selections when the client has multiple institutions, multiple business accounts, or a mix of checking, savings, and credit card accounts. ## Troubleshooting If login fails, verify credentials directly with the bank, check whether the bank requires additional security steps, and retry when the bank is available. If an account is locked, the client may need to unlock online banking access with the institution. ## Disconnecting To stop future syncs, open the integration or account connection page, find the relevant connection, disconnect it, and confirm the action. Existing accounting records should be reviewed before deleting or changing downstream work. ## Security Bank connections use Plaid authorization and token-based access. Wesley should not need direct storage of banking passwords. Disconnect any suspicious connection and contact support if unusual activity appears. # QuickTool For QuickBooks Online (/docs/reference/quicktool-for-quickbooks-online) ## Purpose QuickTool is used when QuickBooks Online data or workflow support needs a focused entry point. Use it for tasks related to connecting, reviewing, or preparing QuickBooks Online context for Wesley workflows. ## Before You Use It Confirm the client, QuickBooks Online company, required access, and intended result. Do not connect or change a QuickBooks company unless the firm and client have approved that source of truth. ## Common Use Cases * Review whether QuickBooks Online is the source data path. * Connect or inspect QuickBooks Online integration status. * Compare source-system records against Wesley review state. * Prepare data for transaction review, journals, reports, or reconciliation. ## Check Before You Leave The QuickBooks Online connection or review path should have a clear status and next owner. If authorization is blocked, send a client request or document the next support action. # Transaction Categorization (/docs/reference/transaction-categorization) ## How Suggestions Work Wesley reviews merchant names, transaction descriptions, amounts, frequency, prior decisions, and available accounting context to suggest categories, vendors, customers, accounts, classes, locations, or posting actions. ## Reviewer Responsibilities AI suggestions are starting points. Reviewers should verify the source transaction, business purpose, account impact, vendor or customer, period, class, location, and any available evidence before posting. ## Improve Accuracy When a suggestion is wrong, correct the transaction and use rules only for patterns that are narrow and repeatable. Clean vendor, customer, and account lists make future suggestions more reliable. ## Common Categories Common transaction outcomes include office supplies, software subscriptions, travel, transportation, marketing, professional services, payroll-related activity, loan payments, transfers, owner activity, and uncategorized items that require client context. ## When Not To Guess Ask the client or request support when the transaction purpose is unclear, the source document is missing, the amount is unusual, the merchant name is ambiguous, or the same row could reasonably map to more than one accounting treatment. # Accounting Operations (/docs/workflows/accounting-operations) ## Payables Open Payables when the client has bills, checks, or A/P records to manage. Use Write Check for manual checks, complete the fields, and save the record back to the client book. ## Receivables Open Receivables when the client has invoices or A/R records to manage. Use New Invoice, complete the invoice fields, and save it back to the client book. ## Fixed Assets Open Fixed Assets when assets and depreciation need review. Add assets with the required purchase, account, and depreciation context so they appear in the depreciation schedule. ## Mileage Use Mileage for reimbursable or deductible trips. Add trips, review vehicles, and keep mileage settings current. ## Recurring Journal Entries Use recurring entries for predictable journal activity. Review the schedule, accounts, debits, credits, and memo context before relying on automation. ## Vendors, Customers, And Accounts Keep vendors, customers, chart of accounts, classes, and locations clean. Transaction coding, reports, and automation quality depend on these lists. ## Check Before You Leave Operational records should support the close. Payables, receivables, assets, mileage, recurring entries, vendors, customers, and accounts should be ready before reconciliation, journals, and reports. # Work Through A Client Book (/docs/workflows/client-book) ## What A Client Book Contains A client book is the firm-side workspace for one client. Use it to review bank activity, manage accounting lists, request client context, reconcile accounts, run reports, and review client-specific settings. ## Start From The Client Book Home The client book home centers on bank and card accounts. From there, open transaction review, client work, reports, accounts, integrations, shared files, communications, or settings. ## Review Bank Activity Open Bank Transactions when new bank or card activity needs coding. Use Add Transactions for missing data, filters and columns to narrow the table, row actions to post or ask, and feed tabs to switch views. ## Add Transaction Data Use Add Transactions when source data is missing. Upload Documents sends statement files into processing. Connect Bank starts the bank connection path. ## Work With Accounting Lists Use Vendors, Customers, Chart of Accounts, Classes, and Locations when transaction coding depends on clean master data. Keep these lists clean before large review or automation runs. ## Use Client Work And Shared Files Use Client Work to manage questions and tasks sent to the client. Use Shared Files to request, receive, organize, and link supporting documents. ## Reconcile, Close, And Report Open Reconciliation after transaction review is done. Review journals before close, lock the period when review is complete, then run financial reports or build a client report package. ## Review Client Settings Use Settings when access, assignments, accounting setup, integrations, audit history, or danger-zone actions affect the work. ## Normal Client Book Loop 1. Start at the client book home. 2. Bring in missing source data. 3. Review and post transactions. 4. Create rules for repeat patterns. 5. Use client work, shared files, and communications when context is missing. 6. Handle A/P, A/R, fixed assets, mileage, vendors, customers, and accounts as needed. 7. Reconcile accounts, review journals, lock periods, and run reports. 8. Check settings when access, setup, or audit history affects the work. # Work With Clients And Documents (/docs/workflows/client-collaboration) ## When To Use This Workflow Use client collaboration when accounting work is blocked by a missing answer, uploaded file, portal access issue, communication history, or client-side integration authorization. ## Client Portal The client portal gives clients a focused place to upload documents, review transactions, answer work requests, view reports, and manage their own access. Use portal screenshots or instructions when explaining exactly what the client should click. ## Request Files From Shared Files, request documents when the accounting team needs statements, receipts, invoices, or other support. Write the request clearly and tie it to the period or transaction context. ## Organize Uploads Use Shared Files to review uploaded documents, keep folders clean, and link files back to transactions, work items, journals, reconciliations, or reports. ## Work Through Client Questions Use Client Work to track open questions and tasks. Status filters help separate unanswered work, completed items, and requests that need follow-up. Open an item to review linked transactions, files, replies, and attachments. ## Review Communications Use Communications when the answer may already exist in a sent request, received reply, or failed email. Check delivery state and message detail before asking again. ## Invite A Client Use Client Access when the client needs portal access. Confirm the recipient, permissions, and access link before sending. ## Recommended Order Confirm portal access -> send the request -> wait for upload, answer, or connection -> review the result in Client Work, Shared Files, Communications, Transactions, or Integrations -> apply the answer back to the accounting workflow. # Client Onboarding (/docs/workflows/client-onboarding) ## Add One Client From the firm Clients page, create a client workspace for each company whose books the firm manages. Add the operating name and any profile details that will help the next person continue setup. ## Bulk Create Clients When onboarding many companies, use the bulk create path from the Clients page. Review imported names before creating records so duplicate or placeholder clients do not become active workspaces. ## Choose The Source Of Truth During onboarding, choose how accounting data will enter Wesley: * Live connection for banks, cards, QuickBooks, or other supported systems. * Uploaded statements for historical periods, cleanup, missing feeds, or manual source documents. * Imported ledger or chart-of-accounts data when the firm already has structured records. * Fresh start when no prior source data should be imported. ## Confirm The First Period Pick the first review period before importing or uploading large batches. This keeps catch-up, cleanup, and monthly work scoped to the correct accounting window. ## Verify Client Setup Before leaving setup, confirm: * The client exists in the firm list. * Source data status is clear: connected, requested, uploading, processing, blocked, or intentionally skipped. * Bank, credit card, and ledger accounts are mapped cleanly. * Client owners or assignees are set where the firm uses assignments. * Open setup tasks or integration requests are visible from the firm dashboard. ## Recommended Order Create client -> choose source -> connect or upload -> verify accounts and coverage -> assign owners -> start transaction review. # Close The Books And Build Reports (/docs/workflows/close-and-reports) ## Start With Reconciliation Open Reconciliation from the client book when transaction review is done and an account needs to tie to a statement. Choose the account, confirm statement dates and balances, clear statement rows, resolve any difference, then save the reconciliation report only when the difference is zero. ## Set Statement Context Before starting reconciliation, confirm the account, last four digits, opening balance, statement ending date, and ending balance. The prior ending balance should make sense against the last saved reconciliation or ledger state. ## Clear Payments And Deposits Review checks, payments, deposits, and credits against the source statement. Use search, pagination, and row checkboxes to find missing or extra items. ## Review Journals After reconciliations are complete, inspect journal entries before locking the period. Review dates, accounts, debits, credits, memo context, recurring entries, and adjusting entries. ## Lock Or Close The Period Lock the period only after reconciliation reports and journal review are complete. A locked period should protect finalized books from accidental changes. ## Run Reports Use Reports for Profit and Loss, Balance Sheet, Trial Balance, General Ledger, AJE report, account/vendor reports, and custom reports. Set the period and report controls before exporting or sharing. ## Build A Client Report Package Use Client Reports when the client needs a repeatable package. Create or choose a template, include the required reports, review the package, then save, export, or publish. ## Recommended Close Order 1. Review and post transactions. 2. Handle operational accounting records: A/P, A/R, fixed assets, mileage, and recurring entries. 3. Reconcile statement accounts and save reports. 4. Review journals and make adjusting entries. 5. Lock the period. 6. Export financial reports or build a client report package. # Document Upload (/docs/workflows/document-upload) ## Use This Workflow When Use document upload when statement files, receipts, invoices, spreadsheets, scanned PDFs, or other supporting records need to become reviewable accounting data. ## Upload Statements Start from client onboarding or Add Transactions when bank or card statement activity is missing. Select the files, confirm the upload, and keep related statements together by account and period. ## Confirm Accounts After processing, review detected accounts before accepting them. Keep account names, institution names, account type, last four digits, and mapping clean so reconciliation and transaction review stay understandable. ## Check Processing Do not begin final review until processing completes. If extracted activity looks incomplete, verify the selected files, statement dates, account coverage, and duplicate uploads. ## Review Extracted Activity Inspect dates, descriptions, amounts, signs, account context, balances, and page coverage. Correct extraction issues before exporting, posting, or using the activity as evidence. ## Link Evidence Back To Work Attach or reference source documents from transactions, journals, reconciliations, shared files, or client work items when the file supports an accounting decision. ## Check Before You Leave The upload should produce clean account records, visible source files, and pending transactions that can be reviewed from the client book. # Configure Integrations And Firm Admin (/docs/workflows/integrations-admin) ## Integrations Hub Use the integrations area when you need to request a client connection, connect an available integration, or inspect source-system status. Each integration should have a clear state: connected, requested, blocked, stale, unavailable, or not needed. ## Request Client Connections Use Request Client when the client must authorize a bank, QuickBooks, or app connection. Keep the request specific so the client knows which system to connect. ## QuickBooks Online And Desktop Use QuickBooks Online screens to review sync state and live data. Use QuickBooks Desktop sync screens to refresh diffs, inspect queued actions, and post approved changes back to QuickBooks Desktop. ## Plaid Bank Connections Use Plaid connection screens to review linked institutions, account status, sync state, and stale or broken connections. ## Client Information And Accounting Setup Use client settings to update client details, chart of accounts, classes, locations, assignments, and access. Make the smallest safe change and return to the workflow that required it. ## Firm Members And Email Automations Use firm Settings to invite members, manage roles, set client access, connect or disconnect Gmail sync, edit email templates, preview messages, insert variables, and save or reset templates. ## Firm Profile And Billing Use firm profile and billing settings when firm identity, portal branding, subscription status, client usage, invoice history, or plan details need review. ## Audit Logs And Danger Zone Use audit logs to understand who changed what and when. Use danger-zone actions only when the impact is understood and the firm intends to make a high-impact or destructive change. ## Recommended Order Confirm the connection or setting needed -> make the smallest safe change -> refresh status or inspect logs -> return to the operating workflow. # Transaction Review (/docs/workflows/transaction-review) ## Start From The Feed Open Bank Transactions from the client book. Use the pending table to review bank and card activity from connected feeds, uploaded statements, imports, or integrations. ## Adjust The View Use filters and columns to expose the evidence needed for review. Narrow by account, date range, source group, status, vendor, amount, or pending type before taking bulk action. ## Use AI Suggestions Wesley can suggest accounts, vendors, customers, classes, locations, and posting actions. Review the transaction group, explanation, source evidence, and unusual amount markers before accepting a suggestion. ## Choose The Right Action * Quick Post when the suggested coding is clear. * Ask client when transaction purpose or support is missing. * Match when a bank row corresponds to an existing record. * Transfer when the row represents movement between accounts. * Exclude when the item should not affect the books. * Create a rule when a narrow, reliable pattern should code the same way next time. ## Use Bulk Actions Carefully Select one or more rows only when they share the same accounting outcome. Confirm that the selected transactions belong together before asking the client, matching, transferring, excluding, or posting. ## Automate Repeat Coding Use Rules for repeat vendor, memo, amount, account, class, or location patterns. Use Autopilot only when the automation scope is explainable, reviewable, and easy to disable if it catches the wrong activity. ## Check Before You Leave The feed should be smaller and clearer. Posted rows should have consistent evidence and coding. Rows that still need context should be assigned to a client request, document request, match, transfer review, or rule decision.