BS to AD Deadline Conversion: The Mistakes That Sink Nepali IP Deadlines
BS AD deadline conversion errors cause missed renewals and lost opposition windows in Nepal. The five mistakes, worked examples, and a method that works.
Nepal's IP records speak Bikram Sambat; your phone, your bank and your calendar speak Gregorian. Between the two sits every IP deadline that matters — the 35-day renewal window, the 6-month grace, the 90-day opposition count.
The conversion between them is not hard. Done carelessly, it is the single most avoidable way Nepali brands lose rights: a renewal believed to be weeks away that has already lapsed, an opposition window that quietly closed at a month boundary.
In short
BS AD deadline conversion is where Nepali IP deadlines are won or lost: the DOI records dates in Bikram Sambat, commercial calendars run in AD, and every window — 35 days for renewal at NPR 3,500 per class, 6 months of grace with the NPR 1,000 fine, roughly 90 days for opposition — is computed from a BS-recorded date. The recurring mistakes are trusting a fixed year offset, converting by hand at month boundaries, counting 35 days as a month, counting the grace period as 180 days, and ignoring holiday extensions. The method that works: fix the source date, convert once with a verified tool, count windows in the correct units, and diarise in both calendars with a buffer.
Why BS/AD deadline conversion rules every IP date in Nepal
The Department of Industry's certificates and Bulletin entries print dates in Bikram Sambat — the Bulletin helpfully carries both calendars, but the operative dates practitioners must verify are the BS ones on the certificate. Meanwhile every working tool a business owns is AD-native.
So every deadline passes through one conversion: registration date (BS) → expiry (+7 years) → renewal windows → a calendar entry someone's phone will actually remind them about. The windows are fixed; the conversion is where the error enters.
The five conversion mistakes, and what each costs
None of these are exotic. All five appear in real renewal files, and all five are eliminated by the same habit: convert once, with a verified tool, and record both dates in the register.
| Mistake | How it happens | What it costs |
|---|---|---|
| Trusting a fixed year offset | BS years sit over half a century ahead of AD, and the exact offset shifts with the month | A deadline calculated to the wrong year entirely |
| Converting by hand at month boundaries | Month lengths differ between the calendars | Days or weeks of error, usually discovered too late |
| Counting 35 days as one month | A calendar-month shortcut loses or gains days | Renewal filed after the normal-fee window — the NPR 1,000 fine, at best |
| Counting the 6-month grace as 180 days | Calendar months are not fixed day counts | A cancellation believed days away when it has already happened |
| Ignoring holiday extension rules | Deadlines landing on public holidays extend to the next working day — only if your calendar knows the Nepali holidays | Relying on luck, especially around festival season |
A worked example that shows the stakes
Take the example our renewal guide works through: a registration dated 2083/05/12 BS. Expiry falls on 12 Bhadra 2090 BS — 28 August 2027 AD. The normal-fee deadline (expiry + 35 days) lands around 2 October 2027; the grace deadline (expiry + 6 calendar months) around 28 February 2028; from 1 March 2028 the registration is cancelled automatically.
Every one of those AD dates is derived, not read. Get the derivation wrong by a month at the start and the error compounds through all three deadlines — with no revival after the last one passes.
A conversion method that leaves no ambiguity
Fix the source date in BS
Read it from the certificate or the Bulletin record — never from memory or a summary sheet. This is the only input the whole chain trusts.
Convert once, verify once
Use a purpose-built converter rather than mental arithmetic, and record both BS and AD forms wherever the date is stored.
Count each window in its correct units
Count days for the 35-day renewal window and the 90-day opposition window; count calendar months for the 6-month grace. Mixing the units is the classic silent error.
Diarise with a buffer, in both calendars
Set the internal deadline at least a week before the legal one. Holiday extensions exist as a safety net, not a plan.
Where conversion errors bite hardest
Renewal is the expensive one — a lapsed trademark is cancelled automatically after grace, and the mark becomes available to anyone. Opposition is the urgent one: the 90-day window runs from the Bulletin's publication date, and a watch report that arrives late hands you a dilemma instead of a case assessment.
Patents and designs inherit the same arithmetic with their own clocks — annual patent maintenance and the 5+5+5 design cycle all key off BS-recorded dates. One conversion discipline, applied portfolio-wide, is the fix.
Want this handled for your brand?
IP Watch monitors new trademark publications in Nepal and alerts you to potentially conflicting marks — with the context needed to review them.
This article is general information, not legal advice.