0113·Invoice date is not in the correct format

What this means

FBR accepts one date format: four-digit year, two-digit month, two-digit day, hyphen-separated. Anything else — day-first ordering, month names, an appended time component, or a timezone offset — is rejected.

Why it happens

• A locale-formatted date was submitted, typically day-first as written in Pakistan.
• A full timestamp was sent where only a date is expected.
• A date object was serialised to an ISO string including time and timezone.
• Timezone conversion shifted the date across a day boundary before formatting.

How to fix it

1. 1Format the date explicitly rather than relying on default serialisation.
2. 2Truncate any time component before submission.
3. 3Treat the invoice date as a calendar date, not an instant — apply the business timezone before formatting, not after.

Related errors

• 0005Date is not in a valid format
• 0042Invoice date is empty
• 0043Invoice date is later than the current date