Interactive demo
See a decision made.
Choose a decision. Watch Cogniquest read the documents, apply the policy, make the call and carry it through, with every step on the record.
Simulation with sample documents. All names, identifiers and figures are fictional.
GST invoice payment approval
A supplier's GST invoice arrives by email. See it verified against GSTIN and IRN, reconciled against the PO and goods receipt, approved and scheduled for payment.
A supplier's GST invoice arrives in the accounts payable inbox as a PDF with its signed QR code. The supplier is in Maharashtra and the buyer in Karnataka, so this is an inter-state supply.
-
Understand
- IntakeInvoice INV/25-26/2093 from a packaging-materials supplier
- Extract36 fields extracted
-
Reason
- GSTIN checksSupplier GSTIN 27•••••••••1Z5 active · buyer GSTIN 29•••••••••1Z8 matches our entity
- IRN & QR checksIRN a3f9…c21e valid and active, not cancelled · QR matches invoice
- Vendor & duplicate checksVendor verified · no duplicate
- 3-way matchQuantities match on all 3 lines
- Unit-of-measure reasoningUOM differs. Normalized: 500 cartons × 6 rolls = 3,000 rolls. Match
- Price, tax & mathLine 2 at ₹32.50 vs PO ₹32.00 (+1.6%), within ±2% tolerance · IGST 18% correct for inter-state supply · total ₹20,50,840.00 verified
-
Decide
- ApprovalApproved for payment: ₹20,50,840.00
-
Act
- Post & schedulePosted · payment scheduled
- Invoice INV/25-26/2093
- Signed QR
- PO-45812
- GRN-7754
- Vendor master
Press play to watch the decision being made.
A supplier's GST invoice arrives in the accounts payable inbox as a PDF with its signed QR code. The supplier is in Maharashtra and the buyer in Karnataka, so this is an inter-state supply.
Decision Record
No one touched this invoice, and every check, from GSTIN to IRN to the last rupee, is on the record.
In production, APWise took a leading Indian e-commerce platform's invoice-to-ERP turnaround from 8 days to under 12 hours, across 145,000 invoices a month.
- Decision
- Approved for payment: ₹20,50,840.00
- Why
- GSTINs valid and active · IRN valid, QR signature verified, QR matches invoice · 3-way match on all lines · Line 1 UOM normalized (500 cartons = 3,000 rolls) · Line 2 price +1.6%, within ±2% · IGST 18% correct for inter-state supply · Totals verified · Vendor and bank details match · No duplicate
- Evidence
- Invoice INV/25-26/2093 p.1 · Signed QR · PO-45812 · GRN-7754 · Vendor master
- Rule Engine
- All checks passed
- S, L, N, D
- Alignment: Yes
- Confidence
- 98%
- Policy
- AP Policy v4.2 (3-way match, ±2% price tolerance) · GST Compliance Rules · Approval Authority Matrix
- Agent
- APWise Validation Agent
- Action
- Posted to ERP with ITC details · Payment scheduled (Net 30) · Supplier notified
Claim approval recommendation
A customer reports a dropped phone with a cracked screen. See the claim checked against the plan, the photos and the repair estimate, then recommended for settlement and ready for an adjuster's sign-off.
A policyholder files a claim in the insurer's app: “Dropped my phone, the screen is shattered.” Attached: the claim form, three photos, the original purchase invoice and a repair estimate from an authorized service center.
-
Understand
- IntakeClaim CLM-2026-31407 opened
- Classify7 of 7 items identified
- Extract28 fields extracted, all cited to source
-
Reason
- Coverage checkCovered under Device Protection Plan DP-PLUS, 0 of 2 annual claims used
- Device matchIMEI matches the registered device
- Photo evidenceFront display cracked, consistent with “dropped”
- Estimate vs evidenceThe estimate includes back-glass replacement ($199), but the photos show no back-glass damage. That line is excluded as unsupported
- Price check & risk signalsDisplay $329 within the $299–$349 range · labor $50 · no risk flags
-
Decide
- RecommendationRecommend approval: $280 (estimate $578)
-
Act
- Route & prepareAwaiting adjuster sign-off
- Claim form
- Plan certificate
- Purchase invoice
- Repair estimate
- Photo 1
- Photo 2
- Photo 3
Press play to watch the decision being made.
A policyholder files a claim in the insurer's app: “Dropped my phone, the screen is shattered.” Attached: the claim form, three photos, the original purchase invoice and a repair estimate from an authorized service center.
Decision Record
The adjuster sees one screen of evidence and one recommendation, and approves it with one click. The customer's repair is authorized the same day.
ClaimWise runs claims intake and adjudication in production for general insurers, across device protection, accidental and liquid damage, and marine lines. On one insurer's marine claims, it took the cycle from 28 days to 2 days.
- Decision
- Recommend approval with adjustment: $280
- Why
- Plan active · Accidental damage covered · IMEI matches registered device · 0 of 2 annual claims used · Front-display damage confirmed by photos; back-glass damage not evidenced, line excluded · Repair price within range · $99 deductible applied
- Evidence
- Claim form · Plan certificate · Purchase invoice · Repair estimate lines 1–3 · Photos 1–3
- Rule Engine
- All checks passed
- S, L, N, D
- Alignment: Yes
- Confidence
- 95%
- Policy
- Device Protection Plan DP-PLUS, Accidental Damage terms · Claims Authority Matrix v3
- Agent
- ClaimWise Adjudication Agent
- Action
- Routed to adjuster (partial approval) · Repair authorization and customer notice drafted
Why these two
Autonomy where policy allows. A person where it requires one.
- APWise
Straight-through approval
Within the authority limit
GSTIN and IRN verification, UOM reasoning, tolerance policy, GST rate logic, duplicate and bank checks
Routine decisions run end to end, governed by your rules and your regulator's
- ClaimWise
Recommendation with human sign-off
Policy requires review of partial approvals
Photo evidence weighed against the repair estimate, an unsupported line excluded, IMEI and plan checks
Agents prepare the decision, and people stay in control where policy says so
That was ours. Now bring one of yours.
Every enterprise has a decision like these: high-volume, unstructured, rule-bound and still done by hand. Tell us which one, and we'll show it running on your own data.