Inbound invoices and credit memos that auto-processing couldn't handle, awaiting manual review.

Documents to Review

BC page: Documents to Review (List) · Source: RSMSTAPurchaseDocumentsReview.Page.al

A focused queue of inbound documents that auto-processing parked in Error — limited to invoices (InvoiceTypeCode = 380) and credit memos (381). This is where AP staff start their day: each row is a document the pipeline couldn’t process automatically, with a side-by-side Compare Purchase Document and Invoice sub-page so you can see PO vs invoice differences without leaving the page.

The list is read-only — you can’t edit or delete here; the actions push the document either back into the pipeline or directly to posting.

Columns

ColumnWhat it shows
Vendor Customer Document No.The supplier’s own document number from the inbound XML
Vendor No.The matched BC vendor (empty = vendor not found, posting blocked)
Vendor NameThe matched vendor’s display name
Purchase Order No.The PO this document is linked to, if any
AmountThe sum of invoice line net amounts

Sub-page: Compare Purchase Document and Invoice

For the focused record, the lower pane shows a line-by-line PO vs invoice comparison. Mismatches are highlighted so AP can resolve quantity or amount differences before posting.

Actions

ActionWhat it does
Auto Process DocumentRe-runs the full auto-process pipeline against the selected documents. Use this once you’ve fixed the underlying issue (e.g. created the missing vendor card)
Send to Posting (F9)For documents not linked to a PO: directly creates the purchase invoice/credit memo and posts it. Fails fast if the vendor isn’t resolved

See also