Questions from the AP desk

The current server is in Google Cloud US Central, not India. Workspaces share the service, with tenant-scoped records and API access. Your own team reviews invoices; service engineers have limited access for reported faults. Private drafts belong to the signed-in operator. See the privacy policy for processing, retention and deletion requests.

No. A batch is a register file and a manifest. The scans stay in your workspace. Your team takes it into your books, whatever you use. Tally XML is an optional preview inside the batch.

EntryLedger produces a selected-batch Tally XML preview with matching ledger masters, purchase vouchers and a manifest. Your owner can save existing company and ledger names. Actual Tally Prime import, GST reports and voucher numbering are not yet verified. Test in a copy of your company first. Downloading is not importing, and repeat imports may create duplicates. There is no direct push into Tally.

Failed checks hold the invoice for review. Some digital PDFs with invalid GSTIN checksums go straight there without a model re-read. New reviews on that path get a locally rendered source preview, but fields or line items may be incomplete and need manual entry. Fit or zoom the source, then correct and confirm before moving to the next exception. If the preview is unavailable, refer to the original invoice before confirming. Older entries without a saved preview do not gain one automatically. Confirmation is logged and makes the invoice ready for export. A checksum-valid GSTIN can still be the wrong supplier: these checks do not prove identity or verify live GST registration.

A dated fixture test covered blur, skew up to 5 degrees, faded toner, uneven lighting and 72dpi. All 13 variants matched the 14 scored fields. That does not prove every field on every supplier invoice will be right. Missing required fields or failed GST and arithmetic checks go to review. Our newer OCR row reader is still off in production. See the results and their limits.

Because it is how document processing is billed across the industry, and it keeps simple invoices cheap: a one-page bill costs ₹1.40, a five-page bundle ₹7.00, and you are never paying for capacity you did not use. EntryLedger reads at ₹1.40 a page, well below the per-page list prices enterprise IDP tools quote; compare on your own volume and quote. No tax is added on top: ₹1.40 is what you pay.

Depth beats breadth for this job, so we read the documents an AP desk actually keys: GST tax invoices, supplier debit notes, supplier credit notes, and bills of supply. The validators are built around one country's tax rules: GSTIN mod-36 checksums, HSN format checks with directory warnings by default, GST arithmetic closure, regime consistency. Notes additionally need the invoice they correct. A bill of supply has no GST, so the tax checks cannot run on it; the GSTINs, HSN, line roll-up and total still do, and the entry says the proof is thinner. A delivery challan, lorry receipt, duplicate copy or proforma is not an accounting entry: it is routed away and not billed. Pricing is per page. Our current server is in the US; we do not claim India-only hosting.

The current product is hosted, with tenant-isolated workspaces. On-prem deployment and dedicated India hosting are not available through self-serve signup. If either is a requirement, talk to us before uploading documents.

Edits save as your private draft, not as approval. Wait for the saved message before leaving. After reloading, compare and restore the copy or discard it. Incomplete numbers and date text can stay in the working copy. Newer invoice or draft versions must be reviewed before you can sign off; a draft never exports or teaches a supplier.

Yes. Saved batch history keeps the original file and its selected invoice and settings snapshot. Re-download does not rebuild it from today's records. If entries or settings changed, you must acknowledge the older snapshot first. Missing or damaged originals return an error, not replacement bytes. Files prepared before retained history was introduced are not backfilled. Downloading is still not importing into Tally.

Owners can edit supplier details, aliases and saved ledger mappings used by the Tally XML preview. Clerks can read the registry, and existing explicit invoice confirmations can still teach it. Owners can preview CSV rows without writing anything, then apply a reviewed import if the registry and mappings have not changed. GSTIN identity is fixed for each record. Master changes never rewrite past invoices or saved batches. The registry is not a live GST registration check.