Does the SDK support calls to check E-File status?

[etrent17]

I would like to know if the SDK can check Lacerte for E-File status on all clients in Lacerte. I read through the Lacerte SDK PDF file that they share on the installer download page, but I was unable to find any conclusive answers there. Does the SDK support this kind of access?

[DatabaseRobert]

No.  Some limited data used to be visible in the data1 file (fields c1_g10 [fed status] and c1_g9 [state status]), but in the 2021 program those fields are no longer exposed to the ODBC link.  And in the 2020 program, even though we efiled over 2000 individual returns, none of them have anything other than "0.00" in both fields.

Extensive information--that is, "line-by-line text corresponding to the F4/status | efile tab"--*used* to be visible in the detail sub-directory "EF", in the files "ClientNum.?A#" (where ? is the module letter [i/IND, f/FID, p/PAR, and so on] and # is the terminal year digit)...
  ...but the last year that those files exist is TY2018.  (So "data path\EF\12345.iA8" for IND client, for example.)

Everything since then is stored "somewhere else", and--since opening the files with NotePad now shows gobbledygook--likely encrypted in the same manner as the database files, after the ODBC connection was put into place.

.

You can still see the F4/status information in Data5, but unless you routinely use those statuses to handle your efiling they will not help you terribly.
  (We use two, one for "select batch of today's transmission | F4/mark them to be done" [and then Filter in the left panel to see ONLY the clients slated for transmission today to work with them (page4.4/attachments, page4.1/filing date)] and then after transmission another for "we sent them".)

.

Long-winded way of saying, "No."



Robert Kirk
LTUGtools

[DatabaseRobert]

I take it back: JasonAtIntuit posted the following for an SQL connection to see efiling info.
  https://proconnect.intuit.com/community/lacerte-sdk-group/sql-to-join-efstatus-to-client-info/gpm-p/...

For me, working in Paradox, I would start from the Data1/client info table, connect the client # (c1_0) field to the EFilings table on the "ClientID" field, and then connect that to the EFStatuses table on the "Id" [line number] field.
  That way you can see the Client # & names (from Data1), the module & state (from EFilings table, EFid field), and what is going on with it (from EFStatuses table, EF Status field) and when (same table, EFStatusDate field [also contains time]).



Robert Kirk
Derwood, MD