Source records
Know which system owns each field.
Banking, invoicing and payment systems describe related activity in different ways. Keep original identifiers and recorded allocations so a reviewer can understand how the files connect.
- Identify the source of bank transactions.
- Retain invoice IDs, customer references and dates.
- Preserve already recorded payments and allocation references.
Current import route
Check the format before discussing a rollout.
The local implementation supports mapped CSV intake and validation within its UK/GBP receipt scope. Currency, date format, field meaning and corrected-file behavior must be checked for any proposed source.
- Describe the export format without sending sensitive records.
- Confirm the entity, currency and complete review period.
- Agree how snapshots and source corrections are handled.
Future connections
Prioritize the connection that solves a real problem.
Connector development will be guided by actual workflow needs. A named system on your requirements list is not a supported integration; permissions, supported records and failure handling need verification before release.
- Tell us which system creates repeated manual work.
- Define the records and refresh frequency required.
- Confirm tested availability before including a connector in a proposal.