Catch the gaps.
Before the handoff.
Check an invoice packet against the requirements you supply. Find missing details, see what needs attention, and get a clear next step.
A preflight you can inspect.
Choose a synthetic HVAC sample, edit the structured packet and rules, then run the check in your browser. These examples are fictional and don’t represent any buyer’s requirements.
01Prepare packet
REQUESTIntegrate this workflow Optional server API
The companion Python service exposes POST /api/v1/preflight for structured JSON requests. This browser demo runs the check locally and does not call that endpoint.
02Inspect results
AWAITING CHECKYour second set of eyes.
Run a preflight to see which supplied requirements are met and which need attention.
- Invoice and work-order alignment
- Required evidence and fields
- Specific actions for each finding
What needs attention
0The supplied structured packet passed these rules. Confirm your buyer’s actual requirements before sending.
Inspect structured result JSON
Checks run locally in your browser. Your edited packet is not sent to an API or saved by this page. Use synthetic data; no real documents or uploads.
A clearer packet.
Not a payment promise.
Invoice Packet Preflight evaluates what’s in the data against the rules you provide. A pass is the beginning of a better handoff.
Your rules, explicit
Requirements are supplied in the request. No claim of buyer approval, endorsement, or universal compliance.
Structured data only
No OCR or document parsing. File metadata and evidence references do not prove document authenticity.
A check, not a submission
Nothing is sent to a buyer or payment portal. Results do not guarantee invoice acceptance or payment.
Built to inspect
Review finding codes, field paths, next actions, and the complete structured JSON result. The same request format is supported by the companion API.