Explanations and entries
How unmatched items are classified, what a citation must contain, how draft entries are built, and what 'needs a person' means.
Input to the model
For each unmatched item: the ledger line, candidate documents found by reference and amount, relevant agreement clauses, the FX policy, and the prior-period explanation if any.
Required output
- Class — one of nine: timing, FX translation, rounding, bank charge, withholding/tax, discount/deduction, duplicate/misposting, missing document, dispute.
- Reason — one paragraph in plain language.
- Citations — at least one: document id, page, and line or cell. Every number in the reason must trace to a citation.
- Draft entry — debit/credit lines in the workspace chart of accounts, or no entry for disputes and missing documents.
- Confidence — high / medium / low.
Validation
Outputs without citations are rejected and re-asked once. A second failure marks the item needs a person and attaches the candidate documents. Numbers in the reason that do not appear in any cited document fail validation.
Draft entries
Built from the chart of accounts you upload (or the default group chart). Entries are drafts: they are exported or sent to the entity controller; the product never posts.
Recurring items
If an item matches a prior-period explained item by reference and amount, it is shown as explained [period], not booked with the previous explanation linked, rather than re-explained.
Disputes
When the documents genuinely contradict each other, the agent produces a dispute summary — both positions, the clause, the evidence — and no entry. Controllers decide.
Reviewing
Accept, edit (class, reason, entry), or send as a question to a named person with the evidence attached. All actions are logged with user and time.