Error Code #015

Information Paper:
Error Code #015
Reject Missing/Invalid Fund Code
DEFENSE TRAVEL
MANAGEMENT OFFICE
Defense Business Management System (DBMS) Reject: Missing/Invalid Fund Code
The document is being rejected for the data element IDs Fund Code, which is Table driven per
Appendix G, Table G-3: DBMS. The fund code element in the document LOA does not match an
entry in the table loaded in the accounting system. This element is located in Account Field 5,
Positions 4-5, of the Lines of Accounting (LOA) according to Appendix R.6 DBMS LOA Formats
(DBMS).
Validate this LOA with your Finance Defense Travel Administrator (FDTA) for DBMS accounting
transactions. The corrective action to take for this type of REJECT depends on the source of the
error. The FDTA should verify with the DBMS accounting system to determine where the problem is.
There are two possible reasons:
1. An accounting system table mismatch: the FC in the document is correct, but is not valid in
DBMS.
• The FC is for a future date and has not yet been loaded into the accounting
system.
• The appropriate DBMS tables must first be updated.
• Once the accounting table is updated, an amendment is created, apply the SIGNED or
T-ENTERED stamp, and it will go through the rest of the routing cycle until the
APPROVED stamp is applied. No updates to the document LOA or the organization’s
LOA in DTS is required.
2. The FC in the DTS LOA is incorrect. The erroneous LOA in DTS must be corrected.
• The finance DTA needs to access DTA Maintenance>Lines of Accounting and correct
the erroneous LOA data element. This ensures no new documents are created with the
bad LOA.
• The next step is to either create a new Budget Item or update the existing Budget Item
in the Budget module. Please note that when creating a new Budget Item you cannot
use the same label name as the previous Budget Item. Another option is to “Mass
Update” the single Budget Item, this can be accomplished by inserting a wildcard (*) into
the account field of the erroneous data element. Both the LOA and Budget must have
the same LOA details (including #wildcards) in order for the document to be
APPROVED.
• Create an amendment, remove the incorrect LOA on the Accounting screen, and select
the corrected LOA (which may or may not have the same name). Apply the SIGNED or
T-ENTERED stamp, and process through the routing list until the APPROVED stamp is
applied. The updated LOA will be sent to the accounting system.
Defense Travel Management Office Revised April 2011
This document is controlled and maintained on the www.defensetravel.dod.mil Web site. Printed copies may be obsolete.
Please check revision currency on the web prior to use.

DEFENSE TRAVEL
MANAGEMENT OFFICE
General Accounting and Finance System - Base Level (GAFS-BQ) Reject: Missing/Invalid Fund
Code
GAFS-BQ uses this error code to identify a document rejected for the data element Fund Code (FC),
which is in Account Field 3, Positions 1-2, according to Appendix R.1 Air Force LOA Format (GAFS-
DTS). The FC in the document LOA does not match an entry in the table loaded in the accounting
system.
Validate this LOA with your Finance Defense Travel Administrator (FDTA) for GAFS-BQ transactions.
The corrective action to take for this type of REJECT depends on the source of the error. The FDTA
should verify with the GAFS (BQ) accounting system to determine where the problem is. There are
two possible reasons:
1. An accounting system table mismatch, the FC in the document is correct, but is not valid in
GAFS (BQ).
• The appropriate GAFS-BQ tables must first be updated.
• Once the accounting table is updated, an amendment is created, apply the SIGNED or T-
ENTERED stamp, and it will go through the rest of the routing cycle until the APPROVED
stamp is applied. No updates to the document LOA or the organization’s LOA in DTS is
required.
2. The FC in the DTS LOA is incorrect. The erroneous LOA in DTS must be corrected.
• The finance DTA needs to access DTA Maintenance>Lines of Accounting and correct
the erroneous LOA data element. This ensures no new documents are created with the
bad LOA.
• The next step is to either create a new Budget Item or update the existing Budget Item
in the Budget module. Please note that when creating a new Budget Item you cannot
use the same label name as the previous Budget Item. Another option is to “Mass
Update” the single Budget Item, this can be accomplished by inserting a wildcard (*) into
the account field of the erroneous data element. Both the LOA and Budget must have
the same LOA details (including #wildcards) in order for the document to be
APPROVED.
• Create an amendment, remove the incorrect LOA on the Accounting screen, and select
the corrected LOA (which may or may not have the same name). Apply the SIGNED or
T-ENTERED stamp, and process through the routing list until the APPROVED stamp is
applied. The updated LOA will be sent to the accounting system.
Defense Travel Management Office Revised April 2011
This document is controlled and maintained on the www.defensetravel.dod.mil Web site. Printed copies may be obsolete.
Please check revision currency on the web prior to use.

DEFENSE TRAVEL
MANAGEMENT OFFICE
Standard Accounting Budget and Reporting System (SABRS) Reject: Missing/Invalid Fund
Code
This document rejected for the data element Fund Code (FC) which is in Account Field 6, Positions 7-
8, according to Appendix R.5 USMC LOA Format (SABRS). The FC in the document LOA does not
match an entry in the table loaded in the accounting sys-tem on X Fund Code Table 020 or the
Activity Address Code (Unit Identifier) and Fund Code were not found on CIF Default Table 302 per
Appendix G, Table G-10: SABRS.
Please validate this LOA with your Finance Defense Travel Administrator (FDTA) for SABRS
transactions. The corrective action to take for this type of REJECT depends on the source of the
error. The FDTA should verify with the SABRS accounting system to determine where the problem
is. There are two possible reasons:
1. An accounting system table mismatch, the FC in the document is correct, but is not valid in
SABRS.
• The appropriate SABRS tables must first be updated. Then you must ensure that the
SABRS accounting system has the LOA data element loaded correctly.
• Once the accounting table is updated, an amendment is created, apply the SIGNED or
T-ENTERED stamp, and it will go through the rest of the routing cycle until the
APPROVED stamp is applied. No updates to the document LOA or the organization’s
LOA in DTS is required.
2. The FC in the DTS LOA is incorrect. The erroneous LOA in DTS must be corrected.
• The finance DTA needs to access DTA Maintenance>Lines of Accounting and correct
the erroneous LOA data element. This ensures no new documents are created with the
bad LOA.
• The next step is to either create a new Budget Item or update the existing Budget Item
in the Budget module. Please note that when creating a new Budget Item you cannot
use the same label name as the previous Budget Item. Another option is to “Mass
Update” the single Budget Item, this can be accomplished by inserting a wildcard (*) into
the account field of the erroneous data element. Both the LOA and Budget must have
the same LOA details (including #wildcards) in order for the document to be
APPROVED.
• Create an amendment, remove the incorrect LOA on the Accounting screen, and select
the corrected LOA (which may or may not have the same name). Apply the SIGNED or
T-ENTERED stamp, and process through the routing list until the APPROVED stamp is
applied. The updated LOA will be sent to the accounting system
Defense Travel Management Office Revised April 2011
This document is controlled and maintained on the www.defensetravel.dod.mil Web site. Printed copies may be obsolete.
Please check revision currency on the web prior to use.