Overview
PO-referenced adjustment documents let your team capture a supplier invoice or credit memo that references a purchase order for traceability only — not for PO-line matching. This applies when a PO has already been fully processed and a later invoice or credit needs to be tied to it for reference and coded to a GL account, rather than validated against remaining PO quantity or value.
For SAP customers, these are labeled Subsequent Debit (adjustment invoice) and Subsequent Credit (adjustment credit).
Without this option, teams either had to force these documents through standard PO matching (which doesn't fit, since there's no remaining quantity or value to match against) or handle them manually outside Vic.ai. PO-referenced adjustment documents give these documents a proper home: the PO stays attached for traceability, the value is GL-coded, and the document is clearly identified to your ERP integration as an adjustment rather than a standard PO-matched invoice or credit.
Setup
This capability is enabled per company and the customer-facing document labels are configurable.
Contact your Vic.ai account team to enable PO-referenced adjustment documents for your company
Confirm the labels you'd like to use for the two document types. Some customers use Subsequent Debit and Subsequent Credit; other ERPs and terminology (debit memo, PO adjustment, price correction, supplemental invoice, etc.) can be configured to match your process
Using PO-Reference Adjustment Documents
Open the supplier document that references a PO that has already been fully invoiced or costed
In the
Document Typefield, select the adjustment type made available for your company (for example, Subsequent Debit or Subsequent Credit)Enter GL coding for the adjustment
The originating PO stays attached to the document for traceability. Vic.ai does not run PO quantity, receipt, or remaining-balance validation on adjustment documents
Submit the document as usual. Vic.ai sends it to your ERP integration clearly identified as a PO-referenced adjustment so your middleware can route it correctly
When to use standard credit memo matching instead
If a credit memo includes a return line on the PO, continue processing it as a standard credit memo — Vic.ai will match it to the PO as it does today. Use the adjustment credit type only when there is no return line and the credit is meant to reference the PO without matching against it. Vic.ai does not auto-detect this distinction; your team selects the correct document type based on whether a return line applies.
Frequently Asked Questions
Does this replace standard invoice or credit memo matching?
No. Standard PO matching continues to be used for documents that should be validated against PO lines. Adjustment documents are for the specific case where a document references a PO for traceability only.
Is this specific to SAP?
No. The underlying capability is generic — SAP customers see Subsequent Debit / Subsequent Credit, but the same capability can be labeled to match other ERPs and terminology.
Who can turn this on?
Contact your Vic.ai account team — it's configured per company, including the names of the labels.