Clear documentation on S @ T SP

Question

Clear documentation on S @ T SP

Navigation

#1 by (2 votes)

1

I need to integrate the SAT into my POS, but I can not find clear documentation on this communication. From what I could understand, I'll have to:

Generate a coupon XML

Digitally Signing

Send to S @ T via DLL (which is standard)

Here are some questions:

Where do I find DLL documentation with possible calls?

I'm going to use S @ T as an NFCe contingency, where do I find out what rules apply in this case?

I do not intend to use third-party components, so I need the official revenue documentation, if any.

Thanks in advance, hug.

sat-cfe

asked by anonymous 01.09.2015 / 15:19

1 answer

Get the client ID of a selected row from the DataTable How to update CakePHP from version 0.2.9 to the latest version, with security

score 2 · Accepted Answer

The documentation exists and is very comprehensive (surprisingly well done) and is on the São Paulo Department of Finance . The documentation is in Legislação , item Legislação em vigor .

If you're reading the whole CAT-147 it's kind of tedious. Please download the PDFs from the Guidance Manual and the ER SAT (Requirements Specification). You will find them in Downloads , item Arquivos vigentes . Take a general exploration on the page and you'll start to form an idea of the thing.

Understand that in a single manual, there are two sides to the technical documentation. One is for SAT equipment manufacturers and another for systems developers (which they call AC, commercial application). In ER SAT , there is a table (item 4.2.2) that lists all the groups, elements, and attributes that compose the CF-e XML, and this will help you build this XML. The first column of this table is important because it indicates the source , who is responsible for providing that data. The lines indicated with AC are the data generated by your application. The others will be filled in later by the SAT equipment.

The flow is simple:

Your application generates a simple XML, containing only the responsibility data of the CA, describing the sale;

This XML is sent to the SAT device through the function EnviarDadosVenda ;

The SAT device completes the XML, validates, signs and returns it to your application;

Your application issues the extract based on the XML data, which is called CF-e-SAT (whose signature makes it a legally valid fiscal document).

You said you do not want to use third-party libraries, but nothing prevents you from checking for other implementations to help you understand the whole thing. I would put more links, but I have no "reputation" for this:)