MosoFin skill · three-way-match · learning guide

From one invoice to a whole month of them

This page shows how the skill decides whether to pay a supplier's bill. It goes one level at a time. The first level is a single order that matches perfectly. The last level is a month where the delivery records live in a different system. The page quotes every rule from the skill itself. It calculates every number in front of you.

The rules are the skill's ownThe page quotes each rule with the step it comes from, so you can read it yourself.
An authority backs each ruleThe authorities are US procurement rules, the GAO's internal-control standard, the fraud examiners' association, the IFRS Foundation and QuickBooks' own documentation. The page gives each one a number and a link.
The page shows the mathOpen "Check it yourself" on any level. Follow every line on a calculator.
Your numbers, your checkAt the end, enter your own order, delivery and invoice. Then watch the same rules run.
Rule: quoted from the skill Fact: from a cited authority, numbered like 1 Example: made-up figures, worked out in full
How it thinks

Five rules the whole skill runs on

Everything on this page applies one of these rules to a bigger situation. The examples use one company, Northbrook Trading, one supplier, Ashford Seating, and the month of September.

Learning path

Seven levels, from simple to complex

Check it yourself

Put in your own order, delivery and invoice

Enter one line of one invoice. Alternatively, load one of the levels above. The page compares price and quantity and applies your tolerance. Then it splits the invoice into the part to pay and the part to dispute. The page sends nothing anywhere.

From the purchase order
From the goods receipt
From the invoice
Your tolerance policy (leave blank for exact match)

The split follows the skill's Step 5. The skill recommends that you pay the matched portion and dispute the remainder. "Matched portion" here means the smaller of received and billed quantity, at the agreed price. The skill's default with no tolerance is exact match, so any difference is an exception. The fifteen exception types and their severities are the skill's own rules, not a published standard.

Sources

Where every fact on this page comes from

Rules are the skill's own. Facts below come from procurement regulation, the US internal-control standard, the fraud examiners' association, an accounting standard-setter and the accounting software's own documentation. They match each source as it read when MosoFin checked it on 21 October 2026. Follow the link for today's wording.

    No outside authority backs the fifteen exception types and their severities, the exact-match default or the matching precedence. The matching precedence is line number, then SKU, then description. These are the skill's own rules. The page marks them as the skill's where they appear.

    Using it

    What it asks, needs and gives back

    Asks firstShould the data source be MosoFin, or an upload? What is your tolerance? Who may approve what? Which services are in scope, and what stands in for a receipt? What is your foreign-currency policy? Who owns exceptions?
    NeedsThe skill needs the invoices, which are always in the books. It needs purchase orders where the system holds them. It needs delivery records, which it usually has to request.
    Gives backThe skill reports Pay / Hold / Reject per invoice. It lists every line side by side with its match basis. It names an owner for every exception. It lists the tests that could not run and the month's patterns.
    NeverThe skill never pays, holds or releases money. It never invents a tolerance. It never lets an untested check read as a pass. It never concludes fraud. It reads nothing before you say yes.