Australia Bank Feeds 3.0.0 Import Schedule, Retries, and Manual Imports
Australia Bank Feeds SuiteApp 3.0.0 introduces a staggered morning import, two-hour automated imports through the afternoon, and a 45-minute retry after failures. Learn what those timings mean for administrators and when to use a manual import.
Starting in NetSuite 2026.2, Australia Bank Feeds SuiteApp version 3.0.0 introduces four import behaviors: a staggered morning window, recurring daytime imports, a 45-minute retry after failure, and a manual-import option. For administrators and finance teams, the useful distinction is whether they are waiting for a scheduled import, following a failed operation, or requesting a refresh for a specific business need.
Key takeaways
- The Australia Bank Feeds 3.0.0 import schedule begins between 8:00 AM and 9:00 AM (AEST), not at one universal start time.
- After the initial import, automated imports run every two hours until 3:00 PM (AEST).
- If an import fails, the system is set to retry after 45 minutes.
- Users can trigger a manual import at any time through the Australia Bank Feeds SuiteApp.
- A scheduled import or retry is not evidence that the expected data has arrived. Confirm the outcome before reporting that a refresh succeeded.
When does Australia Bank Feeds 3.0.0 import bank data?
The Staggered Import Schedule places the initial bank-data import between 8:00 AM and 9:00 AM (AEST). Treat this as a scheduling window rather than a promise that every import starts at 8:00 AM.
The source describes staggering as a way to improve reliability and reduce errors during high-traffic periods. For an administrator updating a runbook, the clearest wording is “the morning import is scheduled between 8:00 AM and 9:00 AM AEST.” Shortening that to “imports at 8 AM” creates an expectation the published schedule does not support.
Keep AEST explicit in support messages and operating guides. If colleagues use a different time reference, convert the published times for their working calendar rather than silently relabeling them. This is especially important when a finance user and an administrator are discussing the same import from different locations.
A scheduling window is not a completion deadline
The source gives the import window, not a guaranteed completion time. When someone reports missing bank data, separate their expected refresh time from evidence that an import completed or failed.
For example, a finance user checking at 8:15 AM AEST is still within the morning scheduling window. That check alone does not establish a failure. A useful first question is whether the concern is an early refresh expectation, an identified failed operation, or missing expected data after an import.
For historical reading, see Australia Bank Feeds enhancements in NetSuite 2024.2. When updating an existing guide, identify the version 3.0.0 timing rules explicitly so readers do not confuse different release contexts.
How often do automated imports run?
After the initial import, Regular Automated Imports run every two hours until 3:00 PM (AEST). Preserve both parts of that rule in your operating guide: the interval and the afternoon cutoff.
“Every two hours” alone suggests an ongoing cadence without a boundary. “Until 3 PM” alone omits how frequently imports occur. Together, the two values explain the published daytime schedule without inventing exact execution slots.
| Import behavior | Published timing | Practical interpretation |
|---|---|---|
| Initial import | Between 8:00 AM and 9:00 AM (AEST) | Plan around a staggered morning window. |
| Subsequent automated imports | Every two hours until 3:00 PM (AEST) | Preserve both the interval and cutoff in runbooks. |
| Failed-import retry | After 45 minutes | Use the failure time to explain the retry expectation. |
| Manual import | At any time | Consider a user-requested refresh when waiting does not meet the business need. |
Do not convert the interval into a list of exact account-specific import times. The source supplies a staggered initial window, a two-hour cadence, and a cutoff; it does not supply a universal timetable of individual execution slots. Likewise, “until 3:00 PM” should not be rewritten as a promise that every account runs an import at exactly 3:00 PM.
What finance teams should check
Before a time-sensitive review, identify which successful import the team is relying on and whether another refresh is needed. The arrival of a scheduled time is not, by itself, confirmation that the information needed for the review is available.
For example, a team preparing an afternoon review can distinguish two questions: “What is the published import schedule?” and “Do we have the bank data needed for this review?” The first is answered by the timing table. The second requires checking the actual outcome rather than assuming the schedule guarantees completeness.
Related reading: Match Bank Data enhancements in NetSuite 2026.2. Keep questions about import timing distinct from questions about subsequent work with bank data.
How long does a failed import wait before retrying?
Under Automatic Retries on Failures, the system is set to retry after 45 minutes if an import operation fails for any reason. This failure-driven retry is distinct from the regular two-hour import cadence.
If a user asks whether a failed import must wait for the next regular run, the supported answer is that the release specifies a 45-minute retry. Do not substitute the two-hour automated interval for that retry rule.
As a timing illustration, a failure at 10:00 AM AEST plus 45 minutes gives 10:45 AM AEST as the retry expectation. This calculation illustrates the published interval; it is not another fixed daily import slot. It also does not guarantee that the retry succeeds or that all expected data is available at that minute.
Suggested failure-review checklist
The following is an operational checklist, not a NetSuite navigation procedure:
- Establish whether an import failed rather than inferring failure from an early check for data.
- Record the failure time with an explicit time reference.
- Use the 45-minute interval when communicating the retry expectation.
- Check the outcome before reporting successful recovery.
- If the business needs a refresh sooner, consider the manual-import option.
In a support handoff, distinguish “a retry is expected” from “the import recovered.” That wording keeps the published recovery behavior separate from the result observed by the team.
Do not describe the retry rule as an unlimited retry loop or a guarantee of recovery. Nor should an incident note assume how the 3:00 PM AEST automated-import cutoff interacts with retries. The source provides the individual timing rules, not a complete recovery policy.
When to consider a manual import
The Manual Import Option lets users trigger an import at any time through the Australia Bank Feeds SuiteApp. Consider this option when waiting for automation does not meet the day's operational need, such as a time-sensitive review outside the regular automated window.
The source establishes the capability but does not provide a menu path or button label. This article therefore does not prescribe an account-navigation sequence.
Before requesting a manual refresh, clarify the reason: is the team working outside the automated window, seeking newer information for a review, or responding to a failed operation? Those situations call for different explanations even though the manual option is available in each case.
A request after the afternoon window does not, on its own, prove that automation failed. A request during the morning window may instead reflect an expectation of an 8:00 AM import that the staggered schedule does not promise.
If an import has failed, communicate the 45-minute retry expectation before discussing a manual refresh. Do not assume that a manual import cancels, postpones, or otherwise changes the retry or regular schedule. After a requested refresh, confirm the outcome and record that the request was manual so colleagues can distinguish it from an automated run.
For related reading, see Reconcile Account Statement enhancements in NetSuite 2026.2.
FAQ
When is the initial bank-data import scheduled?
Australia Bank Feeds SuiteApp 3.0.0 uses a staggered initial import window between 8:00 AM and 9:00 AM (AEST).
How often do automated imports run afterward?
After the initial import, automated imports run every two hours until 3:00 PM (AEST). Keep both the interval and cutoff when describing the schedule.
When does a failed import retry?
If an import operation fails, the system is set to retry after 45 minutes. That is separate from the normal two-hour cadence.
Can users request a manual import outside the automated schedule?
Yes. Users can trigger a manual import at any time through the Australia Bank Feeds SuiteApp.