| Overview |
When exporting journal adjustments from BrightTax to FreeAgent, some entries may fail to export if they use nominal codes that are not configured in FreeAgent or are not supported by the FreeAgent API. BrightTax will display a clear message identifying which entries cannot be exported and why.
| Why Export Errors Occur |
The FreeAgent journal export maps BrightTax journal entries to FreeAgent nominal codes. An export error occurs when:
- The nominal code used in the BrightTax journal does not exist in the client's FreeAgent account
- The nominal code exists in FreeAgent but is configured in a way that prevents journal posting
- The FreeAgent account does not support the type of entry being exported
| What Happens When an Error Occurs |
From the May 2026 update, BrightTax now handles export errors clearly:
- A message is displayed in BrightTax identifying which journal entries cannot be exported
- The message explains which nominal code configuration is causing the issue
- Entries that can be exported are processed successfully — only the affected entries are blocked
| ✔ Tip: Not all journal entries need to fail for an export error to appear. BrightTax will export all supported entries and flag only those that cannot be processed. Review the message carefully to understand the scope of the issue. |
| How to Resolve Export Errors |
Option 1 — Create the Missing Nominal Code in FreeAgent
- Log in to FreeAgent.
- Navigate to the Chart of Accounts or Nominal Codes section.
- Create the missing nominal code that corresponds to the BrightTax journal entry.
- Return to BrightTax and retry the journal export.
Option 2 — Post the Entry Manually in FreeAgent
- For entries that cannot be exported due to nominal code configuration, post those specific journal entries directly in FreeAgent manually.
- Mark those entries as posted in your working papers so they are not double-counted.
Option 3 — Remap the Journal Entry in BrightTax
- If the journal entry in BrightTax is using a nominal code that does not exist in FreeAgent, consider whether the entry can be remapped to a nominal code that does exist in FreeAgent.
- Edit the journal entry in BrightTax to use the FreeAgent-compatible nominal code.
- Retry the export.
| ⚠ Important: Before remapping a journal entry to a different nominal code, confirm the accounting treatment is still correct. Remapping to the wrong code to force an export will result in incorrect entries in FreeAgent. |
| Troubleshooting |
The export error message is not telling me which nominal code is the problem
- Check the Submission History or export log in BrightTax for the full error detail.
- Compare the nominal codes used in your BrightTax journals against the Chart of Accounts in FreeAgent to identify any that are missing.
All entries are failing to export, not just some
- Check that the FreeAgent connection is still active — the authorisation may have expired.
- In BrightTax, go to the FreeAgent integration settings and reconnect if the authorisation has lapsed.
- Retry the export after reconnecting.
| Frequently Asked Questions |
Q: Can I see which entries exported successfully and which failed?
A: Yes. The message displayed in BrightTax after an export attempt identifies which entries were affected. Successfully exported entries will appear in FreeAgent as journal postings.
Q: Will failed entries be retried automatically?
A: No. Failed entries must be resolved manually using one of the options above and then resubmitted.
Q: Does this issue affect the import of trial balance data from FreeAgent to BrightTax?
A: No. This issue only affects the export of journal adjustments from BrightTax back to FreeAgent. The import of trial balance data is a separate process and is not affected.
Comments
0 comments
Article is closed for comments.