ONL022 Export Error
ONL022 Export Error in QuickBooks Online Integration
If you see the error:
ONL022: Account must be marked as billable in QuickBooks Online.
This means the account category applied to an expense is not configured to support billable expenses in QuickBooks Online, preventing the export from completing.
Why the ONL022 Export Error Happens in QuickBooks Online
The ONL022 error typically indicates:
- Billable functionality is not enabled in QuickBooks Online.
- The selected account in the Chart of Accounts does not support billable expenses.
- QuickBooks Online validation failed due to incorrect billable configuration.
When exporting billable expenses, QuickBooks Online requires both company-level billable settings and account-level configuration to be enabled.
This is a QuickBooks Online configuration issue, not a Workspace configuration issue.
How to Fix the ONL022 Export Error
This issue must be resolved in QuickBooks Online.
Enable Billable Expenses
- Log in to QuickBooks Online.
- Select the Gear icon.
- Go to Account and Settings.
- Select the Expenses tab.
- Enable Make expenses and items billable.
- Save your changes.
Update the Account in the Chart of Accounts
- Go to the Chart of Accounts.
- Locate the account used for the expense category.
- Select Edit.
- Ensure the account supports billable expenses.
- Select the appropriate Income account if required.
- Save your changes.
After updating QuickBooks Online:
- Go to Settings > Workspaces.
- Select your Workspace.
- Click Accounting.
- Click Sync Now.
Then retry exporting the report.
FAQ
Can I Retry the Export?
Yes. After enabling billable functionality and selecting Sync Now, retry the export. If the error persists, confirm the correct account is configured.
Does ONL022 Mean My Plan Does Not Support Billable?
Not necessarily. It usually means billable settings are not enabled or the account is not configured correctly.
Is ONL022 Caused by Workspace Settings?
No. ONL022 is triggered by billable configuration settings in QuickBooks Online. Workspace accounting settings are not the cause.