payment-reconciliation
Skill4 starsChanged 7 months agoMITView on GitHub
Use when matching payments, deposits, processor payouts, remittance advice, bank activity, invoices, credit memos, and unapplied cash for finance operations.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- megandmartin/agent-skills-repotheir own version, first seen Jul 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- megandmartin/agent-skills-repo★ 3same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- ar-collectionsSkill
- cfo-briefingSkill
- contract-to-invoiceSkill
- dunning-emailsSkill
- finance-close-checklistSkill
- invoice-health-checkSkill
- revenue-recognition-qaSkill
- usage-billing-reviewSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill to match cash activity to invoices and identify reconciliation exceptions.
- Distinctive: line 36
Do not post entries, apply payments, issue refunds, or write off balances.
- Distinctive: line 37
Do not force-match weak evidence to clear a variance.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Payment Reconciliation
Use this skill to match cash activity to invoices and identify reconciliation exceptions.
Inputs
- Bank export, processor payout report, or payment gateway export.
- Invoice register, AR subledger, customer IDs, and payment references.
- Remittance advice, lockbox files, or customer emails.
- FX rates, fees, chargebacks, refunds, credits, and unapplied cash reports if available.
Workflow
- Normalize dates, currencies, customer names, references, invoice IDs, and amounts.
- Match using strongest evidence first: invoice ID, payment reference, customer ID, exact amount, remittance detail, then fuzzy name/date/amount matching.
- Separate fees, refunds, chargebacks, FX variance, partial payments, and overpayments.
- Assign match confidence: exact, strong, probable, weak, or unmatched.
- Prepare an exception list for manual review.
Output
Return:
- Reconciliation summary: matched amount, unmatched amount, fees, refunds, and material exceptions.
- Match table with payment, invoice, amount, date, confidence, and evidence.
- Unmatched cash and unapplied credit queue.
- Recommended journal or subledger action as a draft only, never posted.
Guardrails
- Do not post entries, apply payments, issue refunds, or write off balances.
- Do not force-match weak evidence to clear a variance.
- Preserve original transaction IDs and source filenames.
- Flag duplicate payments and suspicious activity for human review.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.