What Quality and Security Requirements Apply to the Accounting Export?

For the automated data flow between Mercury and your external Accounting System to work smoothly, specific security and quality requirements apply to both the transmitted CSV files and the connection itself.

Requirements for the Accounting System's CSV Data

The CSV file that your Accounting System sends back to Mercury after processing must meet certain criteria. Violating these criteria will lead to a FAILURE status.

• Encoding:

  The entire file must use UTF-8 encoding to ensure all special characters are transferred correctly.

• Structure:

  Each element in the transmitted data set must represent a complete line, including any necessary line terminators.

• Headers:

  The very first element must contain the column headings (Headers) so Mercury can map the data correctly.

• Size Limit:

  Maximum file size restrictions apply to the CSV file. If your file exceeds these limits, the upload will be rejected. (Contact MMT Support if this becomes a problem.)

Security and Validity of the Connection

The connection between Mercury and your Accounting System is authenticated using a secured token (JWT):

• Token Validity:

  The token generated for the export is valid for one month from its creation.

• Expiration:

  After this period expires, the token becomes invalid. If the export attempt occurs then, you will receive an authentication error, and the export will terminate with FAILURE.

Best Practice:

Although the token is valid for one month, you should initiate the export as soon as possible after finalizing the Plan Items to avoid delays and potential authentication issues.