---
title: Configuring IPAC Bulk Files Without Budgetary Ledger or MIRO
description: Learn how to configure and customize the IPAC bulk file format in SAP for federal agencies without budgetary ledger or MIRO.
image: https://blog.sap-press.com/hubfs/Configuring%20IPAC%20Bulk%20Files%20Without%20Budgetary%20Ledger%20or%20MIRO.jpg
---

[![rheinwerk-sappress-logo-header-1](https://blog.sap-press.com/hubfs/rheinwerk-sappress-logo-header-1.svg)](https://blog.sap-press.com/) [Blog](https://blog.sap-press.com)

- Books 
    - Get an overview of our books and courses on every relevant SAP topic. 
          - [Programming](https://sap-press.com/programming/)
          - [Administration](https://sap-press.com/administration/)
          - [BI](https://sap-press.com/business-intelligence/)
          - [Finance](https://sap-press.com/finance-controlling/)
          - [Logistics](https://sap-press.com/logistics/)
          - [HR](https://sap-press.com/human-resources/)
          - [CRM & Sales](https://sap-press.com/marketing-sales/)
          - [HANA](https://sap-press.com/hana/)
          - [Introductions](https://sap-press.com/introductions/)
          - [E-Bites](https://sap-press.com/e-bites/)
          - [Certification Guides](https://www.sap-press.com/certification-guides/)
          - [Rheinwerk Courses](https://www.sap-press.com/online-courses/)
- Book Subscription 
    - Get unlimited access to all SAP PRESS books! 
          - [SAP PRESS Subscription](https://sap-press.com/subscriptions/)

[FICO](https://blog.sap-press.com/tag/fico)

# Configuring IPAC Bulk Files Without Budgetary Ledger or MIRO

![Nadia Zvarich](https://blog.sap-press.com/hubfs/IMG_1105.jpeg)  by [Nadia Zvarich](https://blog.sap-press.com/author/nadia-zvarich) on October 12, 2026

This article covers how to configure the standard IPAC bulk file format in SAP, what breaks when Budgetary Ledger is not active, and how to customize the format to fill the gaps.

 

It's aimed at SAP FI consultants and functional analysts at federal agencies who need to produce IPAC files without Budgetary Ledger or MIRO in place.

 

Consider the following business requirements.

 

You need to set up the standard IPAC bulk file for payments and collections in a system where Budgetary Ledger is not activated, and invoices are created with transaction FB60 rather than MIRO.

 

The file should be saved locally and uploaded to the IPAC portal manually.

 

To review the specification, your client needs to obtain the IPAC Bulk File Layout document:

- [Bulk File Formats | Bureau of the Fiscal Service](https://fiscal.treasury.gov/accounting/intra-governmental-payment-collection-ipac/bulk-file-format)
- [IPAC Bulk File Layouts](https://fiscal.treasury.gov/system/files/files/ipac/IPACBulkFileLayout.pdf)

For background on the GTAS (Governmentwide Treasury Account Symbol) fields used in the format, see the following:

- [GTAS Configuration | SAP Help Portal](https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/5866bce8a9694933b4ef1f50f7acd83f/bfc722b12e0041968374bcd34f39bfa6.html)
- [Governmentwide Treasury Account Symbol Adjusted Trial Balance System | Bureau of the Fiscal Service](https://fiscal.treasury.gov/accounting/government-wide-treasury-account-symbol-gtas)
- [TFX Glossary | TFX: Treasury Financial Experience](https://tfx.treasury.gov/glossary)

If you work for a government agency, you will most likely use an intragovernmental system to pay invoices: either G-invoicing or its predecessor, IPAC, which some agencies still use. In federal accounting, each transaction carries Treasury Account Symbol (TAS) values that identify both the payer and the payee side. On the accounts payable side, the payee's values are the Trading Partner (TP) TAS values, and your own agency, as the payer, has its own TAS values.

SAP inherits these TP TAS values automatically from purchase and sales order transactions through to payment transactions, but only when Budgetary Ledger is activated. A TAS is built from these components: sub-level prefix code, allocation transfer agency identifier, agency identifier, beginning and ending period of availability, availability type code, main account code, and sub-account code. Not all are populated on every transaction. The IPAC Bulk File Layout specification linked above gives the length, position, and validation rule for each.

 

SAP adds the business event type code (BETC) to that list. The receiver BETC must be valid for the transaction type and must form a valid pair with the receiver TAS.

Here is an example of TAS values populated on an invoice:

![TAS values populated on an invoice](https://blog.sap-press.com/hs-fs/hubfs/image-png-Sep-02-2026-12-39-58-7076-PM.png?width=975&height=578&name=image-png-Sep-02-2026-12-39-58-7076-PM.png)

 

If we check the BSEG table for this document on the G/L line (KOART = ”S”), you will see the following:

![BSEG table](https://blog.sap-press.com/hs-fs/hubfs/image-png-Sep-02-2026-12-40-10-2606-PM.png?width=975&height=383&name=image-png-Sep-02-2026-12-40-10-2606-PM.png)

The G/L line stores a key in BSEG that points to the TAS values in table FMFGUSKONTKEY.

 

The simplest way to think about the TAS fields is that they identify where funds go. A SWIFT payment relies on routing and account numbers to reach the right destination. TAS values play the same role inside intragovernmental payment systems like G-invoicing and IPAC.

Now let's discuss how to configure and customize IPAC bulk files.

 

## Standard Configuration Required

To prevent this error in the Payment Medium Workbench (PMW): “No agency location code/pmt office found for payment method supplement,” activate it at company code level in FBZP. Under the section All Company Codes, select the checkbox “Pyt Meth Suppl.”

Then you need to define the payment method supplement. Follow this menu path:

 

Transaction SPRO: Financial Accounting \> Accounts Receivable and Accounts Payable \> Business Transactions \> Outgoing Payments \> Automatic Outgoing Payments \> Payment Method/Bank Selection for Payment Program \> Define Payment Method Supplements.

 

From an IPAC configuration perspective, these are the required steps from that list to make IPAC work:

 

![Configuration steps](https://blog.sap-press.com/hs-fs/hubfs/image-png-Sep-02-2026-12-40-59-9472-PM.png?width=723&height=309&name=image-png-Sep-02-2026-12-40-59-9472-PM.png)

 

Within the Maintain Payment/Disbursing Offices section, you will need to assign the code of your agency’s payment office.

 

Then, within Maintain Agency Location Codes, you will need to maintain all possible ALCs of other agencies with which you have transactions.

The agency with the checkbox in the “Int ALC” column is your agency.

Choose the ALC and double-click Assign. of Business Act. Type and Reporter Categor.:

 

![Click Assign. of Business Act. Type and Reporter Category](https://blog.sap-press.com/hs-fs/hubfs/image-png-Sep-02-2026-12-41-16-7180-PM.png?width=723&height=335&name=image-png-Sep-02-2026-12-41-16-7180-PM.png)

Check the list of agencies periodically, because the US Treasury may introduce new ALCs.

 

Inside Assign ALC and Payment Office to Payment Method Supplement, you need to enter the payment method supplement, which you created before, and then assign the agency location code and payment office for your own agency.

If your agency has several disbursement or payment offices, you will need several payment method supplements. In this case, we have only one.

 

The payment method supplement can be defaulted on the vendor and customer master records that will be paid through IPAC:

 

![Defaulting payment methods](https://blog.sap-press.com/hs-fs/hubfs/image-png-Sep-02-2026-12-41-39-1587-PM.png?width=723&height=333&name=image-png-Sep-02-2026-12-41-39-1587-PM.png)

Because Trading Partner TAS values can differ from invoice to invoice for the same vendor or customer, you may need to default the single payment indicator on those master records if your configuration groups several invoices into one payment document (if you do not have a check box called “Separate Payment for Each Ref.” in FBZP in the Paying Company Codes section).

If the payment method is assigned at the invoice level instead, you can use the check box called “Pmnt Methods in Company Code” for your IPAC PM.

![Item grouping](https://blog.sap-press.com/hs-fs/hubfs/image-png-Sep-02-2026-12-41-57-9361-PM.png?width=550&height=114&name=image-png-Sep-02-2026-12-41-57-9361-PM.png)

 

## Format to Use

In OBPM1, assign the function modules to the event 30 for format IPAC\_FG\_UPLD: FI\_PAYMEDIUM\_GWA\_IPAC\_FG\_30.

 

See [SAP Note 3597118](https://me.sap.com/notes/3597118/E) for why this function module has to be assigned in OBPM1. Without it, the BIPAC line appears at the end of the file rather than at the beginning.

 

The outgoing payment method for payments has to have the format supplement PAYM and the incoming payment method for collections COLL.

 

The outgoing payment method looks like this:

 

![Outgoing payment method](https://blog.sap-press.com/hs-fs/hubfs/image-png-Sep-02-2026-12-42-37-9154-PM.png?width=723&height=228&name=image-png-Sep-02-2026-12-42-37-9154-PM.png)

 

The configuration for the incoming payment method is identical except that the format supplement is COLL rather than PAYM.

 

If the client processes adjustments separately, one more payment method has to be configured with format supplement ADJUST. The format supplement field offers three values in total: PAYM, COLL, and ADJUST.

 

In our case, the client did not use a separate payment method. Adjustments were handled with payment method I or J and the appropriate BETC code. DISBAJ and COLLAJ are examples of BETCs that indicate an adjustment.

 

In OBPM4, you need to assign your created variant for SAPFPAYM.

![Assign created account](https://blog.sap-press.com/hs-fs/hubfs/image-png-Sep-02-2026-12-42-56-8360-PM.png?width=723&height=553&name=image-png-Sep-02-2026-12-42-56-8360-PM.png)

 

## Customization of the IPAC Format

Because we did not activate Budgetary Ledger and did not use transaction MIRO, the standard logic left gaps. TP TAS values did not appear in the file output at all. The IPAC code does not read table ACDOCA, so even when the standard TP TAS and agency TAS fields are populated there, the format ignores them. It reads from BSEG instead, or from the purchase order when Budgetary Ledger fields are populated in BSEG. Contract number and purchase order were missing as well, since those are populated through MIRO.

 

SAP confirmed the older function modules don't meet the current IPAC requirements and directed customers to the replacements listed in [SAP Note 3597118](https://me.sap.com/notes/3597118/E).

 

Assigning those modules in OBPM1 fixes the file structure.

 

The new modules have gaps of their own. The SGL record (S-record) is not populated, which is acceptable, since the S-record is optional and the IPAC portal does not return an error when it is missing. BETC is treated as optional, which was not correct for our requirements, so we changed the logic to populate it in every case. Contact details are not populated either, because IPAC does not require them, though our requirements did.

 

Everything beyond the file structure, meaning TAS values, BETC, contract number, and contact details, has to be handled in custom function modules assigned through OBPM3 and copied from the standard.

 

In OBPM3, assign your custom function module, copied from FI\_PAYMEDIUM\_GWA\_IPAC\_FG\_30, to event 31.

 

In that module, you can fill in the missing required fields. Note one difference from the ACH format: the ACH module produces output for a single payment, so no loop is needed. The IPAC module receives all payments in the output table at once, which means you have to identify each detail record (D record) individually in order to modify it for each payment.

 

Be aware that some fields the IPAC specification marks as optional, such as description and accounting classification code, are still required by certain agencies for certain TAS value combinations. If you leave them empty, your file will fail in the IPAC portal.

 

The description field is one example. The specification allows up to 320 alphanumeric characters and advises against special characters such as double quotes or question marks. Accounting classification code is another. Both are marked optional, but agencies will reject files without them for certain TAS combinations.

 

It is safer to populate them for all agencies.

 

If you need to use format IPAC\_FG\_ZERO, reconfigure event 30 to function module FI\_PAYMEDIUM\_GWA\_IPAC\_FG\_0\_30 as well, as described in the [same SAP Note.](https://me.sap.com/notes/3597118/E)<https://me.sap.com/notes/3597118/E>

 

Here's an example of a payment file:

 

![Example payment file](https://blog.sap-press.com/hs-fs/hubfs/image-png-Sep-02-2026-12-44-21-0302-PM.png?width=975&height=161&name=image-png-Sep-02-2026-12-44-21-0302-PM.png)

Here's an example of a collection file:

![Example collection file](https://blog.sap-press.com/hs-fs/hubfs/image-png-Sep-02-2026-12-44-36-0831-PM.png?width=975&height=213&name=image-png-Sep-02-2026-12-44-36-0831-PM.png)

 

The H record, highlighted in yellow, is the header record. It contains the ALC and disbursement/payment office for your agency and for the agency you are paying or collecting from. The ALC is assigned on the vendor or customer master record.

 

The D record, highlighted in green, is the detail record.

 

In the collection file, blue marks the TP TAS values and pink marks the TP BETC. Orange marks your own agency's TAS values, and purple marks your agency's BETC. The BETC identifies what kind of collection or payment your agency is initiating. In a payment file, your agency's BETC will be a disbursement code such as DISB or DISNGF. In the collection file, it will be COLL.

 

## Possible Errors

There are a number of possible errors you may run into.

 

First, the combination of TAS values is incorrect. The IPAC portal holds all valid combinations of agency ID, main account, and subaccount, and validates your file against them on submission.

 

`Columns 921-947: Receiver TAS-BETC pair is invalid`

 

These values come from form 7600B. Make sure the same combination reaches the government fields on the SAP invoice, shown earlier.

 

![](https://blog.sap-press.com/hs-fs/hubfs/image-png-Sep-02-2026-12-45-52-7961-PM.png?width=975&height=578&name=image-png-Sep-02-2026-12-45-52-7961-PM.png)

 

Second, the BETC may be incorrect. For example, a disbursement BETC was entered on the collection side for both the TP TAS and your agency TAS values.

 

Third, some TAS value combinations require a description and accounting classification code even within the same ALC, so populate them in all cases.

 

`Columns 146-465: Description is required`

 

Lastly, make sure the payment method supplement is populated on the vendor master and inherited to invoice level. Otherwise, the ALC and payment/distribution code will be missing from the header record, and the file will fail on submission. You can add custom checks to the payment program (F110) through a BTE event 1820 enhancement, but that is a topic for another post.

 

The first two errors are both caused by values that should never have been entered in the first place. To restrict TAS and BETC entries to valid values, configure these tables with the allowed values: Public Sector Management \> Functions for US Federal Government \> US Federal Government Fields \> Maintain US Federal Government Field Values.

![Maintain fields screen](https://blog.sap-press.com/hs-fs/hubfs/image-png-Sep-02-2026-12-46-57-5898-PM.png?width=975&height=473&name=image-png-Sep-02-2026-12-46-57-5898-PM.png)

 

For example, select FMFG\_TP\_BETC and maintain the BETC values your agency is permitted to use.

 

The second reason this error might appear is an invalid combination of agency ID, main account, and subaccount, meaning a combination that doesn't exist in IPAC. Each value on its own may be legitimate, but IPAC doesn't recognize them together. This is why the values should be pulled directly from Form 7600B. Depending on how your team handles invoice processing, there may also be room for a user typo at that step.

## Conclusion

Getting the file structure right requires consultant involvement in the IPAC configuration. Customization is likely to be necessary as well, because SAP does not populate fields the IPAC bulk file specification leaves unmarked as required. TP TAS and BETC fall into that category, and as we found, so do additional fields for certain TAS combinations.

 

[Learn more about finance in SAP on this page](https://learning.sap-press.com/sap-s4hana-finance).

 

This post was originally published 10/2026.

## Recommendation

[![Funds Management for the Public Sector with SAP](https://blog.sap-press.com/hs-fs/hubfs/social-suggested-images/2345-Mar-17-2023-12-38-37-5883-PM.jpg?width=170&name=2345-Mar-17-2023-12-38-37-5883-PM.jpg)](https://www.sap-press.com/funds-management-for-the-public-sector-with-sap_5617/?utm_source=sappressblog&utm_medium=referral&utm_campaign=Blogs&utm_term=guest_zvarich2&utm_content=2345)

**Funds Management for the Public Sector with SAP**

At last, your all-in-one resource for funds management is here! Start with an overview of the funds management process and the SAP S/4HANA user interface. Next, customize all aspects of your budget, from budgetary management to workflows to financial close. Finally, walk through step-by-step instructions for user transactions, including budgeting, posting, and closing. Get everything you need to keep your costs and expenses on track!

[Learn More](https://www.sap-press.com/funds-management-for-the-public-sector-with-sap_5617/?utm_source=sappressblog&utm_medium=referral&utm_campaign=Blogs&utm_term=guest_zvarich2&utm_content=2345)

![Nadia Zvarich](https://blog.sap-press.com/hubfs/IMG_1105.jpeg)

**by [Nadia Zvarich](https://blog.sap-press.com/author/nadia-zvarich)**

Nadia Zvarich is an SAP payroll and accounts payable architect/design solution consultant with strong expertise and deep knowledge in those areas. She has a bachelor’s degree in computer science and applied mathematics, and a master’s degree in accounting. She finds solutions where it seems impossible to resolve and is eager to share it with SAP practitioners. To know more about Nadia, please refer to her profile at LinkedIn: https://www.linkedin.com/in/nadia-zvarich-aa6885199/

[FICO](https://blog.sap-press.com/tag/fico) [Featured](https://blog.sap-press.com/tag/featured)

[![Share on facebook](https://7528309.fs1.hubspotusercontent-na1.net/hub/7528309/hubfs/raw_assets/public/mV0_d-web-default-modules_hubspot/img/facebook-color.png?width=24&name=facebook-color.png)](https://www.facebook.com/share.php?u=https%3A%2F%2Fblog.sap-press.com%2Fconfiguring-ipac-bulk-files-without-budgetary-ledger-or-miro%3Futm_medium%3Dsocial%26utm_source%3Dfacebook) [![Share on linkedin](https://7528302.fs1.hubspotusercontent-na1.net/hub/7528302/hubfs/raw_assets/public/mV0_d-web-default-modules_hubspot/img/linkedin-color.png?width=24&name=linkedin-color.png)](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Fblog.sap-press.com%2Fconfiguring-ipac-bulk-files-without-budgetary-ledger-or-miro%3Futm_medium%3Dsocial%26utm_source%3Dlinkedin) [![Share on twitter](https://7528304.fs1.hubspotusercontent-na1.net/hub/7528304/hubfs/raw_assets/public/mV0_d-web-default-modules_hubspot/img/twitter-color.png?width=24&name=twitter-color.png)](https://twitter.com/intent/tweet?original_referer=https%3A%2F%2Fblog.sap-press.com%2Fconfiguring-ipac-bulk-files-without-budgetary-ledger-or-miro%3Futm_medium%3Dsocial%26utm_source%3Dtwitter&url=https%3A%2F%2Fblog.sap-press.com%2Fconfiguring-ipac-bulk-files-without-budgetary-ledger-or-miro%3Futm_medium%3Dsocial%26utm_source%3Dtwitter&source=tweetbutton&text=) [![Share on email](https://7528311.fs1.hubspotusercontent-na1.net/hub/7528311/hubfs/raw_assets/public/mV0_d-web-default-modules_hubspot/img/email-color.png?width=24&name=email-color.png)](mailto:?subject=Check+out+https%3A%2F%2Fblog.sap-press.com%2Fconfiguring-ipac-bulk-files-without-budgetary-ledger-or-miro%3Futm_medium%3Dsocial%26utm_source%3Demail&body=Check+out+https%3A%2F%2Fblog.sap-press.com%2Fconfiguring-ipac-bulk-files-without-budgetary-ledger-or-miro%3Futm_medium%3Dsocial%26utm_source%3Demail)

### Comments

### Latest Blog Posts

[![How to Customize NACHA (ACH) Formats in SAP: Possible Edge Cases and How to Fix Them](https://blog.sap-press.com/hs-fs/hubfs/How%20to%20Customize%20NACHA%20(ACH)%20Formats%20in%20SAP_%20Possible%20Edge%20Cases%20and%20How%20to%20Fix%20Them.jpg?height=600&name=How%20to%20Customize%20NACHA%20(ACH)%20Formats%20in%20SAP_%20Possible%20Edge%20Cases%20and%20How%20to%20Fix%20Them.jpg)](https://blog.sap-press.com/how-to-customize-nacha-ach-formats-in-sap)

[FICO](https://blog.sap-press.com/tag/fico)

## [How to Customize NACHA (ACH) Formats in SAP: Possible Edge Cases and How to Fix Them](https://blog.sap-press.com/how-to-customize-nacha-ach-formats-in-sap)

[Read More](https://blog.sap-press.com/how-to-customize-nacha-ach-formats-in-sap)

[![The Line-Item Budgeting Approach in Funds Management with SAP](https://blog.sap-press.com/hs-fs/hubfs/The%20Line-Item%20Budgeting%20Approach%20in%20Funds%20Management%20with%20SAP.png?height=600&name=The%20Line-Item%20Budgeting%20Approach%20in%20Funds%20Management%20with%20SAP.png)](https://blog.sap-press.com/the-line-item-budgeting-approach-in-funds-management-with-sap)

[FICO](https://blog.sap-press.com/tag/fico)

## [The Line-Item Budgeting Approach in Funds Management with SAP](https://blog.sap-press.com/the-line-item-budgeting-approach-in-funds-management-with-sap)

[Read More](https://blog.sap-press.com/the-line-item-budgeting-approach-in-funds-management-with-sap)

**Subscribe to our blog!**Get notified about future blog updates.

- <https://www.facebook.com/sappress>
- <https://twitter.com/sappress>
- <https://linkedin.com/company/sap-press>
- <https://www.instagram.com/sap_press/>
- <https://blog.sap-press.com/rss.xml>

### The official SAP PRESS Blog

As the world’s leading SAP publisher, SAP PRESS’ goal is to create resources that will help you accelerate your SAP journey. The SAP PRESS Blog is designed to provide helpful, actionable information on a variety of SAP topics, from SAP ERP to SAP S/4HANA. Explore ABAP, FICO, SAP HANA, and more!

### SAP Blog Topics

- [All Topics](https://blog.sap-press.com)
- [Logistics](https://blog.sap-press.com/tag/logistics)
- [Programming](https://blog.sap-press.com/tag/programming)
- [FICO](https://blog.sap-press.com/tag/fico)
- [Administration](https://blog.sap-press.com/tag/administration)
- [Featured](https://blog.sap-press.com/tag/featured)
- [Business Intelligence](https://blog.sap-press.com/tag/business-intelligence)
- [What Is?](https://blog.sap-press.com/tag/what-is)
- [CRM & Sales](https://blog.sap-press.com/tag/crm-sales)
- [Human Resources](https://blog.sap-press.com/tag/human-resources)
- [Video](https://blog.sap-press.com/tag/video)

### Blog curated by

[![Rheinwerk Publishing & SAP PRESS Logo](https://blog.sap-press.com/hubfs/rheinwerk-sappress-logo-header-1.svg)](https://sap-press.com) [Visit the SAP PRESS Store](https://sap-press.com)

### About

- [Home](https://sap-press.com/)
- [About Us](https://sap-press.com/the-publisher/)
- [Contact](mailto:info@rheinwerk-publishing.com)
- [Legal Notes](https://sap-press.com/legal-notes/)
- [Privacy Policy](https://sap-press.com/privacy/)
- [Terms of Use](https://sap-press.com/terms/)
- [Guest Posting](https://blog.sap-press.com/guest-posting)

© 2026 Rheinwerk Publishing, Inc. | Change Privacy Options

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Nadia Zvarich",
    "url" : "https://blog.sap-press.com/author/nadia-zvarich"
  },
  "dateModified" : "2026-10-12T13:00:01.376Z",
  "datePublished" : "2026-10-12T13:00:01.000Z",
  "headline" : "Configuring IPAC Bulk Files Without Budgetary Ledger or MIRO",
  "image" : [ "https://blog.sap-press.com/hubfs/Configuring%20IPAC%20Bulk%20Files%20Without%20Budgetary%20Ledger%20or%20MIRO.jpg" ],
  "mainEntityOfPage" : {
    "@id" : "https://blog.sap-press.com/configuring-ipac-bulk-files-without-budgetary-ledger-or-miro",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://blog.sap-press.com/hubfs/Logo-1.jpg"
    },
    "name" : "Rheinwerk Publishing, Inc."
  }
}
```