01
Capture
However it arrives.
Drop a PDF, a scan or a phone photo. Batch a hundred at once. Every file gets a queue position and a job you can watch.
- PDF, JPG and PNG
- Batch queue with retry
- Original preserved
Agentic extraction now reads line items, HSN and tax splits
Every invoice has anext best action.
Ledgerline reads the document, reconciles it against the purchase order and goods receipt, surfaces the exceptions worth your attention, and carries the record all the way to payment — without anyone retyping a number.
NO CARD REQUIRED · GST-READY · BUILT FOR INDIAN PAYABLES
Invoice captureOCR extractionPO matchingGRN reconciliationApproval routingPayment trackingGST summariesAP agingCost centersE-invoicing / IRNInvoice captureOCR extractionPO matchingGRN reconciliationApproval routingPayment trackingGST summariesAP agingCost centersE-invoicing / IRN
THE WORKSPACE, ASSEMBLING
Watch a payables
desk build itself.
- 01
The document arrives
A PDF or photo lands in the queue. Ledgerline opens it, reads it, and starts pulling structure out of the page.
- 02
Numbers become records
Vendor, GSTIN, dates, tax splits and every line item are extracted into typed fields — with a confidence score attached.
- 03
Context gets attached
The invoice is matched against its purchase order and goods receipt. Spend lands in the right cost center.
- 04
Exceptions surface first
Quantity mismatches, missing HSN codes and duplicate invoice numbers rise to the top. Everything clean flows on.
app.ledgerline.io/dashboard
Search invoices, vendors…⌘K
RMPayables this month
₹48.2L
+8.2%
Outstanding
₹13.7L
−12.4%
Net GST payable
₹3.18L
+3.1%
Awaiting approval
14
4 flagged
Payables trend
12 monthsA
M
J
J
A
S
O
N
D
J
F
M
Needs review
Qty exceeds GRN by 40 units
INV-2290
HSN code missing on 2 lines
INV-2284
Duplicate invoice number
INV-2279
InvoiceVendorAmountStatus
INV-2291Sundaram Metals₹2.85LApproved
INV-2290Keshav Logistics₹96.2KFlagged
INV-2288Nirmal Packaging₹4.13LPaid
INV-2287Arya Components₹1.59LSubmitted
INV-2285Vertex Tooling₹61.3KApproved
ONE CONTINUOUS PIPELINE
Five stages. No retyping in any of them.
02
Extract
The page becomes data.
A LangGraph agent reads the layout, pulls the header fields and every line item, and scores its own confidence so you know what to double-check.
- Vendor, GSTIN, dates
- Line items with HSN
- CGST / SGST / IGST split
03
Match
Nothing floats free.
The invoice is reconciled against its purchase order and goods receipt. Quantities and rates are compared line by line.
- PO three-way match
- GRN quantity check
- Cost center allocation
04
Approve
The right eyes, in order.
Draft to submitted to approved, with role gates the API enforces. Rejections require a reason. Every transition is written to an audit log.
- Role-gated transitions
- Mandatory reject reason
- Immutable audit trail
05
Settle
Down to the last rupee.
Record full or partial payments with method and reference. Outstanding balances feed AP aging; tax feeds the GST summary.
- Partial payments
- AP aging buckets
- GST reconciliation
And it all lands in one ledger.
Every stage writes to the same record, so the invoice you opened on Monday still carries its full history on Friday.
WHY WE BUILT IT
Most finance teams do not lose time on the hard decisions. They lose it retyping a vendor name, hunting for the purchase order, and asking who approved what. Ledgerline removes that layer entirely — so the only thing left to do is the judgement.
THE CONTROL LAYER
Built for the parts of payables that actually go wrong.
GST that reconciles itself
CGST, SGST and IGST are captured per line and rolled into a monthly summary split by HSN, outward versus inward, B2B versus B2C. Incomplete line items are counted rather than quietly dropped.
GSTR-ready
monthly export
AP aging you can act on
Unpaid and partial invoices are bucketed into current, 1–30, 31–60, 61–90 and 90+ days — with credit and debit notes already netted off, per vendor and per invoice.
5 buckets
per vendor and invoice
Vendors with a memory
One record per supplier carrying GSTIN, payment terms, credit limit, full invoice history, every payment recorded and the live outstanding balance. Duplicates are caught on creation.
Dedup on write
GSTIN and name match
Spend, sliced the way you plan
Cost centers attach at invoice and line-item level, so departmental spend, unallocated spend and top-vendor concentration are all one query away.
Cost centers
invoice and line level
Controls that actually hold
Roles are enforced server-side, not in the browser. Approvals, rejections and payments each require the right role, and every status change lands in an append-only audit log.
Server-enforced
four-role model
WHAT CHANGES ON DAY ONE
The same work, minus the typing.
Today
Someone opens the PDF and retypes the vendor, the date, the tax split and every line into a spreadsheet.
With Ledgerline
The document is read once. Every field lands typed, with a confidence score on the ones worth checking.
Today
The purchase order lives in one inbox, the goods receipt in another, and the invoice in a third.
With Ledgerline
All three sit on the same record, compared line by line, with the mismatch stated in words.
Today
"Who approved this?" is answered by scrolling an email thread.
With Ledgerline
Every status change carries an actor, a timestamp and a reason, in an append-only log.
Today
AP aging is a spreadsheet somebody rebuilds by hand on the last Friday of the month.
With Ledgerline
Aging buckets recompute on every payment, with credit and debit notes already netted off.
FOUR SEATS AT THE DESK
Everyone sees exactly their part.
Ledgerline ships with the four roles a payables process actually has. Each one is a server-side permission, so the interface and the API always agree about what you can do.
Data entry
Uploads and corrects
Drops documents in, fixes anything the agent flagged, and sends the clean record forward. Never has to open a spreadsheet.
Approver
Decides, with context
Sees the invoice, its purchase order, its goods receipt and its exceptions on one screen. Rejections require a reason.
Finance manager
Pays and reconciles
Records full or partial payments, watches AP aging move, and pulls the GST summary at month end.
Admin
Holds the controls
Manages who can do what. Roles are enforced by the API on every request, not hidden in the interface.
What Ledgerline is not
It is not accounting software and it does not file your returns. It produces the GST summary and the GSTR-1 export you hand to your filing tool or your CA, and it keeps the payables record that sits underneath them. If you need a general ledger, this sits alongside one rather than replacing it.
WHAT IS ACTUALLY IN THE BOX
Not a demo. A working system.
41
API endpoints
Invoices, vendors, POs, GRNs, payments, reports and admin — every surface addressable.
5
Aging buckets
Current through 90+ days, netted against credit and debit notes automatically.
4
Enforced roles
Data entry, approver, finance manager and admin — checked on the server, every request.
100%
Audited transitions
Every status change writes an append-only log entry with actor, reason and timestamp.
QUESTIONS
The things people
actually ask us.
Straight answers, including where the product stops. If something here is missing, ask before you commit anything to it.
See pricingIt varies with the document. A clean digital PDF from a regular supplier reads almost perfectly; a creased phone photo of a handwritten challan does not. Rather than claim a headline number we score every extraction and surface the low-confidence fields for review — the point is that you always know which figures to check, not that you never check any.
PDF, JPG and PNG, up to 20 MB per file. Multi-page PDFs are read in full. Scans and photos work, though a flat, well-lit image extracts considerably better than an angled one.
Yes. Everyone who signs up under the same company name joins that workspace and sees the same records, with their own role. Records are isolated per company at the database level, so no other company on Ledgerline can read yours.
It is saved with a "flagged" status and the specific exceptions attached — quantity over the goods receipt, missing HSN code, duplicate invoice number. Nothing is silently dropped, and flagged invoices surface at the top of the dashboard rather than sitting in a queue nobody opens.
No. Ledgerline is useful from the first invoice with nothing else in it. Purchase order and goods receipt matching become available once those records exist, and invoices already in the system link up retroactively by their PO reference.
Authentication runs through Supabase and every API request carries a verified token. Each request is scoped to your organization in SQL, so a request for another company's record returns "not found" rather than the record. Uploaded files are deleted from disk once extraction finishes; the extracted data is what persists.
Yes. Reports export to CSV on every plan, the GST summary exports in GSTR-1 shape, and the Scale plan exposes the full REST API. There is no export paywall and no retention hold on cancellation beyond the notice period in the terms.
The core — capture, extraction, matching, approvals, payments, aging — is jurisdiction-neutral, and invoices carry a currency and exchange rate. The tax layer is specifically Indian GST, so a business filing elsewhere gets the payables workflow but not a tax report that matches its regime.
START IN AN AFTERNOON
Put the next invoicewhere it belongs.
Create an account, upload a real invoice, and watch the extraction, the matching and the approval path run end to end.