Dashboard
Shared delivery and invoice workflow.
Goods received first. Invoice closes the loop later.
Delivery notes stay common across both firms. Company assignment happens from the final invoice.
Admin / staff work queue
Newest items that need attention.
Business health
Delivery-to-invoice controls.
Recent activity
Shared entries help staff avoid duplicates.
Upload documents
Camera photos, images or PDFs. Images are compressed before private storage.
Offline capture queue
If internet drops, compressed pages are kept on this device and can sync later.
Delivery ↔ Invoice Matching
One invoice can cover several deliveries, and one delivery can be invoiced partially.
Goods received but not yet invoiced
Outstanding quantity is calculated from approved delivery-note lines minus confirmed invoice allocations.
| Date | Supplier | Product | Delivered | Invoiced | Pending |
|---|
Month-end Tally XML
Only Admin-verified, fully mapped, reconciled invoices are exportable.
Export history
Editing a previously exported invoice will require a new export.
Tally masters
Read-only master list. PurchaseFlow never creates Tally suppliers or stock items.
XML ledger settings
Staff access
Add an email before that staff member creates an account.
Two legal companies
Delivery notes remain common. These details are used only when a GST invoice arrives.
Recognition policy
Browser OCR → deterministic parser → AI only if incomplete or inconsistent.
Automatically escalates to high-accuracy vision AI.
Optional when not printed. Existing Tally supplier mapping remains mandatory before XML.
Final invoice buyer/GSTIN decides Vijayalaxmi vs Vipul. Delivery-note buyer never hard-assigns company.
Delivery Note
Original document
Processed data
Staff corrects first. Admin approves later.
Products received
Invoice
Original invoice
Invoice verification
Final buyer decides legal company.