Key takeaway
A signed license, an approved supplier profile, a usable purchase order and a payable invoice answer different questions. Establish the buyer’s actual process before depending on timely cash.
Ask finance how this buyer can process your invoice
Before committing optional data preparation or a delivery date, ask the named buyer’s authorized finance and procurement contacts how the company becomes payable. The useful answer identifies the contracting entity, approved supplier record, purchasing authority, invoice requirements, submission channel, acceptance evidence and responsible exception owner. A salesperson’s assurance that finance will sort it out later leaves those questions unresolved.
Public buyer procedures show why the question is concrete. Harvard states that new suppliers must be invited to register and that their profile must be completed and approved before it can process payment. The University of Edinburgh’s published policy returns invoices received after 2 October 2023 unpaid when a current valid purchase-order number is missing or incorrect, with a separate route for registered eInvoicing suppliers.
These are first-party procedural examples checked on 12 October 2026. They are not universal licensing rules, evidence that either university buys this archive or VOID partner claims. They also do not decide a private agreement’s payment obligation. Confirm the actual buyer’s requirements and resolve contractual conflicts with the responsible advisers.
A signed proposal with an incomplete payment path
Hypothetical example: fictional seller S Ltd has signed a single USD 18,000 snapshot license with fictional buyer B Ltd. The stipulated agreement leaves the release date to be confirmed after supplier approval and issued PO or agreed exception evidence. Invoicing follows named acceptance through B’s agreed route. These invented terms are not a receiving program’s advertised conditions.
S has a signed agreement and a procurement requisition approval. Its supplier invitation remains incomplete, and the requisition has not become an issued PO. The license owner should record the administrative gap now rather than counting the signature as proof that an invoice can enter B’s payment queue.
| Readiness item | Completed illustrative evidence | Current decision / owner |
|---|---|---|
| Contracting identity | Executed agreement names S Ltd and B Ltd | Confirmed for this example; finance matches supplier identity. |
| Supplier approval | Invitation received; profile not completed or approved | Pending; S finance and B supplier team resolve. |
| Purchasing authority | REQ-44 approved; no issued PO reference | Pending; B procurement supplies PO or agreed exception evidence. |
| Invoice route | Established B finance contact confirms secure portal | Route known; access and permitted invoice fields still checked. |
| Acceptance evidence | Named package reviewer identified; no delivery yet | Future condition under stipulated terms, not completed acceptance. |
| Release planning | Optional delivery commitment not yet made | Hold new commitment until gaps and timing are resolved. |
Match the invoice to the approved purchasing record
When the actual process uses a PO, compare its legal entities, amount, currency, covered deliverable, line references and period with the proposed invoice and license. A purchase requisition, email approval and issued order are different evidence states. Ask the procurement owner to identify the document that this buyer’s payable system expects; do not manufacture an order number to fill the field.
For the hypothetical snapshot, the reviewer checks whether the eventual PO covers the snapshot itself rather than a separately budgeted evaluation service. If the PO covers only an evaluation, the existing invoice cannot simply be renamed to consume that budget. The issue returns to the authorized procurement and commercial owners for a documented resolution.
If the buyer uses an approved non-PO route, retain its actual authority and requirements. Record who confirmed that route and when. A generic purchasing-document score would hide whether the relevant authority exists.
Keep submission, rejection and receipt separate
Prepare the invoice using finance’s approved requirements and the identified package or service references. Submit through the verified channel, retaining the invoice version, submission identifier, date and acknowledgement. The acknowledgement establishes what was submitted; determine what it actually says before calling the invoice accepted or payable.
If a submission is returned, preserve the reason and correction history. Assign the missing field or authority to its owner and ask which event governs the contractual due date. Do not silently assume that resubmission always restarts the clock or never affects it. An administrative exception does not itself rewrite the agreement, and it is not permission to stop performance already owed.
For example, B’s issued order could contain the correct amount but the wrong seller entity. S finance identifies that mismatch before submission and asks the authorized owners to resolve it. The business does not correct B’s record by changing its own invoice to an entity that is not the contractual seller. This remains part of the hypothetical example, without a conclusion about enforceability.
Share finance evidence through the right channel
Supplier setup may involve tax or bank information. Ask the responsible finance owner which documents are necessary and where the authenticated process receives them. Do not put credentials, tax identifiers or bank documents in a public data inventory or VOID introduction request. Confirm new or changed payment instructions independently before they are acted on.
Invoice attachments are not a substitute for a separately permitted data delivery. A procurement contact who can approve a supplier profile is not automatically the authorized recipient of operational records. Keep the package delivery, evaluation permissions and acceptance evidence in their approved channels, while the invoice references the relevant version.
The completed readiness record should show the unresolved supplier approval and purchasing authority, the confirmed submission route and the future acceptance condition. Give each gap a named owner and a bounded next action. A seller can then adjust an optional commitment before it becomes an avoidable collection problem.
Use the readiness decision alongside the cash schedule
The payment-trigger guide explains the event that makes an amount due; this register asks whether the agreed invoice can navigate this buyer’s actual administration. The cash-and-revenue guide prepares accounting evidence, which is another decision. Neither a usable PO nor an accepted invoice proves that funds have arrived or establishes revenue recognition.
Use Readiness planner to assign supplier and invoice gaps, and Due diligence to request the named finance process. Review cash reserve separately if unresolved administration extends funded preparation exposure. Enter actual payment terms and evidence rather than a presumed standard period or likelihood of collection.
VOID has no upfront seller referral fee. Any conditional compensation from a receiving program is disclosed separately from the company’s license receipt. A permitted named introduction does not register the company as a supplier, authorize bank changes or approve a sample or license. The owner retains those decisions with the actual recipient and responsible advisers.