Recovery
See which invoice-export rows need a closer check.
You receive the pattern name and the source rows. A flag is a candidate for review. It is not a confirmed error. Valbruck Recovery is an operator-assisted private pilot.
Synthetic demonstration · Synthetic Entity A · USD · not a customer result
Two invoice-record questions that require different checks
Question A and Question B use different records. Their amounts are not added together. Payment has not been confirmed, and no cash has been recovered.
Question A
Potentially repeated invoice entries sharing a supplier, reference, currency, and amount. The source rows stay distinct.
- Supplier
- Synthetic Supply Company 01
- Supplier ID
- SYN-001
- Reference
- BILL-7715
- Invoice amount
- $1,000.00
- VCH-0001
- Row 2 · 2026-07-06
- VCH-0002
- Row 3 · 2026-07-08
Check. Do these two records represent one obligation, or two?
Question B
An exported paid-amount field differing from an invoice-amount field. Both amounts come from one export row. No separate payment record was examined.
- Supplier
- Synthetic Supply Company 03
- Supplier ID
- SYN-003
- Reference
- PAID-9001
- Invoice amount
- $1,000.00
- Exported paid field
- $1,100.00
- VCH-0026
- Row 27 · 2026-07-12
Check. Do the invoice amount and the paid field measure the same components? The $100.00 difference is the gap between those two fields. It is not confirmed money received.
Shared documents stay separate. The same demonstration also asks whether a punctuation change, a second supplier ID, or a different amount on BILL-7715 is a separate obligation. Those questions can share documents with Question A, so their amounts are not added to it or to the $100.00 field gap.
What the team does. Compare the rows with the original invoice, any revision, and any payment record.
What the first pass can flag
- A potential duplicate-invoice pattern, as a strict match or a loose match.
- A potential duplicate under different supplier IDs, where normalized supplier names, invoice numbers, and amounts match within the same entity and currency.
- A reused invoice number.
- An exported paid amount higher than the invoice amount. That check requires a usable exported paid-amount field. It does not verify separate payment records.
Where figures overlap, they are not added together. We confirm whether your invoice export supports this first pass during the fit discussion, including the fields and any preparation the checks need. Access and handling are agreed before any file is sent.
What this pass does not do
- The public site does not show a customer's invoice rows. A review returns the pattern and the source rows, and it does not produce a recovered amount, a credit, a purchase-order match, or a benefit figure.
- Valbruck does not contact vendors and does not move money.
- Not accounting, tax, legal, or financial advice.
In the first message, name the product, your business type, and the problem in a few sentences. Do not attach exports, login credentials, or confidential files. A fit discussion comes before any agreed intake.