AstreIn development Synthetic preview
A clearer view of possible supplier overcharges.
Built for manufacturers. Grounded in the evidence.
Astre is developing invoice review that brings paid invoices, POs and contract terms together for your controller.
Mock previews. Nothing is sent, scheduled or saved.
| Paid invoice | Part | Quantity | Unit price | Status |
|---|---|---|---|---|
| INV-DEMO-018 | 00104-A | 100 ea | $12.80 | Review |
| INV-DEMO-021 | 00216-B | 48 ea | $7.40 | Terms missing |
| INV-DEMO-024 | 00308-C | 240 ea | $2.15 | Credit linked |
| INV-DEMO-026 | 00104-A | 60 ea | $12.00 | Aligned |
| INV-DEMO-031 | 00411-D | 80 ea | $9.60 | Date missing |
| INV-DEMO-035 | 00216-B | 120 ea | $7.40 | Held |
INV-DEMO-018 → PO-DEMO-042 → Controller review
Source links stay with the line.Invented records. Real questions to ask. No live scan or ERP connection.
Evidence before assumptions.
Uncertainty stays visible.
Your supplier. Your decision.
// 01 - Connect the evidence
Follow the invoice line to the agreed terms.
See the calculation and the questions still open.
Review queue
Invented records.
Real questions to ask.
Potential price difference
Needs controller reviewThe invoice and PO show different unit prices for the same synthetic part. The linked terms and any amendments still need controller review.
SYN-001 · Part 00104-A · 100 ea
SYN-001 · Part 00104-A · 100 ea
($12.80 − $12.00) × 100 ea = $80.00 USD potential difference
Tax, freight and adjustments excluded. Not an approved or recoverable total.Synthetic invoice INV-DEMO-018, line 08, and PO-DEMO-042, line 12. Exact supplier and part references match; quantity basis is one each. The invoice is explicitly marked paid in this invented example.
Open question: Confirm the applicable price date, approved amendments and whether a credit has already corrected the difference.
Illustrative reference: SYN-001/INV-DEMO-018/00008/00104-A
Illustration only. No approval, claim or supplier contact takes place here.
A flag is the beginning of a review.
Your controller decides what the evidence supports.
Line-level identity. Supplier, part, quantity and unit stay together.
Applicable terms. Dates and amendments need to support the comparison.
Visible calculation. A potential difference is never presented as proven recovery.
// 02 - Keep uncertainty visible
When the record doesn’t support a conclusion,
the right next step is to pause.
A price list without an effective period cannot establish which agreement applied.
Reconcile a linked credit before considering a remaining difference.
Credit is not proof of collected cash.
Keep the context that changes the answer.
Missing evidence and prior corrections belong in view.
// 03 - Leave the decision with finance
From the first agreed scope to the next decision,
keep permissions explicit.
Suppliers · entities · period
Before sharing recordsInvoice · PO · contract
Controller judgmentAccept · dismiss · investigate
Separate supplier approvalMinimum necessary records. Agree the sample, available files and review boundaries first.
Handling agreed in writing. Transfer, access, storage, retention, deletion and subprocessors need agreement before real data.
Supplier contact by approval. Reviewing evidence and authorizing contact are separate decisions.
Historical exports first. No live ERP integration or account connection is offered in this draft.
No intake on this page. Nothing is uploaded, submitted, scheduled or saved.
Development, stated plainly. Local synthetic prototype. No customer outcomes or security certification claimed.
// 04 - Before we begin
Only with your approval. Reviewing a potential finding and authorizing supplier contact are separate decisions. This private draft does neither.
Payment alone does not establish whether a charge matched the applicable terms. The proposed review brings those records together and complements your existing process, without assuming it failed.
Missing contracts, unclear units or uncertain dates limit what can be compared. Unsupported comparisons stay held for review; they are not presented as recoverable cash.
No connector is offered in this draft. A future pilot would start with an agreed historical export and confirmed file support. No account connection or data transfer is available here.
Commercial terms and timing have not been finalized. Scope, fees, the basis for any recovery work and data handling must be agreed in writing before a pilot. This page is not a binding offer.
No. Astre is in development, with a local synthetic prototype. Customer outcomes, security certifications and turnaround guarantees are not established. Before real data is shared, transfer, access, storage, retention, deletion and any subprocessors need written agreement.
A scoped conversation comes before a single record.
Mock dialogs only. Nothing is sent, scheduled or saved.