Introducing SAF/FMFO Accounting Policy & Operations

As part of a SAF/FMF reorganization, SAF/FMFC-A Air Force Accounting and Finance Office (AFAFO) and SAF/FMFS Air Force Accounting Operations Center (AFAOC) have joined forces as a NEW organization, SAF/FMFO (Accounting Policy and Operations), effective 1 Oct 2024.
This reorganization consolidates Air Force Financial Operations accounting support within a centralized organization, from policy development to implementation and sustainment across the Department of the Air Force (DAF). This merger streamlines access to process owners within a single organization and enhances the customer support already being provided to the Commands by increasing the breadth and depth of reach back support.

SAF/FMFO consists of four divisions covering the scope of work and quality products Air Force FM professionals have come to expect from AFAFO and AFAOC – now in one organization. SAF/FMFO’s divisions include Customer Support led by Mr. Bill Sanders, Field Support led by Ms. Kim Burnett, Policy led by Ms. Mick Hale, and Technical Support led by SAF/FMFO Deputy, Mr. T.J. Souza.

Our customers and FM systems users will still have access to help desk support, Subject Matter Expert (SME) knowledge, Power BI research modules, policy management, monthly users forums, dedicated fiscal year end closeout support, and so much more. With SAF/FM resources better aligned, we are looking forward to this exciting new venture and strive to deliver on our mission to provide overarching DAF FM accounting policy and customer support to strengthen user proficiency, including continuing education, targeted assistance, systems operation and monitoring, data analytics, internal controls, and strategic communications.

Organizational change is essential in today’s ever-transforming business environment and is necessary for maintaining relevance and posterity. Rest assured that our vision will always remain the same – Success through Customer Focus. We here at SAF/FMFO are thrilled to continue supporting the world’s greatest airmen and guardians.

If you have any questions or feedback, please contact SAF.DEAMS.StratComms@us.af.mil.

Best of DEAMS Weekly Messages

The Ultimate Links List

General Air Force

Systems

MAJCOM FMs

  • AFAA Reports
  • AFRC/FM
  • AFSOC/FM
  • PACAF Metrics
  • USAFE-AFAFRICA/FM

Power BI

AFRC

301 FW

Daily Systems

Regulations

DFAS

Official FM Sites

Knowledge Ops

Social Media

My Presentations

Most Requested Briefs

Own Your Inbox

15 Years in 45 Minutes

Three Slide Presentation Concept

Leadership Briefings I’ve Gathered

Amazon notes – Working Backwards

Building High Performing Teams

Organizational Culture

Drink TEA Serve TEA

Lessons from Command – Padgett

CPTS Operating Instruction

Time Management – Gilchrist

Congrats You’ve Been Selected for Command

Ideas for Comptroller Command

Reflections on Command – Minken

PowerTrack/Syncada MORDs

Commercial (Syncada, C-MORD)

Legacy – NP in 11th and 12th position in SDN.  PC Code ST. Base obligates.

DEAMS – MP in the 11th and 12th position in SDN. Planned PO. Requisition (PR) Amendment will have Purpose code “0” (zero). Original PO with Purpose code P auto obligates. Approved PR Amendments must be associated to Original PO.  Do not intermix EEIC/OCs on Transportation MORDS.

See Object Classes/EEICs below to use for the HHG/NTS

See below for the acceptable Object Classes/EEICs available

Processed via US Bank – Syncada, https://portal.syncada.com/USBank/Login.aspx

Training audio file and slides for Syncada BI Funds Manager reports is located in the Syncada folder at : https://usaf.dps.mil/sites/10194/Knowledge_Base/Shared_Documents/DCBS_and_Syncada_Training/

Organic (AMC/DCBS/OCONUS, G-MORD)

Legacy – MM in 11th and 12th position in SDN.   PC Code G. Base Obligates

DEAMS – MM in the 11th and 12th position in SDN. Standard PO. Base manually obligates.  Check IPROC to ensure the MORD is listed in the Order Column

Charges Processed by AMC via DCBS to DFAS, https://dcbs.transport.mil/.  Email DCBS.Helpdesk@us.af.mil for DCBS access instructions Sign up for TAC Monitor Role on your DD 2875

See below for the acceptable Object Classes/EEICs available

Preval in the 1st 6 business days of the month.   Training video for DCBS pre-val is located in the DCBS folder at :

https://usaf.dps.mil/sites/10194/Knowledge_Base/Shared_Documents/DCBS_and_Syncada_Training

  • OCONUS PCS Shipment, OCONUS Cargo (Freight) require both a commercial and an organic MORD
  • MTA/PAX Organic Accounting (G-MORD) must be sent to the DCBS.Helpdesk@us.af.mil.  The subject line should include MTA/PAX MORD, CAER account #, and CIC. 

  • Freight/CARGO (Commercial/Organic) cannot use the EEIC/Objects classes designated for Commercial HHG and NTS:
    • For HHG, HHG Prog Code,  HC = 46200 or 220.1101, 46203 or 220.1103, 46250 or 220.1104 , 55792 or 257.2292, 55793 or 257.2293
    • For NTS HHG Program Code,  HS = 55791 or 257.2291
    • All others OC/EEICs allowed will be coded Freight and the HHG program field should be blank
    • HHG Prog Code in TGET is the driver to the Syncada Chart of Accounts (COA) for invoicing
  • Commercial MP MORDS cannot use EEICs for Organic MM MORDs
  • Organic MM MORDS cannot use OCs that crosswalk to EEICs that begin with 462% (those are for Commercial purposes)
    • Please review OCs in the 253 category to select the best OC/EEIC  
    • MM MORDS need to be manually obligated at base level.  Please double check to be sure both the requisition and purchase order are approved
  • The Purchase Order/MORDS must be obligated for the document to flow to TGET

You must check TGET to ensure your MORD/LOA is properly loaded to TGET (this usually occurs 3-5 days after obligation):

For how to check TGET Review the audio or video files located in the DCBS or Syncada folder at: https://usaf.dps.mil/sites/10194/Knowledge_Base/Shared_Documents/DCBS_and_Syncada_Training

Misc Payments MORDS Purpose Codes

Link

Advana Notes

KSD Checklist of acceptable documentation

Data Universal Numbering System (DUNS) to Unique Entity Identifier (UEI) Transition Effective 4 Apr 2022

DEAMS Users will be impacted by the transition from Data Universal Numbering System (DUNS) to Unique Entity Identifier (UEI) codes, which is currently expected to occur on 4 April 2022.  Those with DEAMS Supplier Maintenance and Creation Responsibility will be most impacted.

In DEAMS, the DUNS number has been a nine-digit non-indicative numbering sequence used to identify specific vendors, assigned and managed by Dun & Bradstreet since 1962. In October 2020, the Office of Management and Budget (OMB) directed a Government-wide transition from DUNS to UEI codes to be completed by April 2022. This transition impacts Government Information Systems that use or collect Supplier information, and streamlines how an entity (anyone who does business with the government) receives their ID. UEI codes are scheduled to be activated in DEAMS on 4 April 2022.

Entities already registered in the System for Award Management (SAM) were automatically transitioned from DUNS to UEIs. Information on creating a new UEI is available on the General Services Administration website at https://www.gsa.gov/about-us/organization/federal-acquisition-service/office-of-systems-management/integrated-award-environment-iae/iae-systems-information-kit/unique-entity-identifier-update.

“If your entity is registered in SAM.gov today, your Unique Entity ID (SAM) has already been assigned and is viewable in SAM.gov. This includes inactive registrations. The Unique Entity ID is currently located below the DUNS Number on your entity registration record.” 

For DEAMS Users, the biggest difference will be the number of characters in the field (9 DUNS/12 UEI). To assist Users in selecting the correct UEI site number for a vendor, DEAMS Job Aid “Supplier Record Research_SPD.docx” provides an overview of the process and references other job aids, depending on which responsibilities are being used for the actions. To help ease the transition from DUNS to UEI, a crosswalk will be made available at “go live” on the DEAMS Outreach Portal to help users identify correct vendor records in DEAMS. This crosswalk will only contain existing vendors; it will not capture new entities following the transition.

Our DFAS partners are responsible for creating and maintaining the UEI list in DEAMS, and in the event of interface errors, they may need to validate UEI codes in SAMs.  The SAMs site lists the UEI for a supplier right below the corresponding DUNS, simplifying the validation process. 

Questions should be addressed to users’ respective MAJCOM/CCMD SMEs, or the DEAMS Help Desk.

For any further messaging, access the DEAMS Users Group on milBook.

PBASweb Information

PBASweb manages the Reserve Personnel Appropriation (RPA) by offering automated allocation of funding authority and funds management control for HQ AFRC/FM and providing a real-time status of funds, as well as the mileage obligations and expenditures for Military Personnel Appropriations (MPA). Its customer base is HQ AFRC, NAFs, Wings, Commanders, Base Level FM Personnel

Federal Employee Paid Leave Act Update

Message from the Indianapolis Civilian Payroll Office:

As you may be aware, the Federal Employee Paid Leave Act (FEPLA), authorized by NDAA for FY 20 (PL 116-92), is effective October 1, 2020. 

FEPLA allows  for the substitution of 12 weeks of FEPLA paid leave for FMLA unpaid leave in connection with the birth, adoption or foster placement of employee’s child on or after October 1, 2020. 

DFAS is working to program DCPS for this new leave type, but in the interim agencies should do the following:

  • Determine employee eligibility according to the agency’s policy guidance for FEPLA or the regular FMLA process.  Intermittent employees and temporary appointments less than one year are excluded
  • T&A should reflect type hour code ‘LV’ for FEPLA paid parental leave
  • Track employee usage of FEPLA manually to prevent exceeding the 12-week limit.

If you have any questions contact the help desk at 1-800-729-3277 or DSN 580-7500, Monday – Friday 07:30 am to 4:00 pm EST