Aaron McCausland
03/31/2026, 9:07 PMCeligo AI
03/31/2026, 9:07 PMAI generated answer (using internal Slack threads):Based on the conversations, it seems that the issue you're facing is a common one when importing invoices with a specific transaction date (trandate) from a CSV file into NetSuite. The system defaults to using the current date if the date field is left blank during the import process. To overcome this, you can use a workflow that triggers only on a CSV import to default a date when created. This way, you can ensure that the trandate is set to the date specified in the CSV file, rather than the current date. However, please note that NetSuite has a setting that throws an error if the transaction date and posting period are different. This setting can be overridden, but it's not recommended as it can cause discrepancies between your General Ledger and aging. If you're still facing issues, you might need to look into scripting a solution to match the period if there is a mismatch. This could involve creating a script that runs after the CSV import process to update the trandate on each invoice based on the date specified in the CSV file. Remember, this is a complex process and should be handled with care to avoid any data inconsistencies. Always test your solution in a sandbox environment before deploying it to your live account. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******
Celigo AI
03/31/2026, 9:07 PMSlack thread 1: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.835205078
Slack thread 2: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.835144043
Slack thread 3: here (available only if the original thread was posted in the last 90 days)
Similarity score: 0.829589844
Celigo AI
03/31/2026, 9:07 PM