AI and the Management Paradigm Shift
Working with AI · Part 2
Imagine an invoice arriving just before month-end. AI can read the supplier and amount. It can also check a purchase order and receiving record and post the invoice when conditions are met. Managers then have to decide when posting is allowed, who handles discrepancies, and what evidence is needed to reverse a mistake.
Set authority at each step
Reading, matching, posting, and paying have different consequences. A matching invoice from an approved supplier can enter the payment queue. A quantity discrepancy or a change in bank details goes to a designated reviewer. Payment still follows the company’s approval process. The reviewer should see the relevant documents and the exact fields that disagree, so they can act without reconstructing the case.
Measure the whole workflow
Week 2 of New Machine Age & IT discusses establishing a baseline before testing a recurring process. Track time to posting, exception wait time, duplicate entries, and corrections. A faster posting process can leave another team with a larger queue. Keep a record of who approved each exception and why, so recurring cases can inform the next revision of the rules.
Separate proposing from approving
GitHub’s Copilot coding agent can propose changes through a pull request. Its approval and merging powers are restricted, and reviewers can inspect the proposed changes and request revisions. Apply the same distinction to invoices by showing the purchase order and receiving record beside the proposed entry. Give posting and payment approval separate permissions, check for duplicates, and record where rejected or corrected entries were caught.
GitHub’s coding agent overview · GitHub’s security and governance documentation
When an invoice changes paths
If 12 of the 15 discrepancies turn out to be staggered deliveries, show the quantity received and the expected arrival date together. Reviewers can then identify which invoices should wait for the remaining shipment.
- Match invoice, order and receipt
- Match → post pending payment
- Mismatch → route for review
- Authorized approver releases payment
Illustrative batch. Each invoice is assigned to one route. Automatic posting leaves payment approval pending.
Verify account changes through an established contact channel and retain the approval record. Compare completion times and corrections by route to see whether exceptions are building up.