Instructions for IP Users: Filling out the ER Template, DATIM Submission, and Error Resolution

Shayna Padovano -


The documents described below contain instructions primarily targeted towards Implementing Partners (IPs).  They describe how to fill out the Expenditure Reporting Template, upload and submit the template to DATIM, and resolve any errors the user may encounter in these processes.

Reporting Template and DATIM Submission Instructions

This document contains instructions on how to fill out the Expenditure Reporting Template. The document includes:

  • An overview of the ER template
  • Directions on how to enter metadata in the “Metadata and Error Checks” and expenditure data in the “Expenditure Template” tabs
  • A review of error checks built into the "Metadata and Error Checks" tab
  • An overview of how to upload and submit the template in DATIM
  • Additional DATIM references and support

Version Notes:

  • 9/12/18: Original version
  • 9/28/18: Additional instructions added to show screenshots of upload and submission process; new details on the "summary table", the "run validation button", and the process of reviewing submitted mechanisms
  • 10/25/18: Added a few details including: award numbers cannot be entered with non-alphanumeric characters in DATIM; DUNS numbers that begin with "0" will be truncated in Excel, but the full 9 digits should be entered in DATIM; new slides to reflect that values with  up to 5 decimal places can be read by DATIM, but more than 5 decimal places cannot.

DATIM Error Messages and Resolutions

This document explains the on-screen error messages a user might encounter when uploading a template that is invalid.  The screenshot below lists the types of errors; each one is shown in detail in the document with specific screenshots on what the error message looks like in DATIM, and what the corresponding error is in the ER template.


Version notes:

  • 9/28/18: Original version
  • 10/25/18: Added details regarding: a new error message that displays when a hidden tab in the ER template has been unhidden; values with  up to 5 decimal places can be read by DATIM, but more than 5 decimal places cannot; "non-integer" is no longer an invalid error because DATIM can accept up to 5 decimal places; definition of "non-numeric value" and this error message.


Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request


Powered by Zendesk