Understand which bank transactions Sage can display
Detailed client guidance covering understand which bank transactions Sage can display, including prerequisites, exact controls, verification evidence, failure boundaries and safe recovery steps for the shipped Sage connector.
Audience: Administrators, finance staff and authorised integration operatorsPermission: ReconcileModule v1.0.0
Where to goSage Accounting Automation → Sage Bank Feeds
Before you startConfirm the intended tenant, remote account or invoice context, and your Reconcile access. Keep credentials and tokens out of screenshots, tickets and exported evidence. If a previous write may have reached an external service, verify remote state before retrying.
What you’ll accomplish
Detailed client guidance covering understand which bank transactions Sage can display, including prerequisites, exact controls, verification evidence, failure boundaries and safe recovery steps for the shipped Sage connector. This article is intentionally scoped to the behaviour enforced or exposed by the supplied module and does not treat provider marketing features as implemented integration capabilities.
How the workflow fits together
The connector keeps native CRM records authoritative while mapping verified Contact, Sales Invoice and Contact Payment evidence in Sage. Queue, exception, API, reconciliation and compliance records are separate evidence layers, so each material action should be verified at both the native and remote sides.
Follow these steps
Open Sage Accounting Automation → Sage Bank Feeds.
Confirm you are in the intended tenant and connected business and that your role has the required Reconcile access.
Refresh/select the intended connected bank account.
Load the API-visible activity and compare date, reference, amount and account context.
Use the data as evidence only for actions the provider API exposes.
For provider UI-only reconciliation steps, continue in the provider product rather than treating this view as a write surface.
Fields and decisions to review
This guide’s focusDetailed client guidance covering understand which bank transactions Sage can display, including prerequisites, exact controls, verification evidence, failure boundaries and safe recovery steps for the shipped Sage connector.
Read-oriented viewThe bank activity area is for API-visible evidence and account context; it is not a substitute for every screen in the provider banking product.
Account selectionChoose a refreshed, connected bank-account reference before interpreting transaction activity.
API boundaryOnly data exposed by the supported accounting endpoints can be displayed or verified.
No invented writeThe integration does not claim a banking-UI match/confirm action unless the provider accounting API actually exposes it.
TroubleshootingEmpty results can mean no supported activity, stale references, a connection problem, an incorrect account, or an API capability boundary.
Provider API boundaryThe module exposes read-oriented bank/feed and reconciliation metadata supported by the accounting API. It does not claim to reproduce an unsupported Sage banking UI match/confirm action.
How to confirm it worked
Reopen the native record and the relevant integration history/register. Confirm the stored remote accounting identifier, exact amount/status, latest timestamps and the expected audit or reconciliation evidence. If the provider-side state cannot be independently verified, keep the task unresolved and use the controlled exception or troubleshooting flow.
Questions clients commonly ask
Does this reproduce the provider bank-reconciliation screen?The module exposes read-oriented bank/feed and reconciliation metadata supported by the accounting API. It does not claim to reproduce an unsupported Sage banking UI match/confirm action.
What should I verify before I trust the result?Verify the native record, the mapped remote record, the stored remote identifier, the current status/amount and the audit or history evidence. A success message alone is not the accounting evidence.
Should I press the action again after a timeout?Not until you have checked the remote accounting service and the Exceptions/API evidence. A timeout can occur after the remote side accepted a non-idempotent write, so a blind retry can create a duplicate.
Does the connector replace the native CRM record?No. Native clients, invoices and payments remain the operational source records. The connector records mappings, remote evidence and controlled reconciliation around them.
What should I include in a support case?Include the native record ID, remote ID if known, date/time, action, exact visible error and request/audit identifier. Never send client secrets, access tokens, refresh tokens or authorization headers.
Technical basis for this guidance
This guide was checked against the supplied module code paths: controllers/Sage_accounting_automation.php; models/Sage_accounting_automation_model.php; libraries/Sage_api_client.php; libraries/Sage_reconciliation_service.php; libraries/Sage_document_import_service.php; views/admin; install.php; docs/FEATURE_MATRIX.md. It documents shipped behaviour, validation, routes and evidence controls; it does not claim successful live provider network calls from offline inspection.
Controls, checks and common mistakes
Work in the intended tenant and remote accounting/business context.
Do not paste credentials, access tokens, refresh tokens or private keys into tickets or notes.
Do not bypass a missing mapping, validation error, permission gate, duplicate check or remote-verification requirement.
Do not repeat a non-idempotent write until you know whether the previous request reached the remote service.
Keep native record, remote evidence and audit/history state aligned before closing the task.
Provider and accounting boundaryThe module exposes read-oriented bank/feed and reconciliation metadata supported by the accounting API. It does not claim to reproduce an unsupported Sage banking UI match/confirm action.
