Money Forward Cloud Tax Return setup: five checks before connecting accounts
Choose the accounting year and prepare opening-balance records and a list of accounts. Connect one account first, then compare a short period with the original statement. Importing a transaction does not register it in the books; review and confirm the journal entry separately.
All contents
Test one account in four stages
Compare a short set of imported transactions with the original statement. Check for gaps and duplicates, then separate registered entries from those still awaiting review.
Record the year and existing coverage
Distinguish a new setup, migration and continuation. Locate dated opening records and the existing ledger. Note the connection's import start date separately from the period the books need to cover.
Connect one account with a source statement ready
Check the bank's available history and register through the official flow. Choose a short review period and keep the original dates, amounts and descriptions available for comparison.
Reconcile imported and registered items
Compare the import with the source before reviewing a few entries. Separate missing records, suspected duplicates and unresolved classifications, and establish their causes before processing a larger batch.
Record gaps and the next check
If you add unavailable history separately, compare the dates with the imported range first. Check retrieval status and timestamp, then repeat the verified process for another account or period.
Five things to prepare before connecting accounts
| Prepare | Check | If something is missing |
|---|---|---|
| Year and existing records | New setup, migration or continuing an existing year | Identify what another ledger already contains |
| Dated opening records | Statements and applicable prior-year closing records | Find the relevant date rather than copying today's balance |
| Bank and card list | Service, purpose and access to web statements | Separate connection candidates from other transactions |
| Statement coverage | Required dates, available dates and overlapping imports | Locate source records for the missing period |
| Reconciliation record | Imported, registered, unresolved and suspected duplicates | Test a small sample before batch processing |
This is an editorial setup checklist, not a complete list of Japanese tax obligations.
The day you install the software is not your opening date
Starting the software in September does not establish that your records only need to start in September. Write down the year and period you intend to manage, and whether another ledger already contains part of that period. Distinguish a first setup, a migration and continued use so that an initial setup does not recreate work that has already been completed.
Money Forward's opening-balance guide explains dated opening records and different preparation paths based on the prior year's circumstances. Check the date on your supporting statement before entering a number; today's bank balance is not automatically the relevant opening figure. Existing users should check the carry-forward guidance rather than repeat a first-time setup. Resolve the correct starting records before trying to make later totals agree.
Start with an account whose transactions you can explain
The documented entry point is データ連携 followed by 新規登録, where you select and register a financial service. Confirm the applicable service variant, not just the bank's brand name, and follow the authentication method shown. List the accounts and cards you intend to use first, especially when one financial service contains several accounts.
Our suggested test is one familiar account over a short period before connecting everything. Compare dates, amounts and descriptions with the original statement, and make sure you can identify the account behind each row. Authentication belongs in the official authorization flow. A working note should record which service you connected and what happened, without copying passwords or one-time codes into the checklist.
Check historical coverage before filling a gap
The missing-transactions guide explains that records unavailable in the bank or card's web statement may not be retrievable through the connection. Compare the earliest imported transaction with the beginning of the period you need. A successful connection does not establish full-year coverage. Also check whether an explicit automatic-import start date limits the requested period.
If records are missing, check account visibility and the accounting year. For transactions that remain unavailable, follow the documented manual-entry or import method. Identify the missing dates and compare them with existing entries before adding records, to avoid duplicates.
Count imported transactions separately from registered entries
連携サービスから入力 is where you register journal entries from imported transactions. A row appearing in the imported list does not mean it has been entered in the books. Keep track of registered items, items awaiting review and any records you exclude, with the reason.
Test a few records before using batch registration. Compare each date, amount and description with the source and review the proposed settings. When both a bank and card are involved, or when you already entered a transaction manually, check that the same payment has not become two separate expenses. Keep uncertain account or tax classifications on a review list instead of turning an unverified guess into a reusable automatic rule.
Include a stopped connection in your setup plan
登録済一覧 shows the last acquisition time and acquisition status, including conditions requiring additional authentication. The official guide says manual individual and bulk reacquisition are unavailable in the unpaid state. It also says bulk reacquisition does not resolve a connection in a settings-error state. Identify the actual condition before assuming a paid plan will fix missing data.
Note when to check the connection again, where to look if retrieval stops, which transactions need review and where the source documents are saved. Preparing and submitting the return come later. Check the features and plan needed for those steps separately.
Example: twelve statement transactions, nine imported
This is a hypothetical setup exercise, not measured product performance or a tax example. It does not mean all 12 transactions are deductible expenses.
- Source statement
- 12 transactions listed by date, amount and description
- Imported records
- Nine; identify the three absent source transactions
- Status of the nine
- Seven confirmed as registered, two still under review
- Next investigation
- Coverage and visibility for the missing three; details of the unresolved two
Before adding the missing three, find out why they are absent and check whether they were registered another way. Keep a count of registered transactions and those still awaiting review before moving to the next account.
Things to watch for
Using today's balance for an earlier opening date
Match the supporting document's date to the opening period. Inventing an adjustment simply to force agreement hides the source of a mismatch.
Importing the same coverage twice
A replacement connection or additional import may overlap existing entries. Record what is already in the books before adding the next file or period.
Assuming an automatic suggestion is correct
Imported data does not resolve tax treatment. Review uncertain items before copying a classification into a batch or automatic rule.
Resolve gaps and duplicates before adding more accounts
Keep the year, opening records, connected accounts, imported dates and unresolved transactions together. Once a small sample works, repeat the process for the next account. Check the features and plan needed to prepare and submit the return separately.
Frequently asked questions
Does connecting a bank automatically complete my return?
No. Importing transactions, checking and registering entries, preparing supporting information and completing the return are separate stages. This guide stops at the initial data-validation workflow.
Can a midyear connection retrieve everything since January?
That depends on available bank or card history and the connection settings. Compare the oldest imported date with the period you need, then locate original records and an appropriate input route for any gap.
Can I manually refresh transactions while using the product unpaid?
The reviewed guide says individual and bulk reacquisition are unavailable in the unpaid state. Also investigate status, authentication and coverage before deciding whether a plan change is relevant.
Scope and key points
Who this helps
- You are setting up the individual Japanese Cloud Tax Return product
- You want a preparation and reconciliation process before connecting banks or cards
Limits of this guide
- You need the corporate product or the ME household app
- You need an individual tax ruling or someone to file on your behalf
Key points
- Choose the year and find records for the relevant opening date
- A successful connection does not prove complete historical coverage
- Reconcile imported, registered and unresolved items before processing more
What the sources say
Opening records should match the relevant date; setup and carry-forward depend on existing circumstances
Connecting services, registering entries and preparing or submitting a return are distinct stages
Available web history, year, visibility and the import start date affect coverage
Retrieval status and timestamps are visible; manual reacquisition is restricted in the unpaid state
References
- 1.確定申告はじめてガイド（事業所得や不動産所得を申告）
マネーフォワード · Retrieved Sep 9, 2026
- 2.開業時や導入時の開始残高の入力
マネーフォワード · Retrieved Sep 9, 2026
- 3.新規登録画面の使い方
マネーフォワード · Retrieved Sep 9, 2026
- 4.データ連携で表示されない明細がある場合
マネーフォワード · Retrieved Sep 9, 2026
- 5.連携サービスから入力画面の使い方
マネーフォワード · Retrieved Sep 9, 2026
- 6.登録済一覧画面の使い方
マネーフォワード · Retrieved Sep 9, 2026
About this article
We reviewed six official Money Forward guides covering initial use, opening balances, financial connections, journal registration and missing transactions on September 9, 2026. This is a documentation-based preparation workflow with an editorial example, not a hands-on review or tax determination.
How we use AI in our research and writing ↗