Batch Matching and 

Continuous Monitoring

Implementation Guide

January 2024 
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

1

Table of Contents

SECTION 1: INTRODUCTION TO DO NOT PAY BULK FILE PROCESS ............................ 3

Section 1.1 Do Not Pay Background...........................................................................................3

Section 1.2 Document Purpose ...................................................................................................3

SECTION 2: PRE-PAYMENT BULK MATCHING IN DNP..................................................... 4

Section 2.1 What is Batch Matching? .........................................................................................4

Section 2.2 What is Continuous Monitoring? .............................................................................4

Section 2.3 What are the Similarities Between Batch Matching and Continuous Monitoring? .4

Section 2.4 What are the Differences Between Batch Matching and Continuous Monitoring? .5

Section 2.5 What are the Benefits of Bulk Matching? ................................................................6

SECTION 3: AGENCY PAYMENT PROCESS .......................................................................... 7

Section 3.1 What Type of Payments Does Your Agency/Program Disburse?............................7

Section 3.2 Why Might Your Agency Benefit from Pre-payment Bulk Matching in DNP?......7

Section 3.3 What are Your Current Payment Eligibility Requirements?....................................7

Section 3.4 What is the Timing of Your Current Payment Eligibility Checks 

and Internal Controls?.............................................................................................................7

Section 3.5 How Does Your Program Handle Payment Eligibility Related Data?.....................8

Section 3.6 Who is Responsible for Performing Payment Eligibility Checks? ..........................8

Section 3.7 What is Your Current Process for Verifying Payment Eligibility?..........................8

SECTION 4: IMPLEMENTATION CONSIDERATIONS .......................................................... 9

Section 4.1 Timing – File/Match Results....................................................................................9

Section 4.2 File Size Considerations...........................................................................................9

Section 4.3 File Errors and Communications............................................................................10

Section 4.4 File Naming Errors.................................................................................................10

Section 4.5 Export Details.........................................................................................................10

SECTION 5: IMPLEMENTATION PROCESS – OVERVIEW................................................ 11

Section 5.1 Bulk Matching Discussion and Paperwork Steps...................................................11

Section 5.2 Secure File Transfer Connection Steps..................................................................11

Section 5.3 Final Implementation Steps....................................................................................11

SECTION 6: IMPLEMENTATION PROCESS – DETAILED STEPS ..................................... 12

Section 6.1 Bulk Matching Discussion and Paperwork Steps...................................................12
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

2

Section 6.2 Secure File Transfer Connection Steps..................................................................12

Section 6.3 Final Implementation Steps....................................................................................13

SECTION 7: LEGAL/PRIVACY CONCERNS ......................................................................... 14

SECTION 8: FREQUENTLY ASKED QUESTIONS (FAQs)................................................... 15

SECTION 9: IMPLEMENTATION GUIDE .............................................................................. 17

Section 9.1 Input File Layout....................................................................................................17

Section 9.1.1 Overview .......................................................................................................17

Section 9.1.2 Requirements.................................................................................................17

Section 9.1.3 Standard Header Layout................................................................................19

Section 9.1.4 Standard Trailer Layout.................................................................................21

Section 9.1.5 Standard Master File (Vendor/Payee) Layout – Continuous Monitoring .....22

Section 9.1.6 Standard Payment File Layout – Batch Matching.........................................27

Section 9.1.7 File Naming Convention ...............................................................................34

Section 9.2 Output File Layout .................................................................................................37

Section 9.2.1 Matched Results File Output Layout (for download from the Portal) ..........37

Section 9.2.2 Payee (Continuous Monitoring) File Output.................................................37

Section 9.2.3 Payment & Batch Matching File Output.......................................................41

Section 9.2.4 File Output Quick Reference Guide..............................................................45

Section 10.1 Test Input File Format Examples for Each Delimiter Type.................................46

Section 10.2 Test Output File Format Examples for Each Delimiter Type ..............................46

Section 10.3 Visual Description of Production File Name Examples ......................................47

Section 10.4 Paperwork Requirements .....................................................................................49

Section 10.4.1 DNP Form ...................................................................................................49

Section 10.4.2 Access Group Form.....................................................................................49

Section 10.4.3 File Association Form .................................................................................49

Section 10.4.4 User Enrollment Form.................................................................................49

Section 10.5 Contact Information .............................................................................................49
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

3 

SECTION 1: INTRODUCTION TO DO NOT PAY BULK FILE 

PROCESS

Section 1.1 Do Not Pay Background

Do Not Pay (DNP) operates a resource dedicated to assisting federal agencies and federally 

funded, state-administered programs in preventing and detecting improper payments. DNP’s 

services are no-cost to agencies and state programs. DNP provides centralized access to a 

variety of relevant data sources for verifying payment and award eligibility through data 

matching in the DNP Portal. DNP also provides customized data analytics services to help 

agencies and state programs detect fraud, waste, and abuse. 

DNP is authorized and governed by the Payment Integrity Information Act of 2019 (PIIA) and 

several Office of Management and Budget (OMB) memoranda and circulars. OMB designated 

the Department of the Treasury to host the Working System to assist federal agencies in 

identifying and preventing improper payments. The Bureau of the Fiscal Service (Fiscal 

Service) operates the DNP Business Center.

DNP’s goals are to:

• provide timely, accurate, and actionable information about payees and payments to assist 

customers in identifying, preventing, and stopping improper payments, 

• develop and assist customers in implementing cutting-edge techniques to protect the 

integrity of payments and awards, 

• innovate and introduce new tools, technologies, and strategies to support customers in 

identifying and preventing a wide variety of improper payments. 

Section 1.2 Document Purpose

This DNP Batch Matching and Continuous Monitoring Implementation Guide is intended to 

offer agencies, states, and programs a complete set of technical specifications and requirements 

for establishing Batch Matching and Continuous Monitoring files for matches against approved 

data sources. This guide should give agencies, states, and programs the ability to talk through 

decisions with those who will be responsible for creating the bulk files for matching in the DNP 

Portal. 
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

4 

SECTION 2: PRE-PAYMENT BULK MATCHING IN DNP

Section 2.1 What is Batch Matching?

Batch Matching allows an agency to send a payment file with multiple records over a secure 

connection to the DNP Portal for matching against approved data sources. If you submit the file 

by 5:00 p.m. Central Time, the match results are available for review in the Portal the next 

business day. Batch Matching consists of multiple payment files sent to DNP for screening prior 

to payment disbursement (i.e., pre-payment). The agency may determine the cadence at which to 

send these files to DNP for matching, with results readily available for viewing in the Portal the 

next business day. 

Section 2.2 What is Continuous Monitoring?

Continuous Monitoring allows a comparison of an agency payee file against approved data 

sources based on a specified frequency, such as bi-weekly, monthly, yearly, etc. The DNP data 

sources are refreshed regularly and will continuously match the file to the data sources when 

there is an update to either the agency file or to a data source. This provides continuously 

updating match information when the file or data source is refreshed, rather than a single, onetime match. Continuous Monitoring is intended to assist with both pre-award and pre-payment 

checks.

Section 2.3 What are the Similarities Between Batch Matching and 

Continuous Monitoring?

 Automated Matching: Both processes involve an agency sending data to DNP on an 

established cadence to receive automated next-day bulk record matching against DNP 

data sources.

 Pre-Award/Payment Checks: Both processes are intended to match (potential) payee 

information against DNP data sources in a pre-award or pre-payment capacity, for the 

purpose of preventing and detecting improper payments. Selected data sources should 

align with your agency’s business rules for payment eligibility.

 Secure Connection between Agency and DNP: A secure file transfer connection, such as 

Secure File Transfer Protocol (SFTP) or Connect:Direct, ensures that data is shared 

securely between an agency and DNP. 

 Results Available in the DNP Portal for Download: Match results against authorized data 

sources are available for viewing in the DNP Portal the next business day after receiving 

the file.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

5 

Section 2.4 What are the Differences Between Batch Matching and 

Continuous Monitoring?

 Payees vs. Payments: A Batch Matching file contains payment-level data (including 

payment amount), while a Continuous Monitoring file contains payee-level data.

 Frequency of Matching: A Batch Matching file is matched only once to the available 

data sources at the time of DNP receiving the payment data, while a Continuous 

Monitoring file is matched any time there is an update to either the agency file or to the 

data source.

 Number of Active Files: Previous versions of Batch Matching files are available for 

viewing in the Portal, while only one current Continuous Monitoring file is available for 

viewing at any time. 

Batch Matching Continuous Monitoring

Timing Pre-award/pre-payment Pre-award/pre-payment 

Data Sources Any approved source Any approved source 

Matched Data 

Type

Payment data submitted by 

agency

Payee data submitted by 

agency

Timing of Match At time of file submission At time of file submission or 

database is updated 

High Impacts to 

Programs that 

Need to Verify

Eligibility of 

payments/payees when this 

list changes frequently

Eligibility of payees when 

this list does not change 

frequently or continued 

eligibility of payees

Example of Agency 

Using

Batch Matching to verify 

eligibility of multiple 

applicants at a time, before 

loans are approved

Continuous Monitoring to 

verify continued eligibility of 

vendors before new or 

renewing contracts
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

6 

Section 2.5 What are the Benefits of Bulk Matching? 

 Automated Matching: Once a secure file transfer process has been established, data is 

shared from your agency to DNP at a specified cadence. If a file is received by 5:00 p.m. 

Central Time, the match results are automatically available for review in the Portal the 

next business day. 

 Easy Set-Up: Fiscal Service IT resources help guide you through the process of 

establishing a secure file transfer process to share data with DNP.

 Secure Data Transmission: A secure file transfer connection between your agency and 

the Fiscal Service ensures that data with sensitive personally identifiable information 

(PII) can be transmitted securely for matching in the DNP Portal.

 Unlimited Access: An unlimited number of individuals can be enrolled to access the 

DNP Portal and view the match results of a Batch Matching or Continuous Monitoring 

process.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

7

SECTION 3: AGENCY PAYMENT PROCESS

A Bulk Matching process through DNP can be a valuable component of your payment eligibility 

process. By increasing the variety of data sources you are screening against or the 

frequency/timing of these checks, you can strengthen your agency’s internal controls for 

payments. The following items are questions to consider when preparing to set up a Bulk 

Matching process through DNP.

Section 3.1 What Type of Payments Does Your Agency/Program Disburse?

The type of payments your agency makes will determine which data sources you will need to 

access through the DNP Portal. Depending on the types of payments you would like to screen in 

DNP, your agency may benefit from establishing multiple Bulk Matching processes. For 

example, if your agency may want to differentiate between screening vendor payments and travel 

payments, since the eligibility criteria for each type of payment are likely different.

Section 3.2 Why Might Your Agency Benefit from Pre-payment Bulk 

Matching in DNP?

Your agency may be exploring methods to automate pre-award or pre-payment eligibility 

verification. An example includes ensuring ongoing eligibility for vendors that your agency has 

contracted with or determining beneficiary eligibility prior to award/payment.

Section 3.3 What are Your Current Payment Eligibility Requirements?

Your agency may be required to reference a specific data source in order to determine payment 

eligibility. DNP offers the ability to automate these eligibility checks, as well as to consolidate 

access to a variety of helpful data sources. Consider your current payment eligibility

requirements, as well as future internal control goals, in order to determine which data sources 

are appropriate to match against to strengthen your payment verification and improper payment 

processes.

Section 3.4 What is the Timing of Your Current Payment Eligibility Checks 

and Internal Controls?

Bulk Matching with DNP is intended to be available as a pre-award or pre-payment tool for 

verifying payment eligibility and identifying/preventing improper payments. However, it is 

crucial to consider the length of your payment lifecycle when determining ways to strengthen 

internal controls; this consideration may determine how often to implement data source 

screening through DNP.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

8 

Section 3.5 How Does Your Program Handle Payment Eligibility Related 

Data?

Matches of your data against approved data sources from the Bulk Matching process with DNP

may be exported into various file formats, including CSV, Pipe Delimited, and Fixed Width. 

Any individual enrolled in the DNP program within the appropriate access group can export this 

information. 

Section 3.6 Who is Responsible for Performing Payment Eligibility Checks?

The agency is ultimately responsible for performing payment eligibility checks and making final 

determinations. Enrolled users are able to access the Portal to review match results against 

authorized data sources in order to perform payment eligibility checks according to their 

agency’s business rules and eligibility requirements.

Section 3.7 What is Your Current Process for Verifying Payment Eligibility?

These are questions that need to be considered for each step in the payment lifecycle:

• Pre-Award: How are potential payees, recipients, and beneficiaries screened for 

eligibility? What are the eligibility requirements to receive a payment? How often must 

these requirements be met?

• Pre-Payment: Are verified payees, recipients, and beneficiaries monitored or screened 

prior to payment for eligibility? Are these eligibility checks performed on an ongoing or 

continuous basis? What criteria need to be regularly screened to ensure proper payment 

eligibility?

• At Time of Payment: Are your payments disbursed by the Department of the Treasury 

through the Payment Automation Manager (PAM)? Does your program work with a 

Shared Service Provider (SSP) to disburse payments? How are payees screened at the 

time of payment to ensure payment eligibility? What happens to the payment if a payee 

does not meet the specific payment eligibility criteria at the time of payment?

• Post-Payment: Are payments reviewed after disbursements for any anomalies, 

duplications, missing data, or incorrect values? What kind of analytics are applied to 

your program’s payment data after disbursement? If improper payments are identified, 

what does the recoupment and recovery process look like? 
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

9

SECTION 4: IMPLEMENTATION CONSIDERATIONS

When your agency is preparing to set up a Bulk Matching file with Do Not Pay (DNP), there are 

several logistical considerations to keep in mind. These guidelines may help you to prepare for 

the functional process of interacting with DNP and interacting with the match results.

Section 4.1 Timing – File/Match Results

• For Bulk Matching files that are received by 5:00 p.m. Central Time, match results are

available for review in the DNP Portal the next business day.

• Depending on your specific payment eligibility determination and disbursement 

processes, the timing and cadence of sending files for matching in the Portal is a key 

consideration. At its most frequent cadence, Bulk Matching files can be sent to DNP on a 

daily basis.

File Selection Screen in the Batch Matching Functionality: This screen shows a record of the Batch Matching files that 

have been received by DNP and indicates a date and timestamps for when the files were received and matched in the 

Portal.

Section 4.2 File Size Considerations

While DNP’s file input size limits are robust, there are restrictions on the number of matches that 

can be exported out of the Portal.

• In the event a file has more than 50,000 matches, users are prompted to export their 

matches to a downloadable format (rather than view them directly in the Portal). The 

Portal user interface does not display more than 50,000 matches.

• In the event a file has more than 200,000 matches, users who attempt to export all 

matches receive a dialog box letting them know which matches (by match quality) are

unable to be exported. If these matches need to be reviewed, you may contact your 

Agency Specialist for next steps on receiving this information.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

10 

Export Limit Exceeded Warning Window: If a Batch Matching or Continuous Monitoring file includes more than 200,000 

matches, the agency will need to export by match level category or coordinate with your Agency Specialist to request an 

export outside of the Portal.

Section 4.3 File Errors and Communications

• If an error occurs while transmitting a Bulk Matching file to DNP, the file will not be 

loaded into the Portal for matching. This will occur until the error is resolved and the 

corrected file is resubmitted.

• There are various errors that can occur when transferring a file to DNP. When an error 

occurs, the DNP Application Operations team collaborates with the Agency Specialist to 

communicate the error. When an error occurs, your agency will be contacted by the 

Agency Specialist with more information about the error and course of remedy, as well as 

the name of the file that failed to load.

Section 4.4 File Naming Errors

A Bulk Matching file name must meet specific naming criteria in order to be loaded into the 

Portal for matching. If a file name does not meet this criterion, it will produce an error and will 

not be loaded into the Portal for matching. The file name must be corrected, with a new file 

resubmitted, before it will be accepted. (Please see Section 9.1.7 to learn about the required 

standard File Naming Convention.) 

Note: A Bulk matching file transmitted to the Portal must be dated with the current date of transmission. Files with a date 

node beyond the current date of transmission will produce an error and will not be loaded into the Portal for matching.

Section 4.5 Export Details

Match results may be exported from the Portal in three distinct file formats: 1) CSV, 2) Pipe 

Delimited, or 3) Fixed Width.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

11 

SECTION 5: IMPLEMENTATION PROCESS – OVERVIEW

The following steps outline the process of setting up a Batch Matching or Continuous 

Monitoring File between your agency and DNP. Further details about the technical file 

specifications may be found in the Implementation Guide section. (Please see Section 9.1.7 to 

learn about the technical file specifications for a Batch Matching or Continuous Monitoring 

file.) 

Section 5.1 Bulk Matching Discussion and Paperwork Steps

Step 1: Agency Specialist schedules call to discuss Bulk Matching file details.

Step 2: Onboarding Specialist sends File Association Form to the agency. 

Step 3: Agency signs and returns the File Association Form to Onboarding Specialist. 

Step 4: Onboarding Specialist processes the File Association Form.

Section 5.2 Secure File Transfer Connection Steps

Step 5: Agency works with the Fiscal Service File Transfer Team resources to establish a secure 

file transfer connection. 

Section 5.3 Final Implementation Steps

Step 6: Agency tests connection.

Step 7: Agency sends first iteration of file to DNP via secure file transfer connection. 

Step 8: Agency can view relevant match information in the Portal. 
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

12

SECTION 6: IMPLEMENTATION PROCESS – DETAILED 

STEPS

Section 6.1 Bulk Matching Discussion and Paperwork Steps

Step 1: Agency Specialist schedules a call to discuss Bulk Matching file details.

If an agency is interested in establishing a Bulk Matching process with DNP, they will need to 

meet with the Agency Specialist or Agency Lead to discuss the prospective file. This 

conversation will include how the file will be used, the timing of the file, and general details 

about the file specifications.

Step 2: Onboarding Specialist sends File Association Form to the agency.

After the agency provides the specific file details for the prospective Bulk Matching file, the 

Onboarding Specialist will create a File Association Form that will need to be signed and 

returned by the appropriate Access Group Administrator. This form will document the file 

details and will serve as the official acknowledgement of the Bulk Matching process with DNP.

Step 3: Agency signs and returns the File Association Form to Onboarding Specialist.

After receiving the File Association Form from the Onboarding Specialist, the appropriate 

Access Group Administrator will need to review, sign, date, and return the form via email in 

PDF format. If preferred, digital signatures are permitted; manual signatures are also permitted

via scanning and emailing in PDF format.

Step 4: DNP processes the File Association Form.

After receiving the signed File Association Form from the appropriate Access Group 

Administrator, the Agency Specialist will work with the Onboarding Specialist to process the 

form. This will ensure that the DNP process is set-up to receive the file after a secure file 

transfer connection is established.

Section 6.2 Secure File Transfer Connection Steps

Step 5: Agency works with the Fiscal Service File Transfer Team resources to establish a 

secure file transfer connection.

To send and receive data containing sensitive personally identifiable information (PII) with 

DNP, an agency is required to work with the Fiscal Service File Transfer Team resources to 

establish a secure file transfer connection: SFTP or Connect:Direct, which requires additional 

forms and a longer processing time. This connection is necessary for the agency and DNP to 

share and receive data with sensitive PII, which cannot be shared over unsecure connections such 

as email.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

13

The preferred connection is Secure File Transfer Protocol or SFTP. The agency will need to 

provide a point of contact, an IP address or range, and information on who will be accessing the 

SFTP.

For SFTP, the agency will use a client to connect to the Fiscal Service SFTP server. If you do not 

already have an internal SFTP client that your organization uses, WinSCP is a free and supported 

option.

Step 6: Agency tests connection.

Once the Fiscal Service File Transfer Team configure the agency’s connection, the agency will 

need to test their connection. When sending a test file, put “.TST” or “.TEST” at the end of the 

file to indicate it is a test file. When sending files to DNP, put them in the Inbound folder. If 

DNP will be sending you files, they will be located in the Outbound folder.

Section 6.3 Final Implementation Steps

Step 7: Agency sends first iteration of file to DNP via the Secure File Transfer Connection.

After the File Association Form has been processed and the SFTP connection with the Fiscal 

Service File Transfer Team has been established and tested, the agency may proceed with 

sending the first iteration of the Bulk Matching file to DNP for matching. With SFTP, agencies 

can automate the data files they want sent for frequent or reoccurring transfers. 

Step 8: Agency can view relevant match information in the Portal.

Once the Bulk Matching file has been successfully received by DNP (if received by 5:00 p.m.

Central Time), relevant match results are available in the Portal the next business day. Portal 

users enrolled with the appropriate access group will be permitted to view match results from the 

Bulk Matching file against approved data sources.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

14

SECTION 7: LEGAL/PRIVACY CONCERNS

A request to access any data source in the DNP Portal must be reviewed and approved by Fiscal 

Service Legal. Use of data sources must be related to the purpose of preventing and detecting

improper payments. Depending on the data sources that you select, and the reasons you intend to 

access the data sources, additional feedback may be requested to better understand the intended 

usage of the data. In some cases, a Computer Matching Agreement (CMA) may be required to

access specific data sources using the Bulk Matching functionality in the Portal. Your Agency 

Lead and Agency Specialist are available to assist you with the process of completing the DNP 

Form (Initial Questions application) to request the data sources contained in the Portal. The DNP 

Privacy Analyst is available to support with any requirements if a CMA is determined to be 

necessary before receiving access to approved data sources.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

15 

SECTION 8: FREQUENTLY ASKED QUESTIONS (FAQs)

What happens if there is an error with my Bulk Matching file?

The DNP Application Operations team will communicate with your Agency Specialist if any 

errors occur with a Bulk Matching file. The Agency Specialist will call or email your listed 

technical contact to let them know about the error, and any specific details that have been 

identified. After the issue has been resolved, the Agency Specialist will work with the DNP

Application Operations team to communicate the resolution.

What kinds of errors can occur with a Bulk Matching file?

Several types of errors can cause a Bulk Matching file not to load to the Portal for matching. If a 

file’s name does not adhere to the standard file naming convention, then the file will fail to load 

to the Portal for matching. A file may also fail to load if the data does not align with the standard 

format for the data fields. (Please see Section 9.1.7 to learn about the standard file naming 

convention and standard format for data fields.)

How do I request additional data sources for a Bulk Matching file?

Access to all data sources in the Portal must be reviewed and authorized by Fiscal Service Legal. 

You will need to complete and submit the DNP Form through Salesforce. The application 

allows you to select the data sources that would be useful for your payment eligibility and 

improper payment activities. Depending on the data sources you select, you may need to provide 

additional details on how you plan to use the data sources in your business activities. Please 

coordinate with your Agency Lead and Agency Specialist to initiate the DNP Form process.

After approval for matching against more data sources for a Batch Matching file, how do I 

add these data sources to an existing file?

You will need to have an Access Group Administrator sign and date a File Association Form to 

add new data sources. Please coordinate with your Agency Lead and Agency Specialist to 

initiate the File Association Form process.

Can I have more than one Bulk Matching file?

Yes. An agency or program may establish multiple Bulk Matching files to strengthen their 

payment eligibility and internal controls processes. Files may vary by the data they contain, the 

timing of the matches, and the data sources they match against.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

16

How do I remove a Bulk Matching file that I no longer need?

You will need to have an Access Group Administrator sign and date a File Association Form to 

deactivate an existing Bulk Matching file. Please coordinate with your Agency Lead and 

Agency Specialist to initiate the File Association Form process.

Who do I contact to troubleshoot secure connection issues?

If you experience issues with a new or existing secure connection for transmitting the Bulk 

Matching file from your agency to DNP, please contact your Agency Lead and Agency 

Specialist. They will coordinate a conversation with the Fiscal Service File Transfer team to 

assist with troubleshooting the connection.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

17 

SECTION 9: IMPLEMENTATION GUIDE

Section 9.1 Input File Layout

Section 9.1.1 Overview 

The purpose of this section is to outline the standard file format for Bulk Matching data files sent 

to the Portal for matching activities. Bulk Matching data files would be processed and used for 

either Batch Matching, Continuous Monitoring, or Data Analytics purposes. 

There are two types of Bulk Matching data files that can be sent to the Portal:

1. Master File (Vendor/Payee/Beneficiary) (i.e., Continuous Monitoring): This type 

of file contains a master list of information about a Vendor (a business), or a 

Payee/Beneficiary/Applicant (an individual). It is generally more static, with changes 

being new additions, deletions, or name/address updates. 

2. Payment File (i.e., Batch Matching): This type of file contains payment 

information, documenting what has been or is about to be paid to the Payee. 

Generally the file contains a payee name, payment amount, purpose of payment, and 

the date of payment. A payment file covers a period of time (usually a month). All 

payments in the file are only related to that particular time frame. 

Section 9.1.2 Requirements

File Formats: Bulk Matching files can be accepted by DNP in one of three file formats:

1. Mainframe – fixed length with standard layout provided 

2. Others – tab, comma, pipe delimited

3. XML – tagged file 

The first line of the xml file should be:

<?xml version=”1.0” encoding=”ISO-8859-1”?>

Note: All Header, Trailer, PayeeDetail, and PaymentDetail records need to be enclosed in

<Records>

.....

... 

... 

</Records>
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

18 

Specific File Name:

See “Section 9.1.7: File Naming Convention” for more details.

Default Field Data:

If no information is available for a character field, place a space in the field.

If no information is available for a numeric field, place a zero in the field.

Required Data: 

1. One or more of these - SSN/TIN/EIN or UEI (SAM) AND

2. Business or Person Name AND

3. Agency Identifier - Agency Location Code (ALC)

Note: The DNP Technical Team requests that the sending application not be set to automatically truncate data fields or 

eliminate valuable information until there is a chance to evaluate the issue and make recommendations. 
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

19 

Section 9.1.3 Standard Header Layout 

This section specifies the layout and format of the first record in the file.

XML TagName: Header

Column Name Data 

Type

Field 

Size

Fixed 

Length 

Offset

FMS

XML TagName

XML 

Repres

entatio

n Class

FMS 

Schema 

Source

Column Description

Record Code Character 1 1 RecordCode Code DO NOT 

PAY

Record Identifier - File Header Record. Value is: ‘H’.

File Provider 

Agency 

Location Code

Character 8 2 AgencyLocation

Code

Code FMS XML ALC for Agency submitting file.

DNP Standard 

File Version

Character 5 10 VersionNumber Text FMS XML Value is: ‘1.0’.

File Begin Date Character 10 15 StartDate Date FMS XML Accepted date formats: ‘YYYY-MM-DD’, 

‘YYYY/MM/DD’, or ‘YYYY.MM.DD’.

This field describes the starting point of the dataset and 

should be a valid date. For a Payment file, this would 

be the beginning of a month or period. For a 

Vendor/Payee Master file (i.e., Continuous Monitoring 

file), default to the original system implementation 

date, or ‘2000-01-01’.

Default to a single zero if no data is available.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

20 

Column Name Data 

Type

Field 

Size

Fixed 

Length 

Offset

FMS

XML TagName

XML 

Repres

entatio

n Class

FMS 

Schema 

Source

Column Description

File Through 

Date

Numeric 10 25 EndDate Date FMS XML Accepted date formats: ‘YYYY-MM-DD’, 

‘YYYY/MM/DD’, or ‘YYYY.MM.DD’.

This field describes the ending point of the data and 

should be a valid date. For a payment file, this would 

be the end date of the month or period. For a 

Vendor/Payee Master file (i.e., Continuous Monitoring 

file), it would be the date the data was pulled from the 

originating system.

Default to a single zero if no data is available.

File Expected 

Use Code

Character 15 35 ExpectedUseCo

de

Code DO NOT 

PAY

Values are:

‘BATCH MATCH’ - for payment files.

DNP Application Action: File would be processed 

one time against the DNP Search database.

‘CONTINUOUS’ – for Vendor/Payee Master files.

DNP Application Action: File would be repeatedly 

processed at agreed upon increments until a new 

refresh file is sent, superseding this file.

Continuous 

Monitoring 

Frequency

Character 15 50 ContinuousMon

itoringCode

Code DO NOT 

PAY

Values are: ‘DAILY’, ‘WEEKLY’, or ‘MONTHLY’.

DNP Access 

Group

Character 25 65 AccessGroup Code DO NOT 

PAY

Supply the DNP Access Group (i.e., the group that can

view the results from these files) that has been assigned 

to your Agency.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

21 

Section 9.1.4 Standard Trailer Layout 

This section specifies the layout and format of the last record in the file.

XML TagName: Trailer

Column 

Name

Data 

Type

Field 

Size

Fixed 

Length 

Offset

FMS

XML 

TagName

XML 

Representa

tion Class

FMS 

Schema 

Source

Column Description

Record Code Character 1 1 RecordCode Code DO NOT 

PAY

Record Identifier - File Trailer Record. Value is: ‘T’.

File Total 

Record Count

Numeric 15 2 TotalCount Number FMS XML The total number of ‘P’ or ‘M’ records on the file sent. 

This count excludes any header or trailer rows, as well 

as headings (if included). This count should just be the 

rows that contain the record code of ‘P’ or ‘M’.

File Total 

Payment 

Amount

Numeric 25 17 Amount Amount FMS XML If this is a payment file, supply this amount using all 

numerals, and supply the decimal point (e.g., 

$$$$$$$$.cc) 

Send ‘4321’ interpreted as 4,321.00.

Send ‘4,321’ will fail due to the comma.

Send ’432.1’ interpreted as 432.10.

Default to a single zero if this is a Vendor/Payee 

Master file.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

22 

Section 9.1.5 Standard Master File (Vendor/Payee) Layout – Continuous Monitoring

This section specifies the layout and format of the Continuous Monitoring input file. 

XML TagName: PayeeDetail 

Column Name Data 

Type

Field 

Size

Fixed 

Length 

Offset

FMS

XML TagName

XML 

Repres

entatio

n Class

FMS 

Schema 

Source

Column Description

Record Code Character 1 1 RecordCode Code DO NOT 

PAY

Record Identifier – Master File. Value is: ‘M’.

Payee Identifier Character 50 2 PayeeID Code DO NOT 

PAY

Optional – Agencies’ choice of an identification for 

this record. This could be a Master File Payee number.

Default to a space if no identifier is available.

Agency 

Location Code

Character 8 52 AgencyLocation

Code

Code FMS XML ALC for the Agency owner of this record. Example: 

Fiscal Service submits file for many agencies. Fiscal 

Service ALC would be in the header record, and then 

the data owner agency ALC would be on each record.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

23 

Column Name Data 

Type

Field 

Size

Fixed 

Length 

Offset

FMS

XML TagName

XML 

Repres

entatio

n Class

FMS 

Schema 

Source

Column Description

Tax 

Identification 

Type

Character 4 60 TINCode Code FMS XML 

(TBD) 

Possible values are:

 ‘SSN’ - Social Security Number.

 ‘EIN’ - Employer ID Number (aka Federal 

Employer ID Number or (FEIN)). 

 ‘ITIN’ - Individual Taxpayer ID Numbers are 

issued by the IRS to individuals who are required 

to have a U.S. taxpayer ID number, but who do not 

have, and are not eligible to obtain an SSN. ITINs 

are issued regardless of immigration status, 

because both resident and nonresident aliens may 

have a U.S. filing or report requirement under IRS 

code.

 ‘ATIN’– Adoption Taxpayer ID Number – 

Assigned to an adopted child prior to obtaining an 

SSN.

 ‘PTIN’ – Preparer Taxpayer ID Number.

Default to ‘TIN’ if the Tax Identification Type is 

unknown or unavailable.

Tax 

Identification 

Number (TIN)

Number 9 64 TIN Ident

ifier

FMS XML Tax ID Numbers must be 9 numeric digits long or the 

file will be rejected. Leading or trailing zeros must be 

present.

Business or 

Individual or 

Government

Character 10 73 PartyType Code FMS XML Values are ‘BUSINESS’, ‘INDIVIDUAL’, 

‘GOVERNMENT’ or ‘UNK’. If this is an Individual, 

but operating as a business for your purposes, place the 

word ‘BUSINESS’ in this field. Example would be a 

Sole Proprietorship.

Default to ‘UNK’ if unknown or no data is available.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

24 

Column Name Data 

Type

Field 

Size

Fixed 

Length 

Offset

FMS

XML TagName

XML 

Repres

entatio

n Class

FMS 

Schema 

Source

Column Description

DUNS Number Number 9 83 DUNS_Number Num

ber

FMS XML *The DUNS Number was replaced by the UEI on 

April 4, 2022.

This field will remain, default to a single zero.

Business Name Character 150 92 PartyName Text FMS XML If this is an individual operating a Sole Proprietorship, 

mark the Business or Individual Flag as a 

’BUSINESS’, and place the name information in the 

Person First, Middle, Last, and Suffix Name fields 

below.

Default to a space if this is an individual or no data is 

available.

Business DBA 

Name

Character 150 242 PartyAliasName FMS XML 

(TBD) 

This should only be populated if this is different from 

the Business Name above.

Default to a space if this is an individual or no data is

available.

Person First 

Name

Character 50 392 FirstName Text FMS XML Sole Proprietor’s name or individual’s name.

Default to a space if this is a business or no data is 

available.

Person Middle 

Name

Character 50 442 MiddleName Text FMS XML 

(TBD) 

Sole Proprietor’s name or the individual’s name.

Default to a space if this is a business or no data is 

available.

Person Last 

Name

Character 50 492 SurName Text FMS XML Sole Proprietor’s name or the individual’s name.

Default to a space if this is a business or no data is 

available.

Person Suffix Character 5 542 NameSuffix Text FMS XML 

(TBD) 

Sole Proprietor’s suffix or individual’s suffix.

Default to a space if this is a business or no data is 

available.

Address Line 1 Character 40 547 AddressLine1 Text FMS XML Default to a space if no data is available.

Address Line 2 Character 40 587 AddressLine2 Text FMS XML Default to a space if no data is available.

Address Line 3 Character 40 627 AddressLine3 Text FMS XML Default to a space if no data is available.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

25 

Column Name Data 

Type

Field 

Size

Fixed 

Length 

Offset

FMS

XML TagName

XML 

Repres

entatio

n Class

FMS 

Schema 

Source

Column Description

Address Line 4 Character 40 667 AddressLine4 Text FMS XML Default to a space if no data is available.

City Name Character 50 707 CityName Text FMS XML Default to a space if no data is available.

Postal Code Character 10 757 ForeignPostalCo

de

Code FMS XML Domestic or Foreign.

Default to a space if no data is available.

State Code Character 2 767 StateCode Code FMS XML Use this for U.S./Canada/Territories.

Default to a space if no data is available.

Region Character 50 769 RegionName Code FMS XML Use this for International States or Regions.

Default to a space if no data is available.

Country Code Character 2 819 CountryCode Code FMS XML Must be valid ISO country code.

See https://www.iso.org/obp/ui/#search for a complete 

list of country codes.

Default to a space if no data is available.

Person Date of 

Birth 

Character 10 821 BirthDate Date DO NOT 

PAY

Accepted date formats: ‘YYYY-MM-DD’, 

‘YYYY/MM/DD’, or ‘YYYY.MM.DD’.

Default to a single zero if no data is available.

Person Sex Character 6 831 PersonSex Text DO NOT 

PAY

Values: ‘MALE’, ‘FEMALE’.

Default to a space if no data is available.

Vendor/Payee 

Status

Character 30 837 PartyStatusCode Text DO NOT 

PAY

Value examples: ‘ACTIVE’, ‘INACTIVE’, 

‘REVOKED’, etc.

Default to a space if no data is available.

Phone Type Character 10 867 PhoneTypeCode Code FMS XML 

(TBD) 

Values: ‘HOME’, ‘BUSINESS’, or ‘MOBILE’.

Default to a space if no data is available.

Vendor/Payee 

Phone Number

Character 20 877 PhoneNumber Text FMS XML Area Code and Phone Number (no special characters).

Default to a single zero if no data is available.

Vendor/Payee 

Fax Number

Character 20 897 FaxNumber Text FMS XML 

(TBD) 

Area Code and Phone Number (no special characters).

Default to a single zero if no data is available.

Vendor/Payee 

Email Address

Character 80 917 EmailAddress Text FMS XML Default to a space if no data is available.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

26 

Column Name Data 

Type

Field 

Size

Fixed 

Length 

Offset

FMS

XML TagName

XML 

Repres

entatio

n Class

FMS 

Schema 

Source

Column Description

Vendor/Payee 

Active Date

Character 10 997 PartyActiveDate Date DO NOT 

PAY

Date the Vendor/Payee became active.

Accepted date formats: YYYY-MM-DD; 

YYYY/MM/DD; YYYY.MM.DD.

Default to a single zero if no data is available.

Vendor/Payee 

Expiration Date

Character 10 1007 PartyExpiration

Date

Date DO NOT 

PAY

Date the Vendor/Payee is no longer valid or active.

Accepted date formats: YYYY-MM-DD; 

YYYY/MM/DD; YYYY.MM.DD.

Default to a single zero if no data is available.

Agency Record 

Grouping

Character 30 1017 AgencyRecordG

roup1

Text DO NOT 

PAY

Optional grouping identification for this record. 

Examples: department code, batch/payee classification 

or other grouping.

Default to a space if no data is available.

Agency Record 

Grouping #2

Character 30 1047 AgencyRecordG

roup2

Text DO NOT 

PAY

A second optional field for agency’s choice of 

grouping identification for this record.

Default to a space if no data is available.

Other Agency 

Data

Character 256 1077 TradingPartnerE

xtension

Aggr

egate

FMS XML A third optional field for accepting other agency data 

fields that may be helpful for displaying or researching 

a match by the sending agency.

Default to a space if no data is available.

UEI Character 12 1333 UEI_ID Text FMS XML The Unique Entity Identifier (SAM) for the entity. 

Each UEI consists of 12 alphanumeric characters. 

Example: F847A1795DE4

Default to a space if no data is available.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

27 

Section 9.1.6 Standard Payment File Layout – Batch Matching

This section specifies the layout and format of the Batch Matching input file.

XML TagName: PaymentDetail 

Column Name Data 

Type

Field 

Size

Fixed 

Length 

Offset

FMS

XML TagName

XML 

Repres

entation 

Class

FMS Schema 

Source Column Description

Record Code Character 1 1 RecordCode Code DO NOT 

PAY

Record identifier - payment record. Value is: ‘P’.

Schedule 

Number

Character 14 2 ScheduleNumbe

r 

Text FMS XML Optional schedule number for agency use.

Default to a space if no data is available.

Payment ID Character 50 16 PaymentID Text FMS XML Optional, supplied if agency wants to identify 

payments with an ID that means something to the 

agency.

Default to a space if no data is available.

Agency 

Location Code

Character 8 66 AgencyLocation

Code

Code FMS XML ALC for the Agency owner of this record. Example: 

Fiscal Service submits files for many agencies. Fiscal 

Service ALC would be in the header record, and then 

the data owner agency ALC would be on each record.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

28 

Column Name Data 

Type

Field 

Size

Fixed 

Length 

Offset

FMS

XML TagName

XML 

Repres

entation 

Class

FMS Schema 

Source Column Description

Tax 

Identification 

Type

Character 4 74 TIN_Code Code FMS XML 

(TBD) 

Possible values are:

 ‘SSN’ - Social Security Number

 ‘EIN’ - Employer ID Number (aka Federal 

Employer ID Number or (FEIN)). 

 ‘ITIN’ - Individual Taxpayer ID Numbers are 

issued by the IRS to individuals who are required 

to have a U.S. taxpayer ID number but who do not 

have and are not eligible to obtain an SSN. ITINs 

are issued regardless of immigration status because 

both resident and nonresident aliens may have a 

U.S. filing or report requirement under IRS code.

 ‘ATIN’ - Adoption Taxpayer ID Number – 

Assigned to an adopted child prior to obtaining an 

SSN.

 ‘PTIN’ - Preparer Taxpayer ID Number. If it is 

known whether the Tax Identifier is one of the 

types above, please provide. If the type is not 

known, default field to ‘TIN’.

Default to ‘TIN’ if the Tax Identification Type is 

unknown or unavailable.

Tax 

Identification 

Number

Number 9 78 TIN Ident

ifier

FMS XML Tax ID Numbers must be 9 numeric digits long or the 

file will be rejected. Leading or trailing zeros need to 

be present.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

29 

Column Name Data 

Type

Field 

Size

Fixed 

Length 

Offset

FMS

XML TagName

XML 

Repres

entation 

Class

FMS Schema 

Source Column Description

Business or 

Individual or 

Government

Character 10 87 PartyType Code FMS XML Values are ‘BUSINESS’, ‘INDIVIDUAL’, 

‘GOVERNMENT’ or ‘UNK’. If this is an individual, 

but operating as a business for your purposes, place the 

word ‘BUSINESS’ in this field. Example would be a 

Sole Proprietorship. Default to ‘UNK’ if unknown or 

no data is available.

DUNS Number Number 9 97 DUNS_Number Num

ber

FMS XML *The DUNS Number was replaced by the UEI on 

April 4, 2022.

This field will remain, default to a single zero.

Payee Business 

Name

Character 150 106 OrganizationNa

me

Text FMS XML If this is an individual operating a Sole Proprietorship, 

mark the Business or Individual Flag as a 

’BUSINESS’, and place the name information in the 

Person First, Middle, Last, and Suffix Name fields 

below.

Default to a space if this is an individual or no data is 

available.

Payee Business 

DBA Name

Character 150 256 PartyAliasName Text FMS XML This should only be populated if this is different from 

the Business Name above.

Default to a space if this is an individual or no data is 

available.

Payee First 

Name

Character 50 406 FirstName Text FMS XML Sole Proprietor’s Name or Individual’s Name.

Default to a space if this is a business or no data is 

available.

Payee Middle 

Name

Character 50 456 MiddleName Text DO NOT 

PAY

Sole Proprietor’s Name or Individual’s Name.

Default to a space if this is a business or no data is 

available.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

30 

Column Name Data 

Type

Field 

Size

Fixed 

Length 

Offset

FMS

XML TagName

XML 

Repres

entation 

Class

FMS Schema 

Source Column Description

Payee Last 

Name

Character 50 506 SurName Text FMS XML Sole Proprietor’s Name or Individual’s Name.

Default to a space if this is a business or no data is 

available.

Payee Suffix Character 20 556 NameSuffix Text DO NOT 

PAY

Sole Proprietor’s Name or Individual’s Suffix.

Default to a space if this is a business or no data is 

available.

Payee Address 

Line 1

Character 40 576 AddressLine1 Text FMS XML Default to a space if no data is available.

Payee Address 

Line 2

Character 40 616 AddressLine2 Text FMS XML Default to a space if no data is available.

Payee Address 

Line 3

Character 40 656 AddressLine3 Text FMS XML Default to a space if no data is available.

Payee Address 

Line 4

Character 40 696 AddressLine4 Text FMS XML Default to a space if no data is available.

Payee City 

Name

Character 50 736 CityName Text FMS XML Default to a space if no data is available.

Payee Postal 

Code

Character 10 786 ForeignPostalCo

de

Code FMS XML Domestic or Foreign.

Default to a space if no data is available.

Payee State 

Code 

Character 2 796 StateCode Code FMS XML Use this for International States or Regions.

Default to a space if no data is available.

Region Character 50 798 RegionName Code FMS XML Must be valid ISO country code.

See http://www.iso.org/iso/country_codes.htm for a 

complete list of country codes.

Default to a space if no data is available.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

31 

Column Name Data 

Type

Field 

Size

Fixed 

Length 

Offset

FMS

XML TagName

XML 

Repres

entation 

Class

FMS Schema 

Source Column Description

Payee Country 

Code 

Character 2 848 CountryCode Code FMS XML Must be valid ISO country code.

See http://www.iso.org/iso/country_codes.htm for a 

complete list of country codes.

Default to a space if no data is available.

Payee Date of 

Birth 

Character 10 850 BirthDate Date DO NOT 

PAY

Accepted date formats: ‘YYYY-MM-DD’, 

‘YYYY/MM/DD’, or ‘ YYYY.MM.DD’.

Default to a single zero if no data is available.

Person Sex Character 6 860 PersonSex Text Values: ‘MALE’, ‘FEMALE’.

Default to a space if no data is available.

Phone Type Character 10 866 PhoneTypeCode Code FMS XML 

(TBD) 

Values: ‘HOME’, ‘BUSINESS’, or ‘MOBILE’.

Default to a space if no data is available.

Payee Phone 

Number

Character 20 876 PhoneNumber Text FMS XML Area Code and Phone Number (no special characters).

Default to a single zero if no data is available.

Payee Fax 

Number

Character 20 896 FaxNumber Text FMS XML 

(TBD) 

Area Code and Fax Number (no special characters).

Default to a single zero if no data is available.

Payee Email 

Address

Character 80 916 EmailAddress Text FMS XML Email address.

Default to a space if no data is available.

Payment 

Method Code

Character 5 996 SettlementMech

anism

Code FMS XML 

(TBD)

Values are: ‘CHECK’, ‘WIRE’, or ‘ACH’.

Default to a space if no data is available.

Check Number Character 12 1001 CheckNumber Num

ber

FMS XML 

(TBD) 

Issued check number (includes the check symbol 

number and the check serial number). 

Default to a space if no data is available.

Receiving DFI Numeric 9 1013 ReceivingDFI Num

ber

FMS XML ACH bank routing number of the recipient.

Default to a single zero if no data is available.

Receiver DI Numeric 9 1022 ReceiverDI Num

ber

FMS XML Wire bank routing number of the recipient.

Default to a single zero if no data is available.

DFI Account 

Number

Character 17 1031 DFI_AccountNu

mber

Text FMS XML ACH bank account number of the recipient.

Default to a space if no data is available.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

32 

Column Name Data 

Type

Field 

Size

Fixed 

Length 

Offset

FMS

XML TagName

XML 

Repres

entation 

Class

FMS Schema 

Source Column Description

Beneficiary 

Customer 

Account

Character 34 1048 BeneficiaryCust

omerAccount

Text FMS XML Wire bank account number of the recipient.

Default to a space if no data is available.

IMAD Character 22 1082 IMAD Text FMS XML Input Message Accountability Data (IMAD) - The 

IMAD indicates a unique number that is assigned to a 

transfer upon receipt at the sending financial 

institution.

Default to a space if no data is available.

ACH Payment 

Account 

Indicator

Character 1 1104 ACHPaymentA

cctID

Text DO NOT 

PAY

Values are: ‘S’ = Savings or ‘C’ = Checking.

Default to a space if no data is available.

ACH Trace 

Number

Numeric 15 1105 ACH_TraceNu

mber

Num

ber

FMS XML Default to a single zero if no data is available.

Payment 

Request Date

Character 10 1120 RequestedPaym

entDate

Date FMS XML Accepted date formats: ‘YYYY-MM-DD’, 

‘YYYY/MM/DD’, or ‘YYYY.MM.DD’.

Default to a single zero if no data is available.

Payment 

Cleared Date

Character 10 1130 PaymentCleared

Date

Date DO NOT 

PAY

Accepted date formats: ‘YYYY-MM-DD’, 

‘YYYY/MM/DD’, ‘YYYY.MM.DD’.

Default to a single zero if no data is available.

Payment 

Amount

Numeric 20 1140 Amount Amo

unt

FMS XML Supply this amount using all numerals, and supply the 

decimal point, (e.g., $$$$$$$$.cc.) 

Send ‘4321’ interpreted as 4,321.00.

Send ‘4,321’ will fail due to the comma.

Send ’432.1’ interpreted as 432.10.

Default to a single zero if no data is available.

Payment Status Character 30 1160 PaymentStatus Text DO NOT 

PAY

Such as: ‘PAID’, ‘PENDING’, ‘CANCELLED’.

Default to a space if no data is available.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

33 

Column Name Data 

Type

Field 

Size

Fixed 

Length 

Offset

FMS

XML TagName

XML 

Repres

entation 

Class

FMS Schema 

Source Column Description

Payment Type Character 30 1190 PaymentTypeCo

de

Code FMS XML Default to a space if no data is available.

Agency Record 

Grouping

Character 30 1220 AgencyRecordG

roup1

Text DO NOT 

PAY

Optional grouping identification for this record. 

Examples: department code, batch/payee classification 

or other grouping.

Default to a space if no data is available.

Agency Record 

Grouping #2

Character 30 1250 AgencyRecordG

roup2

Text DO NOT 

PAY

A second optional field for agency’s choice of 

grouping identification for this record.

Default to a space if no data is available.

Other Agency 

Data

Character 256 1280 TradingPartnerE

xtension

Aggr

egate

FMS XML A third optional field for accepting other agency data 

fields that may be helpful for displaying or researching 

a match by the sending agency.

Default to a space if no data is available.

UEI Character 12 1536 UEI_ID Text FMS XML The Unique Entity Identifier (SAM) for the entity. 

Each UEI consists of 12 alphanumeric characters. 

Example: F847A1795DE4

Default to a space if no data is available.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

34

Section 9.1.7 File Naming Convention

The file name of the Bulk Matching file must adhere to a specific standard naming convention. If a file is transmitted that does not 

adhere to this convention, it will fail to load in the Portal. The file name must be established and agreed upon between DNP and the 

agency prior to the signature and acknowledgement of the File Association Form.

• Each node must be separated by a period (.).

• There can be a maximum of only eight characters per node.

• Each node must start with an alpha character.

• There can be a maximum of only 44 characters in the file name total, including node separators.

• Characters allowed in the file name are: Upper-case alpha, numeric, and node separators only.

Full file name example (40 characters):
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

35 

Node Definitions

Node Pos Node Purpose Format Comments Values

1 Application Identifier 'FGVP' Required literal

Valid Value:

'FGVP' is the only valid value

'F' = Fiscal IT

'GV' = Do Not Pay

'P' = Production

2 Environment/Region 

Identifier AX Value identifies target DNPenvironment

Valid Values:

'PR' = Production

'QA' = Quality Assurance or Acceptance

'DV' = Development or Test

3 Organization/Agency 

Identifier AXXX

2-4 character ID must be 

registered in the DNP

application

Valid Examples:

'FMS' = FMS

'BPD' = BPD

'NARA' = NARA

'GSA' = GSA

'VA' = VA

4 File Type AX Type of file being submitted

Valid Values:

'DS' = Data Source or Reference File

'BM' = Batch Matching

'CM' = Continuous Monitoring

5 File Name AXXXX

XXX

Required with one to eight 

characters

Example:

'EPLSFL01'

6 Data Extracted Date 'D'YYM

MDD Date format YYMMDD

Example:

'D' = Date

'D111031' = October 31, 2011

The date the data was pulled from the Agency’s 

system.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

36 

Node Pos Node Purpose Format Comments Values

7 Data Extracted Time 'T'HHM

MSS Time format HHMMSS

Example:

'T' = Time

'T153522' = 3:35:22 pm

The time the data was pulled from the Agency’s 

system.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

37 

Section 9.2 Output File Layout

Section 9.2.1 Matched Results File Output Layout (for download from the Portal)

When viewing the match results from the Portal, only matches to authorized data sources are 

present in this file (the matched results file from a Bulk Matching operation only displays 

records that matched to an authorized data source in the Portal, not all records from the original 

file). The fields below are appended to the Standard Customer Input File or Standard Payment 

File when there is a match to a DNP data source.

Section 9.2.2 Payee (Continuous Monitoring) File Output

Column Name

Start 

Position

End 

Position

Column 

Length

Record Code 1 1 1

Payee Identifier 2 51 50

Agency Location Code 52 59 8

Tax Identification Type 60 63 4

Tax Identification Number (TIN) 64 72 9

Business or Individual or Government 73 82 10

*DUNS Number 83 91 9

Business Name 92 241 150

Business DBA Name 242 391 150

Person Full Name 392 591 200

Person First Name 592 641 50

Person Middle Name 642 691 50

Person Last Name 692 741 50

Person Suffix 742 746 5

Address Line 1 747 786 40

Address Line 2 787 826 40

Address Line 3 827 866 40

Address Line 4 867 906 40

City Name 907 956 50

Postal Code 957 971 15

State Code 972 973 2

Region 974 1023 50

Country Code 1024 1026 3

Person Date of Birth 1027 1036 10

Person Sex 1037 1042 6
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

38 

Column Name

Start 

Position

End 

Position

Column 

Length

Vendor/Payee Status 1043 1072 30

Phone Type 1073 1082 10

Vendor/Payee Phone Number 1083 1102 20

Vendor/Payee Fax Number 1103 1122 20

Vendor/Payee Email Address 1123 1202 80

Vendor/Payee Active Date 1203 1212 10

Vendor/Payee Expiration Date 1213 1222 10

Agency Record Grouping 1223 1252 30

Agency Record Grouping #2 1253 1282 30

Other Agency Data 1283 1538 256

Match Type 1539 1568 30

Match Source 1569 1584 16

Match Level 1585 1602 18

Match Date/Time 1603 1619 17

Matched Party Type Code 1620 1620 1

Matched Tax ID Type Code 1621 1624 4

Matched Tax ID Number 1625 1633 9

Matched Tax ID Type Code (alternate) 1634 1637 4

Matched Tax ID Number (alternate) 1638 1646 9

*Matched DUNS Number 1647 1655 9

Matched Full Name 1656 1855 200

Matched First Name 1856 1930 75

Matched Middle Name 1931 1980 50

Matched Last Name 1981 2030 50

Matched Business Name 2031 2230 200

Matched DBA Business Name 2231 2430 200

Matched Birth Date 2431 2448 18

Matched Death Date 2449 2458 10

Matched List Status Code 2459 2488 30

Matched List Status Code Description 2489 2744 256

Matched List Effective Date 2745 2754 10

SAM Number 2755 2763 9

Exclusion Type 2764 2798 35

Cage Code 2799 2803 5
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

39 

Column Name

Start 

Position

End 

Position

Column 

Length

Reporting Agency 2804 2861 58

National Provider Identifier 2862 2879 18

Waiver Date 2880 2889 10

Waiver State 2890 2891 2

Matched Address Line 1 2892 3041 150

Matched Address Line 2 3042 3191 150

Matched Address Line 3 3192 3341 150

Matched City 3342 3391 50

Matched State Code 3392 3393 2

Matched Zip Code 3394 3408 15

Matched Country Code 3409 3411 3

Cross Reference Name(s) 3412 5431 2020

Whitelist Reason 5432 5481 50

Business Rules Applied 5482 5551 70

Matched Contact Name 5552 5611 60

Matched Phone Number 5612 5641 30

Matched Phone Extension 5642 5651 10

Exemption Type Description 5652 5907 256

Exemption Reinstatement Date 5908 5917 10

Revocation Date 5918 5927 10

Revocation Posting Date 5928 5937 10

Case Number 5938 6193 256

Case Type 6194 6449 256

Collection Code 6450 6454 5

Collection Description 6455 6554 100

UEI 6555 6566 12

Matched UEI 6567 6578 12

Matched Country Description 6579 6628 50

Matched Deductibility Code 6629 6884 256

Matched Tax Year 6885 6888 4

Matched Tax Period Begin Date 6889 6898 10

Matched Tax Period End Date 6899 6908 10

Matched Gross Receipts Not Greater Than 6909 6918 10

Matched Terminated Status 6919 6919 1
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

40 

Column Name

Start 

Position

End 

Position

Column 

Length

Matched Website URL 6920 7175 256

Matched Second Address Type 7176 7200 25

Matched Second Address Line 1 7201 7240 40

Matched Second Address Line 2 7241 7280 40

Matched Second Address City 7281 7330 50

Matched Second Address State 7331 7332 2

Matched Second Address Zip Code 7333 7347 15

Matched Second Address Country Code 7348 7350 3

*The DUNS Number was replaced by the UEI on April 4, 2022.

This field will remain.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

41 

Section 9.2.3 Payment & Batch Matching File Output

Column Name

Start 

Position

End 

Position

Column 

Length

Record Code 1 1 1

Schedule Number 2 15 14

Payment ID 16 65 50

Agency Location Code 66 73 8

Agency Account ID 74 89 16

Payment Identification Code 90 96 7

Tax Identification Type 97 100 4

Tax Identification Number (TIN) 101 109 9

Business or Individual or Government 110 119 10

*DUNS Number 120 128 9

Payee Business Name 129 278 150

Payee Business DBA Name 279 428 150

Payee Full Name 429 628 200

Payee First Name 629 678 50

Payee Middle Name 679 728 50

Payee Last Name 729 778 50

Payee Suffix 779 783 5

Payee Address Line 1 784 823 40

Payee Address Line 2 824 863 40

Payee Address Line 3 864 903 40

Payee Address Line 4 904 943 40

Payee City Name 944 993 50

Payee Postal Code 994 1008 15

Payee State Code 1009 1010 2

Region 1011 1060 50

Payee Country Code 1061 1063 3

Payee Date of Birth 1064 1073 10

Person Sex 1074 1079 6

Phone Type 1080 1089 10

Payee Phone Number 1090 1109 20

Payee Fax Number 1110 1129 20
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

42 

Column Name

Start 

Position

End 

Position

Column 

Length

Payee Email Address 1130 1209 80

Payment Method Code 1210 1214 5

Check Number 1215 1226 12

ACH Bank Routing Number 1227 1235 9

Wire Bank Routing Number 1236 1244 9

ACH Bank Account Number 1245 1261 17

Wire Bank Account Number 1262 1295 34

Input Message Accountability Data 1296 1317 22

ACH Payment Account Indicator 1318 1318 1

ACH Trace Number 1319 1334 16

Payment Request Date 1335 1344 10

Payment Date 1345 1354 10

Payment Amount 1355 1374 20

Payment Status 1375 1404 30

Payment Type 1405 1434 30

Agency Record Grouping 1435 1464 30

Agency Record Grouping #2 1465 1494 30

Other Agency Data 1495 1750 256

Match Type 1751 1780 30

Match Source 1781 1796 16

Match Level 1797 1814 18

Match Date/Time 1815 1831 17

Matched Party Type Code 1832 1832 1

Matched Tax ID Type Code 1833 1836 4

Matched Tax ID Number 1837 1845 9

Matched Tax ID Type Code (alternate) 1846 1849 4

Matched Tax ID Number (alternate) 1850 1858 9

*Matched DUNS Number 1859 1867 9

Matched Full Name 1868 2067 200

Matched First Name 2068 2142 75

Matched Middle Name 2143 2192 50

Matched Last Name 2193 2242 50

Matched Business Name 2243 2442 200

Matched DBA Business Name 2443 2642 200
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

43 

Column Name

Start 

Position

End 

Position

Column 

Length

Matched Birth Date 2643 2660 18

Matched Death Date 2661 2670 10

Matched List Status Code 2671 2700 30

Matched List Status Code Description 2701 2956 256

Matched List Effective Date 2957 2966 10

SAM Number 2967 2975 9

Exclusion Type 2976 3010 35

Cage Code 3011 3015 5

Reporting Agency 3016 3073 58

National Provider Identifier 3074 3091 18

Waiver Date 3092 3101 10

Waiver State 3102 3103 2

Matched Address Line 1 3104 3253 150

Matched Address Line 2 3254 3403 150

Matched Address Line 3 3404 3553 150

Matched City 3554 3603 50

Matched State Code 3604 3605 2

Matched Zip Code 3606 3620 15

Matched Country Code 3621 3623 3

Cross Reference Name(s) 3624 5643 2020

Whitelist Reason 5644 5693 50

Business Rules Applied 5694 5763 70

Estimated Payment Date 5764 5773 10

DOD to Payment Date Difference 5774 5778 5

Payment Adjudication Status 5779 5828 50

Match Adjudication Status 5829 5878 50

Match Adjudication Status Comments 5879 6028 150

Stop Payment Rules Applied 6029 6048 20

DNP Record Payment Owner ALC 6049 6056 8

DNP Record Agency Group Code 6057 6086 30

DNP Record Custom 6087 6814 728

Matched Contact Name 6815 6874 60

Matched Phone Number 6875 6904 30

Matched Phone Extension 6905 6914 10
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

44 

Column Name

Start 

Position

End 

Position

Column 

Length

Exemption Type Description 6915 7170 256

Exemption Reinstatement Date 7171 7180 10

Revocation Date 7181 7190 10

Revocation Posting Date 7191 7200 10

Case Number 7201 7456 256

Case Type 7457 7712 256

Collection Code 7713 7717 5

Collection Description 7718 7817 100

UEI 7818 7829 12

Matched UEI 7830 7841 12

Matched Country Description 7842 7891 50

Matched Deductibility Code 7892 8147 256

Matched Tax Year 8148 8151 4

Matched Tax Period Begin Date 8152 8161 10

Matched Tax Period End Date 8162 8171 10

Matched Gross Receipts Not Greater Than 8172 8181 10

Matched Terminated Status 8182 8182 1

Matched Website URL 8183 8438 256

Matched Second Address Type 8439 8463 25

Matched Second Address Line 1 8464 8503 40

Matched Second Address Line 2 8504 8543 40

Matched Second Address City 8544 8593 50

Matched Second Address State 8594 8595 2

Matched Second Address Zip Code 8596 8610 15

Matched Second Address Country Code 8611 8613 3

*The DUNS Number was replaced by the UEI on April 4, 2022.

This field will remain.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

45 

Section 9.2.4 File Output Quick Reference Guide

Column 

Name Column Description

Match Type Type of Matches:

 Name Match

 TIN + DBA Name Match

 TIN + LAST Name Match

 TIN + NAME Match

 TIN Match

 TIN not in SAM Entity Registration Records

 Name + Middle Initial Match

 DBA Name Match 

 UEI Match

 UEI not in SAM Entity Registration Records

Match Source The DNP data source in which a match was found:

 AIS-OBIT – American InfoSource Obituary

 AIS-PROB – American InfoSource Probate

 ARL – Automatic Revocation List

 CAIVRS - Credit Alert System

 DOD – Department of Defense Death Data

 DOS – Department of State Death Data

 DMF – Death Master File

 DBCK – Treasury Offset Program Debt Check

 SAMENT – System for Award Management Entity Registration Records

 SAM-EXCL-RES – System for Award Management Exclusion Records – Restricted

 SAM-EXCL-PUB – System for Award Management Exclusion Records – Public

 OFAC – Office of Foreign Assets Control

 LEIE-PUB – List of Excluded Individuals and Entities – Public

 LEIE-RES – List of Excluded Individuals and Entities – Restricted

 PUB 78 – Publication 78 Data

 FORM 990-N - IRS Form 990-N (e-Postcard)

Match Level CONCLUSIVE, PROBABLE, or POSSIBLE

Match Date The date and time that the agency file was matched to the data source and the match was 

made.

Matched Party 

Type Code

I – Individual

B – Business

G – Government

U – Unknown

Matched Tax 

ID Type Code

Type of Identifier:

 ATIN - Adoption Taxpayer Identification Number

 EIN - Employer Identification Number

 ITIN - Individual Taxpayer Identification Number

 PTIN - Preparer Taxpayer Identification Number

 SSN - Social Security Number

 TIN - Tax Identification Number (used if one of the other codes is not known) 
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

46 

SECTION 10: APPENDIX

Section 10.1 Test Input File Format Examples for Each Delimiter Type

• Payee & Payment

• XLS/Tab Delimited/XML/Fixed Width

Section 10.2 Test Output File Format Examples for Each Delimiter Type

• Payee & Payment

• XLS/Tab Delimited/XML/Fixed Width

Section 10.3 Visual Description of Production File Name Examples 

Section 10.4 Paperwork Requirements

• Section 10.4.1: DNP Form 

• Section 10.4.2: Access Group Form 

• Section 10.4.3: File Association Form 

• Section 10.4.4: User Enrollment Form 

Section 10.5 Contact Information 

Section 10.1 Test Input File Format Examples for Each Delimiter Type

Test input files for different formats of both Batch Matching (Payment) and Continuous 

Monitoring (Payee) files are available upon request.

Section 10.2 Test Output File Format Examples for Each Delimiter Type

Test output files for different formats of both Batch Matching (Payment) and Continuous 

Monitoring (Payee) files are available upon request.
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

47

Section 10.3 Visual Description of Production File Name Examples

FGVP.PR.GOV.BM.GOVPYMT.D010120.T112233

FGVP.PR.GOV.CM.GOVPAYEE.D010220.T223344
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

48

FGVP.PR.TREAS.BM.TRESPMT.D020120.T121212

FGVP.PR.TREAS.CM.TRESPAYE.D020220.T121313
DNP Batch Matching and Continuous Monitoring Implementation Guide

Last Updated: January 2024

49 

Section 10.4 Paperwork Requirements

Section 10.4.1 DNP Form 

In order to request access to the Portal for matching activities, the agency is required to complete 

the DNP Form through Salesforce. This DNP Form will contain a record of the data sources the 

agency is requesting access to for the purposes of improper payment prevention and detection as 

well as request the functionalities. The agency will also be required to provide explanations for 

why these requested data sources would strengthen their payment eligibility processes. 

After the DNP Form is completed, the Agency Lead and Agency Specialist will review it to

identify any missing details or required clarifications prior to the final legal analysis. After 

coordinating with the agency program to provide additional changes and revisions, the Agency 

Lead and Agency Specialist will submit the document through Salesforce to Fiscal Service Legal 

for review. 

Section 10.4.2 Access Group Form

After Fiscal Service Legal has completed the review and identified the approved data sources, an 

Access Group Administrator (AGA) for the agency will need to review and sign the Access 

Group Form to accomplish one of two tasks: 1) create a new Access Group in the Portal, and 2) 

update authorized data sources for the Access Group’s Online Search functionality. 

Section 10.4.3 File Association Form

After Fiscal Service Legal has completed the review and identified the approved data sources, an 

Access Group Administrator (AGA) for the agency will need to review and sign the File 

Association Form. This form identifies file specification details, in addition to the approved data 

sources. The Agency Specialist will communicate with the agency to confirm these details, then, 

will email a copy of the File Association Form for review and signature. This form must be 

signed to complete the Bulk Matching set-up process. 

Section 10.4.4 User Enrollment Form

A User Enrollment Form must be completed, reviewed, and signed for each individual that will 

require access to the Portal to view Bulk Matching file results. After the prospective enrollee’s 

contact information is provided to the Agency Specialist, a DNP Onboarding Specialist will send

a User Enrollment Form to the appropriate AGA for review and signature. 

Section 10.5 Contact Information

Do Not Pay Help Desk:

• Phone Number: 855-837-4391 

• Email Address: donotpay@fiscal.treasury.gov

• Website: fiscal.treasury.gov/dnp