CONNECTED BUSINESS OPERATIONS
Confirm which invoice a payment belongs to
Review suggested allocations, partial amounts and the remaining balance before confirming a bank match.
Match the amount received, keep the remainder visible
A reviewed allocation links the bank credit to the invoice without hiding a partial payment.
A clear responsibility in your daily work
A bank credit can cover one invoice, only part of an invoice or several obligations. Similar customer names are not a sufficient basis for recording payment. Tsumira separates a reconciliation proposal from its confirmation and keeps the outstanding document amount visible to the decision.
Start from eligible open invoices
Matching considers issued, partially paid and overdue invoices with remaining whole-JPY amounts. Review the customer identity, invoice reference and transaction details. A proposed match can explain why it was selected, but a confidence indicator is supporting information rather than permission to skip the business check. Amounts use whole Japanese yen and Japanese consumption-tax categories. Check whether the document is tax-inclusive or tax-exclusive, which tax treatment applies, and which customer or case it concerns. This finance workflow is designed for that scope; it does not establish suitability for another country's accounting obligations.
- Use document identity and remaining amount together.
Review the actual allocation
A proposal contains explicit document amounts. Confirm that the allocation matches the payment received and does not rely on an old balance. Partial reconciliation has its own state; a payment smaller than the full invoice is not evidence that the remaining amount should disappear or be written off. Preparation, permission to act and the final financial result are separate checks. Review the relevant document state and any approval requirement before issuing, correcting or recording a financial action. AI assistance stays subject to review and the user's permissions; an explanation or proposed action is not proof of execution.
- Make partial payments explicit.
A partial match leaves a real balance
Review the exact allocation and whether the proposal still matches the current balance.
After confirmation inspect the recorded payment and the remaining invoice amount.
Inspect the confirmed result
Confirmation creates and allocates the payment through the finance workflow. Check the resulting transaction state and invoice outstanding amount. Rejected or stale proposals need another review rather than blind reuse, particularly if someone else allocated a payment while the first reviewer was considering the match. Keep the source reference and inspect the resulting document, payment or evidence record. Changes in outstanding amounts need a business explanation, particularly when several people work on the same case. Agree who checks exceptions and who reconciles the final result with the accounting process used by your business.
- Check the resulting payment and remaining invoice balance.
A concrete workflow
Prepare the context
Choose an incoming bank transaction and inspect its reference, counterparty, amount and relevant open invoices.
Review the decision
Review the proposed document allocations, checking partial amounts and whether the proposal still reflects the current balance.
Check the result
Confirm only the intended match, then inspect payment evidence and the remaining amount on each affected invoice.
An illustrative working example
Illustrative working example
A customer sends JPY80,000 toward an invoice with JPY100,000 outstanding. The reviewer checks the identity and allocates the received amount. The remaining JPY20,000 stays a separate collection question; the match is not a request to erase it.
Questions about this topic
Is a suggested match final?
No. A proposal is reviewed before confirmation. Rejected or outdated proposals should not be treated as paid invoices.
Can reconciliation be partial?
Yes. Partial reconciliation and invoice balances are represented explicitly; review the allocated amount.
Does this move money at the bank?
This workflow records and allocates an imported payment. It does not itself establish bank-transfer execution.
Can we ignore differences between payment and invoice?
No. Investigate a difference and use the appropriate financial action rather than silently changing the allocation.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Stripe Connect
Workflow concept: Compare payment amount and reference with the remaining invoice balance before confirming a match.
Microsoft Excel
Workflow concept: Review split-payment allocations in a checked reconciliation worksheet.
Gmail
Workflow concept: Check a customer’s remittance explanation when an imported transaction is ambiguous.