The milestone decides how it’s checked
Not every charge can be matched the same way — an advance payment has no delivery behind it. So the check is chosen by the type of milestone being billed, not by the order:
One rule applies to every type: the total billed against a milestone, across all its invoices, cannot exceed that milestone’s share of the order.
The three outcomes
- Matched — every check passed.
- Partial — the only thing outstanding is a goods receipt. The invoice isn’t wrong; it just can’t be fully verified yet. Record the receipt and re-run the match.
- Exception — at least one check failed. The match panel names the line and shows expected versus actual, with the difference.
What Seloria flags
Tolerances
Three settings control how strict the match is:These tolerances are stored per organization and are not yet editable from Settings. If you need different values for your organization, contact support.
Resolving an exception
You have three ways out, and which one is right depends on what the flag is telling you:- Fix the record. If the goods receipt hadn’t been entered yet, record it and use Re-run match. Most partials and over-receipt flags disappear this way.
- Correct the invoice. If the supplier billed the wrong quantity or the lines were mis-entered, edit it and re-run the match.
- Approve with an override. If the difference is legitimate — an agreed price change, a freight charge that was never on the order — the approver can approve anyway, but must write down why.

