Automate French-style account matching
Match debit/credit entries within your third-party accounts and assign matching codes.
Introduction
French-style account matching (assigning codes to pair debits and credits in 401/411 accounts) isn't natively supported by Anglo-Saxon ERPs like NetSuite or SAP. Result: unsettled third-party accounts, unreliable aged balance, and blocked closing.
Phacet imports your GL exports for third-party accounts, intelligently matches debits and credits (exact, partial, multi-line) and assigns matching codes. Ambiguous cases are surfaced with suggestions and a confidence score.
When to use this Phacet
Built for accountants, bookkeepers or CFOs who want to:
• Automate third-party account matching (401/411) without spending days on it.
• Solve the French-style matching problem in an ERP that doesn't support it natively.
• Make the aged balance reliable by ensuring every payment is properly matched.
• Unblock monthly closing by removing the matching bottleneck.
AI skills involved
Automatically match your data across files, tools and systems
Phacet cross-references your data across sources - invoices vs. payments, POs vs. receipts, bank lines vs. GL entries, CRM deals vs. billing records. It tells you exactly what matches, what's missing, and what's off. No VLOOKUP, no manual comparison.
Validate every line against your rules, thresholds and references
Define your rules once - negotiated prices, spending caps, expense policy, contract conditions, approval thresholds - and Phacet applies them to every single row, every time. Every discrepancy is flagged with the exact reason, ready for review.
Route exceptions to the right person and track every decision
Phacet doesn't decide edge cases alone. It routes ambiguous results to the right person with full context - original document, matched data, confidence score. Your team validates, corrects or rejects. Every decision is logged. The AI learns from each correction and gets more accurate over time.
Every AI result linked to its source — audit-ready by default
Every output Phacet produces is traceable back to the exact source line - the PDF page, the ERP row, the bank entry. You can always answer "why did Phacet flag this?" with a precise reference. Confidence scores, decision logs and source citations are built in, not bolted on.
Business impact
81% time savings on matching
From 1-3 days per month to 2-3 hours. High-confidence matches pass automatically; ambiguous cases are reviewed.
Third-party accounts finally cleared
Accounts 401 and 411 are matched systematically. The aged balance reflects reality; dunning is reliable.
NetSuite/SAP problem solved
French-style lettrage finally works, even if your ERP doesn't natively support it. The matched FEC export is ready.
Integrated with everything
Steps to get Started
Load your General Ledger exports
On accounts 401 (suppliers) and 411 (customers), in CSV, Excel or FEC format.
Phacet matches entries by exact amount
Partial amount or multi-line grouping — each match receives a confidence score.
Validated matches receive a matching code
Ambiguous cases are surfaced with suggestions for human review.
The result is exportable as a matched FEC
Or in a format compatible with your ERP. The automatic matching rate is tracked.
Unlock your AI potential
Do more with your existing resources using tailored AI solutions.
Frequently Asked Questions
Yes. Phacet handles cases where a payment partially covers an invoice, or one payment covers multiple invoices.
Yes. This is one of the main use cases. NetSuite doesn't handle French-style lettrage natively — Phacet fills this gap.
Generally 60-80% from the first cycle on a FEC with auxiliary accounts. The rate improves over time.
Yes. A FEC export with matching codes (EcritureLet column) is generated automatically.
Yes. Each validation or correction improves the model. The automatic matching rate increases month after month.
