Connect HubSpot invoices and journals to MoneyForward with Sanka
Use Sanka to review HubSpot-sourced invoices and journal entries, then export them to MoneyForward Cloud Accounting.
Last updated: June 3, 2026
Set up MoneyForward with Sanka so HubSpot-sourced invoices and journal entries can be reviewed in Sanka before they are exported to MoneyForward Cloud Accounting, and so the MoneyForward records stay traceable back to the original Sanka data. Start with a test business, validate the result, then move to your live business once your account and tax mappings are confirmed.
Prerequisites
Sanka workspace admin access.
A MoneyForward Cloud Accounting business you can use for testing first.
A connected MoneyForward integration in Sanka.
Draft Sanka invoices with a customer, issue date, due date, currency, and line items, or journal entries you intend to export.
An operating rule for MoneyForward accounts, tax classes, sub-accounts, and departments.
Account mappings and tax mappings that map Sanka line items and accounts to MoneyForward accounts and tax classes.
A review process for duplicate exports. If a Sanka record is already linked to MoneyForward, review the existing reference before exporting again.
Sample prompt
/sanka Review this MoneyForward export plan before making any changes. Confirm the target business, the Sanka invoice or journal entry, account mappings, tax mappings, issue date, amount, debit/credit, duplicate export risk, and whether accounting should approve the content before posting. Do not export live data or recreate MoneyForward records until I approve the plan.
HubSpot to MoneyForward workflow
Use this workflow when HubSpot is the CRM source and MoneyForward is the accounting destination.
Review the HubSpot company, billing contact, deal, line items, amount, currency, tax, and payment terms in Sanka.
Create or review the Sanka invoice from the HubSpot deal, or the journal entry for accounting.
Export the reviewed Sanka invoice or journal entry to MoneyForward Cloud Accounting.
Keep the Sanka data, HubSpot deal, MoneyForward reference, payment status, and export history linked for audit.
Before go-live, decide how MoneyForward accounts, tax classes, sub-accounts, departments, payment matching, and reconciliation exceptions should be handled.
Connect
In Sanka, open Workspace > Integrations.
Select Create integration, then choose MoneyForward.
Authorize the target MoneyForward business, or enter the test credentials provided by your admin.
Confirm MoneyForward appears in the integration list, then share access with the teammates who need to export data.
Export rules
MoneyForward export creates MoneyForward Cloud Accounting records from a Sanka invoice or journal entry.
For journal export, Sanka accounts and tax classes are converted to MoneyForward accounts using the configured account mappings and tax mappings.
Issue date, amount, debit/credit, description, and reference are copied where available.
Sanka records the MoneyForward reference and export history so your team can trace which Sanka record created the MoneyForward entry.
Re-syncing or updating an existing MoneyForward record is not part of the basic export flow. If a record has already been exported, review the existing MoneyForward data before exporting another copy.
Map invoice, journal, and reconciliation fields
Review these mappings before the first live export.
Source
Field to check
MoneyForward impact
HubSpot deal
Deal name, close date, owner, amount, currency, line items
Source context for the Sanka data and export history
Sanka invoice
Customer, issue date, due date, invoice number, line items, tax
MoneyForward partner, issue date, reference, and tax treatment
Sanka journal entry
Account, sub-account, debit/credit, amount, tax class, description, posting date
Posted as a journal through account mappings and tax mappings
Accounting owner can decide whether to export, adjust, or hold
HubSpot writeback
Invoice URL, payment status, reconciliation status, open balance
Sales and CS can see customer status without asking finance
Export Sanka invoices to MoneyForward
In Sanka, open Commerce > Invoices.
Select the invoices you want to send to accounting.
Select Export.
Set Export destination to Integration, then choose the MoneyForward integration in Integration.
Review the selected invoices, then click Export invoices.
Export Sanka journal entries to MoneyForward
In Sanka, open Accounting > Journal entries.
Select the journal entries you want to export.
Confirm the account mappings and tax mappings resolve correctly for the target business.
Select Export, then choose the MoneyForward integration as the destination.
Confirm posting date, debit/credit, amount, account, and tax class, then run the export.
After export, open MoneyForward and review the record before posting it. Confirm the partner, issue date, account, tax class, debit/credit, and amount.
Validate the setup
Use a test business first and export one small invoice or journal entry.
Confirm the account mappings and tax mappings apply correctly and that debits and credits balance.
In Sanka, open export history and confirm the export status and linked MoneyForward reference.
Try a journal entry that is missing an account or tax mapping and confirm it is blocked before export.
Review after export
In Invoices or Journal entries, confirm the Sanka data remains available for audit and that the export history shows the result.
In MoneyForward, confirm the record is not posted until your accounting team approves it.
If accounting changes accounts, tax classes, or amounts in MoneyForward, note the final accounting treatment in your internal process.
If the export fails, review the Sanka data and the account and tax mappings first, then check the business and authentication status.
Troubleshooting
MoneyForward is connected but export fails
Check the selected business, authentication status, the Sanka invoice or journal entry, account mappings, and tax mappings. Most export failures are caused by missing mappings, unbalanced debits and credits, or expired authorization.
The journal does not balance
Review the Sanka line item accounts, amounts, taxes, and rounding, and confirm the account mappings and tax mappings apply correctly.
MoneyForward posted the wrong account
Check the account mappings and tax mappings. Review whether the Sanka account resolves to the correct account in the target business before exporting again.
Duplicate records were created
Check Sanka export history and the MoneyForward reference before exporting again. The basic export flow creates a record and does not automatically merge with or update an existing MoneyForward entry.
Checkpoints
Use Sanka invoices, journal entries, export history, action history, workflow history, and audit logs together with the MoneyForward record to confirm what happened before replying to a customer or asking AI to make a code change.
1Checked accounting approval2026/05/10 16:30MoneyForward journalConfirmed balance and accounts before postingSanka user
A safe review should include the Sanka invoice or journal entry, target business, account mappings, tax mappings, debit/credit, amount, export history, duplicate risk, and accounting approval state.
Go-live tips
Run at least one export in a test business before using a live MoneyForward business.
Confirm the account mappings and tax mappings before the first live export.
Keep the first live batch small and compare Sanka totals against MoneyForward totals.
During the first week after go-live, review export history and MoneyForward records daily.
