Accounting & Bookkeeping · How-to guide

Export, edit and re-import banking feeds

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 use the supported Excel round trip to review or update feed fields in bulk without changing the original bank statement values carelessly.

Audience: Senior accounting staffFeature: Feed spreadsheet editingModule v1.4.5

Jump to steps

Where to goAccounting → Banking → Banking Feeds → Export to Excel Edit

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

Use the supported Excel round trip to review or update feed fields in bulk without changing the original bank statement values carelessly. 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 export_banking_feeds_excel and import_edited_banking_feeds controller actions and explanatory notes in the banking interface. This is different from importing a new statement file.

The round trip is intended to update local feed review data. It does not update the financial institution.

If a row no longer matches because identifiers were changed, restore the original export and reapply only the supported edits.

Follow these steps

Filter the feed to the intended bank account and period.
Export using the Edit option.
Keep a protected copy of the original export.
Change only supported review fields.
Import the edited file.
Check success and error results.
Reopen the feed and verify every changed row before posting.

Settings to check

Export scopeIncludes the currently selected or eligible feed rows.

Editable columnsOnly change columns supported by the import process.

Transaction identityMust remain stable so rows can be matched back.

Import resultReports accepted and failed updates.

Original amount and dateShould remain consistent with bank evidence unless correcting an import error.

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 alter bank amounts to force reconciliation.
Do not delete identity columns.
Do not edit rows already posted without review.
Protect the exported file as financial 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.

Browse connected topics:banking reconciliation check report approval mapping double-entry Plaid

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

Export, edit and re-import banking feeds

What you’ll accomplish

How it works

Follow these steps

Settings to check

Check it worked

Common mistakes to avoid

Related guides