Customer work, connected.

Help & supportMyAccount
Accounting & Bookkeeping · How-to guide

Bulk match bank transactions

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

Match a feed row or selected feed rows to multiple compatible Accounting transactions using the module's bulk-match tools.

Audience: Senior accounting staffFeature: Bulk matchingModule v1.4.5
Jump to steps
Where to goAccounting → Banking → Banking Feeds → Bulk 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

Match a feed row or selected feed rows to multiple compatible Accounting transactions using the module's bulk-match tools. 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 provides get_bulk_match_data and bulk_transaction_action plus user messages that distinguish successful and failed parts.

Bulk matching is useful for batch deposits or settlements, but differences may represent fees, withholding or timing. Record those separately according to policy.

Reconciliation remains the final check that all bank statement activity is accounted for.

Follow these steps

  1. Filter to one bank account and period.
  2. Select the intended feed transaction or rows.
  3. Go to Bulk Match and review candidate transactions.
  4. Select only transactions represented by the bank settlement.
  5. Compare selected totals and references.
  6. Verify the bulk match.
  7. Check the success and failure summary and open each resulting match.

Settings to check

Selected feed rowsMust be reviewed and belong to the intended bank account.
Candidate transactionsCan include multiple source payments or ledger entries.
Total comparisonSelected Accounting amounts must equal or explain the bank total.
Match summaryReports successful and failed parts.
VarianceRequires resolution before reconciliation.

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 use bulk match to hide a difference.
  • Keep gateway fees or bank charges separate where required.
  • Check failed items individually.
  • Do not mix different bank accounts.
  • 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.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page