# Invoice-to-payment metadata packet template | SourceX

Canonical: https://refer.sourcex.si/resources/invoice-to-payment-metadata-packet
Last updated: 2026-11-05

A referral partner can collect eight facts about invoice-to-payment records without reading any of them: which systems and modules hold orders, receipts, invoices and review packets; how many years each covers; which object types exist; which key they share; who reconciles them today; a rough annual volume; any upcoming access event; and what nobody knows yet. That packet comes from one conversation with the controller or accounts payable manager and is enough for SourceX to judge whether a first call is worth having.

This template belongs to the [invoice-to-payment guide](/guides/chain-invoice-to-payment), which explains how the chain links across SAP, Ariba and SharePoint. Here the job is the form itself: what goes in each field, where the answer comes from, and what stays out.

## The packet: eight fields and an Illustrative filled sample

Illustrative: the entries below describe a fictional company. None of them required opening a record.

| Packet field | Sample entry | Usually supplied by |
|---|---|---|
| 1. Systems and modules | Ariba Buying for orders; SAP for goods receipts, invoice verification and payment; a SharePoint library for review packets | Controller |
| 2. Years held | Ariba since 2019, SAP since 2012, SharePoint packets since 2020 | IT or system owners |
| 3. Object types | Order versions, change orders, goods receipts, invoices, payment blocks and releases, packet files with version history | AP manager |
| 4. Shared key | Order number appears in all three; order version number only in Ariba and SAP | AP manager |
| 5. Linkage owner | AP team lead reconciles packets to SAP for invoices over a set threshold | Controller |
| 6. Rough volume | About 60,000 invoices a year, perhaps one in ten reviewed by hand | AP manager |
| 7. Access event | SharePoint migration planned next year; Ariba contract renewal after that | CFO or IT |
| 8. Unknowns | Which export fields hold version numbers; whether packets before 2022 kept history; supplier contract limits | Left for SourceX review |

"About 60,000 invoices a year, perhaps one in ten reviewed by hand, packets in SharePoint since 2020" is the kind of answer fields 2 and 6 need. Precision is not the goal; an honest range with its source is.

## How to ask for each field without opening a record

Each field has a question that produces a description rather than a document.

- **Systems and modules.** "Where does an order start, where is it received, where is the invoice checked, and where does the reviewer look?" Four places, sometimes three.
- **Years held.** "When did each system go live, and was history migrated from what came before?" A go-live date without migrated history is a different answer from one with it.
- **Object types.** "Which of these exist: order versions, change orders, receipts, blocks, releases, review files?" A checklist works well here.
- **Shared key.** "If I gave you an invoice number, how would you find its order, receipt and review packet?" The answer names the key and exposes any step where people search by supplier name instead.
- **Linkage owner.** "Who matches review packets to invoices today, if anyone?" Often the honest answer is "nobody formally," which belongs in the packet.
- **Rough volume.** "Roughly how many invoices a year, and what share get a manual review?" Let the company give a range; do not derive one.
- **Access event.** "Is any of these systems being replaced, renewed or migrated, and is there a documented date?"
- **Unknowns.** "What would you need to check before answering more precisely?" Write the answers down as they are.

If someone offers to pull a report or forward a sample, thank them and say a description is enough. Partners never take copies. The broader method for any system is in [how to prepare a metadata-only inventory](/guides/how-to-prepare-a-metadata-only-inventory-of-business-systems).

## What never goes in the packet

| Leave out | Why | What to write instead |
|---|---|---|
| Invoice and order amounts | Commercially sensitive and not needed to judge fit | Rough invoice count per year |
| Supplier names | Confidential, often under supplier agreements | Number of active suppliers, as a range |
| Invoice images and order PDFs | Raw records, and partners never handle them | Object types and whether files keep version history |
| Bank and payment details | Sensitive financial data | Whether payments run in SAP |
| Approver names below the sponsor | Personal data with no role in the packet | Job titles of the linkage owner and sponsor |

A packet with any of these in it should be rewritten before it goes anywhere.

## The version field: one column that decides whether the chain holds

Field 4 looks minor, but it decides whether the chain can be followed at all. SAP's documentation explains why: in Ariba, changing an order creates a new requisition version that goes through approval, and the approved new version is sent to the supplier. Changes to accounting fields also create a version, but by default it is not sent to the supplier. So an order can have several versions, and an invoice is matched against one of them.

If the review packet records which order version the reviewer saw, the chain from order version to receipt to approved invoice can be followed end to end. If it does not, the case that matters most, an amended order that never reached the reviewer, looks like an ordinary hold. Microsoft's documentation says SharePoint version history lists each saved version of a file with the date and the person who saved it, which is why "packet files with version history" in field 3 matters as much as the key in field 4. The [missing-context page](/guides/invoice-to-payment-missing-context) walks through one such hold.

SAP's invoice blocking also matters here: a variance above tolerance posts the invoice but blocks it for payment, release is a separate step, and the block covers the whole invoice. Field 3 should therefore say whether blocks and releases exist as records, not just whether invoices do.

## Access events that set the timing

Field 7 is the only legitimate source of urgency in the packet. An ERP replacement, an Ariba renewal or a SharePoint migration is a real, documented date after which older records may be harder to reach or describe. If one is coming, the [ERP replacement handoff checklist](/resources/a-data-opportunity-handoff-checklist-for-an-erp-replacement) helps time the conversation, and the [SharePoint systems page](/systems/microsoft-sharepoint) covers that library on its own. Companies on a lighter AP stack can compare with the [Bill.com invoice history page](/systems/bill-com-export-invoice-history). If nothing is scheduled, write "none known" and do not invent a deadline.

## Handing the packet over

The packet goes with an introduction to the CEO, who can authorize a licensing discussion; the CFO or controller often sponsors it. The AP manager and administrators fill in the fields but cannot approve anything.

The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license 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. Partners sign the Channel Partner Agreement before submitting introductions, and the first valid introduction within the 90-day window is credited when the company submits a verified application. SourceX funds the reward separately; it never comes out of the company's payout, as the [rewards page](/rewards) explains. Illustrative only: a USD 100,000 Actual Supplier Payout on a company's first qualifying transaction would mean a USD 55,000 default reward. [What you need to receive a referral payment](/resources/what-do-i-need-to-receive-a-referral-payment) lists the paperwork on your side, and the [completeness scorecard](/resources/invoice-to-payment-completeness-checklist) grades the trail in more detail.

## 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 controller can fill in all eight fields, including the unknowns, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before sending the packet with your introduction.

## Sources

- https://help.sap.com/docs/buying-invoicing/purchasing-guide-for-procurement-professionals/change-and-cancel-order-processes
- https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint
- https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/ed84b70c199d4470ae2e5ccb93b2e45b/7870b6531de6b64ce10000000a174cb4.html
- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
