Troubleshooting Bank Import Schedule...

Encountering issues with your NetSuite bank import schedule can disrupt banking data operations. This guide provides practical steps to resolve common errors in setting up or managing an import schedule.

Troubleshooting Common Errors

Record Not Saved

Problem: An error occurs if any fields under the Import Schedule subtab are partially filled.

Solution:

Ensure every field is either filled (using default or preferred values) or left entirely blank.
Partial entries are not allowed.

Format Profile Without Active Linked Accounts

Problem: Import operations require at least one active account linked to the profile. Without it, no schedule can run.

Solution:

Link an active account in the Account Linking subtab.
Ensure this is done prior to setting the schedule.

Note: The selected time zone in the import schedule determines the import times. However, the Format Profile and Match Bank Data pages will display times in your local time zone.

Who This Affects

NetSuite Administrators setting up import schedules.
Finance Teams relying on accurate banking data.
NetSuite Developers managing integration and customization of import schedules.

Key Takeaways

Always complete all fields in the Import Schedule subtab to avoid errors.
Link at least one active account to a format profile to activate scheduling.
Schedules are based on the time zone selected in the settings, but reports adapt to your local time zone.

Frequently Asked Questions (4)

What should I do if I encounter a 'Record Not Saved' error when setting up a bank import schedule in NetSuite?

To resolve the 'Record Not Saved' error, ensure that all fields in the Import Schedule subtab are either completely filled or entirely left blank. Partial entries are not allowed and will trigger this validation error.

How can I resolve the 'No Active Linked Accounts' error when managing bank import schedules?

To resolve the 'No Active Linked Accounts' error, link at least one active account in the Account Linking subtab. Without an active account, the Import Schedule subtab fields will remain unavailable for setup.

Do I need to consider timezones when scheduling bank imports in NetSuite?

Yes, it is important to align your import schedule's timezone with your operational timezone to ensure consistent import operation times. Import times are converted based on the set timezone settings.

How can I ensure my bank import schedules run smoothly without performance issues?

Monitor active account connections in the Account Linking subtab, avoid congested data periods by optimizing schedules, and for larger volumes, adhere to Bank Feeds SuiteApp limits, possibly by splitting profiles if necessary.

Troubleshooting Bank Import Schedule Errors in NetSuite