Cleveland Accounting - Accounts Payable -- Online Customer Service

Providing responsive, professional finance and accounting services for the people who defend America means delivering timely useful information. Our site allows customers the ability to request support or provide feedback. Every individual is unique, but they often face similar issues. Browse our frequently asked questions database before submitting a question for best results.

Effective October 2019 - Accounts Payable Module Categories have been setup by Request Type instead of Command/BSO!

To better serve our customers, we have recently made some changes to our ticket submission page. When submitting a ticket required fields now include a phone number, Command and/or Vendor Name, and Contract/Invoice Nbr.  Including this information will help our teams expedite resolution to customer inquiries and enhance your askDFAS experience. We are always interested in your feedback and suggestions for improvement.  Please click on the link below to complete a short survey and/or provide recommendations in the comment field.Thank you for being a valued DFAS customer!ICE Customer Survey: https://go.usa.gov/xAbtH

A/P Liaison - Tanya Higgins (tanya.l.higgins2.civ@mail.mil) Leola Epps (leola.l.epps.civ@mail.mil) or Clint Sorensen (clinton.e.sorensen2.civ@mail.mil)

No.

Category

Subcategory

Frequently Asked Question

Viewed

Viewer Rating

LZ005

A/P CUSTOMER SERVICE

Payment Status

Status of Invoices for Payment

8,004

LY004

A/P CUSTOMER SERVICE

WAWF Invoice Status

WAWF Recalls

4,209

LZ002

A/P CUSTOMER SERVICE

Payment Status

Status of Invoices for Payment

3,009

E;005

SF1081's REQUEST - (NON-MOCAS)

USMC SF1081 Requests

Voucher Requests

2,230

E;012

SF1081's REQUEST - (NON-MOCAS)

USMC SF1081 Requests

SF1080 and SF1081 - Definitions

2,058

LY002

A/P CUSTOMER SERVICE

WAWF Invoice Status

WAWF Invoice Submission

1,903

LZ001

A/P CUSTOMER SERVICE

Payment Status

Reasons for Payment Delays

1,747

A>001

Electronic Submissions

Electronic Deletions/Reversals/Recalls

Electronic Deletions/Reversals/Recalls Requirements

1,729

Q/008

SF1081's REQUEST - (NON-MOCAS)

Navy ERP - SF1081 Request

Reasons For a 1081

1,680

LZ007

A/P CUSTOMER SERVICE

Payment Status

Receipt of Funds

1,456

LY003

A/P CUSTOMER SERVICE

WAWF Invoice Status

WAWF System Questions

1,226

E;011

SF1081's REQUEST - (NON-MOCAS)

USMC SF1081 Requests

Redistribute Requests (RDR)

1,175

LW001

A/P CUSTOMER SERVICE

ID of Payment Received

Receipt of ACH/EFT Payments

1,051

R}001

DCAS SF1080 Transfer

Navy

SF1080

1,045

LZ008

A/P CUSTOMER SERVICE

Payment Status

Suspended Invoices - SF1081 correction is not required

993

E;007

SF1081's REQUEST - (NON-MOCAS)

USMC SF1081 Requests

621/1081 Request Definition and Requirements

991

Q/002

SF1081's REQUEST - (NON-MOCAS)

Navy ERP - SF1081 Request

1081 Back-Up

939

E;004

SF1081's REQUEST - (NON-MOCAS)

USMC SF1081 Requests

Payment History and Missing Payments

886

E;003

SF1081's REQUEST - (NON-MOCAS)

USMC SF1081 Requests

Invoice Requests

864

Q/007

SF1081's REQUEST - (NON-MOCAS)

Navy ERP - SF1081 Request

What information is needed when sending a request?

845

A?001

Electronic Submissions

Electronic Pay Date Changes

Electronic Pay Date Changes Submissions

726

LY001

A/P CUSTOMER SERVICE

WAWF Invoice Status

Identifying the Pay Office

609

LY005

A/P CUSTOMER SERVICE

WAWF Invoice Status

Receipt of Funds

609

Q/001

SF1081's REQUEST - (NON-MOCAS)

Navy ERP - SF1081 Request

1081 Processing Timeframe

595

LZ004

A/P CUSTOMER SERVICE

Payment Status

V-Status

572

V[002

NON RECEIPT OF PAYMENT

EFT Reject/Non-Receipt of Paper Check

Have Not Received Payment Even After Updating Banking Information

558

A-001

Electronic Submissions

Electronic Vendor ID

Electronic Vendor ID Submissions

549

E;009

SF1081's REQUEST - (NON-MOCAS)

USMC SF1081 Requests

MOCAS

547

Q,004

VENDOR PAYMENT SETUP

Notice of Assignment(NOA)/Novation Agrmt

Establishing Payments to an Assignee

534

LW002

A/P CUSTOMER SERVICE

ID of Payment Received

Identification of Paper check Received

529

LZ003

A/P CUSTOMER SERVICE

Payment Status

Frozen or Suspended Funds

497

V[001

NON RECEIPT OF PAYMENT

EFT Reject/Non-Receipt of Paper Check

Payment Confirmed by DFAS is Not In My Account

482

Q/004

SF1081's REQUEST - (NON-MOCAS)

Navy ERP - SF1081 Request

Do I really need a 1081 for this?

447

LZ006

A/P CUSTOMER SERVICE

Payment Status

T-Status

440

Q/006

SF1081's REQUEST - (NON-MOCAS)

Navy ERP - SF1081 Request

Registers covered by an SF 1081

425

Q/005

SF1081's REQUEST - (NON-MOCAS)

Navy ERP - SF1081 Request

Cross Department SF 1081

410

LX001

A/P CUSTOMER SERVICE

Payment History Request (One Pay System)

Payment History

396

T[001

DEBT COLLECTIONS

Amount Due Contractor/Underpayments

394

Q,006

VENDOR PAYMENT SETUP

Notice of Assignment(NOA)/Novation Agrmt

NOA /Novation Agreement - DFAS Accounts Payable

380

L'002

FUNDS REQUIREMENT

Prevalidation Approvals /Requests

M Status - Invoice Suspended - Tips to determine possible issue

321

R}002

DCAS SF1080 Transfer

Navy

DCAS SF1080 Transfer -Navy

316

L'001

FUNDS REQUIREMENT

Prevalidation Approvals /Requests

M Status - Suspended Invoice

312

LZ009

A/P CUSTOMER SERVICE

Payment Status

Suspended Invoices - SF1081 correction is not required

310

E;002

SF1081's REQUEST - (NON-MOCAS)

USMC SF1081 Requests

Differences between 621 vs 1081

291

A>002

Electronic Submissions

Electronic Deletions/Reversals/Recalls

Common reasons for payment delays when an invoice has cycled into One Pay Entitlement system

290

E;001

SF1081's REQUEST - (NON-MOCAS)

USMC SF1081 Requests

Refund Receivables (RREs)

260

E;013

SF1081's REQUEST - (NON-MOCAS)

USMC SF1081 Requests

Misc. Receipts

239

Q,003

VENDOR PAYMENT SETUP

Notice of Assignment(NOA)/Novation Agrmt

Assignee Documents

236

LT001

Centrally Billed Accounts (CBA)

Electronic CBA-Corrections

Electronic CBA Corrections

236

E;014

SF1081's REQUEST - (NON-MOCAS)

USMC SF1081 Requests

Reimbursable Order Number (RON) Reconciliations

232

Page 001

You are entering an Official U.S. Government System

By using this Information system consent to the following conditions:

The USG routinely intercepts and monitors communications on this IS for purposes including, but not limited to, penetration testing, COMSEC monitoring, network operations and defense, personal misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.
At any time, the USG may inspect and seize data stored on this IS.
Communications using, or data stored on, this IS are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any USG-authorized purpose.
This IS includes security measures (e.g., authentication and access controls) to protect USG interests--not for your personal benefit or privacy.
Notwithstanding the above, using this IS does not constitute consent to PM, LE or CI investigative searching or monitoring of the content of privileged communications, or work product, related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Such communications and work product are private and confidential. See User Agreement and User Rules of Behavior for details.

Privacy Act Statement:

The Information accessed through this system is Controlled Unclassified Information (CUI) and must be protected in accordance with the PRIVACY ACT OF 1974.

The Privacy Act of 1974 covers the information you provide to AskDFAS. To receive a copy of the Privacy Act Statement for the actions you enter into the system, please see your supervisor.
Authority: Title 5 U.S.C. Chapters 53, 55, 81; Title 10 U.S.C. Chapters 11, 61-73; Title 37 U.S.C.; GAO Manual for Guidance of Federal Agencies, Title 6, Chapter 4, para. 4.2.B.2; and E.O. 9397
Purpose of Use/Dissemination: Data gathered by the AskDFAS system is shared/disseminated to DFAS operations personnel with a need-to-know to include customer service representatives, accountants or technicians for purposes of use in identifying, researching and satisfying ticket inquiries within DFAS accounting systems. PII information types subject to gathering are listed here:
Routine Uses: Those generally permitted under the 5 U.S.C. 522A(B) of the Privacy Act as required.
Disclosure: Disclosure is voluntary.

Section 508 Compliance Statement

In accordance with Section 508 of the Rehabilitation Act of 1973, as amended, (29 U.S.C. 794d), DFAS is committed to ensuring that AskDFAS functionality and content is accessible to all customers. Send feedback or concerns related to the accessibility of this website to the DFAS 508 coordinator at: dfas.indianapolis-in.zta.mbx.section508@mail.mil. For more information about Section 508, please visit the DoD Chief Information Officer (CIO) Section 508 Website available at https://dodcio.defense.gov/DoDSection508.aspx

MANDATORY NOTICE AND CONSENT PROVISION FOR ALL DOD INFORMATION SYSTEM USER AGREEMENTS

By clicking the Consent button on the prior page to enter the system, you acknowledge:

You are accessing a U.S. Government (USG) information system (IS) (which includes any device attached to this information system) that is provided for U.S. Government-authorized use only.
You consent to the following conditions

The U.S. Government routinely intercepts and monitors communications on this information system for purposes including, but not limited to, penetration testing, communications security (COMSEC) monitoring, network operations and defense, personnel misconduct (PM), law enforcement (LE), and counterintelligence (CI) investigations.
At any time, the U.S. Government may inspect and seize data stored on this information system.
Communications using, or data stored on, this information system are not private, are subject to routine monitoring, interception, and search, and may be disclosed or used for any U.S. Government-authorized purpose.
This information system includes security measures (e.g., authentication and access controls) to protect U.S. Government interests -- not for your personal benefit or privacy.
Notwithstanding the above, using an information system does not constitute consent to personnel misconduct, law enforcement, or counterintelligence investigative searching or monitoring of the content of privileged communications or data (including work product) that are related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants. Under these circumstances, such communications and work product are private and confidential, as further explained below:

Nothing in this User Agreement shall be interpreted to limit the user's consent to, or in any other way restrict or affect, any U.S. Government actions for purposes of network administration, operation, protection, or defense, or for communications security. This includes all communications and data on an information system, regardless of any applicable privilege or confidentiality.
The user consents to interception/capture and seizure of ALL communications and data for any authorized purpose (including personnel misconduct, law enforcement, or counterintelligence investigation). However, consent to interception/capture or seizure of communications and data is not consent to the use of privileged communications or data for personnel misconduct, law enforcement, or counterintelligence investigation against any party and does not negate any applicable privilege or confidentiality that otherwise applies.
Whether any particular communication or data qualifies for the protection of a privilege, or is covered by a duty of confidentiality, is determined in accordance with established legal standards and DoD policy. Users are strongly encouraged to seek personal legal counsel on such matters prior to using an information system if the user intends to rely on the protections of a privilege or confidentiality.
Users should take reasonable steps to identify such communications or data that the user asserts are protected by any such privilege or confidentiality. However, the user's identification or assertion of a privilege or confidentiality is not sufficient to create such protection where none exists under established legal standards and DoD policy.
A user's failure to take reasonable steps to identify such communications or data as privileged or confidential does not waive the privilege or confidentiality if such protections otherwise exist under established legal standards and DoD policy. However, in such cases the U.S. Government is authorized to take reasonable actions to identify such communication or data as being subject to a privilege or confidentiality, and such actions do not negate any applicable privilege or confidentiality.
These conditions preserve the confidentiality of the communication or data, and the legal protections regarding the use and disclosure of privileged information, and thus such communications and data are private and confidential. Further, the U.S. Government shall take all reasonable measures to protect the content of captured/seized privileged communications and data to ensure they are appropriately protected.

In cases when the user has consented to content searching or monitoring of communications or data for personnel misconduct, law enforcement, or counterintelligence investigative searching, (i.e., for all communications and data other than privileged communications or data that are related to personal representation or services by attorneys, psychotherapists, or clergy, and their assistants), the U.S. Government may, solely at its discretion and in accordance with DoD policy, elect to apply a privilege or other restriction on the U.S. Government's otherwise authorized use or disclosure of such information.
All of the above conditions apply regardless of whether the access or use of an information system includes the display of a Notice and Consent Banner ("banner"). When a banner is used, the banner functions to remind the user of the conditions that are set forth in this User Agreement, regardless of whether the banner describes these conditions in full detail or provides a summary of such conditions, and regardless of whether the banner expressly references this User Agreement.

AskDFAS Rules of Behavior

By clicking the Consent button on the prior page to enter the system, you acknowledge as an Authorized user you shall:

Hold a U.S. Government security clearance commensurate with the level of access granted.
Access only that data, control information, software, hardware, and firmware for which they are authorized access and have a need-to-know, and assume only those roles and privileges for which they are authorized.
Observe policies and procedures governing the secure operation and authorized use of a DoD information system.
Use AskDFAS only for authorized purposes.
Immediately report all IA-related events, potential threats, and vulnerabilities involving AskDFAS to either the System ISSM, System Manager, or contact DFAS CSSP at 327-212-9172. After hours, call DMI at 1-844-DISA-HLP (844-347-2457), press 5 or email: dfasdmiservicedesk@mail.mil .
Ensure that system media and output are properly marked, controlled, stored, transported, and destroyed based on classification or sensitivity and need-to-know.
Not introduce or use unauthorized software, firmware, or hardware with AskDFAS.
Ensure that devices that display or output sensitive information in human-readable form are positioned to deter unauthorized individuals from reading the information and/or obtain a privacy screen filter for your monitor.
Ensure that all documents, equipment, and machine-readable media containing sensitive data are cleared, properly marked, and sanitized before being released outside of the Department of Defense.
Protect Common Access Card (CAC) and/or personal identification number (PIN). Do not record, write or display PINs at any time. PINs will be kept confidential and are not to be shared with anyone. Only the individual will have knowledge of the login ID and PIN combination. This unique login ID and PIN combination will be used as the basis for holding the individual accountable for actions associated with their login ID. PINs shall not be composed of easily guessed names or personally related items such as children's or spouse's names addresses, etc. If you believe your PIN has been compromised, promptly change the PIN and immediately notify the Information System Security Manager (ISSM).

Personally Identifiable Information (PII):

You may be granted access to personal information about an individual that identifies, links, relates, or is unique to, or describes him or her, e.g., name, phone numbers, rank/grade. Such information is also known as personally identifiable information (PII).

Users Shall:

Comply with DFAS policies for safeguarding and protecting PII.
Follow DFAS policies and procedures for reporting a PII breach.

Administrative and Privileged users shall:

Utilize public key (PK)-enabled government owned computers while accessing DoD systems for administrative and/or privileged use.
Connect to the application system via DFAS Network.

If you have any questions or comments about the information presented here, please contact the System Manager.

Information Types Subject to Gathering:

Social Security Number (SSN) (full or in any form)
Birth Date
Child Information
Citizenship
Disability Information
DoD ID Number
Driver's License
Employment Information
Financial Information
Gender/Gender Identification
Home/Cell Phone
Law Enforcement Information
Legal Status
Mailing/Home Address
Marital Status
Medical Information
Military Records
Mother's Middle/Maiden Name
Name(s)
Official Duty Address
Official Duty Telephone Number
Other ID Number
Personal E-mail Address
Place of Birth
Position/Title
Protected Health Information (PHI)
Race/Ethnicity
Rank/Grade
Work E-mail Address
In addition to the above, other data elements may be requested or required in the course of researching and responding to ticket submissions.