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.

11

Numbered tables

2 diagrams

1. 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.

Table SF-1The two accounting views of one event
ViewQuestionSAP componentUSSGL accountsStatement
ProprietaryWhat happened to assets, liabilities, net position, revenue, and expenseFI General Ledger with subledgers1000 to 3000 and 5000 to 7000Balance Sheet, Statement of Net Cost, Statement of Changes in Net Position
BudgetaryWhat happened to budget authorityFunds Management, with the budgetary ledger writing to FI4000Statement of Budgetary Resources, SF 133
MemorandumStatistical trackingFI statistical postings8000Supporting schedules

2. Funds Management master data

Table SF-2FM account assignment elements
ElementFieldMaster tableMeaningWhat GFEBS public procedures show
FM areaFIKRSFM01Scope of budget controlCompany code and business area both appear as ARMY
FundGEBERFMFINCODEA source of funding with its own legal restrictions and validityExamples 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 centerFISTLFMFCTR, hierarchy FMHISVAn organization that receives and manages budgetExamples A76DD and A2ABM
Commitment itemFIPOS, FIPEXFMCIWhat the money is spent on or where revenue comes fromFour-character values such as 21T0 for travel and 22NL. Derived from the element of resource. The G/L account appears as 6100.21T0.
Functional areaFKBERTFKBPurpose or programExamples 131096QLOG and 121018TTDY. Built from the Army management structure code and the management decision package.
Funded programMEASUREFMMEASUREA lower-level program or project that is funded separatelySet equal to the WBS element for projects. ARMY is the default holding value.
Budget periodBUDGET_PDFMBUDGETPDPeriod of availability for multi-year fundsNot shown in the public material
GrantGRANT_NBRGMGRSponsor-funded agreementNot 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

Figure SF-1Funds Management update: from coding block to ledgers
Business document carries the coding blockFunds Management decides what it is and whether budget existsLedgers updatedSource documentRequisition, order, earmarkedfunds, invoice, payment, journal,payroll, travelCoding block (COBL)HKONT G/L accountKOSTL, AUFNR, PS_PSP_PNRGEBER fundFISTL funds centerFIPOS commitment itemFKBER functional areaMEASURE funded programDerivation (FMDERIVE)Fills missing FM fields fromaccount, cost object, materialgroup, or custom rulesResult is stored on the documentMaster data checksFund validity dates and expirationBudget object statusCommitment item financialtransaction and categoryUpdate profileSets the value type and the datethat decides the budget yearPayment budget and commitmentbudget settingsAvailability controlCompares consumable budget toconsumed and committed amountsWarning or error by toleranceprofileCommitment chainA follow-on document reduces itspredecessorOrder reduces requisition, invoicereduces orderBudgetary ledger derivationMaps the FM event to USSGL4000-series debit and creditFMIOIOpen commitmentsvalue types 50, 51, 65, 80-82FMIFIITActualsvalue types 54, 57, 58, 61, 66FMIT, FMAVCTTotals by budget addressAvailability control ledgerBKPF, BSEG, ledgersProprietary and budgetary linesFederal reporting ledgers
Table SF-3Value types and the documents that create them
Value typeNameCreated byTableBudgetary meaning
50Purchase requisitionME51N, requisition interfacesFMIOICommitment
51Purchase orderME21N, contract interfacesFMIOIObligation, undelivered order
52Business trip commitmentTravel requestFMIOIObligation
80Funds blockFMW1FMIOIAdministrative hold
81Funds reservationFMX1FMIOIReservation or commitment
82Funds precommitmentFMY1FMIOICommitment
65Funds commitmentFMZ1FMIOIObligation without a purchase order
83Forecast of revenueFMV1FMIOIAnticipated collection
54InvoiceMIRO, FB60, goods receipt depending on profileFMIFIITAccrued expenditure, delivered order unpaid
57PaymentPayment document, payment conversion FMF0FMIFIITOutlay
58 / 61Down payment request / down paymentF-47 / F-48FMIFIITAdvance
66Transfer postingFB50 and reclassificationsFMIFIITAdjustment between FM addresses
95Secondary cost postingCO allocations when CO integration is activeFMICOITInternal 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 FMIOI and adds itself. An invoice reduces the order. Each reduction is its own line with amount type 0200.
  • 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 FMF0 does it in a batch.
  • Statistical lines, flagged in STATS, appear in reports and do not consume budget.

4. Budget Control System

Figure SF-2Budget authority from appropriation to outlay: SAP records and USSGL accounts
AuthoritySAP recordUSSGL budgetary accountsAppropriationPublic law, TreasurywarrantApportionmentOMB SF 132Allotment andsub-allotmentFunding authorizationdocuments down the fundscenter hierarchyCommitmentCertified requisition orfunds commitmentObligation to outlayOrder, receipt, invoice,paymentFMBH / FMBLProcess ENTRBudget type: appropriationTop funds centerFMBH / FMBLBudget type: apportionmentor status change ofthe same budgetFMBH / FMBLProcess TRAN or SEND/RECVSender and receiverfunds centersEBAN or KBLK/KBLPFMIOI value type 50or 65, 81, 82EKKO, BKPFFMIOI value type 51FMIFIIT 54 and 574119 to 4450Appropriation realized,unapportioned4450 to 4510Apportioned, available forallotment4510 to 4610Allotted, available forcommitment4610 to 4700Committed4700 to 4801, 4901,4902Obligated, delivered, paid

Budget types, statuses, and the exact account pairs are configuration. The DoD USSGL Transaction Library defines the required entries.

Table SF-4Budget Control System concepts
ConceptWhat it isWhere stored or set
Budget categoryPayment budget (9F) or commitment budget (9G)FM area settings
Budget typeA classification of budget, such as appropriation, apportionment, allotment, reimbursable authority, continuing resolutionCustomizing. Federal attributes of each type in FMFG_BUTYPE.
Budgeting processWhat the entry does: enter, supplement, return, transfer, with send and receive sides, carry overField on the entry document line
Entry documentThe record of one budget action with header, lines, and optional workflowFMBH, FMBL. Entered in FMBB.
Document typeClassifies entry documents and sets number range and authorizationCustomizing. GFEBS procedures show type ALLT for allotment.
VersionBudget versions allow a working version and the version of record, version 000Field on totals and documents
Budget addressThe combination of fund, funds center, commitment item, functional area, funded program, and grant that holds budgetFMBDT
Posting addressThe combination a document posts to. It is mapped to a budget address by a derivation.Budget structure and derivation
Availability control ledgerTotals of consumable budget and consumed amounts by control address. 9H for payment budget, 9I for commitment budget.FMAVCT
Tolerance profileThresholds that issue a warning, an error, or a notification, by activity groupCustomizing
StatusPreposted, 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, FMAVCREINIT rebuilds it.
  • FMAVCR01 shows 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 FMBB together 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.

Table SF-5Earmarked funds categories
CategoryCreateValue typeUseGFEBS document types in public procedures
Funds blockFMW180Hold budget so it cannot be usedNot shown
Funds reservationFMX181Reserve budget for a purpose not yet defined in detailNot shown
Funds precommitmentFMY182Commit budget for a planned requirementM1, labeled FCM commitment
Funds commitmentFMZ165Obligate budget when there is a legal liability and no purchase orderF9 miscellaneous obligation, F1 travel obligation paid through the Integrated Automated Travel System, F6 PowerTrack transportation obligation
Forecast of revenueFMV183Record expected revenueNot shown
  • Header KBLK, items KBLP, consumption history KBLE. Each item carries its own fund, funds center, commitment item, G/L account, and cost object.
  • An invoice entered in FB60 references the earmarked funds number and item. The reference is stored on the invoice line in BSEG-KBLNR and KBLPOS, and the consumption appears in KBLE.
  • 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.

Table SF-6Budgetary ledger objects named in the SAP US Federal component
ObjectPurpose
FMFGBLAREA, FMFGBLAREAT, FMFGBLAREAFLDBudgetary ledger areas: the kinds of event the ledger posts for, and the fields each uses
FMFGBLAREADOCTYFI document type used for budgetary ledger postings in each area
FMFG_BUTYPEBudgetary ledger attributes of each budget type
FMFGBLDRVAREAEAADerivation rule that sets expended appropriations for actuals
FMSGLCLASSClassification of SGL accounts
FMFG_BL_YRCL, FMFGYECLAAYear-end closing rules for the budgetary ledger and pre-closing of anticipated accounts
FMFG_ABP, FMFG_ABP_HDR_DEF, FMABP_AREASAutomatic budget postings, for example budget created automatically from reimbursable orders or collections
FMFONDS, FMFONDSTAssignment 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.

Table SF-7Standard event-to-account logic the budgetary ledger must reproduce
EventBudgetary entryProprietary entry in the same or a linked document
Appropriation enactedDr 4119 Cr 4450Dr 1010 Cr 3101
ApportionmentDr 4450 Cr 4510None
AllotmentDr 4510 Cr 4610None
CommitmentDr 4610 Cr 4700None
ObligationDr 4700 Cr 4801None
Goods or services receivedDr 4801 Cr 4901Dr 6100 or asset Cr 2110. Dr 3107 Cr 5700.
PaymentDr 4901 Cr 4902Dr 2110 Cr 1010
Advance paidDr 4801 Cr 4802Dr 1410 Cr 1010
Reimbursable order accepted, without advanceDr 4221 Cr 4210None
Reimbursable earned and billedDr 4251 Cr 4221Dr 1310 Cr 5200
Reimbursable collectedDr 4252 Cr 4251Dr 1010 Cr 1310
Downward adjustment of a prior-year unpaid obligationDr 4801 Cr 4871None
Upward adjustment of a prior-year unpaid obligationDr 4881 Cr 4801None
Rescission of new authorityDr 4450 Cr 4392Dr 3106 Cr 1010 where funds are returned
Temporary reduction under a continuing resolutionDr 4450 Cr 4395None

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 to FMUSFGFACTS1T, and ledger 97 to FMUSFGFACTS2T. The attribute keys are in FMFGKEY, FMFGKEY96, and FMFGKEY97.
  • 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.
Table SF-8Treasury-facing functions in the SAP US Federal component
FunctionWhat it supportsObjects named in the component
Treasury account symbol structureApplication of funds groups funds into the Treasury account they belong toApplication of funds master, FM1081_FUND_ROW
Fiscal station and Agency Location CodeIdentifies the accounting station and the disbursing or reporting officeFMFGT_FSN, FMFGT_ALC_GWA
Governmentwide accounting reporter rulesWhether an office reports classification at the time of the transactionFMUSFG_GWA_ACTIO, FMUSFG_GWA_ELIGI, FMUSFG_GWA_RCVAL
Treasury subclassSubclass codes by document type, account, and fundFMUSFG_TS, FMUSFG_TSA
IPACOutgoing IPAC files, incoming IPAC transactions, automatic document creationFMFGT_IPACED, FMFGT_IPAC_FILE, FMFGT_IPAC_STATS, FMFGT_IPAC_ACCT, transaction FMFG_IPAC
SF 1081Voucher and schedule of withdrawals and credits between appropriationsFM1081_FUND_ROW and form interface
Prior reported dataKeeps what was already reported so only changes go outFMFG_PRIOR_RPT, FMFG_PRIOR_RPTKF
Trading partner exceptionsNon-federal partners that would otherwise look federalFMFG_TRADE_ID
Reporting layoutsDefinitions for federal report formatsFMFGRLAYOUT, FMFGRLAYOUT_DEF

8. Payables functions required by federal law

Table SF-9Prompt Payment Act and related functions
FunctionRule it supportsObjects named in the component
Due date calculationPayment is due a set number of days after the later of invoice receipt and acceptanceBaseline date ZFBDT, payment terms, material group to payment terms mapping T023P
Interest penaltyLate payments accrue interest at the Treasury rateRates T023R, minimum and maximum T023B, reason codes T023U
Fast pay and accelerated payCertain invoices are paid before acceptance or on shortened termsT023Q, exclusion table FMFGT_EXCL
Reason codesWhy an invoice was paid late, early, or adjustedFMFGRC, FMFG_REASONS, FMFG_PPA_INV_HD, FMFG_PPA_INV_LN
Statistical samplingLow-value invoices may be certified by sampleFMFGT_SS04
Contractor registrationVendor data must match the governmentwide registrationFMCCRTVENDOR, FMCCRTUPDATES, FMFG_LFACCR, display-only fields FMFG_CCRFDDISP
Pending purchase order changesChanges that need approval before they take effectFMFG_VEKPO, FMFG_MM_PEND_CHG
Recurring obligationsObligations recorded on a schedule, such as leases and utilitiesFMROHDR, FMROLINE, FMROPOS
Treasury offsetDelinquent debts are referred for offsetPrograms listed in the GFEBS role map: RTREAS_OFFSET_FILE, RTREAS_OFFSET_UPDATE

9. Period-end and year-end

  1. Clear interface queues. Reprocess or resolve IDocs in error and batch input sessions.
  2. Complete goods receipts and service entry sheets for the period. Post accruals for received and unbilled items.
  3. Run the payment conversion so paid invoices show as outlays.
  4. Run depreciation, settlement of orders and projects, and allocations.
  5. Reconcile Funds Management to the general ledger. The GFEBS role map lists two federal reconciliation reports and an abnormal balance report under reconciliation postings.
  6. Reconcile Fund Balance with Treasury by Treasury account symbol.
  7. Close posting periods in FI (OB52), materials (MMPV), CO (OKP1), and FM.
  8. Produce the trial balance extract for DDRS. The GFEBS role map lists custom SFIS trial balance and DDRS trial balance transactions.
Table SF-10Year-end steps specific to a federal system
StepWhat happensTransactions seen in the GFEBS role map
Review open commitments and obligationsClose items that are complete. Deobligate invalid balances.FMMC, FMY2, FMZ2, custom open commitment and open obligation reports
Carry forward open documentsRequisitions, orders, and earmarked funds move to the new year with their budget, per fund rulesCommitment carryforward in FM
Unfilled customer ordersReport and carry forward reimbursable orders not yet earnedFMFG_RPT_E_UNFILLED, custom unfilled orders report
Cancelling appropriationsFive 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 entriesAnticipated accounts are closed. Budgetary and proprietary closing entries post.FMFG_YEAR_END_CLOSE, F.80
Close ordersSet orders to technically complete and closedCO99
Year-end certificationBudget holders certify status of fundsFMB_B01
Balance carryforwardGeneral ledger and special ledger balances roll to the new year. Fund balances carry forward in FM.FAGLGVTR, GVTR, FMSU
Rebuild availability controlRecompute the control ledger for the new yearFMAVCREINIT

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

Table SF-11Checks that prove the two views agree
CheckCompareA difference means
ObligationsOpen FMIOI value type 51 and 65 by fund to USSGL 4801Budgetary ledger did not post for some documents, or manual 4801 journals exist
CommitmentsOpen FMIOI value type 50, 81, 82 to USSGL 4700Same causes
Delivered orders unpaidFMIFIIT value type 54 not yet converted to USSGL 4901, and to payables 2110Payment conversion not run, or invoices posted without FM assignment
OutlaysFMIFIIT value type 57 to USSGL 4902 and to Fund Balance with Treasury activityPayments posted outside the payment program, or disbursing returns not matched
BudgetFMBDT by budget type to USSGL 4119, 4450, 4510, 4610Budget entered without budgetary ledger posting, or the wrong account pair
Tie pointsBudgetary to proprietary relationships, for example 4801 change against undelivered order activity, 4902 against expended appropriationsOne side of a dual entry is missing
Document levelFMIFIIT-KNBELNR to BKPF-BELNRFM lines without an FI document or FI lines with an FM assignment and no FM line

Sources

  1. SAP PSM-FG component tables (public listing)
  2. SAP Help: US Federal Government (PSM-FG)
  3. SAP Help: Customizing the Budgetary Ledger
  4. U.S. Army Financial Management School: GFEBS Desktop SOP (public copy)
  5. GFEBS role to transaction code mapping (public copy)
  6. DODIG-2012-066: GFEBS did not provide required financial information
  7. DODIG-2014-090: GFEBS Budget-to-Report business process
  8. DODIG-2020-035: Followup audit of GFEBS Acquire-to-Retire and Budget-to-Report
  9. DoD FMR Volume 1, Chapter 7: DoD Standard Chart of Accounts
  10. Treasury: USSGL

Educational reference. Standard product tables and public sources only. Not an official DoD, DFAS, SAP, or Oracle publication.