Open finance skill
Remittance matching review
Which remittance notices can be tied confidently to payments and invoices?
Match stated payer, amount, date, and invoice references while preserving partial and ambiguous allocations for review.
Inputs
- ✓Remittance advice
- ✓Payments
- ✓Open invoices
Outputs
- ✓Exact matches
- ✓Partial matches
- ✓Ambiguous queue
Checks performed
- ✓Invoice reference
- ✓Amount and date
- ✓Allocation completeness
Guided synthetic example
See the check from input to decision
A remittance email lists two invoices, but the bank deposit is slightly lower than their combined value.
This is the operating model we use at Level. The percentages are estimated shares of the work in a typical review. Actual effort varies with data quality, complexity, and the issue found.
Start with the source records
About 15% of work| Evidence | Reference | Amount |
|---|---|---|
| Remittance | INV-410 + INV-414 | $18,750 |
| Bank deposit | DEP-81 | $18,625 |
| Difference | Unknown | $125 |
Run the deterministic check
About 20% of workMatch invoice references first, then compare payer, amount, date, and allocation completeness.
Surface the flagged result
About 10% of workNeeds review
The remittance and deposit differ by $125, so the allocation remains partial rather than matched.
Use recorded finance judgment to analyze possible reasons
About 25% of workAt Level, we record the review logic, known explanations, and questions our finance professionals use in this situation. AI applies that documented human judgment to organize the most plausible reasons, without pretending it knows which reason is true.
Possible reasons to investigate
The difference might be a fee, short payment, credit, withholding, or an unrelated deposit issue.
Make the final human judgment
About 20% of workA Level finance professional validates the source evidence, challenges the AI-assisted analysis, and decides which explanation is supported.
Make the operating decision
About 10% of workConfirm the reason and authorized allocation before applying the payment to either invoice.
Use this system
Start with the example, then inspect the structure
- Download the invented input and expected output.
- Replace one field at a time with a safe test value.
- Compare the result with the expected structure.
- Have a finance professional review every exception before acting.
MCP preview
run_synthetic_example {"slug":"remittance-matching-review"}Human review is part of the system
This check organizes evidence and surfaces exceptions. A person with finance domain expertise still needs to interpret the result, validate the source records, and discuss the operating decision.
Open source does not mean open client data. We publish reusable finance tools, checks, templates, and playbooks. Client records, workpapers, credentials, communications, and private configurations remain confidential.