Accounting & Bookkeeping · How-to guide

Match a bank transaction

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Connect a feed row to an existing Accounting transaction such as a customer payment, supplier payment, transfer or manual entry.

Audience: Accounting staffFeature: Transaction matchingModule v1.4.5

Jump to steps

Where to goAccounting → Banking → Banking Feeds → Match

Before you startThis guide follows Accounting and Bookkeeping module version 1.4.5. The required access is Accounting Banking: Edit. A related screen can remain hidden when an optional module is inactive, a source record is in an ineligible status, the selected account is inactive or the user is not an assigned approver.

What you’ll accomplish

Connect a feed row to an existing Accounting transaction such as a customer payment, supplier payment, transfer or manual entry. It forms part of Pixie CRM Enterprise CRM's Accounting & Bookkeeping module and uses the module's permission-aware controller, status and mapping flow rather than a generic spreadsheet process.

How it works

The controller includes match_transactions, match_transaction_save, unmatch and candidate-data actions. It also provides automatic matching and a closest-date window setting in the feed workflow.

Matching does not create a second ledger entry; it associates the bank evidence with the existing Accounting transaction.

When a single bank settlement covers several source transactions, use the supported bulk-match workflow and confirm the summed amount.

Follow these steps

Go to Match on the feed row.
Check automatic candidate suggestions.
Compare amount, direction, date, reference, customer or vendor.
Select the correct existing transaction.
Save the match.
Go to both records and verify the connection.
Include the matched line in bank reconciliation.

Settings to check

Feed amount and directionMust be compatible with the candidate transaction.

Date windowCandidate matching can use a closest-date window.

Reference and payeeSupport identification.

VarianceExact, under or over differences require review.

Matched transactionShould represent the same economic event.

Check it worked

After the action is saved, Pixie CRM keeps the Accounting record connected to its source and updates the visible status or ledger data supported by this workflow. Review the saved result rather than relying only on a success message. Where the action posts accounting data, total debits and credits must balance and the accounts must match the approved mapping or manual selection.

Open the saved record and confirm its final status.
Review the source reference and every debit and credit line where ledger data was created.
Use the relevant register, ageing, reconciliation or report to verify the wider effect.

Common mistakes to avoid

Do not match solely on amount.
Do not combine unrelated transactions unless the supported bulk logic represents the settlement.
Investigate variances.
Unmatch through the supported action if evidence changes.
Use the least destructive correction available and record the reason for material changes.
Do not bypass a permission, approval or closed-period control by changing unrelated data.

Accounting and data safetyDeletion, reset, void, refund, mapping, journal and reconciliation actions can change financial history. Use approved access, retain supporting evidence and validate the result in the General Ledger or relevant control report.

Browse connected topics:invoice payment banking reconciliation transfer supplier bill vendor check report approval mapping double-entry Plaid customers

Was this guide useful?Your response is stored only in this browser.

Match a bank transaction

What you’ll accomplish

How it works

Follow these steps

Settings to check

Check it worked

Common mistakes to avoid

Related guides