← ALL PLUGINS
COREv1.0.0·MIT · FORKABLE

Payment Reconciliation.

artifi-core-reconciliation

Automated + manual payment-to-invoice matching

A complete payment-to-invoice reconciliation workflow that combines automated and manual matching. Mode 1 (Full Reconciliation) runs the 6-pass reconciliation agent first — exact amount, reference number, cross-reference, approximate FX, amount grouping, and Haiku fuzzy matching — then analyzes what remains and proposes manual matches for complex patterns like N:N splits and partial payments. Mode 2 (Quick Manual Match) lets you directly apply a payment to specific invoices with split amounts and rounding write-offs. Mode 3 (Health Check) provides a read-only status dashboard showing matched, partial, and unmatched counts with aging analysis and next-action recommendations.

↗ View on GitHubClone the repo
6-pass automated matching (exact, reference, FX, grouping, fuzzy)N:N split matching with rounding write-offsPartial payment application (invoice stays open)Before/after summary with match rate
COMMANDS · 3

Slash commands, shipped.

Each command is a guided procedure Claude follows step by step — with your review at every decision point.

/reconcile
Run full reconciliation workflow

Execute the complete reconciliation: assess current state, run the automated 6-pass matching agent, analyze remaining unmatched items grouped by party, propose manual matches (1:1, 1:N, N:1, N:N, partial), apply confirmed matches, categorize unresolvable items, and show before/after summary with match rate.

/match-payment
Manually match a specific payment

Directly match a specific payment to one or more invoices. Search for the payment, list open invoices for the same party, specify applied amounts per invoice, preview the match with status changes, and apply with confirmation. Supports partial matching and rounding write-offs up to $100.

/reconciliation-status
Check reconciliation health

Read-only status dashboard showing AP and AR payment reconciliation breakdown (matched, partial, unmatched), open invoice counts, aging of oldest unmatched items, and recommended next action.

HOW IT BEHAVES

One run, step by step.

The plugin prepares, validates, and previews. You confirm. Only then does anything reach the ledger — through the same governed gateway everything else uses.

Full Reconciliation
Assess current state — load unmatched payment and open invoice counts for AP and AR
Run automated reconciliation agent (6-pass matching algorithm)
Review agent results — how many matched, what remains unmatched
Group remaining unmatched items by party (vendor/customer)
For each party: load payments + invoices, propose manual matches using 6 strategies
Present match proposals as tables with amounts, logic explanation, and differences
User reviews and confirms matches (one confirmation per party batch)
Apply confirmed matches via submit("reconciliation", "match", {...})
Categorize unresolvable items (missing bills, unknown parties, overpayments)
Show before/after summary with total match rate
Quick Manual Match
Identify the payment (by ID or search)
List open invoices for the same party with amounts due
User specifies which invoice(s) and amounts to apply
Preview the match — show status changes for payment and each invoice
Apply after confirmation
VALIDATION GATE · 5 CHECKS

Every run
must pass.

If any checkpoint fails, the workflow stops and reports the issue. Nothing posts to the ledger until every check passes — the same dry-run-first discipline as the rest of the platform.

Legal entity exists and has posted transactions
Agent run completed successfully (Mode 1)
All proposed matches are valid — same party, amounts within limits, invoice has amount_due > 0
User has reviewed and confirmed match preview before applying
Post-reconciliation counts match expected changes
REFERENCE DATA · 3 FILES

Knowledge you can read and edit.

Formulas, templates, and regulatory rules live in plain files — not hardcoded values. Swap them for your firm’s policies when you fork.

matching-strategies.md

Six matching strategies in priority order: exact 1:1, partial, 1:N split, N:1 group, N:N complex, rounding write-off — with decision rules and examples

reconciliation-types.md

AR vs AP scope configuration, submit payload format, financial update behavior, and audit trail structure

troubleshooting.md

Common issues: no matches found, tax payments without bills, rounding differences, party mismatches, agent failures, and multi-currency FX handling

MIT · BUILT FOR ARTIFI · OPEN FOR EVERYONE

Run it here.
Or take it with you.

Out of the box it works with the Artifi ledger: Claude fetches your data, runs the procedure, validates the result, and submits through the governed gateway via MCP.

Or fork it. Skills, commands, validation logic, and reference data are all MIT-licensed. Swap the MCP tool calls for your own backend, or use the reference files as standalone Claude project resources.

MORE CORE PLUGINS
artifi-core-financial-reports
Financial Reports
Complete financial reporting suite
artifi-core-budget-planning
Budget Planning
Four-mode budget planning system
artifi-core-cost-allocation
Cost Allocation
Multi-method cost allocation engine