Skip to Content
Technical Articles
Author's profile photo Emerson Alves Tosin

Financial Posting Configuration

Introduction

An important task for SAP ERP X Concur integrations is the configuration of importing accounting documents. At this point, we will have to keep in mind what type of document, account scheme, cost objects, filters and the frequency of document import. In this Post I will show you step by step how to configure. Come on!?

Main Part

The relevant Concur document types are displayed according to the integration activities you initially activated on the screen. Configuration of integration with SAP Concur.

If you only selected the integration activityPayment request (invoice), for example, this will be the only document type available.

Please note that not all Concur use cases are supported, but you can use the following BAdIs to implement release-relevant deviations:

  • BADI_CTE_FIN_POST_DOC_CHANGES – for minor field modifications
  • BADI_CTE_FIN_POST_USES_CASES – for customer-specific postings in reports
  • BADI_CTE_FIN_POST_ADJUST_DOC – for changes to accounting data

 

Types of documents in Concur

To go to the next step, click Continue

 

General Settings

By default, only actual postings are considered. However, by selecting the checkbox below, you can also allow test user postings on your system.

Select one of the two expense account options available:

  • Accounts as used in Concur
    In this case, the accounts must exist with identical IDs in the Concur system and in the SAP system.
  • Process Concur Accounts as Symbolic Accounts
    If you choose this option, go to the SAP Concur Integration Setup screen and choose Ledger Posting -> Symbolic Accounts. There you can indicate your account mappings. In the General Change column, enter the symbolic account and in the Account column, select the real account.

The option you choose is valid for all accounts.

 

Expenses – Launch Settings

Choose a posting date and, if you want to prevent posting date and find it in a financial closing period, you can select the Recalculate option, in which case the system will automatically select the first day on which postings are again possible. Then select a financial document type that classifies accounting documents. Go to the next step by clicking Continue.

 

Expenses – Filter Definitions

If you want to connect to multiple systems with Concur, select a relevance filter below to restrict the import of accounting documents. Without a relevance filter, all entries will be considered for this system.

For expense reports, choose whether you want company and filter entries to be derived from Employee Fields or Concur Header Fields.

In this table, enter the corresponding criteria with which the filter can identify documents relevant to the posting – for example, if you selected the relevance filter Country, enter US and GB. Optionally, you can click Default Logical System, in which case the system ID will be added automatically.

If you are using travel advances in addition to expense reporting: The filter and company for travel advances always come from the employee fields. If you choose employee fields for expense reports, the same filtering criteria are applied to travel advances. However, if you determine header fields for expense reports, make sure who has also selected a relevance filter for travel advances.

Once you have completed this wizard, the traffic light on the SAP Concur Integration Setup screen (in the Journal Posting column) will turn green. Please note, however, that if you are using the Mapping Service and the client credentials you previously entered in the System Setup wizard have changed, or if your SAP system is not yet registered for the mapping service, the semaphore will change to yellow. In this case, run the System Setup wizard again and adjust the credentials.

 

Expenses – Account Definition

For the posting process, the SAP system needs the supplier and company account information. Concur provides the necessary company details in a custom field. Enter the custom field that contains the company. Company entries are derived from Concur Employee Custom Fields.

Company Code for Travel Advances: You can only choose a different company value for travel advances if, in the previous screen, you selected Header Fields for Expense Reports. Otherwise, the amount you selected for expense reporting is also applied to travel advances.

Vendor Determination: The information required for the vendor account is provided in Custom17 – one of the custom fields.

This can be:

  • the supplier account ID directly
  • the Personal Number and the Company
  • or the user ID (Employee Central) and the Company

Supplier Account ID and Personnel Number can be obtained from this financial system. User ID (Employee Central) is required for standard integration with SAP Success Factors Employee Central and can only be obtained with the composite employee API, ie it is not visible in the financial system. In the Employee Central system, you will find the Company under Job Info -> Company.

 

Expenses – Cost Object Mapping

Here you can assign Cost Object Type and Concur ID to SAP cost object types.

Only cost object types that you previously configured in the integration system setup are listed.

If you have combined different cost object categories into one list when setting up your cost object integration, you also need to indicate the cost object category in the table below. However, if all cost object categories are distributed over different lists, you only need to indicate the cost object ID here.

Custom field entries are derived from the Concur expense report allocation fields. If you are using multiple lists for your cost objects, make sure that the company code you indicate in the table below matches the cost center company. The company code of the other cost objects is determined directly from the cost object itself.

Note for customers not using the default export function:

If a certain cost object category is missing from the table below, run the corresponding wizard and make sure the export is set to manual. This allows you to associate missing cost object types without exporting them.

 

Invoice – launch settings

For your payment requests (invoices), select a posting date, a document type, a company code and, if necessary, set a relevance filter to restrict the import of accounting documents. The relevance filter entries are derived from the Concur custom fields in the payment request header. To prevent the posting date from being in a financial closing period, you can select the Recalculate option, in which case the system will automatically select the first day on which postings are again possible.

Select a relevance filter if you work with multiple financial systems connected to your Concur system. Then enter all the values ​​listed in the table below. For example, if you click the Country relevance filter, enter US, GB in the table.

 

Invoice – cost object mapping

Here you can assign cost object type and Concur ID to SAP cost object types.

Only cost object categories that you set up during integration setup are displayed.

If you have combined different cost object categories into one list when setting up your cost object integration, you also need to indicate the cost object category in the table below. However, if all cost object categories are distributed over different lists, you only need to indicate the cost object ID here.

Custom field entries are derived from the Concur payment order allocation fields. If you are using multiple lists for your cost objects, make sure that the company code you indicate in the table below matches the cost center company. The company code of the other cost objects is determined directly using the cost objects itself.

Note for customers not using the default export function: If a certain cost object category is missing from the table below, run the corresponding wizard and make sure the export is set to manual. This allows you to associate missing cost object types without exporting them.

 

Automatic import

If you want journals to be imported automatically, select the Automatic import option below. The job schedule is valid for all receiving systems. In the Batch User field, enter the user authorized for task processing.

Please note that the schedule is customer specific. Also, before scheduling an import, check for generic schedules using transaction SM37.

You can also assign a specific application server for the scheduled batch job:

  1. Execute transaction SM37 to open the Simple Task Selection screen.
  2. In the Task Name field, enter CTE* and as the Username enter *.
  3. In the Task Status section, select just Released and then click Run.

4.On the Task Overview screen, select the task and from the menu bar click Task -> Change.

  1. The Change Task screen opens. In the Execution target field, use the input help to select an application server.
  2. Save your entries.

You can always import objects manually with transaction CTE_POST_IMP – even if you have selected the Automatic export option.


 

Conclusion

Before thinking about configuring the import of accounting documents, we must analyze all the necessary requirements for this. Mainly how these documents will fit the customer’s business rules. Very common that BADI’s are implemented to follow the business rules. Have a nice work!

Assigned tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.