If bank transactions or Trial Balance data are not importing correctly into Bright AP or BrightBooks, or you are having issues disconnecting or linking a bank feed, the following steps may help resolve the issue.

Important: Always keep a backup of the original file before making changes or re-importing data. This ensures you can revert to the original file if required.

CSV import completes but no figures appear

If a CSV file uploads without showing an error, but no figures appear in the Trial Balance:

1. Check that the CSV column mapping is correct.
2. Confirm that the date, nominal code, debit, and credit columns are mapped to the correct fields.
3. Make sure all required columns are present and match the expected Bright AP template.
4. Re-open the dataset and go to Nominal Ledger > Trial Balance.
5. Check that the expected nominal codes show the imported balances.

If no balances appear, review and correct the column mapping before attempting the import again. Re-uploading the same file without correcting the mapping is unlikely to resolve the issue.

Bank statement CSV fails to upload

If a CSV file downloaded directly from your online banking platform fails to upload, the file format may not match the format expected by Bright AP.

Check the following:

• Column headers and order
• Date format
• Required transaction fields
• Any additional or missing columns

If the bank's export format does not match the required format, re-save or amend a copy of the file using the correct headers and format before uploading it again.

Note: Confirm the required CSV column specification with the Product Team before publishing or providing specific formatting instructions.

Disconnecting a bank feed

To disconnect or unlink a bank feed:

1. Go to Settings > Bank Feeds for the relevant client.
2. Locate the bank feed you want to disconnect.
3. Select the Disconnect or Unlink option.

If the option is not available, the bank feed may have been set up at practice level rather than client level.

In this case, check the practice-level bank feed settings and disconnect the feed from there if appropriate.

Journal import validation message

A journal import validation message means that one or more rows in the file have failed Bright AP's journal validation.

Common causes include:

• Debits and credits are not balanced.
• An invalid or incorrect nominal code has been used.
• One or more required fields are missing.
• A row contains data that does not meet the journal import requirements.

Review the validation message carefully. It should identify the specific row, nominal code, or issue that needs attention.

Correct the affected rows in the original file and then re-import the corrected file rather than repeatedly importing the same file.

Contact Support

If you are still unable to import the data or manage the bank feed after checking the steps above, contact Bright AP Support.

When contacting Support, provide:

• The practice and client name
• The type of import or bank feed involved
• The original file, if appropriate
• Any validation or error messages displayed
• Details of the steps already taken

This information will help Support investigate the issue more efficiently.