Procurement · Purchase to payment

The other half of your books, built the same way.

Vendors → Purchase Orders → Bills → Debit Notes → Payments Made. The same connected flow as your sales — pointed the other direction — so payables get the same discipline as receivables.

Start your 14-day trial

The purchase document chain

  1. Purchase Order

    Raise it, email it to the vendor, and track what's arrived against what was ordered.

  2. Purchase Bill

    Record the vendor's invoice — stock comes in, the payable is booked, input credit is captured.

  3. Debit Note

    Return goods or claim adjustments; stock goes back out and the payable reduces.

  4. Payment Made

    Pay by bank, cash, UPI or cheque, allocated bill by bill — oldest first if you want.

No PO needed for the everyday case: goods arrive with the vendor's invoice, you enter the bill directly, and everything downstream just works.

Never enter the same vendor invoice twice.

Every bill records the vendor's own invoice number and date — and LedgrBook blocks a duplicate for the same vendor in the same financial year, with a link to the existing bill. It's the single most common bookkeeping error in a busy shop, and it simply can't happen here.

Due dates and payables aging run from the vendor's invoice date, not your entry date — so a bill entered late still ages correctly.

Built for real purchasing

Bill it as it arrives

Recording the bill is the goods receipt: stock comes in dated the vendor's bill date, no separate GRN step to forget.

Smarter price prefills

Line rates prefill from your product's purchase price or the last price this vendor charged — and every saved bill teaches the system the newest price.

Vendor advances

Paid ahead? The unallocated amount sits as an advance, and the next payment screen offers to apply it first.

Partial everything

Convert part of a PO into a bill, return part of a bill on a debit note — quantity-level control the whole way.

Your buy prices are yours.

A single per-role toggle — "view purchase prices & costs" — hides cost values everywhere: product masters, purchase documents, vendor screens and reports. Sales staff see what they need to sell; only the people you choose see what things cost. Enforced at the server, not just hidden on screen.

Every vendor, one screen.

Outstanding payables, every PO, bill, debit note and payment, a running ledger with printable statements, contacts and activity — one page per vendor. And because every bill carries input-credit eligibility and the vendor's GSTIN, your GSTR-3B input credit is being assembled while you work, not reconstructed at filing time.

Overview view

Questions about purchases & vendors

Yes — a duplicate bill number for the same vendor in the same financial year is blocked automatically, with a link to the existing bill.

Give your payables the same discipline as your sales.

GST-ready billing, stock and accounts — together