A native SAP solution for complying with electronic invoice regulations. Automatically generates allocation numbers (TANs) for outgoing invoices and validates them for incoming ones – all fully integrated into your existing SAP processes.
An ABAP-native solution, no external installation needed.
Built natively into your SAP environment, GAL automates allocation number handling for both outgoing and incoming invoices - with full compatibility across key business modules.
GAL installs quickly with minimal setup and runs natively within your SAP system - no external tools, no user disruption.
Ensures every invoice meets regulation requirements - Runs silently behind the scenes, alerting users only when action is required.
Stay in control with complete visibility over all invoice statuses and flows, ensuring nothing slips through the cracks.
Embedded into core SAP modules - including Finance, Sales, Logistics, and Real estate invoices.
Automatically generates TANs for outgoing invoices and validates them on incoming ones - fully embedded in the invoicing process.
Easily update or correct invoice status when manual intervention is required.
Track and manage all relevant invoices and their statuses from a single SAP dashboard.
Manages user authentication behind the scenes through a built-in, seamless process - no external steps required.
Supports both direct communication from SAP to the tax authority and indirect access through external middleware — adaptable to your infrastructure.
Embedded into core SAP modules - including Finance, Sales, Logistics, and Real estate invoices.
Automatically generates TANs for outgoing invoices and validates them on incoming ones - fully embedded in the invoicing process.
Easily update or correct invoice status when manual intervention is required.
Track and manage all relevant invoices and their statuses from a single SAP dashboard.
Manages user authentication behind the scenes through a built-in, seamless process - no external steps required.
Supports both direct communication from SAP to the tax authority and indirect access through external middleware — adaptable to your infrastructure.
According to the Israel Tax Authority’s directive, as of April 1, 2024, any business issuing invoices that meet certain criteria is required to obtain a Tax Allocation Number from the tax authorities, which must appear on the invoice issued to the customer. In addition, when recording an invoice in the system, it is mandatory to enter the supplier’s Tax Allocation Number in order to be eligible to claim the input VAT. As of 2024, a Tax Allocation Number is required for any VAT-inclusive invoice where the pre-VAT amount is NIS 25,000 or higher, and where the customer for whom the invoice was issued is a VAT-registered business, or where the customer explicitly requested such a Tax Allocation Number. GAL (Government, Authority, Local Taxes) is an ABAP-based solution designed to fully support and comply with these regulatory requirements.
GAL is a production-ready solution. It has already been successfully implemented and is actively running at customer sites. The product is stable, fully validated in real-world environments, and ready for broad deployment.
Yes. GAL currently supports the Real Estate module (RE-FX) as an add-on, available for an additional fee. In addition, for organizations that use other modules that generate customer invoices—such as the legacy Real Estate module (RE), Loans (CML), Leasing, and similar solutions—we provide an API. This API enables customers to easily and independently perform the required adjustments, using the structured and controlled working environment built into the product.
Yes. The product includes comprehensive support, such as ongoing version updates, technical documentation covering installation, customization, authorizations, and user guides, a ticketing system for issue handling, and online assistance when required.
What should we do in case of future changes to the Israel Tax Authority interface?
The Tax Allocation Number is stored in a dedicated table and can be viewed in the details of the journal entry posted for the invoice. In addition, the Tax Allocation Number for the relevant invoices can be viewed in the customer or vendor account display, using transactions FBL5N (customers) and FBL1N (vendors).
The Tax Allocation Number is populated only for invoices that include input VAT and for which a Tax Allocation Number exists in the system. If an invoice requires a Tax Allocation Number according to the Israel Tax Authority’s definitions but no such number has been assigned, an error message will be generated in the error log.
Yes, provided the organization follows the standard process defined by the localization team—entering the interim invoice using a dedicated VAT code and posting it to a clearing account, with reconciliation performed upon receipt of the tax invoice. In this case, the Tax Allocation Number (as well as the supplier’s VAT registration number) is taken from the interim invoice document entered in the system. The process is also supported for organizations that work by canceling the interim invoice or posting an advance payment and then re-entering the tax invoice after payment. Any other workflow will be reviewed on a case-by-case basis.
No. The Tax Allocation Number is not defined as a mandatory field, as only invoices that meet the criteria defined by the Israel Tax Authority are required to include it, and suppliers may also request a Tax Allocation Number retroactively after the invoice has been issued. However, if the Israel Tax Authority’s criteria are met and no Tax Allocation Number has been entered, a system message will be issued accordingly. This message type can be customized to an error, in which case the invoice will not be saved.
Yes. According to the Israel Tax Authority’s regulations, a Tax Allocation Number must be stated on a customer invoice if it meets the defined criteria. Nevertheless, it is also possible to request a Tax Allocation Number retroactively—for example, in cases of communication issues—provided that the customer is informed of the assigned number.
Yes. This can be done using the dedicated monitor built for this purpose, provided that the user has the appropriate authorization object assigned.
The entire topic of emergency numbers, including all related business logic, is currently under review by the Israel Tax Authority, and it may even be canceled. We are awaiting a final decision, and any decision that is made will be fully implemented and supported within the system.
At this time, no—and unfortunately this is outside our control. The only service currently provided by the Israel Tax Authority for validating a Tax Allocation Number requires submitting the Tax Allocation Number itself in order to retrieve the invoice details. There is currently no option to submit invoice details in order to receive a Tax Allocation Number. According to the Israel Tax Authority, such a service may be developed in the future.
A dedicated field titled “Tax Allocation Number” has been added to both logistical and financial vendor invoice screens, including transactions FB60, FB65, FV60, FV65, and MIRO. This field is used to enter the Tax Allocation Number. If the number is not available at the time the invoice is entered, it can be updated later through a dedicated process.
No. The system includes a set of customization tables that provide flexibility for organizational-level settings as well as parameters defined by the Israel Tax Authority, such as date-dependent threshold amounts. Code changes—requiring the delivery of a new correction or a recommendation to modify existing code—would only be necessary if the Israel Tax Authority issues new regulations that change the underlying business logic beyond what can be handled parametrically.
Yes. The Tax Allocation Number is automatically validated before the invoice is saved by invoking a service provided by the Israel Tax Authority. The validation is based on the entered Tax Allocation Number and enables a comparison between the invoice details registered with the tax authority and the invoice details entered in the system. If the Tax Allocation Number is invalid, an appropriate system message is displayed.
Yes.
No. The field appears only for company codes that have been defined as relevant in the system customization. This logic is designed to avoid impacting SAP implementations that include company codes not related to Israel and therefore not subject to these requirements.
The product is fully supported across all SAP systems running ECC 6.0 EhP 0 and higher. All S/4HANA versions are fully supported as well.
No.
No. No external installations are required—neither software nor hardware.
The product is developed in ABAP and is delivered to the organization using standard SAP Change Requests (CRs). As with all Dpro products, customers receive a complete installation kit that enables a smooth self-installation process. This is a structured and proven process that has been refined and validated over the past ten years. Upon contract signing, the relevant stakeholders in the organization receive an email containing all required installation information, including links to installation instructions, documentation, relevant videos, and the support ticketing site. Authorized users are also granted access to a dedicated folder containing the installation kit, including the CRs themselves and detailed installation guides. The first step—importing the CRs into the SAP development (DEV) system—is performed by the Basis team. Next, the business teams configure the product to align with the organization’s business processes. Finally, the development teams perform the required final adjustments to forms, programs, and interfaces using the provided documentation and dedicated API tools. At this stage, the organization conducts sanity and process tests to ensure full alignment with its requirements. Once validated, the product is transported by the Basis team to the quality assurance (QAS) system for in-depth testing, and upon successful completion, it is deployed to the production system.
No. All product objects are delivered under our dedicated namespace /DCM/.
No. There is no risk of such conflicts, as the product uses a dedicated namespace. All objects are uniquely named within the SAP landscape, ensuring there are no conflicts with standard SAP objects or customer-specific Z objects.
Yes. The service URL can be customized. By default, the system can be configured to communicate directly with the Israel Tax Authority service, but it is also possible to define an alternative endpoint. To support this, a proxy service can be configured to forward requests and responses to and from the Israel Tax Authority server as-is, using a REST-based service.
No. The system includes multiple customization tables that provide flexibility for both organization-level settings and parameters defined by the Israel Tax Authority, such as date-dependent threshold amounts. Code changes—requiring the delivery of a new Change Request or a recommendation to modify existing code—would only be necessary if the Israel Tax Authority issues new regulations that alter the business logic beyond what can be handled parametrically.
Yes. At this stage, the solution supports the BAPI BAPI_ACC_DOCUMENT_POST, which is commonly used for interfaces in many organizations. The documentation provided with the solution clearly explains the required steps and specifies the exact field to be used for passing the Tax Allocation Number within the interface.
As part of the installation instructions, we provide clear and detailed guidance on the authentication process, including which roles within the organization need to contact the Israel Tax Authority, and when and how this should be done. We also provide recommendations based on the organization’s structure regarding the number of required users and authentication tokens. In addition, the authentication process—which must be renewed periodically—can be managed directly from within the system.
Simplify SAP. Empower users.
Drive faster decisions with smarter tools – across every department.
