Customer work, connected.

Help & supportMyAccount
Accounting & Bookkeeping · How-to guide

Use posted bank transactions and the banking register

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

Follow this guide to review bank transactions already represented in Accounting and compare them with the bank-account ledger balance.

Audience: Accounting staffFeature: Posted bankingModule v1.4.5
Jump to steps
Where to goAccounting → Banking → Posted Bank Transactions / Banking Register
Before you startThis guide follows Accounting and Bookkeeping module version 1.4.5. The required access is Accounting Banking: View. 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

Review bank transactions already represented in Accounting and compare them with the bank-account ledger balance. 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 module provides separate posted-bank-transaction and banking-register tables. Posted status concerns the Accounting workflow; reconciliation concerns agreement with the external statement.

A posted transaction can remain unreconciled because of timing or an incorrect match. A reconciled item should have supporting bank evidence.

Use Bank Reconciliation Detail for the completed reconciliation record.

Follow these steps

  1. Select the bank account.
  2. Go to Posted Bank Transactions and filter the period.
  3. Check source references and unusual entries.
  4. Go to the Banking Register for running balance context.
  5. Compare the register with the statement and feed.
  6. Resolve missing, duplicate or unmatched items.
  7. Proceed to reconciliation.

Settings to check

Posted statusIndicates a feed row has created or matched Accounting activity.
Bank accountSelects the related ledger account.
Transaction referenceTraces to the source or manual entry.
Debit or credit directionShows the bank-account movement.
Running balanceSupports period review but must be reconciled to the statement.

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 assume Posted means reconciled.
  • Use the correct opening date.
  • Investigate manual adjustments.
  • Protect exported bank-register data.
  • 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