Transactions in Worthic can enter the system in several ways: manual entry, statement import, mobile upload, emailed document extraction, API submission, or a custom account integration. The important distinction is between a confirmed transaction, which is already part of the account record, and a pending transaction or extracted candidate, which needs review.
Worthic keeps these flows connected to the same account model. A transaction belongs to an account, can carry categories, tags, notes, source information, and supporting documents, and can be reviewed from the Transactions workbench or from document review surfaces.
Adding transactions manually
For transactional accounts, users can add a transaction from the account or transaction controls. The manual transaction flow captures the account, date, amount, description, category, tags, and any supporting detail required by the account type. Existing transactions can be opened in the same editing flow to correct fields, attach supporting records, update tags, or change review status.
For split transactions, Worthic can create a transaction group so one imported or entered movement can be divided into multiple category lines. This is useful where one bank transaction covers several expense categories or where one receipt needs to be allocated across different purposes.
Balance-tracking-only accounts behave differently. These accounts do not use a normal transaction ledger. Their manual flow is presented as an account value adjustment, because the account is being maintained as a point-in-time balance rather than a list of transaction movements.
User transaction import from web and mobile
Users can upload transaction documents from the web app, including from account and document areas, and through your AI assistant. When an upload is treated as an intake document, Worthic analyses it, looks for transaction rows, and creates transaction candidates where possible. These candidates are not blindly accepted; they are routed into review so the user can confirm, edit, exclude, or discard them.
A document uploaded as a transaction attachment or account record attachment is different. In that case it is supporting evidence for an existing record, not a new extraction job. Worthic files the document against the relevant transaction or account record rather than creating new transactions from it.
Mobile uploads use the same broad intake model. Files submitted from the mobile companion are uploaded into the workspace, processed in the background where applicable, and can be tracked by upload status. Mobile uploads are useful for receipts, statements, or other documents captured away from the desktop workflow.
Emailed document extraction
Worthic can also receive documents by email. Accepted email attachments are ingested as document-intake items and are routed to the Document Inbox for review and extraction. This supports workflows such as forwarding bank statements, broker statements, invoices, receipts, or account notices into Worthic rather than downloading and uploading them manually.
Where a submission is treated as a viewer-only or personal reference document, Worthic stores it as a file without transaction analysis. That matters because not every document upload is intended to affect financial records.
API document submission
The API supports document submission for integrations and external workflows. An API client can submit a document file for Worthic processing, typically using a review-oriented submission mode so the document goes through extraction and appears in the Inbox or transaction review flow. API reference uploads can also be used for filing documents without extraction.
For tighter integrations, the API also supports transaction endpoints. Depending on the client’s permissions and configuration, an integration may create confirmed transactions directly or submit proposed transactions for review. This gives Worthic two patterns: trusted systems can write known-good transaction data, while lower-confidence sources can propose entries that a user confirms later.
Custom account integration and transaction syncing
Custom account integrations can be built around the source that is actually available. A bank, broker, rental platform, or internal system might provide statement files, email notifications, exports, API data, or webhook-style submissions. Worthic can support these through mapped statement imports, emailed document ingestion, API document submission, direct transaction creation, or transaction proposals.
This should not be confused with a universal automatic bank feed. A custom integration depends on the provider’s export quality, access method, available identifiers, and reconciliation rules. Once configured, synced transactions still need sensible review controls, especially where duplicates, missing balances, currency mismatches, or ambiguous categories are possible.
Sync Health surfaces problems that affect transaction intake, such as imported documents that could not be routed correctly or feed/import issues that need attention. It helps separate normal review work from actual sync or routing failures.
Transaction review and document Inbox
Worthic separates document-level review from transaction-level review.
The Document Inbox is where newly received or uploaded documents can be inspected, routed, filed, deferred, or discarded. It is the right place to decide what a document is and whether it should become part of the transaction workflow.
The Transactions workbench is where the extracted or synced transaction rows are handled. Pending transactions and extracted candidates can be confirmed, edited, or discarded. Excluded duplicate candidates can be restored or permanently cleared. Users can also filter for uncategorized transactions, apply tags, search transaction text, and work through review queues without losing sight of the account context.
Together, these flows let Worthic support quick manual entry, document-driven extraction, and integration-based syncing while keeping user review in the loop where the source data is uncertain.