Skip to Content
Author's profile photo Bohdan Petrushchak

Default posting rules for bank statement

Hello SAPers!

If you’ve ever configured or provided post go-live support for topics related to electronic bank statement, then you most probably encountered error message saying: “Following entries are missing in table T028G”. This a standard error message that is triggered during upload of electronic bank statement when external business transaction key (BTC) from bank statement has not been mapped against bank posting rule (check assignment in t-code OT83 under tab “Assign External Transaction Types to Posting Rules”).

As you can see from screenshot above, one of the operations in bank statements was provided with business transaction code 051, which is not maintained. This error results in termination of bank statement upload i.e. you’re not able to upload it and post documents.

This is quite trivial error, which can be fixed quite easily (from technical perspective). However, if you’re working in big international company with support functions outsourced to third-party providers, you might expect long lead times until the issue is fixed (sometimes it can take up to 3 days just to get initial response).

Previously, the only way to fix this issue was to add missing key into customizing. One of the newer features of SAP allows simple workaround – configuration of so called default posting rules for miscellaneous transactions. The logic behind this feature is as follows:

  • allocate as many external business transaction codes to posting rules as you can;
  • add two additional entries with fixed key “UNALLOCATED” and assign them to posting rules for so called miscellaneous operations i.e. operations that do not have fixed account determination for accounts corresponding with bank accounts; relevant accounts should be entered by user directly during the post-processing of bank statement in FEBAN;

  • after uploading of electronic bank statement, you’ll still see the message “Following entries are missing in table T028G”, however the upload won’t be terminated anymore and you’ll be able to process bank statement;
  • operations with unassigned business transaction codes will be displayed with default posting rules in FEBAN, however once you have bank statement in FEBAN, you can change posting rule manually (if you have proper authorization:) and complete the posting.

To sum up: the main of advantage behind configuration of default posting rules for unallocated business operations is that missing settings won’t slow down the processing of bank statements and can be handled on a business as usual mode with low priority.

As mentioned before, this is quite new feature, however I’m nor sure what is a minimal EHP-level. It is available for EHP-8 for sure and most probably for EHP6 / 7 as well.

Just in case, default posting rules for miscellaneous operations can be configured as follows (see screenshot below). Setting are provided for both EBS with one and two posting areas.

I hope this information will be useful for some of you:) Please also check out my other posts about handling of bank-statement-related issues:


Bohdan Petrushchak




Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Jelena Perfiljeva
      Jelena Perfiljeva

      Thanks for sharing!Very nicely explained.

      You've mentioned it's one of the new features but the specific availability is not clear from the post. Have you tried to find an SAP note that implements it?

      Author's profile photo Bohdan Petrushchak
      Bohdan Petrushchak
      Blog Post Author

      Jelena Perfiljeva thanks for raising this question! I checked and to be honest I'm a bit confused. The oldest OSS note relevant to this topic is  (i.e. 301553 - Electr. acct statemt: unknown busin. transactn code) mentions that this option exists "as of release 4.5A", but I didn't found any earlier notes that would shed any light upon this topic. Then, there are also two OSS-notes that were issued later (i.e. 397778 - Account statement: log for business trans code UNALLOCATED (for Multicash) and 1124923 - Account statement: log for GVC UNALLOCATED (for MT940)), but none of them lists any specific prerequisite notes. So it seems this is in fact quite old option, that until recently was hidden in plain sight of OSS-portal:)

      Author's profile photo Bastiaan Jansen
      Bastiaan Jansen

      It has been available for a really long time. However I guess it's not that well known.

      Author's profile photo Sunil K Roge
      Sunil K Roge

      Posting rule definition with single account mapping is not possible. It throws error on attempt to save. Any business function need to be activated for that? We are on ECC 6.6 SP20.




      Author's profile photo James Xu
      James Xu

      Hi Experts,


      Do you know which SAP notes can open T028G table can be maintain directly in PRD ? previous we know that but forget the notes number.




      Author's profile photo Bohdan Petrushchak
      Bohdan Petrushchak
      Blog Post Author

      Hi James Xu,

      In my opinion that's not a good practice to maintain T028G directly in production, especially once this workaround became available. But if that's the task you should do, please check out the following link. It might be helpful.



      Author's profile photo Sekar Paramasivam
      Sekar Paramasivam


      Configured UNALLOCATED and assigned a generic posting rule IN BAI  format ( USA)  the UNALLOCATED is not working as you mentioned. Still it says that the Ext transaction number is missing and is not directed to post as assigned under unallocated external transaction. This is bit urgent and appreciate  your guidance

      Author's profile photo Bohdan Petrushchak
      Bohdan Petrushchak
      Blog Post Author

      Hi Sekar Paramasivam ,

      From what I can see this functionality should work just fine with BAI-format. Just in case, please refer to OSS-notes 2835665 - Wrong posting rule determination - BAI bank statement format. It has useful recommendations on posting rules derivation and clearly mentions that UNALLOCATED key should work. I cannot help you more than that. If this is an urgent issue, reach out to fellow ABAP developer and ask him to troubleshoot the upload of bank statement in debug mode.