SAP expert series, part 3
SAP Funds Management and US Federal Accounting in Depth
How SAP Public Sector Management records budget authority, checks funds, tracks commitments through outlay, derives USSGL budgetary accounts, closes the year, and supports Treasury reporting, with the DoD IG findings that show where it breaks.
Numbered tables
2 diagrams1. Why a commercial ledger is not enough
A commercial general ledger answers what the entity owns, owes, earned, and spent. Federal accounting adds a second question for every dollar: what legal authority allowed it, and what stage of use has that authority reached. SAP answers the second question in Funds Management and turns the answer into USSGL budgetary accounts through the US Federal extension.
| View | Question | SAP component | USSGL accounts | Statement |
|---|---|---|---|---|
| Proprietary | What happened to assets, liabilities, net position, revenue, and expense | FI General Ledger with subledgers | 1000 to 3000 and 5000 to 7000 | Balance Sheet, Statement of Net Cost, Statement of Changes in Net Position |
| Budgetary | What happened to budget authority | Funds Management, with the budgetary ledger writing to FI | 4000 | Statement of Budgetary Resources, SF 133 |
| Memorandum | Statistical tracking | FI statistical postings | 8000 | Supporting schedules |
2. Funds Management master data
| Element | Field | Master table | Meaning | What GFEBS public procedures show |
|---|---|---|---|---|
| FM area | FIKRS | FM01 | Scope of budget control | Company code and business area both appear as ARMY |
| Fund | GEBER | FMFINCODE | A source of funding with its own legal restrictions and validity | Examples 202010D12, 202011D12, and 202010A12. Reading the examples, the value holds Treasury main account 2020, a two-digit qualifier, a funding-type letter, and a two-digit fiscal year. That structure is inferred from the examples and is not stated in the source. |
| Funds center | FISTL | FMFCTR, hierarchy FMHISV | An organization that receives and manages budget | Examples A76DD and A2ABM |
| Commitment item | FIPOS, FIPEX | FMCI | What the money is spent on or where revenue comes from | Four-character values such as 21T0 for travel and 22NL. Derived from the element of resource. The G/L account appears as 6100.21T0. |
| Functional area | FKBER | TFKB | Purpose or program | Examples 131096QLOG and 121018TTDY. Built from the Army management structure code and the management decision package. |
| Funded program | MEASURE | FMMEASURE | A lower-level program or project that is funded separately | Set equal to the WBS element for projects. ARMY is the default holding value. |
| Budget period | BUDGET_PD | FMBUDGETPD | Period of availability for multi-year funds | Not shown in the public material |
| Grant | GRANT_NBR | GMGR | Sponsor-funded agreement | Not shown in the public material |
GFEBS examples come from the U.S. Army Financial Management School desktop procedures dated 2013. Values and structures can have changed since.
- A commitment item has a financial transaction and a commitment item category. Financial transaction 30 with category 3 is an expenditure. Category 2 is revenue. Financial transaction 90 marks cash and bank accounts, and 60 and 80 mark receivables, payables, and clearing accounts that do not consume budget.
- A fund has a validity period and, in the federal extension, expiration and cancellation dates. Posting to an expired fund is limited to adjustments. Posting to a cancelled fund is blocked.
- Funds centers form one hierarchy per variant. Budget is distributed down the hierarchy and availability can be checked at any level.
- Cost objects can carry a fixed FM assignment in
FMZUOB, so that a cost center or WBS element always posts to the same funds center and fund.
Derivation
Users rarely key every FM field. The derivation strategy in FMDERIVE fills them. A strategy is an ordered list of steps: derivation rules, which are lookup tables, table lookups, assignments, function calls, and enhancements. FMDERIVATIONANALYSIS replays a posting and shows which step set each field. When an obligation lands on the wrong fund or commitment item, the derivation trace is the first place to look.
3. How a posting updates Funds Management
| Value type | Name | Created by | Table | Budgetary meaning |
|---|---|---|---|---|
| 50 | Purchase requisition | ME51N, requisition interfaces | FMIOI | Commitment |
| 51 | Purchase order | ME21N, contract interfaces | FMIOI | Obligation, undelivered order |
| 52 | Business trip commitment | Travel request | FMIOI | Obligation |
| 80 | Funds block | FMW1 | FMIOI | Administrative hold |
| 81 | Funds reservation | FMX1 | FMIOI | Reservation or commitment |
| 82 | Funds precommitment | FMY1 | FMIOI | Commitment |
| 65 | Funds commitment | FMZ1 | FMIOI | Obligation without a purchase order |
| 83 | Forecast of revenue | FMV1 | FMIOI | Anticipated collection |
| 54 | Invoice | MIRO, FB60, goods receipt depending on profile | FMIFIIT | Accrued expenditure, delivered order unpaid |
| 57 | Payment | Payment document, payment conversion FMF0 | FMIFIIT | Outlay |
| 58 / 61 | Down payment request / down payment | F-47 / F-48 | FMIFIIT | Advance |
| 66 | Transfer posting | FB50 and reclassifications | FMIFIIT | Adjustment between FM addresses |
| 95 | Secondary cost posting | CO allocations when CO integration is active | FMICOIT | Internal cost movement |
- The update profile on the FM area decides two things for each value type: whether it consumes payment budget, commitment budget, or both, and which date sets the budget year. A profile can use the posting date, the delivery date, or the due date.
- The commitment chain keeps consumption from double counting. A purchase order created from a requisition reduces the requisition in
FMIOIand adds itself. An invoice reduces the order. Each reduction is its own line with amount type0200. - When an invoice is paid, payment conversion changes the invoice line from value type 54 to 57. With online payment update it happens at payment posting. Otherwise the program behind
FMF0does it in a batch. - Statistical lines, flagged in
STATS, appear in reports and do not consume budget.
4. Budget Control System
Budget types, statuses, and the exact account pairs are configuration. The DoD USSGL Transaction Library defines the required entries.
| Concept | What it is | Where stored or set |
|---|---|---|
| Budget category | Payment budget (9F) or commitment budget (9G) | FM area settings |
| Budget type | A classification of budget, such as appropriation, apportionment, allotment, reimbursable authority, continuing resolution | Customizing. Federal attributes of each type in FMFG_BUTYPE. |
| Budgeting process | What the entry does: enter, supplement, return, transfer, with send and receive sides, carry over | Field on the entry document line |
| Entry document | The record of one budget action with header, lines, and optional workflow | FMBH, FMBL. Entered in FMBB. |
| Document type | Classifies entry documents and sets number range and authorization | Customizing. GFEBS procedures show type ALLT for allotment. |
| Version | Budget versions allow a working version and the version of record, version 000 | Field on totals and documents |
| Budget address | The combination of fund, funds center, commitment item, functional area, funded program, and grant that holds budget | FMBDT |
| Posting address | The combination a document posts to. It is mapped to a budget address by a derivation. | Budget structure and derivation |
| Availability control ledger | Totals of consumable budget and consumed amounts by control address. 9H for payment budget, 9I for commitment budget. | FMAVCT |
| Tolerance profile | Thresholds that issue a warning, an error, or a notification, by activity group | Customizing |
| Status | Preposted, posted, and reversed entry documents. Budget can be held until released. | Entry document header |
- Availability control reads
FMAVCT, not the line items. If the ledger is out of step after a configuration change or a failed update,FMAVCREINITrebuilds it. FMAVCR01shows consumable budget, consumed amount, and available amount by control object for a year. It is the system view of status of funds.- The GFEBS role map shows budget distribution in
FMBBtogether with custom distribution and threshold transactions, and a year-end certification step. - DoD IG reported that GFEBS became the Army General Fund system of record for fund distribution in fiscal year 2013, and that 22 appropriations totaling $176.5 billion were not recorded in it on time that year.
5. Earmarked funds
Earmarked funds documents commit or obligate budget without a purchasing document. They are the SAP record behind miscellaneous obligations, travel orders, training, and transportation charges.
| Category | Create | Value type | Use | GFEBS document types in public procedures |
|---|---|---|---|---|
| Funds block | FMW1 | 80 | Hold budget so it cannot be used | Not shown |
| Funds reservation | FMX1 | 81 | Reserve budget for a purpose not yet defined in detail | Not shown |
| Funds precommitment | FMY1 | 82 | Commit budget for a planned requirement | M1, labeled FCM commitment |
| Funds commitment | FMZ1 | 65 | Obligate budget when there is a legal liability and no purchase order | F9 miscellaneous obligation, F1 travel obligation paid through the Integrated Automated Travel System, F6 PowerTrack transportation obligation |
| Forecast of revenue | FMV1 | 83 | Record expected revenue | Not shown |
- Header
KBLK, itemsKBLP, consumption historyKBLE. Each item carries its own fund, funds center, commitment item, G/L account, and cost object. - An invoice entered in
FB60references the earmarked funds number and item. The reference is stored on the invoice line inBSEG-KBLNRandKBLPOS, and the consumption appears inKBLE. - The completion indicator on the item closes the remaining amount. Setting it releases unliquidated budget, which is a deobligation.
- Because there is no contract or receiving report behind a funds commitment, auditors test these documents for a valid obligating event and for timely liquidation. They are the SAP equivalent of the miscellaneous obligation document.
6. The budgetary ledger
The budgetary ledger is the part of the US Federal extension that writes USSGL 4000-series lines. It listens to FM updates and derives a debit and credit account pair from the event, the value type, the budget type, and fund attributes.
| Object | Purpose |
|---|---|
FMFGBLAREA, FMFGBLAREAT, FMFGBLAREAFLD | Budgetary ledger areas: the kinds of event the ledger posts for, and the fields each uses |
FMFGBLAREADOCTY | FI document type used for budgetary ledger postings in each area |
FMFG_BUTYPE | Budgetary ledger attributes of each budget type |
FMFGBLDRVAREAEAA | Derivation rule that sets expended appropriations for actuals |
FMSGLCLASS | Classification of SGL accounts |
FMFG_BL_YRCL, FMFGYECLAA | Year-end closing rules for the budgetary ledger and pre-closing of anticipated accounts |
FMFG_ABP, FMFG_ABP_HDR_DEF, FMABP_AREAS | Automatic budget postings, for example budget created automatically from reimbursable orders or collections |
FMFONDS, FMFONDST | Assignment of a cancelled fund to a current fund, used to pay old obligations from current authority |
Object names and descriptions come from a public listing of the SAP PSM-FG component tables.
| Event | Budgetary entry | Proprietary entry in the same or a linked document |
|---|---|---|
| Appropriation enacted | Dr 4119 Cr 4450 | Dr 1010 Cr 3101 |
| Apportionment | Dr 4450 Cr 4510 | None |
| Allotment | Dr 4510 Cr 4610 | None |
| Commitment | Dr 4610 Cr 4700 | None |
| Obligation | Dr 4700 Cr 4801 | None |
| Goods or services received | Dr 4801 Cr 4901 | Dr 6100 or asset Cr 2110. Dr 3107 Cr 5700. |
| Payment | Dr 4901 Cr 4902 | Dr 2110 Cr 1010 |
| Advance paid | Dr 4801 Cr 4802 | Dr 1410 Cr 1010 |
| Reimbursable order accepted, without advance | Dr 4221 Cr 4210 | None |
| Reimbursable earned and billed | Dr 4251 Cr 4221 | Dr 1310 Cr 5200 |
| Reimbursable collected | Dr 4252 Cr 4251 | Dr 1010 Cr 1310 |
| Downward adjustment of a prior-year unpaid obligation | Dr 4801 Cr 4871 | None |
| Upward adjustment of a prior-year unpaid obligation | Dr 4881 Cr 4801 | None |
| Rescission of new authority | Dr 4450 Cr 4392 | Dr 3106 Cr 1010 where funds are returned |
| Temporary reduction under a continuing resolution | Dr 4450 Cr 4395 | None |
Account pairs follow the USSGL as cited in DoD IG reports on GFEBS and in the Treasury Financial Manual. The DoD USSGL Transaction Library is the authoritative list, by DoD Transaction Code.
7. Federal reporting ledgers and Treasury attributes
- The federal extension keeps special ledgers that hold balances with reporting attributes. A public table listing ties ledger 95 to totals table
FMUSFGT, ledger 96 toFMUSFGFACTS1T, and ledger 97 toFMUSFGFACTS2T. The attribute keys are inFMFGKEY,FMFGKEY96, andFMFGKEY97. - The names refer to FACTS I and FACTS II, the Treasury systems that GTAS replaced. The attribute concept is the same: each balance carries values such as federal or non-federal, trading partner, apportionment category, and authority type.
- DoD IG described the same design in GFEBS: the standard general ledger did not meet federal reporting needs, Special Ledger 95 was built for Treasury reporting, and a custom Z1 ledger was added in April 2010 to carry the DoD reporting attributes.
- Attributes are derived when the document posts. If a derivation is missing or wrong, the balance carries a blank or invalid attribute, which fails a GTAS validation or a DDRS edit.
- DoD IG tested 20 required attributes in GFEBS. Eleven were inconsistent in Special Ledger 95 and eight in the Z1 ledger, including trading partner, custodial indicator, and prior-year adjustment code.
| Function | What it supports | Objects named in the component |
|---|---|---|
| Treasury account symbol structure | Application of funds groups funds into the Treasury account they belong to | Application of funds master, FM1081_FUND_ROW |
| Fiscal station and Agency Location Code | Identifies the accounting station and the disbursing or reporting office | FMFGT_FSN, FMFGT_ALC_GWA |
| Governmentwide accounting reporter rules | Whether an office reports classification at the time of the transaction | FMUSFG_GWA_ACTIO, FMUSFG_GWA_ELIGI, FMUSFG_GWA_RCVAL |
| Treasury subclass | Subclass codes by document type, account, and fund | FMUSFG_TS, FMUSFG_TSA |
| IPAC | Outgoing IPAC files, incoming IPAC transactions, automatic document creation | FMFGT_IPACED, FMFGT_IPAC_FILE, FMFGT_IPAC_STATS, FMFGT_IPAC_ACCT, transaction FMFG_IPAC |
| SF 1081 | Voucher and schedule of withdrawals and credits between appropriations | FM1081_FUND_ROW and form interface |
| Prior reported data | Keeps what was already reported so only changes go out | FMFG_PRIOR_RPT, FMFG_PRIOR_RPTKF |
| Trading partner exceptions | Non-federal partners that would otherwise look federal | FMFG_TRADE_ID |
| Reporting layouts | Definitions for federal report formats | FMFGRLAYOUT, FMFGRLAYOUT_DEF |
8. Payables functions required by federal law
| Function | Rule it supports | Objects named in the component |
|---|---|---|
| Due date calculation | Payment is due a set number of days after the later of invoice receipt and acceptance | Baseline date ZFBDT, payment terms, material group to payment terms mapping T023P |
| Interest penalty | Late payments accrue interest at the Treasury rate | Rates T023R, minimum and maximum T023B, reason codes T023U |
| Fast pay and accelerated pay | Certain invoices are paid before acceptance or on shortened terms | T023Q, exclusion table FMFGT_EXCL |
| Reason codes | Why an invoice was paid late, early, or adjusted | FMFGRC, FMFG_REASONS, FMFG_PPA_INV_HD, FMFG_PPA_INV_LN |
| Statistical sampling | Low-value invoices may be certified by sample | FMFGT_SS04 |
| Contractor registration | Vendor data must match the governmentwide registration | FMCCRTVENDOR, FMCCRTUPDATES, FMFG_LFACCR, display-only fields FMFG_CCRFDDISP |
| Pending purchase order changes | Changes that need approval before they take effect | FMFG_VEKPO, FMFG_MM_PEND_CHG |
| Recurring obligations | Obligations recorded on a schedule, such as leases and utilities | FMROHDR, FMROLINE, FMROPOS |
| Treasury offset | Delinquent debts are referred for offset | Programs listed in the GFEBS role map: RTREAS_OFFSET_FILE, RTREAS_OFFSET_UPDATE |
9. Period-end and year-end
- Clear interface queues. Reprocess or resolve IDocs in error and batch input sessions.
- Complete goods receipts and service entry sheets for the period. Post accruals for received and unbilled items.
- Run the payment conversion so paid invoices show as outlays.
- Run depreciation, settlement of orders and projects, and allocations.
- Reconcile Funds Management to the general ledger. The GFEBS role map lists two federal reconciliation reports and an abnormal balance report under reconciliation postings.
- Reconcile Fund Balance with Treasury by Treasury account symbol.
- Close posting periods in FI (
OB52), materials (MMPV), CO (OKP1), and FM. - Produce the trial balance extract for DDRS. The GFEBS role map lists custom SFIS trial balance and DDRS trial balance transactions.
| Step | What happens | Transactions seen in the GFEBS role map |
|---|---|---|
| Review open commitments and obligations | Close items that are complete. Deobligate invalid balances. | FMMC, FMY2, FMZ2, custom open commitment and open obligation reports |
| Carry forward open documents | Requisitions, orders, and earmarked funds move to the new year with their budget, per fund rules | Commitment carryforward in FM |
| Unfilled customer orders | Report and carry forward reimbursable orders not yet earned | FMFG_RPT_E_UNFILLED, custom unfilled orders report |
| Cancelling appropriations | Five years after expiration, remaining balances cancel. Open payables and receivables move to the cancelled-fund treatment. | FMFG_CANCELED_AP, FMFG_CANCELED_AP_MM, FMFG_CANCELED_AR |
| Pre-closing and closing entries | Anticipated accounts are closed. Budgetary and proprietary closing entries post. | FMFG_YEAR_END_CLOSE, F.80 |
| Close orders | Set orders to technically complete and closed | CO99 |
| Year-end certification | Budget holders certify status of funds | FMB_B01 |
| Balance carryforward | General ledger and special ledger balances roll to the new year. Fund balances carry forward in FM. | FAGLGVTR, GVTR, FMSU |
| Rebuild availability control | Recompute the control ledger for the new year | FMAVCREINIT |
The step descriptions are the standard federal year-end sequence. The transaction column lists what the public GFEBS role-to-transaction mapping places under its year-end close activity.
10. Reconciling Funds Management to the general ledger
| Check | Compare | A difference means |
|---|---|---|
| Obligations | Open FMIOI value type 51 and 65 by fund to USSGL 4801 | Budgetary ledger did not post for some documents, or manual 4801 journals exist |
| Commitments | Open FMIOI value type 50, 81, 82 to USSGL 4700 | Same causes |
| Delivered orders unpaid | FMIFIIT value type 54 not yet converted to USSGL 4901, and to payables 2110 | Payment conversion not run, or invoices posted without FM assignment |
| Outlays | FMIFIIT value type 57 to USSGL 4902 and to Fund Balance with Treasury activity | Payments posted outside the payment program, or disbursing returns not matched |
| Budget | FMBDT by budget type to USSGL 4119, 4450, 4510, 4610 | Budget entered without budgetary ledger posting, or the wrong account pair |
| Tie points | Budgetary to proprietary relationships, for example 4801 change against undelivered order activity, 4902 against expended appropriations | One side of a dual entry is missing |
| Document level | FMIFIIT-KNBELNR to BKPF-BELNR | FM lines without an FI document or FI lines with an FM assignment and no FM line |
Sources
- SAP PSM-FG component tables (public listing)
- SAP Help: US Federal Government (PSM-FG)
- SAP Help: Customizing the Budgetary Ledger
- U.S. Army Financial Management School: GFEBS Desktop SOP (public copy)
- GFEBS role to transaction code mapping (public copy)
- DODIG-2012-066: GFEBS did not provide required financial information
- DODIG-2014-090: GFEBS Budget-to-Report business process
- DODIG-2020-035: Followup audit of GFEBS Acquire-to-Retire and Budget-to-Report
- DoD FMR Volume 1, Chapter 7: DoD Standard Chart of Accounts
- Treasury: USSGL
Educational reference. Standard product tables and public sources only. Not an official DoD, DFAS, SAP, or Oracle publication.