Japan Bank Feeds Installation Checklist: Eligibility and Setup

Use this Japan Bank Feeds installation checklist to confirm account eligibility, required SuiteCloud features, and installation access before installing the public SuiteApp. The key boundary is account location: connections are limited to accounts located in Japan.

Key takeaways

• Account scope: Connected accounts must be located in Japan. Do not assume an institution’s presence in Japan makes its overseas accounts eligible.
• Required features: Enable Custom Records, Client SuiteScript, and Server SuiteScript on the SuiteCloud subtab.
• Installation access: Use a role with access to SuiteApp Marketplace.
• Installation sequence: Go to SuiteApps, search for Japan Bank Feeds, open its tile, and click Install.
• Validation boundary: Daily imports produce transactions ready for reconciliation; they do not establish that reconciliation is complete.

1. Which bank accounts are eligible for Japan Bank Feeds?

Start with the location of each intended account, rather than your company’s location or the name of its banking group. Japan Bank Feeds connections are limited to accounts located in Japan. Support for multiple financial institutions operating in Japan does not establish coverage for every account held with those institutions worldwide.

For a multinational rollout, separate Japan-based accounts from accounts located elsewhere before agreeing on scope. This prevents an installation decision from becoming an unsupported promise to cover all banking activity.

Complete these planning checks:

1. Identify the intended Japan-based accounts. Put accounts located in Japan on the proposed connection list and exclude accounts located outside Japan.
2. Separate mixed-country account lists. Evaluate individual accounts rather than treating an entire banking relationship as eligible.
3. Review proposed GL associations with accounting. Pair each intended feed account with its relevant GL account for review. This is recommended preparation, not an additional installation prerequisite.

For example, a rollout may include accounts located in Japan and another country at the same financial institution. Keep only the Japan-based accounts in the proposed Japan Bank Feeds scope. Track the remaining accounts separately rather than assuming this installation addresses them.

A useful planning record identifies each intended account, its location, and its proposed GL association. That record is a recommended review aid—not a prescribed NetSuite form or a documented installation requirement.

2. Review supported languages and capabilities

Japan Bank Feeds is a single-page SuiteApp that transfers bank data from financial institution accounts in Japan into NetSuite. It supports English and Japanese. Confirm that this language coverage fits the administrators and banking users participating in the rollout.

The documented processing components are Financial Institution Records and the Bank Statements Parsers Plug-in. They process data from a third-party authorized data service provider. These names provide implementation context; they do not establish a requirement to build a custom integration.

Capability	Documented scope	Recommended planning check
Multiple financial institution connections	Connect multiple financial institutions operating in Japan to NetSuite.	Identify intended institutions and Japan-based accounts.
Automated daily imports	Import bank transactions ready for bank reconciliation.	Assign someone to review import results after connection setup.
Consolidated account visibility	View information for bank accounts in Japan on one page.	Agree which accounts reviewers should expect to see.
GL account mapping	Map feed bank accounts to their relevant GL accounts.	Have accounting review the proposed associations.

Use these capabilities to define what the banking team will validate after installation. For example, seeing an expected account in the consolidated view addresses account visibility; it does not by itself verify the account’s GL mapping or daily import results. Review those as separate items.

The Japan Bank Feeds setup and import overview provides implementation context. Keep connection setup, transaction import, and reconciliation review distinct: the documented import output is ready for reconciliation, not already reconciled.

3. Which SuiteCloud features are required before installation?

All three documented prerequisites appear on the SuiteCloud subtab. Verify each feature individually before installing Japan Bank Feeds.

Required feature	Location	Required setting before installation
Custom Records	SuiteCloud subtab	Enabled
Client SuiteScript	SuiteCloud subtab	Enabled
Server SuiteScript	SuiteCloud subtab	Enabled

Use the exact feature labels in the readiness record. A note saying only “SuiteScript enabled” leaves the check ambiguous because the prerequisites identify Client SuiteScript and Server SuiteScript separately. Neither check substitutes for Custom Records.

If any required feature is not enabled, enable it before installation. Record the three results separately so the installation owner can distinguish confirmed settings from checks that remain outstanding.

Keep required settings separate from recommended preparation. Reviewing GL mappings is useful, but it does not replace any of these three feature requirements. Conversely, confirming all three features does not establish that account mappings have been reviewed.

Treat this as an installation checklist, not evidence of a release-specific configuration change. The supplied capability and installation documentation does not establish a before-and-after behavior, a migration requirement, or a requirement for existing connections to be changed.

4. What access is needed to install Japan Bank Feeds?

Japan Bank Feeds is a public SuiteApp. Users whose role has access to SuiteApp Marketplace can install it. Check the role that will actually perform the installation, rather than relying on the installer’s job title.

Complete the access review:

1. Identify the installation owner and selected role. Make that role the subject of the Marketplace access check.
2. Confirm SuiteApp Marketplace access. Use a role with that access for installation.
3. Assign the later validation review. Identify banking and accounting participants who will review intended accounts, GL mappings, and daily import results.

Marketplace access establishes the documented installation condition. It should not be treated as confirmation that the same role can perform every subsequent connection-management or day-to-day banking task. The supplied material does not enumerate those operating permissions.

For a practical handoff, distinguish who installs the SuiteApp from who reviews the banking results. One person may participate in both activities, but the checklist should still show which checks have actually been completed.

5. How do you install the Japan Bank Feeds SuiteApp?

After confirming account scope, required features, and installation access, follow the documented sequence:

1. Go to SuiteApps.
2. Enter Japan Bank Feeds in Search SuiteApps.
3. Click the Japan Bank Feeds tile.
4. Click Install in the upper-right corner.

Use the exact SuiteApp name in the search and installation record. Record the prerequisite checks completed before the installation action so the next reviewer can distinguish installation readiness from later validation.

Do not close the banking rollout merely because the installation procedure has been performed. Prepare this recommended handoff for the next stage:

Validation item	Review question
Intended connections	Do the proposed connections match the agreed list of accounts located in Japan?
Visible account information	Is the expected Japan-based account information represented in the consolidated account view?
GL account mapping	Have feed bank accounts been reviewed against their relevant GL accounts?
Daily import results	Have the daily import results been reviewed as transactions ready for reconciliation?

These checks reflect documented capabilities; they are not additional installation prerequisites. Give each review item an owner and record what remains outstanding. This lets the administrator hand over the installation without implying that the accounting team has already accepted the imported results.

FAQ

Which accounts are eligible for Japan Bank Feeds?

Connections are limited to accounts located in Japan. In a multinational rollout, separate Japan-based accounts from accounts located elsewhere, even when they share a financial institution relationship.

Which SuiteCloud features must be enabled?

Enable Custom Records, Client SuiteScript, and Server SuiteScript on the SuiteCloud subtab before installing Japan Bank Feeds. Check both SuiteScript features separately.

Who can install Japan Bank Feeds?

A user whose role has access to SuiteApp Marketplace can install the public SuiteApp. That access is not confirmation of subsequent connection-management permissions.

Does Japan Bank Feeds reconcile imported transactions automatically?

The documented capability is automated daily import of transactions ready for reconciliation. Do not treat imported transactions as already reconciled.

Related reading

• Match Bank Data workflow changes
• Reconcile Account Statement enhancements overview
• Yodlee format profile availability for new NetSuite accounts
• Auto Bank Statement Import SFTP configuration