Money Forward Cloud Accounting integration

Connect from Bookkeeping → Integrations → Money Forward Cloud Accounting. Journal imports start enabled. Wallet monitoring, automatic transaction feeds and MakePay notifications start disabled.

Connect an office

Create a production Money Forward API key with access to the Accounting service and the intended offices. Enter the complete mf_api_pro_ key, select Check API key, choose an accessible office and select Review office. Inspect its native name and office code, choose a fiscal period, and confirm the office before saving.

Money Forward documents entering a key into a SaaS settings screen. This connection does not require MakePay to register an OAuth application. The server exchanges the key for a short-lived session and encrypts the saved key in the context of your MakePay company and connection. Keys and sessions are not returned in connection summaries. See the API key overview and Accounting API.

Each connection targets one native office. Disconnect before selecting another office. Reconnecting the same office restores its connection identity and export history; review any retained automation settings. A native office can have only one active MakePay connection.

Journals and wallet feeds

Journals shows the latest 100 imported native journals for the selected fiscal period, including exact amounts, account lines and attachments. They remain journals and are not shown as customer invoices or outstanding balances. Imports run in bounded pages. Continue import requests the next page; scheduled sync resumes unfinished scans. Changed or inconsistent pages restart safely. A record not seen in the latest completed import is labelled for review rather than treated as a deleted invoice.

To export wallet activity, enable Monitor connected wallets, choose your company's wallet addresses and select a native manual clearing channel linked to an active asset account. Create or configure that channel in Money Forward first. Select expense detection and/or income feeds, then confirm that transaction exports use whole-yen JPY values. Monitoring starts when enabled; transfers between your own wallets, swaps, unconfirmed sources, sandbox sessions and payments already handled by another invoice connector are excluded.

Review each source and enter its accounting value in JPY before exporting a transaction feed. The source's UTC date is retained and displayed for approval. Token quantities are not converted into fiat values automatically. Automatic feeds are optional: expenses require a current approved local JPY expense; income requires a confirmed native JPY MakePay settlement. Other sources need a reviewed valuation. Automatic feeds do not automatically approve journal tax allocations.

The direct-key Accounting API supports journals and transaction feeds. Money Forward's separate Invoicing API has a different authentication contract; invoice matching, invoice creation and MakePay invoice checkout are unavailable through this connection.

Approve journal posting

After the feed is verified, choose the expense/revenue account, optional sub-account, native tax code and invoice classification. Enter the expected tax in whole yen and explicitly confirm that the clearing account's tax should be zero. A missing numeric native tax rate is shown for review and is never interpreted as zero.

The connection checks native account/tax eligibility and fiscal settings before first dispatch. The returned journal must prove the original transaction, date, fiscal year, gross amounts, accounts, sub-account, classification and expected tax allocations. Posting approval can be corrected before dispatch. Once dispatched, it remains locked for recovery.

This journalization path supports included-tax/inside-tax and exempt-office settings. Separate-tax offices need manual VAT lines; export the transaction feed and manage those journal lines and receipts in Money Forward. The connection does not change the office's tax configuration. See Money Forward's tax settings guide.

Receipts and recovery

Upload or link an invoice/receipt to the wallet source in Bookkeeping. PDF, PNG, JPEG and WebP files up to 5 MB are supported, with at most five per native journal. When required by settings, owned source receipts must be available before the expense feed is exported. After the native journal is verified, select Send receipt for each document, then Verify export. A verified feed alone is not a completed accounting export.

Each receipt intent preserves its original document, hash, native journal and filename. Successful acknowledgment saves the exact native file ID before checking the journal's attachments. Duplicate document content does not cause another upload. Known acknowledged files can recover through native attachment proof even if the local file later becomes unavailable. A removed native attachment is not uploaded again automatically.

After an uncertain transaction or journal response, recovery looks up the original native source reference or transaction relationship without posting a replacement. An uncertain or partial receipt acknowledgment requires review in Money Forward; a changed attachment count does not establish which file was uploaded. Use the displayed export reference and native file name when investigating. Cloud Box plan limits and native file-retention rules apply; see the voucher specification.

Optional in-app notifications cover expense review, export progress/completion and sync errors. Repeated events are deduplicated. Disconnecting stops scheduled processing and retains history. Handled in Money Forward hides a source from the active review workflow without claiming a verified journal or receipt.