How does Portfolio Based Access work?

The National Data Center is pleased to introduce a service to allow our customers faster, more secure access to their Chapter 13 cases - Portfolio Based Access (PBA). With this system, an NDC customer can securely upload a file that directs the NDC security system to allow access to those cases in your portfolio. All NDC data systems simultaneously are granted access - Online/Web, Reporting Services, and Bulk Data Services. You can refresh your Portfolio Access as frequently as possible, 24 hours a day. The Portfolio Access file is very similar to the NDC Request File, so there is nothing new to learn or program to prepare a properly formatted file.,

Quick Details

When you upload a Portfolio Access file to our ftp server we use the records in the file to grant access to trustee cases. Each file should be a complete list of your company's portfolio; we cannot accept 'delta' Access files now. Though we anticipate you will only create a new PBA file when there has been a change to your managed portfolio, it is certainly possible to drop off a file as often as once daily.

The access granted by the import of your PBA file stays in effect until you provide a new PBA file. Thus, we house your portfolio until you refresh it.

What's the difference between the Portfolio Access file and the Request File?

You'll use request files with proper legal documentation to request one-time-only information on a purchased portfolio, or a portfolio under consideration for purchase, or a subset of your existing portfolio. After matching cases from your Request file, a set of output files are created, zipped together, and made available on our secure FTP server, as before. No access to the NDC online systems will be granted due to cases matched via the Request file. Access to your party-in-interest cases can only be granted via a Portfolio Access file. This case access is valid until the next PBA file we receive from you.

Where do I put the Portfolio Access File?

Every NDC customer is assigned a directory on our secure FTP server, and a new subdirectory called PORTFOLIO_ACCESS has been created where PBA files can be dropped in 24 hours a day. They are processed once per day at approximately 2 am (PST)/5am (EST)2 am

I want to update my PBA file – can I send in just the new cases?

The PBA system does not currently support ‘delta’ files, therefore, each PBA file will be matched and the NDC’s internal portfolio of cases for your company will be completely refreshed.

What is the format of the Portfolio Access File?

It is very similar to our NDC Request File. We can provide complete documentation on the format, matching system, and _OUT file of the Request file at any time. See a quick version of the file format below.

What is a Portfolio Based Access file?

For the NDC to import your PBA data, we need an input file from the customer specifying exactly what cases they would like us to lookup in our database. This NDC Portfolio-Based Access File has a format allowing us to try several methods to find matches against our data. The format is as follows:
• A text file with the name structure <customer_defined_string>_PORTFOLIO_ACCESS.txt. For example, you may call the file NDC01123_portfolio_access.txt, or you may call it PORTFOLIO_ACCESS.txt
• The file includes six columns, separated by pipe char '|’, ending with a carriage return.
• Data within each field should not be delimited with quotes
• The format of the file is (using pipe characters):
• <NDC Trustee ID>|<case_num>|<last-4 debtor 1 ssn>|<last-4 debtor 2 ssn>|<customer_supplied_code>
• Note the primary matching routines rely on 1) a combination of the NDC TrusteeID. This input produces the fastest, most accurate matches. Other tests (for example a combination of Debtor1SSN and Case_Num) will be accepted but matches will be less reliable.,
• No header line in the file

The fields are:

  1. NDC Trustee ID - OPTIONAL -   The valid 4-5 character NDC Trustee ID; please reference the NDC Trustee IDs document to list valid trustee IDs. Please see NDC_TRUSTEE_LIST for a complete list of all Trustees that participate with the NDC and each trustee’s NDC TrusteeID
  2. Case_Num ,- REQUIRED -   Only numeric values allowed. Please omit any dashes, commas or other alpha characters. Also, the case numbers as supplied to the NDC by our Data Providers can differ from the case number tracked in the customer’s database, often by leading zeros. The NDC does not modify or correct any information as it is delivered to us from our Data Providers. Max 9 characters Note: Normally, NDC Case numbers are only seven chars however there are a few trustees that will prepend additional digits to the court case number to label a case in their internal systems uniquely. This is normally due to the Trustee having to serve in two different courts, each using different Pacer systems, and the additional digits help the Trustee keep track of what court the case originates.
  3. Debtor 1 SSNlast 4last 4 - OPTIONAL (only if 1 & 2 above are supplied) -   The last-4 SSNs as recorded in the Trustee’s data for Debtor 1. Only numeric values are allowed. Please omit any dashes, commas or other alpha characters. Max 4 characters
  4. Debtor 2 SSNlast 4 - OPTIONAL -    The last 4 SSNs are recorded in the Trustee’s data for Debtor 2. Only numeric values are allowed, please omit any dashes, commas or other alpha characters. Max 4 characters ,
  5. Customer Supplied Code - OPTIONAL -    May be any string up to 50 characters. We do not use the string at this time (it may be a client code internal to your systems), but we may be able to display this on our website at a future date.


Here's a sample PBA file:

ROSA|0309623|9438||128-88058550

|0309660|9794||128-88059029

|0409623|9111||122-88058551
 ROSA||4597|122-8805855A

RASO|0309625|9438||128-88058554



In this example, the first line no debtor one or debtor two ssn was supplied. The second line includes everything except debtor 2 ssn and NDC Trustee ID. The 3rd line is the least amount of information we can use to identify a case – a case number and the redacted (last 4) debtor 1 SSN (as well as your internal customer code). Note as little information given in the 3rd example, accurate matching is significantly reduced. The 4th line will not match anything because we need 2 items: Trustee ID, case number, or debtor 1 SSN. The 5th line contains all the proper fields. However, RASO is not a recognized NDC Trustee ID – in this case, our matching algorithm would apply other rules to match the record. In this case it would next attempt to match on case number & debtor 1 ssn.,two. However,one,

Note: the log file for our matching is contained in the file PBA_OUT.txt

How is data matched?

multi-stepThe NDC has a multi-step method to match data from the PBA File against our trustee data involving tests that take each line from your file - and the fields contained in that line - and begin testing against the NDC case data until we match an NDC case.  Issue codes are noted if there are problems with the input data or when a match is found, an issue code is raised showing the test that found a match. The issue code system for this file is described in the Request File Processing documentation.

As a general example of the file, here is a sample 4-line PBA_OUT file:

 

TRUSTEEID|CASE_NUM|SSN1|SSN2|cust_code|issue_code|trusteeid_match|case_num_match

RAPD1|0302768||||SN1|RAPD1|0302768             

|0310081|6437|||TN6|LOUS|0310081

BOWE|0212715||||SN1X|BOWE|0212715

 

Here are some individual 1 line examples with explanations and interpretations:

 

Example 1 – NDC Match:

 

PBA_OUT File (sample 1 line)

|1342024|2801||4031141900410496_U01

REQUEST_OUT (based on line Request File line above)

|1342024|2801||4031141900410496_U01|RNT05|FWRHB|1342024  |40650

 

A case number, SSN1, customer code and no Trustee ID were supplied. The Issue codes raised where T (no trustee code), R (redacted SSN1) and ‘05’ – a match based on SSN1 + case number – the Trustee ID was identified as FWRHB (Tom Powers / Fort Worth TX)

 

Example 2 – NDC Match:

 

PBA_OUT  File (sample 1 line)

ABER|1150130|1074||7001062298171103

REQUEST_OUT (based on line Request File line above)

ABER|1150130|1074||7001062298171103|RN01|ABER|1150130  |40652

Only TrusteeID, case number, SSN1, Customer code supplied in Request File. NDC returns issue codes N (no/invalid SSN2), T (no trustee code), R (redacted SSN1) but was able to match to NDC Trustee ABER (Dale Wein  / Aberdeen SD)

 

Example 3 – NDC Nomatch:

 

PBA_OUT  File (sample 1 line)

BUFF|0601870|119701066||0176641100250165

REQUEST_OUT (based on line Request File line above)

BUFF|0601870|1066||0176641100250165|RN|||40652

 

the TrusteeID, case number, SSN1, Customer code supplied in Request File. NDC returns issue codes N (no/invalid SSN2), R(redacted SSN1), but could not match to a NDC case. This can happen if the trustee, for whatever reason, did not enter the case in their back office systems, or the case is too new (not likely in this case because the example above indicates the case was from 2006.)an

 

 

,Based on the matching test we may not have matched based on the TRUSTEEID or CASE_NUM you provided us – that’s why we supply the actual data that matched. Common reasons why these don’t match 100% to the data you supplied

  • The case_num we have on file for that case has some transposed numbers – Trustees sometimes do not store the exact court case number in their systems. Thus, that is the case number we have reflected in the NDC databases.
  • The TrusteeID is different – you may not have the correct TrusteeID included in the file, but based on a test of case_num and/or SSN, we were able to find the case and correct TrusteeID

 

The IssueCodes are based on a 0-10 numbering of tests and single character values to indicate problems with the data. There can be several issue codes indicated for any particular line of a Request File, and having issue codes does not necessarily mean we could not match your data.single-character

 

If there is no matched TrusteeID/Case Number and no issue codes, your input was fine but the NDC does not have the case registered in our databases.

TEST Number

Test description

To Correct the issue

X

Expired case match. The NDC defines an expired case as 

  1. The case’s Closed_DT is greater than 2 years from today 
  2. The NDC will calculate the last Receipt record for this case and if it is greater than 2 years old (from today)

Per your NDC subscriber agreement, the NDC charter does provide any information for cases that have marked as expied.

 

Important Note: though we did match your input record, because of the expired status of this case no data will be provided in any of the files (e.g. Case, Claims, Payment, Receipt, etc).

U

Unusable data, no trusteeID and case_num 

Could not find an appropriate trustee id, case_num

T

Invalid Trustee ID

The trustee ID supplied did not match any NDC standard trustee codes. Please see https://www.ndc.org/downloads/NDC_Trustee_IDs.doc for all currently defined trustee ID’s.

S

Invalid SSN1 (either 0000 or <> 4 characters)

Please check the SSN1 data, it is probably blank or contains characters

R

SSN1 Redacted

Redacted SSN1 detected – NDC will be deprecating this test as all input SSNs should be redacted.

Q

SSN2 Redacted

Redacted SSN2 detected – NDC will be deprecating this test as all input SSNs should be redacted.

P

Non Participating Trustee ID

Please see https://www.ndc.org/downloads/NDC_Trustee_IDs.doc for all currently defined trustee ID’s.

N

Invalid SSN2 (either 0000 or <> 4 characters)

Please check the SSN2 data, it is probably blank or contains characters

K

Bad court_code

Note: The NDC does not issue K code any longer as we do not validate against Court data.

 

The court code supplied did not match any NDC standard trustee codes. Please see https://www.ndc.org/downloads/NDC_Court_Codes.xls  for all currently defined trustee ID’s.

 

NOT USED

G

Pipe removal/Cleaning from CustCode

CustCode cannot contain the pipe symbol ‘|’, our cleansing processing has removed this symbol

F

Dash removal/cleaning from SSN2

SSNs cannot contain the dash symbol ‘-’, our cleansing processing has removed this symbol

E

Dash removal/cleaning from SSN1

SSNs cannot contain the dash symbol ‘-’, our cleansing processing has removed this symbol

D

Dash removal/cleaning from Case Num

Case numbers cannot contain the dash symbol ‘-’, our cleansing processing has removed this symbol

C

Found in court data only

Note: The NDC does not issue C code any longer as we do not validate against Court data.

 

 

All records in the PBA or Request file are scrubbed against our daily updated court data (e.g. Pacer). If we find the data ONLY in the court data and cannot find a matching NDC record, ‘C’ is raised. In this case the REQUEST_OUT file will only contain a matching Case_Num and no matching Trustee_ID. The main reasons C issue code:

  1. The case is already opened/closed quickly and the Trustee never entered it into their back office system
  2. The case is too new and we have not received the matching NDC/Trustee data yet
  3. Matching error – the NDC’s Court-Case matcher did not find a matching NDC record

H

Invalid Check Number

Voucher Request Only (beta 2011)

A

Bad Case Num specification

The case number contains non-numeric characters, or is not 7 digits

 

 

 

00

Match on Court Code & case num

Note: The NDC does not issue C code any longer as we do not validate against Court data.

 

Case match

01

Match on trusteeID & case num

Case match

02

Test 2: Match on case num & ssn1

Case match

03

Test 3: Match on case num & ssn2 = ndc ssn1

Case match

04

Test 4: Match on alternative trusteeID, alternates are: COLM1<>COLM2

Case match – Not used 1/1/06

05

Test 5: Check for matching case_num and last 4 of SSN1 if the first 4 of D1_SSN = '0000'

Case match

06

Test 6: Match on case num & ssn1 = ndc ssn2

Case match

07

Test 7: Match on input SSN1 = NDC SSN1 only (latest PETITION_FILE_DT) 

Case match – Not used 1/1/06

08

Test 8: Match on input SSN1 = NDC SSN2 only

Case match – Not used 1/1/06

09

Test 9: Match on input SSN2 = NDC SSN1 only

Case match – Not used 1/1/06

10

Test10: Match on input SSN2 = NDC SSN2 only

Case match – Not used 1/1/06

12

Match on case num & input ssn2 = ndc ssn2

 

13

Match on SSN1 & Court code

Note: The NDC does not issue 13 code any longer as we do not validate against Court data.

 

14

Check for matching case_num and last 4 input ssn2 = last 4 ndc ssn2

 

15

Check for matching case_num and last 4 input ssn1 = last 4 ndc ssn2

 

16

Check for matching case_num and last 4 input ssn2 = last 4 ndc ssn1

 

17

Match on TrusteeID & input ssn1 = ndc ssn1

 

18

Match on TrusteeID & input ssn1 = ndc ssn2

 

19

Match TrusteeID + CheckNumber

Voucher Request File only match (in beta 2011)

90

Set 'X'= expired flag on any returned results

Internal NDC codes

99

Match generated from customer_case_map, normal matching will be skipped

Internal NDC codes


How about exceptions to the Profile Based Access file?

If we are unable to process your PBA file we will contact you to resolve the problem.,

A file called PBA_OUT.txt will be generated each time we process your request file. This file will list how we matched the records we found in your PBA file or if there was a no-match.
What security measures is the NDC taking to ensure that I have access to cases?
The NDC considers our security measures one of our highest business priorities. We will begin random and scheduled audits of all PBA files to ensure case information requested from the NDC meets the security protections enforced by the Trustees for party-in-interest access only.

What does PBA Cost?

PBA is a free service. 

What's next?

There are a few services we can offer after you’ve got your PBA file uploaded successfully – please inquire about our Bulk Data services in which you can receive all the data you would see on-line however it’s delivered via text files or spreadsheets.

I've got more questions about my PBA file.

Please call the National Data Center or email us at [email protected]

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.