Authorities Communication with the B2A Manager
(PY-DE-BA)
Purpose
You use this component to enable electronic data exchange between employers and authorities.
Until now you have exchanged application data from the areas of tax, social insurance, statements, and so on with the responsible authorities on paper or disc. You can use the B2A Manager (Business-to-Administration Manager) to send and receive data quickly and simply over the Internet.
To do
so, you create data records in the relevant area (tax, social insurance,
statements, and so on) for the corresponding authorities. You can then use the
B2A Manager to send and manage these data records.
Or, you use the B2A Manager to request certain information from the relevant
authorities and then subsequently send your data.
The exact procedure for the process of authorities communication depends on both the area and the country you are working in. Refer to the country-specific documentation.
Integration
To be able to send data using the B2A manager, you must have first created the appropriate data records in the corresponding area (for example, tax, social insurance and so on).
Implementation Considerations
Customizing
To see whether specific Customizing settings have to be made for your country for authorities communication with the B2A Manager, refer to the country-specific documentation.
If Customizing settings have to be made for your country, refer to the Implementation Guide (IMG) for Payroll <Country> in the section Business to Administration (B2A).
Encryption
Depending on the authority, the data may have to be encrypted before it is transferred with the B2A Manager. If this is the case, you will require the encryption software of a third-party administrator that is linked to the SAP System using an open interface.
For more information, see the IMG for Payroll <Country>, under Business to Administration (B2A) -> Set Up Encryption.
Features
Depending on the country, you can send data electronically
● from different areas
○ Tax
○ Social insurance
○ Statements and so on
● and with different data formats
○ String
○
XML (eXtensible
Markup Language)
● Different communication paths
○ E-mail with file attachments
○ HTTPS (Hyper Text Transfer Protocol Secure Sockets)
● Different encryption procedures
○ PEM (Privacy Enhanced Mail)
○ PKCS#7 (Public Key Cryptography Standards No.7)
As a rule, the communication path and, if required, the encryption method are determined by the responsible authority and implemented correspondingly by the B2A Manager.
For example, for the data exchange with the receiving offices of health insurers in Germany, data is exchanged by e-mail with the standard PEM encryption.
Transfer by E-Mail (E-Mail Procedure)
The relevant data is sent with the e-mail as a file attachment and is exchanged with the relevant authority.
The advantage of this method is that it can be spread widely.
Transfer by HTTPS in XML Format
The relevant
application data is exported to XML and exchanged directly with HTTPS.
Not all authorities support the XML procedure.
See also: