# Invoice rollout: rejected-invoice trails | SourceX

Canonical: https://refer.sourcex.si/guides/moment-invoice-processing-rollout-ap-automation-advisors
Last updated: 2026-11-05

Often yes, but the rollout is where that history gets lost. Many AP systems record a rejected invoice with the approver's reason, a duplicate flag or a matching discrepancy, then the new tool migrates only open and posted invoices. Before cutover, ask the company's authorized owner one metadata question: do the records retain rejected invoices and the reasons for rejection? If they do, and the company wants to explore licensing, introduce its decision-maker to SourceX through the referral route.

## Do the records retain rejected invoices and the reasons for rejection?

In a well-run AP function they usually do, at least in the system being replaced. Whether they survive the rollout is a separate question, and it is the one an AP automation advisor is placed to ask.

The reason is structural. A rejected or held invoice often never posts to the general ledger, so it sits outside the transaction history that a migration plan treats as "the data". Microsoft's documentation for Dynamics 365 Finance, for example, distinguishes a Workflow rejected status, where the list shows the rejection reason the approver gave, from a Workflow failed status caused by validation errors. Under three-way matching, the invoice is matched to the purchase order and the product receipt, and a quantity or price outside tolerance becomes a matching discrepancy that can be set to require approval before posting. Each of those states leaves a record of a human decision. Nothing ensures that any of them has a place in the new tool's import template.

That decision trail is what makes the archive interesting for AI training and evaluation: the invoice, what was wrong with it, who decided, and how it was resolved. The [AP exception handling records page](/data-types/accounts-payable-exception-handling-process) explains the record types in detail; this page is about the rollout moment and the question.

### The record chain behind one rejected invoice

Illustrative. A 260-person building-products distributor is moving from an ERP approval workflow to a new invoice capture tool. One supplier invoice produces five records:

| Step | Record created | Usually stored in | Default rollout treatment |
|---|---|---|---|
| 1. Capture | Invoice image and header fields | Old capture tool | Often migrated if still open |
| 2. Duplicate check | Flag linking it to an earlier invoice with the same number | Old capture tool or ERP | Frequently not migrated |
| 3. Match | Price variance against the purchase order | ERP matching details | Kept only if the ERP stays live |
| 4. Rejection | Approver's reason, date and user | Workflow history | Rarely in the import template |
| 5. Resolution | Credit memo, corrected invoice and AP clerk note | ERP plus shared mailbox | Split across systems |

The posted outcome (step 5's corrected invoice) migrates. The steps that explain it (2 to 4) are the ones a rollout plan most often leaves in a system scheduled for read-only access or shutdown. Your question is aimed at exactly that gap.

## Why are duplicate and mismatch resolution trails easy to overlook?

Because an invoice processing rollout is measured on throughput. The project tracks capture accuracy, touchless rates, approval times and vendor onboarding. Historical exceptions are not needed to process next month's invoices, so they are rarely in scope for the import.

Three things make the gap wider. Duplicate flags and match discrepancies are often held by the capture tool being replaced, not the ERP, so they vanish with its subscription. Rejection reasons may be free text in a workflow history table that no standard report exposes. And resolution is split: the credit memo posts in the ERP while the clerk's explanation sits in a shared mailbox.

Retention rules do not fill the gap either. The IRS default record-keeping period is three years, with seven for certain bad-debt deductions, and creditors or insurers can require longer. Those rules describe what supports a tax return; they say nothing about whether every rejected invoice, duplicate flag or clerk note is kept. A company can comply fully and still lose the decision trail.

## Four metadata questions for the owner

Stay at metadata level: what exists, how much, how long, which system and who owns it.

1. **Are rejections kept with reasons?** Does the current system keep rejected and held invoices with the approver's reason, date and user, or only the final posted invoice?
2. **Do duplicates and mismatches keep their resolution?** Are duplicate flags and matching discrepancies stored with the note or credit memo that resolved them, and in which system?
3. **What happens to the old system?** Is it going read-only, archived or decommissioned, and is the exception history inside the agreed archive scope?
4. **How much, and whose?** Roughly how many years and how many exceptions per month, who owns AP history, and do any vendor contracts restrict reuse?

Note each answer as yes, partly, no or unknown. You never ask for exports, screenshots or logins, and you do not sample rejected invoices to show SourceX. If the company uses an AP platform alongside its ERP, the [Bill.com invoice history export page](/systems/bill-com-export-invoice-history) shows the kind of questions to ask about one specific system's history, and the [NetSuite referral guide](/guides/how-erp-consultants-spot-referral-opportunities-during-netsuite-projects) covers the same discipline for ERP projects.

## How do you disclose the reward and get the owner's permission?

Ask permission before mentioning SourceX, and disclose your interest before the owner decides anything. For example: "That exception history may have value outside the company. May I mention one option? I am a SourceX referral partner, so I may receive a reward if it goes ahead."

If the owner agrees, explain that SourceX licenses approved business data directly from companies for AI training and evaluation and pays the company under a license agreement, and that SourceX pays any eligible referral reward separately, under its [terms](/terms), never deducting it from the company's payout. If the owner says not now, the rollout carries on unchanged.

Keep the numbers exact. The default reward is the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout, with no cap. As an Illustrative reference only: if a company were paid $120,000 for a qualifying completed handoff, the default reward would be $56,000. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.](/rewards) explains the full calculation.

## Does the company qualify, and who can authorize a licensing discussion?

Check the basics before you raise it. The 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.

| Question | Typical answer during an AP rollout | Stays unknown until SourceX reviews |
|---|---|---|
| Which records exist? | Rejected, held and duplicate-flagged invoices with reasons | Whether a buyer needs that record type |
| Who owns them? | The company; vendor terms may limit some fields | The rights review result |
| Who can authorize? | CEO, often the owner | Final dataset scope |
| How much and how long? | A rough count and span in years | The company's offer |

Before you submit any introduction, you need to have signed the Channel Partner Agreement. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application; one partner is credited per company. The [partner hub](/for) lists guides by role.

## Go deeper on invoice processing rollout records

- [Invoice processing rollout introduction email](/resources/invoice-processing-rollout-introduction-email): a ready-to-adapt email for introducing an opted-in owner and their AP exception history to SourceX.
- [Invoice processing rollout meeting agenda](/resources/invoice-processing-rollout-meeting-agenda): a timed agenda for raising rejected-invoice history at a rollout checkpoint.
- [Invoice processing rollout archive context checklist](/resources/invoice-processing-rollout-archive-context-checklist): a checklist of cutover, read-only and license dates to confirm before the old system goes dark.

## 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 owner confirmed that rejected invoices and their reasons are still on record before cutover, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before you make the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/vendor-invoice-workspace
- https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/three-way-matching-policies
- https://www.irs.gov/businesses/small-businesses-self-employed/how-long-should-i-keep-records
