Sage Intacct displays dates in some defined formats. When the admin sets up an Intacct Company, they have the ability to set a date format that is to be preferred for displaying on pages and documents. This configured date format is set as default setting for new user accounts. Although, the user can later change the date format according to their choice from “My Preferences” page.
After setting up the preferences in our environment, if we enter a date using a different format, it is re-formatted to the one set in our preferences. Date format can be changed at anytime we want.
The supported date formats are:
| 2 digit Year formats | Full Year formats |
| DD MM YY MM DD YY YY MM DD DD.MM.YY MM.DD.YY YY.MM.DD DD/MM/YY MM/DD/YY YY/MM/DD DD-MM-YY MM-DD-YY YY-MM-DD | DD MM YYYY MM DD YYYY YYYY MM DD DD.MM.YYYY MM.DD.YYYY YYYY.MM.DD DD/MM/YYYY MM/DD/YYYY YYYY/MM/DD DD-MM-YYYY MM-DD-YYYY YYYY-MM-DD |
While using printed document templates, the date format selected in the personal preferences to be reflected in printed documents is not certain.
When we convert SO or PO transactions in a workflow, we can specify that the target transaction should inherit the source transaction date. If not selected so, the target transaction will by default take today’s date as transaction date. However if the inherited source transaction date falls in a closed period, we need to change the target transaction to a date in an open period before GL posting. Because, if the company is not configured to use separate transaction and GL posting dates, then the transaction dates becomes the GL posting date as well.
Intacct sets all the automatically-created AP summaries in the consistent ISO date format of YYYY-MM-DD24:MI:SS. This helps grouping or matching transactions to the appropriate summary, and thus removes the risk of date format mismatch posting errors.
For bank reconciliations using Auto match/Auto match with Review as well as for entering or editing exchange rate dates, including the From Date, To Date, and Effective start date, the date format preference must be set to MM/DD/YYYY only.
When importing a CSV file into Intacct, there is an option to choose the date format for the import. If Intacct fails to import the file with the selected date format, it attempts to search for the format used in the file and imports the data using that date format.
While working with dates in the API, the format depends on what function we are using. For generic functions, dates are in the format mm/dd/yyyy as shown below:
<create>
<APBILL>
.
.
<WHENCREATED>01/10/2020</ WHENCREATED>
.
.
<APBILL>
</create>
For explicit functions, dates are in the form of objects:
<create_arpayment>
.
.
<datereceived>
<year2020</year>
<month>7</month>
<day>10</day>
</datereceived>
.
.
</create_arpayment>
Some functions related to audit trails accept query parameters for timestamps in the format MM/DD/YYYY HH:MM:SS.
Time is important only for transactions that occur in a different time zones.
This is all about how Intacct maintains date formats for all our transactions and documents.