Bank Feed¶
The Bank Feed displays cleared transactions pulled from your connected bank accounts. Use it to review incoming and outgoing activity and match each transaction to the corresponding payable or receivable charge it represents.
What Appears on the Bank Feed¶
Only posted (cleared) transactions appear on the Bank Feed. Pending transactions — those authorized but not yet cleared by your bank — are not shown until they post.
Transactions reach the feed through multiple routes:
- Automated bank connections (Plaid or Stripe Financial Connections): transactions sync automatically as they clear at your bank.
- Bank export import: upload a bank export file (e.g. MT940, CSV) and Credence imports the transactions, skipping any duplicates.
Allocation Statuses¶
Each transaction carries one of three statuses:
- Unallocated — the transaction has an amount that has not yet been matched to a charge. These require action.
- Allocated — the full transaction amount has been matched to one or more charge items. No further action needed.
- Excluded — the transaction has been intentionally removed from the workflow (e.g. it was already accounted for outside of Credence).
Allocating a Transaction¶
Allocation is the process of matching a bank transaction to the charge item(s) it pays for or collects against.
- Withdrawals (negative amounts) are allocated against Payable charge items — the expenses you owe a vendor — or negative Receivable charge items for tenant refunds.
- Deposits (positive amounts) are allocated against Receivable charge items — the charges owed to you by tenants.
A single transaction can be split across multiple charge items, and a single charge item can be satisfied by multiple transactions (partial payments).
When a transaction is allocated, Credence posts the corresponding ledger entries to the appropriate accounting period.
To correct an allocation, use Unallocate from the transaction detail page. Unallocate automatically reverses or removes the related bundles and returns the transaction to Unallocated status for re-matching. The charge links are cleared only after the bundle reversals succeed: when a related bundle cannot be reversed — for example because the accounting period is closed and you do not have permission to post into closed periods — Unallocate is blocked and the reason is shown. Allocate is blocked with its reason under the same closed-period conditions.
Transaction Audit History¶
A transaction's audit history includes changes to the transaction and its payable and receivable match allocations. Each allocation entry shows the linked charge item's description and the allocated amount.
New allocation history remains visible after unallocation deletes the match link, including both its addition and removal. Older events without a stored timeline association are omitted from the transaction timeline. All history remains subject to the audit retention period.
Excluding a Transaction¶
Transactions that do not correspond to any charge in Credence — such as bank fees already recorded elsewhere or transfers between accounts that are tracked separately — can be excluded. A transaction can only be excluded if it has no existing allocations and no posted ledger entries tied to it.
Excluded transactions can be re-included at any time from the transaction detail page.