This run sheet belongs to the invoice processing rollout guide for AP automation advisors, which explains why the rejected-invoice trail matters. Use this page when the meeting is booked and you need the clock, the questions and the close.
Booking the slot and filling the four chairs
Hold the meeting after the new tool is chosen and before the import template is frozen. At that point the team can still describe the old approval workflow from memory, and the migration scope is not yet fixed. A one-line invite sets expectations: "Thirty minutes on what the old AP system knows about invoices it stopped. Description only; no files or screenshots."
| Seat | Why this person | Blocks they answer |
|---|---|---|
| AP manager or AP lead | Runs the approval workflow and knows why invoices are rejected or held | 1, 2 and 3 |
| ERP or capture-tool administrator | Knows which statuses, flags and notes are stored as records | 2 and 3 |
| Controller or CFO | Decides what happens to the old system and who owns AP history | 4 and 5 |
| Rollout project lead | Holds the cutover date and the import template scope | 1 and 4 |
If the controller cannot attend, run the first four blocks and book ten minutes with them later for block five. Silence from an absent owner is never consent. Keep your own notes as a short table: block, answer, who gave it, open item.
The 30-minute run sheet
Illustrative. A 310-person industrial supplies wholesaler is moving invoice capture and approvals from its ERP workflow to a dedicated AP automation tool. The advisor runs this agenda in the week the import template is drafted.
| Block | Question for the block | Who answers | A good answer sounds like |
|---|---|---|---|
| 0-4 min: cutover | When do new invoices start flowing through the new tool, and what does the import template cover? | Project lead | "Go-live is set in the plan; the template covers open invoices and vendor master only." |
| 4-11 min: rejections | Are rejected and held invoices kept with the approver's reason, date and user? | AP lead and administrator | "Yes. Rejected invoices stay in workflow history with the reason text, back to 2019." |
| 11-18 min: duplicates and mismatches | Are duplicate flags and price or quantity discrepancies stored with the note or credit memo that resolved them? | Administrator | "Duplicate alerts sit in the capture tool; match variances and approvals sit in the ERP." |
| 18-25 min: old system and owner | Is the old capture tool going read-only, archived or switched off, and who owns AP history? | Controller | "The capture subscription ends after cutover; finance owns the records." |
| 25-30 min: decision | Does the company want to hear how licensing of approved records works, and who would lead it? | Controller or CFO | "Yes. Our CEO is the authorized contact." |
Why block two carries the meeting
A rejected invoice often never posts, so it sits outside the history a migration treats as the data. In Dynamics 365 Finance, for example, a Workflow rejected status shows the reason the approver gave and is kept separate from a Workflow failed status caused by validation errors. Ask the administrator to describe what the system stores, not to prove it with a report.
Why block three needs the administrator
Duplicate and mismatch decisions live in different places. Dynamics 365 Finance can be set to reject an invoice number already used on a posted invoice, and three-way matching turns a price or quantity outside tolerance into a discrepancy that can require approval before posting. Each is a recorded human decision, and neither has an obvious column in a new tool's import template.
Listening for the answer behind the answer
Not every reply is a clean yes. These are the common ones and what each should change in the room.
| What you hear | What it usually means | Move in the meeting |
|---|---|---|
| "We only keep paid invoices." | Rejected history may exist but is not reported | Ask the administrator whether workflow history is purged; note "unknown" |
| "Reasons are in the approver's email." | The decision exists but outside the system | Note "partial" and which mailbox or folder type holds it |
| "The capture vendor holds the duplicate alerts." | The flags go with the subscription | Flag it for the archive context checklist |
| "A shared services provider runs our AP." | Ownership may depend on a service contract | Ask who controls the history; stop if the company does not |
| "We are moving to the cloud ERP next year too." | A second retention event is coming | Record it as a separate date, not a reason to rush |
Leaving with "partial, five years, capture tool and ERP, controller to confirm" is a good result. You are collecting a description, not winning every block. The AP exception handling records page is useful background for what a complete record looks like.
Three statements before the closing block
Say these in plain words before asking for a decision.
What SourceX does. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. Attending this meeting shares nothing.
Your interest. You are a SourceX referral partner. If a qualifying license completes and every payment condition is met, SourceX may pay you a reward under the terms. It is funded separately and never deducted from the company's payout. Illustrative only: a company paid USD 100,000 for a qualifying completed handoff would mean a default reward of USD 55,000 on its first qualifying transaction.
Fit. The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
What stays unknown until SourceX reviews it: demand for this record type, the rights review result including vendor contract limits, any de-identification needed for supplier details, any offer, and any reward. Partners never ask for or handle invoices, approval histories or vendor files.
The decision written into the minutes
Read one outcome aloud with the name attached, and write it down the same day.
| Outcome | When it fits | Owner of the next step | What follows |
|---|---|---|---|
| Introduce now | Block two is yes or partial, AP history is company-owned, the controller opted in | Advisor | Send the introduction email to the named contact |
| Revisit after cutover | Answers depend on an administrator's check or the final import scope | AP lead | Agree a review date tied to the documented go-live |
| Stop | The owner declines, or a provider controls the records | Advisor | Note the reason; the rollout continues unchanged |
Before you submit any introduction, sign the Channel Partner Agreement. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. If the company also runs a separate payables platform, the Bill.com invoice history page shows the system-level questions, and the sell-side kickoff agenda applies the same time-boxed method to a different meeting.
Next step
Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If the minutes say "introduce now" and the controller named a contact, register as a partner, check the company against who qualifies, and read the program terms before you send the email.