How it works
Upload your supplier scans. Check exceptions beside the source, then select approved invoices for a batch: a register file and a manifest. The scans stay in your workspace. Tally XML is optional.
Four steps, no new habits
You keep working as before. Scans in, checks out. Less typing.
Send the scans
Drop PDFs, JPGs, PNGs. One file or a hundred. Photocopies, crooked phone shots, three-page bundles. We handle each PDF page separately, using its text layer or a page image.
Read and extract
Digital text or OCR goes through the extraction rules first. Unresolved reads can use a vision model with the available text as context. Some digital PDFs with invalid GSTIN checksums go straight to review without a model re-read. The same checks apply to every path.
Prove the math
Here's the gate. GSTIN checksum. HSN check. Do the lines add up. Do the taxes add up. Does the place of supply match the tax paid. Pass and it is ready for a batch. Fail and a person sees why.
Prepare a batch
Filter by date or supplier and select the approved invoices to include. Download one ZIP with a register file and a manifest. The scans stay in your workspace. If you use Tally, the ZIP also includes an XML preview with matching ledger masters and purchase vouchers. Actual Tally Prime import and GST reports are not yet verified. Test in a copy of your company before using it in your books.
What happens at each stage
Each stage has a contract: what comes in, what goes out, and what gets logged.
Send the scans
Invoices can arrive as digital PDFs or images of paper. Each page is handled separately.
In
- PDFs, JPGs and PNGs from the uploader
- Multi-page bundles and mixed batches
- Photocopies with skew, grain and uneven lighting
Out
- Pages kept in bundle order; rendered locally when an image is needed
- Duplicates flagged by content hash
- Every source file logged against its invoice
Read and extract
The live pipeline tries digital text or OCR first. Some digital PDFs with invalid GSTIN checksums go straight to review without a model re-read. Their source preview is rendered locally; fields or line items the rules did not read may need manual entry. Repeated pages can reuse cached reads, but validation still runs. The newer table and thermal-row reader is still off in production.
In
- Digital PDF text, or page images with available OCR text
- Unresolved reads keep the vision-model fallback unless the page is routed directly to review
- Indian amounts (1,00,000.00) and DD/MM/YYYY dates normalized
Out
- Draft fields: seller and buyer GSTINs, invoice no., date, IRN
- HSN-coded line items with quantities and rates
- Failed checks and unresolved references held for review
Prove the math
The gate. Four validators decide whether an entry is allowed to exist at all.
In
- GSTIN mod-36 checksum on both seller and buyer
- HSN format checked; directory misses warn by default
- Arithmetic closure from line items to grand total
- Regime consistency: place of supply vs CGST/SGST vs IGST
Out
- Verdict per invoice: AUTO-EXPORT or NEEDS_REVIEW
- Machine-readable reasons, e.g. line[2] tax off, checksum digit
- Every validator result logged to the invoice
Prepare a batch
Only validated or explicitly human-confirmed entries can be selected. Preparing a batch does not import it.
In
- Entries that passed the checks or were explicitly confirmed by a human
- Vendor and ledger mappings confirmed once in your workspace
Out
- Selected-batch ZIP: the register file, the batch manifest, and, for Tally, an XML preview with matching masters and purchase vouchers. The scans stay in your workspace.
- Batch manifest with invoice IDs and source references; review history stays in EntryLedger
- Download does not import, change approval status or prevent duplicates in any ledger
Pick up where you left the review
A call comes in halfway through a supplier bill. Keep a working copy without signing off early.
Save the working copy, not the approval
Edits save to your private draft. Wait for the saved message before leaving. After a reload, compare and restore the copy, or discard it. If another tab or reviewer changed the record, review the difference before continuing. A draft never makes the invoice ready for export.
Read the source while you correct
Fit or zoom the scan beside the fields. Correct buyer details, place of supply, quantities, HSN and taxes, including UTGST and printed adjustments. Add or undo printed rows. Check the current issues before explicitly confirming and opening the next exception.
Keep the file you actually prepared
Batches use your selected invoices: a register file in CSV, XLSX or JSON, plus Tally XML as an optional preview. Saved batch history retains the original file and its invoice and settings snapshot. A later correction raises a warning before re-download. Missing or damaged files are not silently rebuilt. A download is not proof of import.
Let the owner keep supplier details in order
Search the workspace's supplier registry. Owners can edit details and ledger mappings, or preview a CSV import before applying it. Clerks can read the registry; existing explicit confirmations can still teach it. Master edits do not rewrite old invoices or saved files. This is not a live GST registration lookup.