IOCL Fuel Module Date Bug

Our in-house freight management system, built several years ago on the Axpert platform, has one stubborn issue left to resolve. The fuel-top-up module that pushes amounts to the Indian Oil (IOCL) fuel-card portal used to work flawlessly; today the .exe that handles the call still launches, our API still responds, yet the IOCL site never receives the update. All we get back is the message “Invalid date format.”

I have tried every regional and UI date configuration I can think of, but the executable keeps throwing the same error. Unfortunately, no one on the current team is sure what date pattern the original developer used inside that module.

What I need from you:

• Investigate the Axpert-based code and the companion .exe
• Identify the actual date string being generated and the format IOCL expects
• Patch or rewrite the module so that fuel amounts post successfully to the IOCL portal
• Provide the fixed executable (or equivalent script) along with a brief note on the change for future maintenance

If you have experience with Axpert, legacy .NET/Win32 utilities, or direct integration with IOCL services, you’ll likely solve this quickly. Once the portal starts accepting transactions again without the “Invalid date format” response, the job is done. Let me know how soon you can jump in and what access or logs you’ll need first.