Start with previous work
Import linked historical applications. Inspect the evidence and confirm supported payer relationships together, without labeling every old transaction.
Cash application for lean B2B finance teams
Turn customer payments into clear invoice allocations.
A payment arrives. The name is unfamiliar, several invoices are involved, and the remittance is somewhere else. Bring current evidence and previous payment applications together. Reuse supported payer relationships, then investigate what is still unclear.
Financial rows stay in this tabNo bank credentialsYou approve; your ledger posts
Synthetic example · one ACH, three invoices
ACME TREASURY
Customer: Acme Distribution
$9,750
Remittance: “INV-101 $4,000; INV-102 $3,500; INV-103 $2,500 less $250 freight claim.”
| Invoice | Apply cash | Still open |
|---|---|---|
| INV-101 | $4,000 | $0 |
| INV-102 | $3,500 | $0 |
| INV-103 | $2,250 | $250 |
$250 stays unresolved. Applying the cash does not accept the freight claim, create a credit or mark every invoice settled.
Try the history-backed demoThe work between your bank and your books
Don’t rediscover how a familiar customer pays.
A short payment, not a write-off
Apply the amount actually received. Preserve the remaining invoice balance and review a claimed deduction separately.
An amount match without evidence
Two invoices can be worth the same amount. Keep ambiguity visible and draft a focused request for the missing remittance.
From existing exports to reviewed instructions
Bring three sources together.
01
Bring current truth and history
Import current open invoices and incoming receipts, optional remittance advice and earlier payment-to-invoice applications. History informs payer proposals, never today's balances.
02
Resolve the exceptions
Confirm payer relationships. Review rules-based proposals, edit partial allocations, or leave cash unapplied when evidence is missing.
03
Export, then record
Download approved allocation instructions, unapplied amounts and a source-bound audit. Your finance team records the result in its existing accounting system.
Less data access. Clear limits.
Deterministic matching keeps financial CSV rows and decisions in page memory—no saved browser ledger or mailbox access. Refreshing or leaving clears the session. Remit has its own Clerk account, separate from ScopeMentor; hosting uses Vercel. Optional AI remains closed unless separately enabled and consented to.
See the exact data boundaryBuilt around incoming AR.
This release supports one legal entity per batch and structured CSVs. It is not full bank reconciliation, payment initiation, an ERP connector or an autonomous bookkeeper. AI extraction is not enabled. Signing in alone does not authorise paid processing.
Check formats and supported casesSee what happens when the evidence is incomplete.
Try twelve fictional receipts with earlier application history: supported payer relationships, shared-treasury conflicts, missing evidence, bundled and partial payments. The example uses no bank connection, upload or AI call.
Open synthetic example