The reason why data does not pull into form 300.00 is usually rooted in the fact that in the directories of sales types and receipt types, the declaration line codes are not set or are specified incorrectly. Until this link is configured, documents are posted, but the system does not understand which line of the FNO to reflect them in — hence the empty data.
How to fix this
You need to check and configure the sales type and receipt type — enter into them the declaration line codes that correspond to the actual operations. After correctly configuring these directories, the data will automatically pull into FNO 300 when generating the declaration.
In addition, it is worth setting up direct exchange with the IS ESF — this ensures correct transfer of invoice data and synchronization of information between systems, which also affects the completeness of data in the declaration.
Frequently asked questions
Why does data still not get into the declaration even when documents are filled out correctly?
Most often the problem is not in the documents themselves, but specifically in the directories — if the sales type or receipt type is not linked to the required declaration line code, the program will not be able to correctly classify the operation for FNO 300.
Do documents need to be re-posted after configuring the sales and receipt types?
Yes, after the declaration line codes are correctly set in the directories, documents posted earlier may need to be re-posted so that the data falls into the correct lines of the declaration.
Why set up direct exchange with the IS ESF if the problem was in the declaration?
Exchange with the IS ESF ensures the relevance of invoice data in the system, which directly affects the completeness and accuracy of the information that subsequently forms the declaration figures.