Invoice date vs posting date. 2B cares which month you claimed.

March 31st. The courier brings a bundle of supplier photocopies. You photograph them on April 4th. The invoices are for March. The scan is for April. If the CSV writes today's date into the voucher column, Tally posts into April. GSTR-2B for March never sees it. GSTR-2B for April shows a line you cannot explain. The CA says: who typed this? Nobody typed it. The software did.

Three timestamps show up in AP and people treat them as one. Invoice date on the paper. Day you scanned it. Day Tally posts the voucher. GSTR-2B is built from what the supplier furnished, in tax periods, not from your WhatsApp camera roll. Mixing them is a FY-end sport.

Day-first paper, ISO in the file

Indian invoices print 28/03/26 or 28-03-2026. US models like 03/28. If extraction swaps day and month you get 3 April or an invalid 28th month. Review sees the crop. Do not "fix" it to today so the import stops complaining. Today is the wrong date.

FY in India for many companies is April-March. A 31 March invoice posted into April books is a close question, not an OCR question. Tally will refuse or park based on your period settings. Read Tally import help for the current release. We will not invent a hotkey or a lock message.

2B period vs Tally month

You posted in April. They furnished in March's GSTR-1. 2B for March has the line; your April ITC report does not, or the reverse. That is timing, which the 1 / 2B / 3B post already separates from typos. Using scan date as voucher date manufactures timing gaps you then blame on the supplier.

Section 16's time limit is in the Act, not in our date parser. Link section 16. A wrong year on the voucher can push you across that line. Confirm 16(4) when you file. Do not take a November date from an old blog.

Ambiguous prints

Some bills print only "March 26" or a stamp over the date. Some print two dates: invoice and due. We need the invoice date. Due date in the voucher date column is a different lie: you post in the future and 2B never lines up. If both are visible, the crop for invoice_date should be the invoice line, not the due line.

FY printed as 2025-26 on the header is not a day. Do not parse the header year as 01/04. The line date still wins.

What EntryLedger does not choose

We do not select the Tally company, the FY, or "post into the open period." Export writes the invoice date we extracted. If your import map uses "system date," that is your wizard, not ours. Change the map.

Missing date: required field failure, NEEDS_REVIEW. The clerk types what the crop shows. If the crop is a smudge, ask the supplier. Guessing 01/04 because it is April is how FY dumps get a thousand identical dates.

March pile in April

Factories get courier bundles after the 31st. That is ordinary. Score it in your first batch: how many invoices have invoice_date in the previous month. No fake percentage from us. Your paper will say. Process: extract March dates, import into the period the CA wants, do not rewrite to April so "this month's batch is clean March paper is also where the 16(4) clock bites hardest.."

Backdated vouchers in Tally may need rights. That is an accounts-head setting. Capture should not fight it by lying about the date.