Implementation steps

Step 1
Choose your modules

You decide which modules you want to use.

The available modules are explained in this section. The taxcode solution and indirect tax validation modules can be implemented individually as stand-alone solutions.  The other modules require the implementation of at least the sales and/or purchase modules.

Step 2
Choose your countries

Choose which of the countries that your company is registered in, you want to activate on Taxmarc.

Step 3
Choose your configuration landscape

Based on your system landscape and in consultation with the Taxmarc team, decide on the best implementation strategy.

If you have one global SAP landscape, you will probably want to opt for a full Core/Agent implementation in that system. But if you have multiple SAP systems or even non-SAP systems that you want to connect, you will probably want to designate one of your SAP systems as the Core, serving all other systems including the Core system itself.

Step 4
Choose your functional implementation partner

Based on the complexity of your business flows and the level of customization in your SAP system and in consultation with the Taxmarc sales team, you decide on the best implementation approach.

If your SAP system is pretty much ‘vanilla’ (i.e., not much customization) and you have knowledgeable power users you may be able to opt for the plug&play implementation. This is in principle fully self-guided, but the Taxmarc team will be available as a backup. Note that this approach does not require you to have simple tax scenarios, just follow standard SAP flows.

For example, a drop ship (‘TAS’) transaction results in an ABC tax scenario that involves both sales and purchase documents. Although that makes the scenario more complex, it will work without any issues as long as you follow standard SAP flows (meaning the SO generates the PO so it is linked to it in the standard document flow).

If you want to include more complex tax functionality that is part of the Taxmarc solution but requires more configuration, you will need the support of one of our implementation partners. Examples of this are ABC consignment flows. Or an AB cross export transaction where the goods are first imported into an EU country where your company is registered but that is not the final destination country.

To implement the external engine for a non-SAP system you will also require an implementation partner to make sure the data required by the Taxmarc Core is correctly provided by the external system. We need to make sure the 2 systems ‘speak the same language’, meaning that for example an export indicator means the same thing to both systems.

If your system is heavily customized and you use a lot of non-standard flows, you will definitely need an implementation partner and you will need help with technical developments. Mostly in BADI’s provided in the Taxmarc solution but possibly also in your existing code.

Examples of this are cases where you see a sales order and purchase order as part of one flow for tax purposes, but they are not linked in a standard way in SAP. Or in cases where you have X-system flows. Or your use of data is non-standard like your plant in a sales transaction is not your actual dispatch location.

Meet some of our clients

We are trusted by

Back to top