tallyca — WhatsApp text → PDF (CLI)

Generate GST-style invoice PDFs (or generic PDFs) directly from raw WhatsApp/Telegram text

Install

npm install -g tallyca

Note: This package uses Playwright (Chromium) to render PDFs. The first install may take longer due to browser download.

Commands

1) Auto-detect & generate PDF (recommended)

Use this when you want a single “magic” command that decides invoice vs generic automatically:

tallyca from-text --company "ABC Traders" --output invoice_186.pdf --text "Okay. Now, I want to post invoice data as Sales Voucher in ABC Traders.

Party Name : XYZ Build
Invoice No. : 186
Date : 2/1/2026
Item: Ambuja Cement 2523 @ 18 %
Qty: 140 Bag
Rate: 279.66/Bag
HSN Code : 25322210
Amount : 39152.40

Make sure to use voucher class Sales @ 18 %. Post this as Item Invoice."

You can also pipe text:

echo "Party Name: XYZ Build
Invoice No.: 186
Amount: 39152.40" | tallyca from-text --company "ABC Traders" --output invoice_186.pdf

2) Generate invoice PDF (raw text OR flags)

a) Raw text (parse automatically)

tallyca generate:invoice --company "ABC Traders" --output invoice_186.pdf --text "Party Name : XYZ Build
Invoice No. : 186
Date : 2/1/2026
Item: Ambuja Cement 2523 @ 18 %
Qty: 140 Bag
Rate: 279.66/Bag
HSN Code : 25322210
Amount : 39152.40
Make sure to use voucher class Sales @ 18 %."

b) Structured flags (when you already extracted fields)

tallyca generate:invoice \
  --company "ABC Traders" \
  --party "XYZ Build" \
  --invoice-no 186 \
  --date "2/1/2026" \
  --voucher-class "Sales @ 18 %" \
  --item "Ambuja Cement|140 Bag|279.66|18%|25322210" \
  --output invoice_186.pdf

--item format:

Description|Qty Unit|Rate|Tax%|HSN

Repeat --item multiple times for multiple line items.

3) Generate generic PDF (receipts / notes)

tallyca generate:generic \
  --title "Payment Receipt" \
  --body "Payment of ₹39152.40 received from XYZ Build against Invoice 186." \
  --output receipt.pdf

Why you don’t see src/commands on npm

This CLI is configured to run commands from the compiled output:

• OCLIF is set to load commands from ./dist/commands (built JS)
• npm publish includes /dist (see package.json → "files": ["/dist", ...])

So on npm you should see dist/commands/... rather than src/commands/....

If you want the TypeScript sources to appear on npm as well, you can add /src/commands to the "files" list — but it’s not required for the CLI to work.

Publish (for maintainers)

npm login
npm publish --access public

(prepack runs automatically during publish and generates oclif.manifest.json.)